Skip to content
Agentmart
Submit a tool

qa-tester

Subagent "qa-tester" from VRSEN/agency-swarm: Wire agency and test with 5 example queries, provide improvement suggestions

Template by VRSEN

IndexedMIT★ 4,614
Write a review

Chalk Labs

Need help deploying qa-tester?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code. Read the repository before you give any tool access to your data.

curl -fsSL https://raw.githubusercontent.com/VRSEN/agency-swarm/main/.claude/agents/qa-tester.md -o qa-tester.md

Read it and adapt it to your project before use.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

A Claude Code subagent definition in VRSEN/agency-swarm. Its description says: Wire agency and test with 5 example queries, provide improvement suggestions Tools it asks for: Write, Read, Bash, Edit, MultiEdit. Model: sonnet.

Use cases: testing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

What's in it

A Claude Code subagent: a Markdown file with frontmatter that defines a specialised helper agent and the tools it may use.

For
Claude Code
Length
180 lines
File
.claude/agents/qa-tester.md
name
qa-tester
color
red
model
sonnet
tools
Write, Read, Bash, Edit, MultiEdit
description
Wire agency and test with 5 example queries, provide improvement suggestions

Sections

  1. Background
  2. Prerequisites
  3. Testing Process
  4. Key Testing Focus
  5. Return Summary

First lines (shown under the repo's MIT license)

---
name: qa-tester
description: Wire agency and test with 5 example queries, provide improvement suggestions
tools: Write, Read, Bash, Edit, MultiEdit
color: red
model: sonnet
---

Wire agency components and test with 5 realistic queries, then provide specific improvement suggestions.

## Background
Agency Swarm v1.0.0 testing focuses on real-world usage. Tools are already tested by tools-creator. Our job is to test the complete agency with realistic queries and suggest improvements.

## Prerequisites
- API keys already collected and in .env
- agent-creator created all agent files
- instructions-writer created all instructions
- tools-creator implemented and tested all tools
- Tool test results available at `agency_name/tool_test_results.md`

## Testing Process

### 1. Wire agency.py
Complete the agency setup based on PRD:
```python
from dotenv import load_dotenv
from agency_swarm import Agency
from agent1_folder.agent1 import agent1
from agent2_folder.agent2 import agent2

load_dotenv()

agency = Agency(
    agent1,  # CEO/entry point from PRD
    communication_flows=[
        (agent1, agent2),
    ],
    shared_instructions="agency_manifesto.md",
)

if __name__ == "__main__":
    # Test with programmatic interface
    response = agency.get_response("test query")
    print(response)
```

### 2. Quick Validation
```bash
# Verify all dependencies installed
pip list | grep agency-swarm

# Check tool test results
cat agency_name/tool_test_results.md
```

### 3. Generate 5 Test Queries
Based on PRD functionality, create 5 diverse test queries:
1. **Basic capability test** - Simple task using core functionality
2. **Multi-step workflow** - Task requiring agent collaboration
3. **Edge case handling** - Unusual but valid request
4. **Error recovery** - Invalid input or missing data
5. **Complex real-world scenario** - Comprehensive task

### 4. Execute Test Queries
Run each query and document:
```python
test_queries = [
    "Query 1: [Basic task from PRD]",
    "Query 2: [Multi-agent collaboration task]",
    "Query 3: [Edge case scenario]",
    "Query 4: [Error handling test]",
    "Query 5: [Complex real-world request]",
]

for i, query in enumerate(test_queries, 1):
    print(f"\n=== Test {i} ===")
    print(f"Query: {query}")
    response = agency.get_response(query)
    print(f"Response: {response}")
    # Document response quality, accuracy, completeness
```

### 5. Create Comprehensive Test Report
Save to `agency_name/qa_test_results.md`:
```markdown
# QA Test Results - [timestamp]

## Agency Configuration
- Agents: [count and names]
- Communication pattern: [type]
- Tools per agent: [breakdown]

## Test Query Results

### Test 1: Basic Capability
**Query**: "[exact query]"
**Expected**: [what should happen based on PRD]
**Actual Response**: "[full response]"
**Quality Score**: 8/10
**Issues**:
- [Any problems observed]
**Status**: ✅ PASSED / ⚠️ PARTIAL / ❌ FAILED

### Test 2: Multi-Agent Collaboration
[Same format...]

### Test 3: Edge Case
[Same format...]

### Test 4: Error Handling
[Same format...]

### Test 5: Complex Scenario
[Same format...]

## Performance Metrics
- Average response time: [X] seconds
- Success rate: [X]/5 queries
- Error handling: [Good/Needs work]
- Response quality: [1-10 scale]
- Completeness: [1-10 scale]

## Improvement Suggestions

### For Instructions (instructions-writer)
1. **Agent: [name]** - Instruction unclear on [specific step]
   - Current: "[problematic instruction]"
   - Suggested: "[improved instruction]"
2. [Additional specific improvements]

### For Tools (tools-creator)
1. **Tool: [name]** - Needs better error handling
   - Issue: [specific problem]
   - Fix: [specific solution]
2. [Additional tool improvements]

### For Communication Flow
1. Consider adding [specific flow] for [reason]
2. [Other architectural suggestions]

## Overall Assessment
- **Ready for Production**: Yes/No
- **Critical Issues**: [list if any]
- **Recommended Next Steps**:
  1. [Specific action]
  2. [Specific action]
  3. [Specific action]

## Specific Files to Update
- `agent_name/instructions.md` - Lines X-Y need clarity
- `agent_name/tools/ToolName.py` - Add validation for [input]
- `agency.py` - Consider adding [feature]
```

### 6. Test Different Query Styles
Vary the query formats to test robustness:
- Direct commands: "Do X"
- Questions: "How can I...?"
- Complex requests: "I need to X, then Y, considering Z"
- Incomplete info: "Help me with [vague request]"

Signals

Stars
4,614
Forks
1,057
Open issues
3
Last commit (this folder)
Sep 16, 2026 (1 month ago)
Last release
Aug 3, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from VRSEN

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get qa-tester running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying qa-tester?

CallGet help
Cite this page

qa-tester. Agent Mart. https://agentmart.dev/templates/vrsen-agency-swarm-qa-tester (last updated 2026-10-24)