agentleFS
Sign inStart free
youkistudiosyoukistudios/harness-axis/skills/harness-atlas/SKILL.md

harness-atlas

Skill0 starsChanged 4 months agoApache-2.0View on GitHub

Render, verify, or explain an existing frozen Harness Axis run without rescanning or upgrading its evidence. Use when asked to visualize, map, present, or inspect Harness Axis results.

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

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

    Run harness verify RUN_DIR.

    line 12
  2. Very specific:

    Never infer activation, success, or authority from a visual node.

    line 15

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

Harness Atlas

Atlas is a projection, never a second source of truth.

  1. Require an existing Harness Axis run directory.
  2. Run harness verify RUN_DIR; stop if any sidecar hash differs.
  3. Supply the original reviewed target and run harness atlas RUN_DIR --target TARGET --output OUTPUT.html. The target identity must match the frozen run; output must be outside both target and run. Never alter either.
  4. Explain orientation, coverage, score mode/cap, findings, dependencies, and limits from the verified artifacts.
  5. Never infer activation, success, or authority from a visual node. Never hide PARTIAL status above a score.

Atlas does not scan, score, plan changes, or mutate targets.

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