Skip to content

ericrisco/rsc-harness / skills/harness

harness

Flagged

Use when governing a workspace's control plane, code or not — the `01-TOOLS/` tooling layer, the `02-DOCS/` chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy `XX-*` folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la documentación": moved into 02-DOCS/raw/ and documented), writes root CLAUDE.md/AGENTS.md. NOT the bootstrap front door (that is `init`, which hands off here).

references/wiki-index-template.md

View on GitHub
# Knowledge Base Index

> **OKF v0.1 reserved file** — `index.md` carries **no frontmatter** (it is a
> directory listing for progressive disclosure, per the OKF spec). Links are
> standard markdown, relative to this file (`topic/article.md`), NEVER wikilinks.
>
> **Human navigation lives in the `.base` views** (`Articles.base`, `Worklog.base`,
> `Decisions.base`) — live tables over frontmatter, sorted by score/status/date.
> This index is the **machine-readable catalog + fallback** the agent maintains;
> it is not the primary surface a human browses in Obsidian.

## {topic-name}

{One-line description of this topic.}

| Article | Summary | Updated | Score |
|---------|---------|---------|-------|
| [{Article Title}]({topic-name}/{article-file}.md) | {One-line summary} | {YYYY-MM-DD} | {N.N} |
| [{Archived Article}]({topic-name}/{archived-file}.html) | [Archived] {One-line summary} | {YYYY-MM-DD} | {N.N} |

## {another-topic}

{One-line description of this topic.}

| Article | Summary | Updated | Score |
|---------|---------|---------|-------|
| [{Article Title}]({another-topic}/{article-file}.md) | {One-line summary} | {YYYY-MM-DD} | {N.N} |

> **Score**: composite quality score (inbound links, source count, cited count,
> freshness; minus conflicts and orphan penalty). Regenerated on every
> Maintenance Pass. Articles below the rewrite threshold get picked up by
> Micro-Improve and Deep Improve.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall