agentleFS
openclosed-orgopenclosed-org/axum-harness/.agents/skills/harness-zoom-out/SKILL.md

harness-zoom-out

Skill48 starsChanged 6 months agoApache-2.0View on GitHub

Explains an unfamiliar repository area one layer up using ownership, callers, seams, evidence level, and gate context. Use when the user or agent is unfamiliar with a code area, needs a map before editing, or asks how a module fits into the harness.

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:

    Use this skill to map context before making changes.

    line 11
  2. Distinctive:

    Do not propose changes unless the user asks for recommendations.

    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

Harness Zoom Out

Use this skill to map context before making changes.

Workflow skills guide process. Ownership skills still decide writable boundaries.

Output

Provide a concise map of:

  1. owner skill and writable boundary
  2. module purpose in repository language
  3. main callers and downstream consumers
  4. public seams and adapters
  5. relevant declared metadata indexes
  6. executable evidence available: tests, validators, gates, scripts, command output
  7. known gaps or uncertainty

Do not propose changes unless the user asks for recommendations.

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.