Skip to main content

Contributing to The Agency

Thank you for considering contributing to The Agency! It’s people like you who make this collection of AI agents better for everyone.

Ways to Contribute

Create New Agents

Add specialized agents to fill gaps or address new domains

Improve Existing Agents

Enhance workflows, add examples, update best practices

Share Success Stories

Document how you’ve used agents successfully

Fix Issues

Report bugs, fix typos, improve clarity

Code of Conduct

This project and everyone participating in it is governed by our Code of Conduct. By participating, you are expected to uphold this code:
Treat everyone with respect. Healthy debate is encouraged, but personal attacks are not tolerated.
Welcome and support people of all backgrounds and identities.
What we create together is better than what we create alone.
Keep discussions focused on improving the agents and the community.

How to Contribute

1. Create a New Agent

Have an idea for a specialized agent? Here’s how to add one:
1

Fork the repository

# Fork on GitHub, then clone your fork
git clone https://github.com/YOUR_USERNAME/agency-agents.git
cd agency-agents
2

Choose the appropriate category

Select or propose a category:
  • engineering/ - Software development specialists
  • design/ - UX/UI and creative specialists
  • marketing/ - Growth and marketing specialists
  • product/ - Product management specialists
  • project-management/ - PM and coordination specialists
  • testing/ - QA and testing specialists
  • support/ - Operations and support specialists
  • spatial-computing/ - AR/VR/XR specialists
  • specialized/ - Unique specialists that don’t fit elsewhere
3

Create your agent file

# Create new agent file
touch category/category-agent-name.md

# Example:
touch marketing/marketing-email-specialist.md
Follow the agent template structure.
4

Test your agent

Use the agent in real scenarios:
  • Does it produce the expected outputs?
  • Is the personality distinctive?
  • Are the deliverables concrete and useful?
  • Do the workflows make sense?
5

Submit a Pull Request

# Create a branch
git checkout -b add-agent-name

# Add your changes
git add .
git commit -m "Add [Agent Name] specialist"

# Push to your fork
git push origin add-agent-name
Then open a Pull Request on GitHub.

2. Improve Existing Agents

See ways to enhance an agent? Contributions welcome:
What to Add:
  • Real-world code examples
  • Use case scenarios
  • Success stories
  • Best practices
Example Contribution:
## Real-World Example: E-commerce Checkout

When optimizing a checkout flow, Frontend Developer:

1. Analyzed current funnel (65% completion)
2. Identified friction points (5-step process)
3. Redesigned as 2-step with auto-save
4. Implemented with progressive disclosure
5. Result: 82% completion (+17%)

[Code example follows...]

3. Share Success Stories

Used these agents successfully? Share your experience:
Post in GitHub Discussions with:
  • Project Context: What were you building?
  • Agents Used: Which agents did you activate?
  • Process: How did you use them?
  • Results: What outcomes did you achieve?
  • Lessons Learned: What would you do differently?
Write a detailed case study for the README:
## Case Study: [Project Name]

### Challenge
[What problem were you solving?]

### Approach
[Which agents did you use and how?]

### Results
[Quantifiable outcomes]

### Key Insights
[What made this successful?]
Created external content? Share it:
  • Link to your blog post
  • YouTube tutorial video
  • Conference talk
  • Podcast episode
Add to the README or discussions.

4. Report Issues

Found a problem? Let us know:
1

Check existing issues

Search GitHub Issues to avoid duplicates
2

Provide context

Include:
  • What agent(s) are affected
  • What you expected to happen
  • What actually happened
  • Steps to reproduce
  • Your environment (if relevant)
3

Suggest solutions

If you have ideas for fixes, share them!

Pull Request Process

Before Submitting

  • Follows agent template structure
  • Includes personality and voice
  • Has concrete code/template examples (2-3 minimum)
  • Defines success metrics
  • Includes step-by-step workflow
  • Proofread and formatted correctly
  • Tested in real scenarios
  • Fills a real gap (not duplicate)

Submitting Your PR

1

Create descriptive PR

## Agent Information
**Agent Name**: [Name]
**Category**: [engineering/design/marketing/etc.]
**Specialty**: [One-line description]

## Motivation
[Why is this agent needed? What gap does it fill?]

## Testing
[How have you tested this agent? Real-world use cases?]

## Checklist
- [x] Follows agent template structure
- [x] Includes personality and voice
- [x] Has concrete examples
- [x] Defines success metrics
- [x] Tested in real scenarios
2

Community review

Other contributors may provide feedback. Address comments and make improvements.
3

Iteration

Work with reviewers to refine your contribution.
4

Approval & merge

Once approved, maintainers will merge your contribution!

Style Guide

Writing Style

Be Specific

“Reduce page load by 60%” not “Make it faster”

Be Concrete

“Create React components with TypeScript” not “Build UIs”

Be Memorable

Give agents personality, not generic corporate speak

Be Practical

Include real code, not pseudo-code

Formatting Guidelines

# Use proper heading hierarchy

## Section headers with emojis (optional)

### Subsections

- Use **bold** for emphasis
- Use `code` for technical terms
- Use > blockquotes for important notes

Tone Guidelines

Good: “Let’s optimize this API endpoint for better performance”Avoid: “We must optimize the API endpoint immediately” (too formal)Avoid: “Yo, this API is slow, let’s fix it” (too casual)
Good: “Here’s the best approach based on industry standards”Avoid: “Obviously, you should do this” (condescending)Avoid: “Maybe you could try this?” (too uncertain)
Good: “Implement virtualization to handle large datasets efficiently”Avoid: “You need to implement virtualization because your table is slow” (assumes incompetence)Avoid: “First open your editor, then create a file…” (too basic)

Recognition

Contributors who make significant contributions will be:

README Credit

Listed in the acknowledgments section

Release Notes

Highlighted in release announcements

Agent Credit

Credited in the agent file itself

Community Showcase

Featured in “Agent of the Week” (if applicable)

Questions?

GitHub Discussions

Ask questions and discuss ideas

GitHub Issues

Report bugs or request features

Creating Agents

Detailed guide for creating agents

Agent Template

Template structure reference

Thank You!

Your contributions make The Agency better for everyone. Whether you’re:
  • Adding a new agent
  • Improving documentation
  • Fixing bugs
  • Sharing success stories
  • Helping other contributors
You’re making a difference. Thank you!
Made with ❤️ by the community, for the community

Build docs developers (and LLMs) love