test-factory

/test-factory - Test Generated Skills or Agents

Quick testing helper for generated skills and agents to ensure they work correctly.

---

Usage

/test-factory skill [skill-name]
/test-factory agent [agent-name]
/test-factory prompt

---

What This Command Does

Helps you test generated output:

• Provides test invocation examples
• Checks if skill/agent is loaded
• Suggests test cases
• Validates basic functionality

---

Test a Skill

/test-factory skill my-skill

Output:

Testing: my-skill

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 1: Verify Skill is Loaded

For Claude Desktop:
- Open Skills menu (⌘K or Ctrl+K)
- Search for "my-skill"
- Should appear in list

For Claude Code:
- Skill should be in ~/.claude/skills/my-skill/
- Check: ls ~/.claude/skills/my-skill/

Status: [Checks and reports if found]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 2: Test Invocation

Try these test commands:

**Basic Test**:

@my-skill

[Provide test input based on skill's purpose]

**Example Use Cases** (from skill documentation):
1. [Use case 1 from HOW_TO_USE.md]
2. [Use case 2 from HOW_TO_USE.md]
3. [Use case 3 from HOW_TO_USE.md]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 3: Verify Output

Expected behavior:
[Description from SKILL.md capabilities]

Test with sample data:
[Show sample_input.json if exists]

Expected output format:
[Show expected_output.json if exists]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Troubleshooting:

If skill doesn't respond:
1. Restart Claude Desktop or Claude Code
2. Verify installation: /install-skill generated-skills/my-skill
3. Check YAML frontmatter: /validate-output skill generated-skills/my-skill

If output is wrong:
1. Check input format matches documentation
2. Review HOW_TO_USE.md for examples
3. Customize SKILL.md if needed

---

Test an Agent

/test-factory agent code-reviewer

Output:

Testing: code-reviewer agent

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 1: Verify Agent is Loaded

Run this command:

/agents

You should see "code-reviewer" in the list of available agents.

Location:
- Project-level: .claude/agents/code-reviewer.md
- User-level: ~/.claude/agents/code-reviewer.md

Status: [Checks and reports]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 2: Test Auto-Invocation

The agent should auto-invoke when you:
[Description from agent's YAML frontmatter]

**Try this task**:

[Suggest a task that matches agent description]

Claude should automatically delegate to the code-reviewer agent.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 3: Test Manual Invocation

You can also invoke explicitly:

Use the code-reviewer agent to review my recent changes

This forces Claude to use this specific agent.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Step 4: Verify Agent Behavior

Expected:
- Agent uses its own context window (separate from main)
- Agent has access to: [Tools from YAML]
- Agent uses model: [Model from YAML]
- Agent returns results to main conversation

Watch for:
- Agent delegation message: "Using code-reviewer agent..."
- Agent completion message
- Results integrated back into main conversation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Troubleshooting:

If agent doesn't invoke:
1. Restart Claude Code
2. Check /agents lists it
3. Make description more specific
4. Try manual invocation

If agent has wrong tools:
1. Edit .claude/agents/code-reviewer.md
2. Update tools: field in YAML
3. Restart Claude Code