Thanks for your interest in contributing to the Paperclip companies collection! This repo contains ready-to-import agent company templates for Paperclip.
Each top-level directory is a self-contained agent company that follows the Agent Companies spec:
<company-slug>/
COMPANY.md # Company metadata (name, description, schema, authors, goals)
README.md # Human-readable overview
LICENSE # License file
agents/ # One subdirectory per agent, each with an AGENTS.md
skills/ # One subdirectory per skill, each with a SKILL.md
teams/ # (Optional) Team definitions with TEAM.md files
- Create a directory at the repo root with your company's slug (lowercase, hyphenated).
- Add a
COMPANY.mdwith YAML frontmatter containing at minimum:name,description,slugschema: agentcompanies/v1version(semver)licenseauthors(list withnamefield)goals(list of strings)
- Add a
README.mdthat explains how the company works, its org chart, skills, and how to import it. - Add a
LICENSEfile. - Define agents in
agents/<agent-slug>/AGENTS.md. - Define skills in
skills/<skill-slug>/SKILL.md. Skills can be inline or reference an upstream repo. - Test the import locally:
paperclipai company import --from /path/to/your-company --dry-run
- Fix bugs, improve agent instructions, or add skills via pull request.
- Keep changes scoped to one company per PR when possible.
- If a company references upstream skills (e.g., gstack, superpowers), prefer updating the upstream repo and bumping the reference commit rather than forking the skill inline.
- Use
agentcompanies/v1as the schema version. - Agent slugs should match directory names (lowercase, hyphenated).
- Keep AGENTS.md files focused on the agent's role and cognitive mode.
- Skills should be single-purpose and composable.
- Include a getting-started section in your README with the
paperclipai company importcommand. - Reference the Agent Companies spec and Paperclip repo in your README.
- Fork the repo and create a branch.
- Make your changes.
- Verify your company imports cleanly with
--dry-run. - Open a pull request with a clear description of what the company does and why it's useful.
By contributing, you agree that your contributions will be licensed under the same license as the project (MIT).