agentleFS
Sign inStart free
federbenjaminfederbenjamin/feder-skills/skills/full-picture/SKILL.md

full-picture

Skill3 starsChanged 37 days agoMITView on GitHub

Map a system, an issue, or a decision as one rendered page — the parts, how they connect, what exists over time, and what a change touches. Use on "I don't have the full picture", "show me a visual", "what does each of these do", "map this out".

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. pragyesh85-SPT/The-heritage-of-fable5★ 1same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    ALWAYS draw two under this heading — before first, then after — with the same node names in both so the eye can diff them.

    line 16
  2. Distinctive:

    Read the code that produces each part before drawing it.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Produce ONE self-contained HTML file (Mermaid via CDN) and deliver it rendered in the side panel (SendUserFile with display: render; where that tool is absent, name the path). Put it beside the session's other docs written for the user.

Sections, in this order:

  1. The parts — one table: part · what it is · where it comes from · who uses it · does the user see it.
  2. How they connect — a Mermaid diagram per state. When a change is on the table (§4 exists), ALWAYS draw two under this heading — before first, then after — with the same node names in both so the eye can diff them; otherwise one. One note under them naming the surprising edge.
  3. Over time — a grid: rows = moments, columns = the parts; cells colored real / thin / empty. The first row-group is always "today". Add one row-group per option when options exist.
  4. What changes — only when a change is on the table: surface → change, then "not touched".
  5. Sources — the file:line list. The only place a citation appears; the body carries none.

Rules:

  • Read the code that produces each part before drawing it. A doc's description is not a source.
  • Plain words in the body; repo names only where the user already uses them.
  • The chat reply is a four-line reading order plus the next action. No ASCII diagram in chat, no .md fallback.

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