Edit Tool

Edit Tool — Unified Skill/Agent/Script Editor

Triage

CRITICAL: Always triage first, then act.

1. Analyze request against decision tree
2. Explain decision to user: ✅ [TYPE] because: pollution cost (~X tokens × Yfreq), context mode (main|fork), key factor
3. Branch to guide or provide direct guidance

graph TD
    A[Tool Request] --> AA{Plugin<br/>version/release?}
    AA -->|Yes| PLUGIN[✅ edit-plugin]
    AA -->|No| B{Deterministic<br/>shell only?}
    B -->|Yes| C{AI needed to<br/>decide when/how?}
    C -->|No| BASH[✅ Bash Script<br/>0 tokens]
    C -->|Yes| D{Token<br/>budget?}
    D -->|<500| WRAP[✅ Skill + scripts/]
    D -->|>500| SKILL_REF[✅ Skill + reference.md]

    B -->|No| E{Pollution<br/>cost?}
    E -->|High >2000 tokens<br/>OR deep exploration| AGENT[✅ Sub-Agent]
    E -->|Medium 500-2000| F{Context<br/>mode?}
    F -->|Needs isolation| FORK[✅ Skill context:fork]
    F -->|Needs main context| SKILL_BIG[✅ Skill + reference.md]

    E -->|Low <500| G{Frequency?}
    G -->|1+ per session| SKILL[✅ Skill]
    G -->|Rare <1/10| DIRECT[❌ No tool needed]

    style PLUGIN fill:#B2DFDB,stroke:#00897B,stroke-width:2px,color:#000
    style BASH fill:#90EE90,stroke:#000,stroke-width:2px,color:#000
    style SKILL fill:#FFD700,stroke:#000,stroke-width:2px,color:#000
    style WRAP fill:#FFA500,stroke:#000,stroke-width:2px,color:#000
    style SKILL_REF fill:#FFA500,stroke:#000,stroke-width:2px,color:#000
    style SKILL_BIG fill:#87CEEB,stroke:#000,stroke-width:2px,color:#000
    style FORK fill:#DDA0DD,stroke:#000,stroke-width:2px,color:#000
    style AGENT fill:#DDA0DD,stroke:#000,stroke-width:2px,color:#000
    style DIRECT fill:#FFB6C1,stroke:#000,stroke-width:2px,color:#000

Default: All skills are dual-invocable (both /name and model auto-invoke). disable-model-invocation: true is opt-out for rare edge cases.

Modifying Existing Tools

1. Locate and read existing file (SKILL.md or agent .md)
2. Enumerate functional outputs — every behavior/capability = preservation contract
3. Make surgical edits using Edit tool (not Write/overwrite)
4. Regression check: verify each output from step 2 is retained
5. Update description if changing triggers
6. Validate: YAML valid, triggers clear, instructions actionable

Creating New Tools

💡 Before creating: consider running /search-skill to discover existing solutions.

1. Ask for details if missing: purpose, triggers, tools needed
2. Determine type via triage decision tree above
3. Use pick-model skill for model selection
4. Branch to appropriate guide:

Skill frontmatter (quick ref — see references/skill-guide.md for full spec):

• name — lowercase-hyphens
• description — triggers + use cases (max 1024 chars)
• context — main (default) | fork
• model — opus | sonnet | haiku
• allowed-tools, argument-hint, hooks — optional

Agent frontmatter (quick ref — see references/agent-guide.md for full spec):

• name, description — required
• tools / disallowedTools — allowlist or denylist
• model — opus | sonnet | haiku | inherit (default)
• permissionMode, maxTurns, skills, mcpServers, memory, hooks, background, isolation — optional

MANDATORY Validation (CREATE only)

STOP — answer YES/NO before proceeding:

Skill: ANY NO → STOP. Recommend alternative (fork, agent, direct request). Agent: ALL NO on Q3a → STOP. Recommend skill or bash script instead.

Key Principles

• Preserve function: MODIFY must not remove capabilities unless explicitly requested
• <500 tokens ideal for SKILL.md; use progressive disclosure for overflow
• Single responsibility: One focused purpose per tool
• Token-efficient: Tables, bullets, Mermaid over prose
• Context-aware: Main for quick tasks, fork for research, agent for deep exploration

Parallelization

See references/frameworks.md for edge cases, conversion guide, and extended examples.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.