agentsclimarketplace

Harness docs maintain

Skill cekrauseee/harness/skills/harness-docs-maintain

File-native project continuity and engineering standards for coding agents.

Install
npx -y skills add cekrauseee/harness --skill harness-docs-maintain

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Maintain concise, canonical, English developer documentation in README.md and docs/. Use when documenting a project change, architecture, module, setup, command, workflow, contract, or stable decision, or when reorganizing documentation and removing stale or duplicate guidance.

SKILL.md

2.3 KB, 430 tokens by cl100k_base, as published. Nobody here has run it

Harness Docs Maintain

Update the narrowest canonical document affected by the change. Documentation must describe verified current behavior, not the implementation process or agent conversation.

Procedure

  1. Read docs/index.md, then only the documents routed for the affected subject.
  2. Verify each claim against source, configuration, tests, or an explicit user decision.
  3. Update the narrowest canonical file. Create docs/modules/<subject>.md when a bounded topic would make a macro document harder to scan.
  4. Update docs/index.md when adding, moving, renaming, or removing a document.
  5. Remove or replace stale and duplicate guidance in the same change.
  6. Use harness-artifact for a final user-facing HTML visualization. Keep drafts in the Harness workspace.
  7. Run harness-docs-audit after structural changes.

Placement

  • Use README.md for the project entry point and first-run path.
  • Use docs/project.md for product purpose, scope, concepts, and boundaries.
  • Use docs/architecture.md for cross-cutting structure, components, data flow, and invariants.
  • Use docs/development.md for setup, commands, testing, and contributor workflow.
  • Use docs/modules/*.md for focused subsystem behavior and contracts.
  • Use docs/artifacts/*.html only for final user-facing visualizations and list them in docs/artifacts/index.md.

Writing Rules

  • Write in English, even when the request is in another language.
  • Use simple, objective, coherent, and concise language.
  • Prefer active voice, short sentences, descriptive headings, and one main idea per paragraph.
  • Keep names, paths, commands, constraints, and ownership explicit.
  • Avoid marketing language, decorative prose, raw investigation logs, and repeated explanations.
  • Prefer a compact table for exact mappings. Use Mermaid only for meaningful multi-component relationships or sequences.
  • Mark uncertainty and verify it before presenting it as fact.
  • Keep operational memory, session state, drafts, and provisional decisions in the Harness, not in versioned documentation.

What ships with it: 1 file

273 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.