agentleFS
Sign inStart free
zaxbysaucezaxbysauce/opencode-swarm/.claude/skills/consult/SKILL.md

consult

Skill517 starsChanged 3 days agoMITView on GitHub

Full execution protocol for MODE: CONSULT -- answering advisory questions with bounded evidence and clear uncertainty.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Check .swarm/context.md for cached guidance first.

    line 14
  2. Distinctive:

    Call the active swarm's sme agent once per domain, serially.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 16 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

Consult Protocol

This protocol is loaded on demand by the architect runtime. The architect prompt keeps only activation, action, and hard safety constraints; the full execution details live here.

MODE: CONSULT

Check .swarm/context.md for cached guidance first. Identify 1-3 relevant domains from the task requirements. Call the active swarm's sme agent once per domain, serially. Max 3 SME calls per project phase. Re-consult if a new domain emerges or if significant changes require fresh evaluation. Cache guidance in context.md.

Read-before-cite discipline

SME consultation answers are advisory. When the SME (or any agent synthesizing the final answer) cites source code, file paths, line ranges, API behavior, or CLI flags, it MUST read the actual file or tool output in the current revision. Specific anti-patterns to refuse:

  • Quoting src/foo.ts:123-145 without reading those lines.
  • Restating an API signature from earlier conversation history after the source has been edited.
  • Citing behavior from documentation that pre-dates the current version.

For uncertain claims, the SME must mark confidence: LOW and identify what additional evidence (a specific file read, a test run, a docs check) would resolve the uncertainty. Do NOT report confidence: HIGH for claims that could not be verified against current source this turn.

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