claude-skills/templates/agent-template.md
Claude a088c8ba77
fix: phantom-path sweep — 888 unresolvable references to zero
A directory reorg added a skills/ path segment; hundreds of references never
followed. This sweep repoints every path-like reference in SKILL.md, agents,
commands, orchestration, and templates to verified on-disk targets:

- 30 root commands + 19 root agents: missing skills/ segment inserted
- 7 c-level persona agents: 17 hallucinated reference filenames substituted
  with the real files (e.g. okr_execution.md -> process_frameworks.md)
- 5 research skills: phantom scripts/office/validate.py step replaced with a
  runnable stdlib zip-integrity check
- email agents: skills frontmatter corrected to productivity/email
- orchestration/ORCHESTRATION.md + templates: stale paths fixed;
  agent-template now requires trigger phrasing in descriptions (root cause)
- 76 more files across engineering, c-level-advisor, compliance-os,
  research-ops, ra-qm, marketing, productivity; dual-publish pairs mirrored
- dead refs dropped/replaced where no target ever existed (REGISTRY.md,
  trend_analyzer.py, cursor-microinteractions.md)

New: scripts/check_paths.py linter (CI gate G1) + narrow allowlist for
teaching examples. Verified: 540 files scanned, 0 unresolvable.

https://claude.ai/code/session_019AJddAL1NADWMXsy1qNPQF
2026-06-10 14:33:00 +00:00

9.1 KiB

name description skills domain model tools
cs-agent-name What this agent does, followed by trigger phrasing. MUST include a "Use when…" (or "Spawn when…" / "Invoke via…") clause plus at least 1 concrete trigger example. Up to 1024 characters allowed — completeness of triggers beats brevity. Example — "Senior backend engineer agent. Use when designing APIs, picking a database, or extracting a service from a monolith (e.g., 'help me choose between Postgres and DynamoDB')." skill-folder-name domain-name sonnet
Read
Write
Bash
Grep
Glob

Agent Name

Purpose

[Paragraph 1: Describe what this agent does and which skill package it orchestrates]

[Paragraph 2: Describe target users, their roles, and why they need this agent]

[Paragraph 3: Explain the gap this agent bridges and the outcomes it enables]

Skill Integration

Skill Location: ../../domain-skill/skill-name/

Python Tools

  1. Tool Name

    • Purpose: What this tool does (one sentence)
    • Path: ../../domain-skill/skill-name/scripts/tool_name.py
    • Usage: python ../../domain-skill/skill-name/scripts/tool_name.py [arguments]
    • Features: Key capabilities (bullet list)
    • Use Cases: When to use this tool
  2. Second Tool (if applicable)

    • Purpose: What this tool does
    • Path: ../../domain-skill/skill-name/scripts/second_tool.py
    • Usage: python ../../domain-skill/skill-name/scripts/second_tool.py [arguments]
    • Features: Key capabilities
    • Use Cases: When to use this tool

Knowledge Bases

  1. Reference Name

    • Location: ../../domain-skill/skill-name/references/reference_file.md
    • Content: What knowledge this file contains
    • Use Case: When to consult this reference
  2. Second Reference (if applicable)

    • Location: ../../domain-skill/skill-name/references/second_reference.md
    • Content: What knowledge this file contains
    • Use Case: When to consult this reference

Templates

  1. Template Name (if applicable)
    • Location: ../../domain-skill/skill-name/assets/template.md
    • Use Case: When users would copy and customize this template

Workflows

Workflow 1: [Primary Use Case Name]

Goal: One-sentence description of what this workflow accomplishes

Steps:

  1. [Action Step] - Description of first step
    # Command example if applicable
    python ../../domain-skill/skill-name/scripts/tool.py input.txt
    
  2. [Action Step] - Description of second step
  3. [Action Step] - Description of third step
  4. [Action Step] - Description of fourth step
  5. [Action Step] - Description of final step

Expected Output: What success looks like (deliverable, metric, decision made)

Time Estimate: How long this workflow typically takes

Example:

# Complete workflow example with real commands
command1
command2
# Review output

Workflow 2: [Advanced Use Case Name]

Goal: One-sentence description

Steps:

  1. [Action Step] - Description
  2. [Action Step] - Description
  3. [Action Step] - Description
  4. [Action Step] - Description

Expected Output: What success looks like

Time Estimate: Duration estimate

Workflow 3: [Integration Use Case Name]

Goal: One-sentence description

Steps:

  1. [Action Step] - Description
  2. [Action Step] - Description
  3. [Action Step] - Description

Expected Output: What success looks like

Time Estimate: Duration estimate

Workflow 4: [Optional Fourth Workflow]

Goal: One-sentence description

Steps:

  1. [Action Step] - Description
  2. [Action Step] - Description

Expected Output: What success looks like

Time Estimate: Duration estimate

Integration Examples

Example 1: [Example Name]

#!/bin/bash
# script-name.sh - Brief description

# Setup variables
INPUT_FILE=$1

# Execute workflow
python ../../domain-skill/skill-name/scripts/tool.py "$INPUT_FILE"

# Process output
echo "Analysis complete. Review results above."

Example 2: [Example Name]

# Multi-step workflow example

# Step 1: Prepare data
echo "Step 1: Data preparation"

# Step 2: Run analysis
python ../../domain-skill/skill-name/scripts/tool.py input.csv

# Step 3: Generate report
echo "Report generation complete"

Example 3: [Example Name]

# Automation example (e.g., weekly report, daily check)

DATE=$(date +%Y-%m-%d)
echo "📊 Report for $DATE"

# Execute tools
python ../../domain-skill/skill-name/scripts/tool.py current-data.csv > report-$DATE.txt

Success Metrics

[Metric Category 1]:

  • [Metric Name]: Target value or improvement percentage
  • [Metric Name]: Target value or improvement percentage
  • [Metric Name]: Target value or improvement percentage

[Metric Category 2]:

  • [Metric Name]: Target value or improvement percentage
  • [Metric Name]: Target value or improvement percentage

[Metric Category 3]:

  • [Metric Name]: Target value or improvement percentage
  • [Metric Name]: Target value or improvement percentage

[Metric Category 4] (optional):

  • [Metric Name]: Target value or improvement percentage

References


Last Updated: [Date] Sprint: [sprint-MM-DD-YYYY] (Day X) Status: Production Ready Version: 1.0