agentleFS
link7373link7373/agentic-sales-marketing/.claude/skills/setup-team/SKILL.md

setup-team

Skill1 starsChanged 3 months agoMITView on GitHub

Onboard a business onto the team — read the charter, interview for gaps, seed the knowledge base, and lay out the road to the first sale. Run this first, once.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Interview for gaps: Ask the operator about gaps conversationally — one topic at a time, plain language, multiple-choice where possible.

    line 14
  2. Distinctive:

    Quick verification: If links were provided (site, store, socials), have market-researcher visit them and record honest first impressions — …

    line 16
  3. Distinctive:

    Seed the knowledge base: Write:

    line 17
  4. Very specific:

    If knowledge/business-context.md already has status seeded or active, the team is already set up — confirm with the operator before …

    line 29
  5. Very specific:

    All nine knowledge files above.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/setup-team — Bring the Team Online

Inputs: a filled (or partially filled) START-HERE.md. Agents: Head of Growth leads; market-researcher assists with quick verification lookups.

Steps

  1. Read the charter. Parse every section of START-HERE.md. Build a gap list of blank, vague, or contradictory answers.
  2. Interview for gaps. Ask the operator about gaps conversationally — one topic at a time, plain language, multiple-choice where possible. "I don't know" is acceptable; record it as an open question for /research-market, not a blocker.
  3. Classify the business. Model (B2B / B2C / hybrid), sales motion (self-serve page/marketplace vs conversation-led), maturity (nothing built / assets exist / selling already). These drive every future branch.
  4. Quick verification. If links were provided (site, store, socials), have market-researcher visit them and record honest first impressions — what exists, what state it's in.
  5. Seed the knowledge base. Write:
    • knowledge/business-context.md — the classified picture: product, model, motion, maturity, goals, budget, time, constraints, assets, open questions.
    • knowledge/decision-log.md, knowledge/approvals-log.md, knowledge/results-history.md, knowledge/pipeline.md, knowledge/tool-registry.md, knowledge/budget.md, knowledge/competitors.md — initialized with headers and the operator's approval preferences from the charter. Set each file's status header (stub/seeded) honestly.
    • Existing customers and live leads go into knowledge/pipeline.md now, with a dated next action each. A business that already sells is not starting from zero, and its existing customers are the first source of testimonials (/grow-referrals) and win-loss insight (/close-deal) — the fastest evidence available.
  6. Confirm the approval contract. Restate the three gates (money, outbound, publishing) and any charter modifications; record in knowledge/approvals-log.md as the standing contract.
  7. Seed the first tool connections. From the charter's existing tools and the plan's likely needs, queue /connect-tools for the 1–2 most urgent categories. Don't connect everything — connect what the next 30 days need.
  8. Set up the rhythm. With operator approval, create two scheduled tasks (per CLAUDE.md → Operating rhythm & automation): weekly Monday /measure, first-Monday-monthly /review-monthly. Register both in knowledge/tool-registry.md under Scheduled automation. If scheduling tools aren't available, record that and note the rhythm runs manually at session start.
  9. Present the road. Show the zero-to-first-sale sequence from playbook.md §2, marked up for this business: which steps are done, which are next, expected pace given budget/time. Recommend the immediate next skill (usually /research-market).

Before you start

  1. Required inputs: START-HERE.md in any state — even blank; the interview fills gaps.
  2. If knowledge/business-context.md already has status seeded or active, the team is already set up — confirm with the operator before re-running (re-setup overwrites the business picture; it does not erase logs or results).

If things go wrong

  • Operator can't answer core questions (what they sell, to whom) → record as open questions for /research-market; never invent answers.
  • Scheduling tools unavailable → note in tool-registry; the rhythm runs manually.
  • Operator goes quiet mid-interview → park progress in knowledge/pending.md and seed what's known so far.

Outputs

Seeded knowledge/ base; a road-to-first-sale summary the operator can understand in two minutes; the next step queued. Close with the report per templates/skill-report.md.

Writeback

All nine knowledge files above; setup decisions (tag: other) to knowledge/decision-log.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.