agentleFS
Sign inStart free
kvantatechkvantatech/RedLine/.github/skills/build-status-views/SKILL.md

build-status-views

Skill1 starsChanged 3 months agoMITView on GitHub

Type: skill (deterministic) · Used by: build-status · Status: STUB (P0 scaffold — not yet implemented)

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:

    When implemented, read the status.json single source of truth and render two human-facing views: STATUS.md (rewriting only the region …

    line 7
  2. Very specific:

    All totals/rollups are COMPUTED by the renderer at build time — never stored back into status.json.

    line 9

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

build-status-views

Render human views (STATUS.md + dashboard.html) from the status.json SSOT — zero model calls.

Type: skill (deterministic) · Used by: build-status · Status: STUB (P0 scaffold — not yet implemented)

Prompt

When implemented, read the status.json single source of truth and render two human-facing views: STATUS.md (rewriting only the region between the AUTOGEN markers) and architecture-dashboard.html. Inputs: status.json -> Outputs: regenerated STATUS.md region + dashboard HTML. All totals/rollups are COMPUTED by the renderer at build time — never stored back into status.json.

Tools

none — deterministic (plain code)

Data

  • Reads: status.json (SSOT — does not exist yet; a local status.json is the sensible home if/when this is implemented)
  • Writes: STATUS.md (between AUTOGEN markers only) and docs/redline-architecture.html
  • Until then both views are hand-maintained (STATUS.md at repo root; the diagram in docs/)

Notes

Activation: P0. One artifact, two lifecycle phases: build-readiness rollups now -> live SLOs at WS4. Hard rules: zero model calls (pure render); totals are computed, never stored; only the AUTOGEN-marked region of STATUS.md is rewritten.

Frozen skill registry: AGENTS.md in this repo

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