agentleFS
Sign inStart free
ucsandmanucsandman/claude-skills/team/SKILL.md

team

Skill5 starsChanged 2 months agoMITView on GitHub

Fan a task out to the Claude Code + OpenClaw (MoltFire) team. Use for /team <task> or "have both agents" handle something.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 8 projects that use this

  • ncklrsSkill

    seo-content-strategist

    Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read ~/clawd/agent-comms/team/PROTOCOL.md FIRST and follow it exactly, then ~/clawd/agent-comms/team/LESSONS.md.

    line 8
  2. Distinctive:

    Recon before you design: Before proposing any adapter, wrapper, bot, or browser automation, enumerate what the target already exposes — …

    line 20
  3. Very specific:

    Do your own share of the work.

    line 41
  4. Distinctive:

    Never approve anything on Wes's behalf.

    line 64
  5. Distinctive:

    No secrets in envelopes, events, or artifacts.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “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

/team — two-agent task execution

Read ~/clawd/agent-comms/team/PROTOCOL.md FIRST and follow it exactly, then ~/clawd/agent-comms/team/LESSONS.md. This skill is the Claude Code entry point; the protocol file is the source of truth for classifier, transport, ledger, tiers, and failure rules.

Paths here are home-anchored (~/…) on purpose. agent-comms/team/... is relative and does not resolve from the usual cwd, and ~/agent-comms is a DIFFERENT repo with no team/ dir. A relative path silently skips the protocol and the lessons file.

Procedure

  1. Recon before you design. Before proposing any adapter, wrapper, bot, or browser automation, enumerate what the target already exposes — list its API routes, CLI commands, and exported functions FROM SOURCE. Never accept "there is no X" from a README, a report, or the other agent; a negative capability claim rules out whole designs, so verify it directly. Two agents agreeing on an inherited premise is one check, not two. (See LESSONS.md 2026-08-10.)
  2. Classify the task with the PROTOCOL.md Classifier. Announce the lead in one sentence.
  3. Create the task (you are the receiving agent): node ~/clawd/agent-comms/team/bin/team-ledger.mjs create --slug <slug> --instruction "<task>" --origin claude-code --lead <claude|openclaw> then update --task <id> --status in_progress.
  4. If YOU lead:
    • dashclaw_session_start for the task.
    • Decompose. For each piece that belongs to OpenClaw's domain, send a DELEGATION envelope (PROTOCOL.md Transport) via Bash: openclaw agent --agent main --message "<envelope>" --timeout 300 Send the delegation, then log a delegation event (send first, then log). Log the returned answer as received context; MoltFire logs its own reply event itself.
    • Do your own share of the work. Apply the Tier rules from PROTOCOL.md (guard/record/approval) to every consequential action.
    • Integrate, verify, write artifacts to agent-comms/team/tasks/<id>/artifacts/.
    • Log a result event, report to the user in this session, log done, update --status done, dashclaw_session_end.
  5. If OPENCLAW leads: send the LEAD_HANDOFF envelope (PROTOCOL.md Transport) via openclaw agent --agent main --message ... --timeout 1800 (the whole task runs inside that call — LEAD_HANDOFF window, not the 300s delegation window), log a lead_assigned event, then act as specialist: answer any DELEGATION envelopes MoltFire sends back during the task, and relay MoltFire's final report to the user verbatim when it arrives in the command output.
  6. Failure handling: PROTOCOL.md Failure rules verbatim. Delegation timeout (300s) → log error, retry once, degrade to solo with a note. LEAD_HANDOFF timeout (1800s) → check the task's events-openclaw.jsonl first; fresh events mean the lead is alive — poll the ledger, never spawn a second lead. Cap 10 exchanges.

Hard rules

  • You log events ONLY with --from claude.
  • Specialists (either direction) answer once and stop. No sub-delegation.
  • Never approve anything on Wes's behalf; Tier 2/3 waits for his approval via DashClaw. Fail closed if DashClaw is unreachable.
  • No secrets in envelopes, events, or artifacts.

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.

Check your setup, free