company-creator

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

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/Douglas-v/strategic-ai-paperclip-lab --skill company-creator-douglas-v
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: company-creator
Source: https://github.com/Douglas-v/strategic-ai-paperclip-lab/tree/main/paperclip/.claude/skills/company-creator
Command: npx skills add https://github.com/Douglas-v/strategic-ai-paperclip-lab --skill company-creator-douglas-v

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Creating a well-structured agent company package requires understanding the Agent Companies specification, designing an org chart with reporting lines, defining workflows, and writing many interlinked files. This Skill guides the AI through interviewing the user, reading the spec, and generating a complete, spec-compliant company package either from scratch or from an existing git repository. ## Core Features & Use Cases - Two Creation Modes: Build a company from scratch via a structured interview, or analyze an existing git repo (URL, local path, or tweet) and wrap its skills and structure into a company. - Spec-Compliant Package Generation: Produces COMPANY.md, AGENTS.md, TEAM.md, PROJECT.md, TASK.md, SKILL.md files plus a .paperclip.yaml vendor extension, all following the agentcompanies/v1 schema with correct slugs, reporting structures, and source references. - Workflow-Aware Agent Design: Infers the right organizational pattern (pipeline, hub-and-spoke, collaborative, or on-demand) and writes agent instructions that define handoffs, triggers, and execution contracts. - Use Case: A user points the AI at a GitHub repo containing several skills and asks to turn it into a company. The Skill analyzes the repo, proposes a lean agent roster, references the existing skills by commit SHA instead of copying them, and outputs an importable package with README and LICENSE. ## Quick Start Ask the AI to create an agent company from this repository or from a description of the team you want, then answer its interview questions to confirm the agents and workflow.

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, local path, or a tweet linking to it. The Skill clones or reads the repo, scans for SKILL.md and agent configuration files, proposes agents and a workflow pattern, then generates a company package that references the repo's skills by commit SHA rather than copying them.

What files does an agentcompanies/v1 company package contain?

A package contains a root COMPANY.md with schema agentcompanies/v1, plus agents/<slug>/AGENTS.md files, and optionally TEAM.md, PROJECT.md, TASK.md, and SKILL.md files. A .paperclip.yaml vendor extension configures adapters and environment inputs per agent.

Should I copy external skills into my company package or reference them?

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

When should I not use the company-creator skill?

Do not use it to import an existing company package, since that is handled by the Paperclip CLI import command. It also should not be used to modify a company that is already running in Paperclip.

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 should start with a CEO who manages the others, while teams or departments do not require a CEO and use a top-level agent with reportsTo set to null.

Which adapter types are valid in the .paperclip.yaml file?

The only valid adapter types are claude_local, codex_local, opencode_local, pi_local, cursor, gemini_local, and openclaw_gateway. Omit the adapter block entirely unless the repo or user context clearly warrants one, since unknown adapter types cause import errors.