company-creator

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

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

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 an org chart, 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 .todero.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 this repository using the company-creator skill and confirm the proposed 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 or local path and the skill clones or reads it, scans for SKILL.md and agent configs, 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 .todero.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) skills when the user explicitly asks or the source repo is private or may become unavailable.

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

Only set an adapter when the repo clearly targets a specific runtime or the user requests one, using valid types like claude_local, codex_local, or cursor. Omitting the adapter block lets Todero use its default and avoids import errors from unknown types.

How many agents should a new agent company have?

Keep it lean with three to five agents for a typical startup-style company, usually led by a CEO who manages the others. Teams or departments do not require a CEO, and larger rosters are only suggested when the scope demands it.