agentleFS
Sign inStart free
ohm41321ohm41321/luciazero/skills/discipline-report/SKILL.md

discipline-report

Skill6 starsChanged 3 months agoMITView on GitHub

Analyze Luciazero stop-outcome logs for evidence-backed verification habits. Use for discipline stats, recurring nudge or strict-block patterns, local behavior reports, or machine-readable JSON.

The file

We split this skill into the rules it gives an agent

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

  • 3

    Very specific

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

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

    Use the first only when on PATH.

    line 15
  2. Very specific:

    Treat recorded outcomes as observations, not causes.

    line 25
  3. Very specific:

    Use --project . for this repo or another name/id as needed.

    line 32

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

Discipline report

Resolve the first available local CLI:

luciazero discipline [--days N] [--project PATH_OR_ID] [--json]
node <this-skill-dir>/../../bin/luciazero.js discipline [--days N] [--project PATH_OR_ID] [--json]

Use the first only when on PATH; use the second from a checkout/package. If neither local form exists, report unavailable offline. Use npx only when package resolution is explicitly allowed.

The command reads luciazero-stats.log, accepts current schema-versioned JSON lines and legacy space-delimited records, ignores malformed lines without failing, and never sends data over the network. Telemetry includes turn/Bash wall time plus Bash, verify, and skill counts; parallel Bash intervals are merged. Raw commands and skill names are never persisted.

Treat recorded outcomes as observations, not causes. nudge means no recognized later verify; strict-block means its strict command was red. Explanations must say likely unless the log records the cause.

Non-Bash remainder includes tools, hooks, scheduling, and reasoning; do not label it as model latency without another measurement.

Use --project . for this repo or another name/id as needed. Use --json for dashboards or /retro.

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