doc-harness-e2d34a — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited doc-harness-e2d34a (Agent Skill) and scored it 87/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 3 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 3 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Doc Harness creates and maintains five status documents per project that enable any agent or human to understand and resume project work purely from reading files — no external memory needed.
Core principle: "Write It Down or Lose It" — all information in context is temporary. If it is not written to a file and registered in FILE_INDEX, it will be lost.
| Document | Role | Answers |
|---|---|---|
| CLAUDE.md | Project entry point | "What is this project? What are the rules? Where do I start?" |
| CURRENT_STATUS.md | Active state | "What just happened? What's happening now? What's next?" |
| FILE_INDEX.md | File catalog | "What files exist, what are they, and where are they?" |
| WORKLOG.md | Permanent history | "What exactly happened in phase 2, three weeks ago?" |
| DOC_HARNESS_SPEC.md | Complete reference | Full specification for unusual situations |
Metaphor: A project in motion is like a moving car.
Kimi has no slash commands. Use the table below to map user requests to the correct procedure.
| User says | Procedure | See |
|---|---|---|
| "Set up doc-harness" / "init project docs" / "create status documentation" | Init — create the five documents for a new or existing project | references/init.md |
| "Check documentation health" / "audit project docs" / "run a health check" | Check — audit file health and reflect on principles | references/check.md |
| "Sync project state" / "update status docs" / "catch up documentation" | Sync — repair drift, refresh dates, register missing files | references/sync.md |
| "Save everything" / "flush context" / "prepare for compact" / "ensure nothing is lost" | Flush — emergency save: extract all important context into documents. Runs five phases: (A) sync, (B) context inventory, (C) write and register, (D) verification, (E) flush marker. Phases B and C are the defining feature — they scan context for information that exists only in memory and write it to files. Without Phase B and C, flush has failed and is indistinguishable from sync. | references/flush.md |
| "Resume this project" / "continue work" / "where were we" / "back to project" / "pick up where we left off" / "what's the current status" | Resume — structured state recovery. Execute Recovery Chain, produce Recovery Report, verify understanding before continuing. Four phases: (A) Recovery Chain, (B) Recovery Report synthesis, (C) Understanding Verification, (D) Resume decision. | references/resume.md |
| "Recall" / "remember" / "find in docs" / "search project docs" / "where did we discuss" / "why did we decide" / "what is the current plan" | Recall — retrieve information from registered documents along the Doc Harness hierarchy | references/recall.md |
"I am this project's agent. My role is [role from the lock]."
Trigger: Work goal fundamentally changes; user explicitly declares a new phase; project pauses (>3 days); car body exceeds ~200 lines.
Five steps (strict order):
Interrupt safety: Step 1 is protective. If compact occurs during Steps 2-5, data is safe. On next session start, run mid-transition detection (three-way coherence check: CLAUDE.md phase / WORKLOG TOC / CURRENT_STATUS tire tracks) and repair deterministically.
| Type | Location | Lifecycle |
|---|---|---|
| Iron rules | CLAUDE.md | Permanent, phase-independent |
| Driving manual | CURRENT_STATUS | Lives and dies with the phase |
At phase transition, review each driving-manual principle: promote to iron rule (if ≥3 phases)? Keep? Remove?
| Fact Type | Sole Source |
|---|---|
| Current state / progress | CURRENT_STATUS.md |
| File catalog | FILE_INDEX.md |
| Historical details | WORKLOG.md |
| Project overview / rules | CLAUDE.md |
See references/spec.md for full details.
| File | When to read |
|---|---|
| references/init.md | User asks to set up / initialize doc-harness |
| references/check.md | User asks to audit / check documentation health |
| references/sync.md | User asks to sync / update status docs |
| references/flush.md | User asks to save / flush context before compression |
| references/resume.md | User asks to resume / continue project work after context loss or on arrival |
| references/recall.md | User asks to recall / search / find information in project docs |
| references/spec.md | Unusual situation, edge case, or understanding design rationale |
Language note: All documents are written in English with Chinese annotations where helpful. Kimi should respond in the user's language regardless of document language.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.