company-creator

Name: company-creator
Author: IncomeStreamSurfer

69stars33forks

How to install company-creator?

incomestreamsurfer/paperclip-surfers/company-creator

$npx -y skills add IncomeStreamSurfer/paperclip-surfers --skill company-creator

Installs into the current project.

Summary

Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers

Files · 1

View on GitHub

SKILL.md

1	# Company Creator
2
3	Create agent company packages that conform to the Agent Companies specification.
4
5	Spec references:
6
7	- Normative spec: `docs/companies/companies-spec.md` (read this before generating files)
8	- Web spec: https://agentcompanies.io/specification
9	- Protocol site: https://agentcompanies.io/
10
11	## Two Modes
12
13	### Mode 1: Company From Scratch
14
15	The user describes what they want. Interview them to flesh out the vision, then generate the package.
16
17	### Mode 2: Company From a Repo
18
19	The user provides a git repo URL, local path, or tweet. Analyze the repo, then create a company that wraps it.
20
21	See [references/from-repo-guide.md](references/from-repo-guide.md) for detailed repo analysis steps.
22
23	## Process
24
25	### Step 1: Gather Context
26
27	Determine which mode applies:
28
29	- From scratch: What kind of company or team? What domain? What should the agents do?
30	- From repo: Clone/read the repo. Scan for existing skills, agent configs, README, source structure.
31
32	### Step 2: Interview (Use AskUserQuestion)
33
34	Do not skip this step. Use AskUserQuestion to align with the user before writing any files.
35
36	For from-scratch companies, ask about:
37
38	- Company purpose and domain (1-2 sentences is fine)
39	- What agents they need - propose a hiring plan based on what they described
40	- Whether this is a full company (needs a CEO) or a team/department (no CEO required)
41	- Any specific skills the agents should have
42	- How work flows through the organization (see "Workflow" below)
43	- Whether they want projects and starter tasks
44
45	For from-repo companies, present your analysis and ask:
46
47	- Confirm the agents you plan to create and their roles
48	- Whether to reference or vendor any discovered skills (default: reference)
49	- Any additional agents or skills beyond what the repo provides
50	- Company name and any customization
51	- Confirm the workflow you inferred from the repo (see "Workflow" below)
52
53	Workflow — how does work move through this company?
54
55	A company is not just a list of agents with skills. It's an organization that takes ideas and turns them into work products. You need to understand the workflow so each agent knows:
56
57	- Who gives them work and in what form (a task, a branch, a question, a review request)
58	- What they do with it
59	- Who they hand off to when they're done, and what that handoff looks like
60	- What "done" means for their role
61
62	Not every company is a pipeline. Infer the right workflow pattern from context:
63
64	- Pipeline — sequential stages, each agent hands off to the next. Use when the repo/domain has a clear linear process (e.g. plan → build → review → ship → QA, or content ideation → draft → edit → publish).
65	- Hub-and-spoke — a manager delegates to specialists who report back independently. Use when agents do different kinds of work that don't feed into each other (e.g. a CEO who dispatches to a researcher, a marketer, and an analyst).
66	- Collaborative — agents work together on the same things as peers. Use for small teams where everyone contributes to the same output (e.g. a design studio, a brainstorming team).
67	- On-demand — agents are summoned as needed with no fixed flow. Use when agents are more like a toolbox of specialists the user calls directly.
68
69	For from-scratch companies, propose a workflow pattern based on what they described and ask if it fits.
70
71	For from-repo companies, infer the pattern from the repo's structure. If skills have a clear sequential dependency (like `plan-ceo-review → plan-eng-review → review → ship → qa`), that's a pipeline. If skills are independent capabilities, it's more likely hub-and-spoke or on-demand. State your inference in the interview so the user can confirm or adjust.
72
73	Key interviewing principles:
74
75	- Propose a concrete hiring plan. Don't ask open-ended "what agents do you want?" - suggest specific agents based on context and let the user adjust.
76	- Keep it lean. Most users are new to agent companies. A few agents (3-5) is typical for a startup. Don't suggest 10+ agents unless the scope demands it.
77	- From-scratch companies should start with a CEO who manages everyone. Teams/departments don't need one.
78	- Ask 2-3 focused questions per round, not 10.
79
80	### Step 3: Read the Spec
81
82	Before generating any files, read the normative spec:
83
84	```
85	docs/companies/companies-

People who liked this also viewed

6 picks

Type

company-creator

69stars33forks

View on GitHub

How to install company-creator?

incomestreamsurfer/paperclip-surfers/company-creator

$npx -y skills add IncomeStreamSurfer/paperclip-surfers --skill company-creator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Company Creator
2
3	Create agent company packages that conform to the Agent Companies specification.
4
5	Spec references:
6
7	- Normative spec: `docs/companies/companies-spec.md` (read this before generating files)
8	- Web spec: https://agentcompanies.io/specification
9	- Protocol site: https://agentcompanies.io/
10
11	## Two Modes
12
13	### Mode 1: Company From Scratch
14
15	The user describes what they want. Interview them to flesh out the vision, then generate the package.
16
17	### Mode 2: Company From a Repo
18
19	The user provides a git repo URL, local path, or tweet. Analyze the repo, then create a company that wraps it.
20
21	See [references/from-repo-guide.md](references/from-repo-guide.md) for detailed repo analysis steps.
22
23	## Process
24
25	### Step 1: Gather Context
26
27	Determine which mode applies:
28
29	- From scratch: What kind of company or team? What domain? What should the agents do?
30	- From repo: Clone/read the repo. Scan for existing skills, agent configs, README, source structure.
31
32	### Step 2: Interview (Use AskUserQuestion)
33
34	Do not skip this step. Use AskUserQuestion to align with the user before writing any files.
35
36	For from-scratch companies, ask about:
37
38	- Company purpose and domain (1-2 sentences is fine)
39	- What agents they need - propose a hiring plan based on what they described
40	- Whether this is a full company (needs a CEO) or a team/department (no CEO required)
41	- Any specific skills the agents should have
42	- How work flows through the organization (see "Workflow" below)
43	- Whether they want projects and starter tasks
44
45	For from-repo companies, present your analysis and ask:
46
47	- Confirm the agents you plan to create and their roles
48	- Whether to reference or vendor any discovered skills (default: reference)
49	- Any additional agents or skills beyond what the repo provides
50	- Company name and any customization
51	- Confirm the workflow you inferred from the repo (see "Workflow" below)
52
53	Workflow — how does work move through this company?
54
55	A company is not just a list of agents with skills. It's an organization that takes ideas and turns them into work products. You need to understand the workflow so each agent knows:
56
57	- Who gives them work and in what form (a task, a branch, a question, a review request)
58	- What they do with it
59	- Who they hand off to when they're done, and what that handoff looks like
60	- What "done" means for their role
61
62	Not every company is a pipeline. Infer the right workflow pattern from context:
63
64	- Pipeline — sequential stages, each agent hands off to the next. Use when the repo/domain has a clear linear process (e.g. plan → build → review → ship → QA, or content ideation → draft → edit → publish).
65	- Hub-and-spoke — a manager delegates to specialists who report back independently. Use when agents do different kinds of work that don't feed into each other (e.g. a CEO who dispatches to a researcher, a marketer, and an analyst).
66	- Collaborative — agents work together on the same things as peers. Use for small teams where everyone contributes to the same output (e.g. a design studio, a brainstorming team).
67	- On-demand — agents are summoned as needed with no fixed flow. Use when agents are more like a toolbox of specialists the user calls directly.
68
69	For from-scratch companies, propose a workflow pattern based on what they described and ask if it fits.
70
71	For from-repo companies, infer the pattern from the repo's structure. If skills have a clear sequential dependency (like `plan-ceo-review → plan-eng-review → review → ship → qa`), that's a pipeline. If skills are independent capabilities, it's more likely hub-and-spoke or on-demand. State your inference in the interview so the user can confirm or adjust.
72
73	Key interviewing principles:
74
75	- Propose a concrete hiring plan. Don't ask open-ended "what agents do you want?" - suggest specific agents based on context and let the user adjust.
76	- Keep it lean. Most users are new to agent companies. A few agents (3-5) is typical for a startup. Don't suggest 10+ agents unless the scope demands it.
77	- From-scratch companies should start with a CEO who manages everyone. Teams/departments don't need one.
78	- Ask 2-3 focused questions per round, not 10.
79
80	### Step 3: Read the Spec
81
82	Before generating any files, read the normative spec:
83
84	```
85	docs/companies/companies-

People who liked this also viewed

6 picks

Type