company-creator

Generate agent company packages conforming to the agentcompanies/v1 specification.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill company-creator-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: company-creator
Source: https://github.com/adamtpang/summon.company/tree/main/.agents/skills/company-creator
Command: npx skills add https://github.com/adamtpang/summon.company --skill company-creator-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an idea or an existing repository into a structured, spec-compliant agent company package requires knowing the Agent Companies format, designing org charts, and writing workflow-aware agent instructions, which is tedious and error-prone to do by hand. ## Core Features & Use Cases - Two creation modes: Build a company from scratch via a guided interview, or analyze an existing git repo and wrap its skills and structure into a company package. - Spec-compliant generation: Produces COMPANY.md, AGENTS.md, TEAM.md, PROJECT.md, TASK.md, and SKILL.md files following the agentcompanies/v1 schema, plus a .paperclip.yaml vendor extension. - Workflow-aware org design: Infers pipeline, hub-and-spoke, collaborative, or on-demand workflow patterns and writes agent instructions that define handoffs, triggers, and reporting structure. - Use Case: Point it at a repo containing code-review and deployment skills, and it generates a lean engineering company with a CEO, CTO, and engineer agents that reference those skills by commit-pinned GitHub sources. ## Quick Start Ask the assistant to create an agent company from the repository at a given GitHub URL using the company-creator skill.

Frequently Asked Questions about company-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an agent company from an existing GitHub repo?

Provide the repo URL and the skill clones or reads it, scans for SKILL.md and agent config files, infers agent roles and a workflow pattern, then generates a company package. Discovered skills are referenced by commit-pinned GitHub sources rather than copied by default.

What files does an agentcompanies/v1 company package contain?

A package contains a root COMPANY.md plus optional agents/, teams/, projects/, tasks/, and skills/ directories, each holding AGENTS.md, TEAM.md, PROJECT.md, TASK.md, or SKILL.md files. A .paperclip.yaml vendor extension configures adapters and env inputs per agent.

Should external skills be copied or referenced in a company package?

Reference them by default using a sources entry with kind github-file, the repo, path, full commit SHA, attribution, license, and usage set to referenced. Only vendor (copy) skill content when the user explicitly asks or the source repo may become unavailable.

When should I set an adapter in .paperclip.yaml?

Only set an adapter when the repo clearly targets a specific runtime, the user requests one, or the role requires it. Valid types include claude_local, codex_local, opencode_local, pi_local, cursor, gemini_local, and openclaw_gateway; otherwise omit the block so Paperclip uses its default.

How many agents should a new agent company have?

Keep it lean: three to five agents is typical for a startup-style company. From-scratch companies usually start with a CEO who manages everyone, while teams or departments do not require one.