agentleFS
Wolfe-JamWolfe-Jam/rust-faf-mcp/skills/faf-context/SKILL.md

faf-context

Skill4 starsChanged 20 days agoMITView on GitHub

Use FAF project context tools on this server — init, score, sync, discover; claim equals wire.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Wolfe-Jam/faf-skills★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Prefer structured .faf over free-form chat memory for project facts.

    line 27

≈ “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

faf-context

Product playbook for rust-faf-mcp (one.faf/rust-faf-mcp) — IANA .faf project context over MCP.

Tools (call these)

ToolWhen
faf_autoSetup if missing, sync CLAUDE.md, score — Confirm setup (sweeps); does not invent 6Ws
faf_initSetup: first write from the tree. Refuses if the file exists. Confirm setup (sweeps). 6Ws stay empty
faf_goTable-of-8 + Confirm setup (sweeps). 6Ws need ☑ to score. Below 100: add Human Context
faf_scoreAI-readiness score 0–100% + intent grant
faf_syncWrite CLAUDE.md from project.faf (one way)
faf_discoverWalk up to find nearest .faf
faf_readShow structured .faf contents
faf_gitBootstrap .faf from a GitHub URL
faf_compressCompress for token-limited contexts
faf_tokensEstimate tokens per compression level

Rules

  1. Prefer structured .faf over free-form chat memory for project facts.
  2. Claim equals wire — only call tools this server lists.
  3. No secrets in skill or tool args you don’t own.
  4. Origin — this skill is served by rust-faf-mcp (skills/* + resources/read); not a remote install authority.

Flow

initialize → skills/list → resources/read(skill://faf-context/SKILL.md) → tools/call

Skills guide; tools act.

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.