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/inbox-readme-template.md

View on GitHub
# Inbox — drop any raw data here

This is the **ingest folder** of your knowledge base. Throw anything in here
and an agent will process it into the wiki on the next sweep.

> Aquí cae cualquier dato en crudo. No hay formato rígido. El sistema se
> adapta a tu caos, no al revés.

## What you can drop

Anything. Really:

- Facturas, extractos bancarios, modelos de impuestos — `*.pdf`
- Fotos de recibos, capturas, pizarras — `*.png`, `*.jpg`, `*.heic`
- Exports de APIs, payloads — `*.json`
- Hojas de cálculo, CSVs de transacciones — `*.csv`, `*.xlsx`
- Notas sueltas, markdown, txt — `*.md`, `*.txt`
- Páginas guardadas, documentos — `*.html`, `*.docx`, `*.eml`

If the agent can read it, it gets ingested. If it can't, the original is
preserved and a gap is logged for you — nothing is ever silently dropped.

## How it works

1. **You drop** files here (or whole folders).
2. **The agent sales a pasear** — run a sweep by saying *"procesa el inbox"*
   (or it runs on a schedule, see below). For each file it:
   - detects the format and extracts the content,
   - classifies it into a topic (`finanzas/`, `legal/`, `crm/`, …) by what
     it's *about*, not what format it is,
   - relates it to what's already in the wiki (cross-links),
   - compiles it into a wiki article.
3. **Processed files move** to `_processed/YYYY-MM-DD/` as an audit trail —
   the byte-for-byte original is also preserved under
   `../raw/<topic>/_originals/`.
4. **Each new file feeds and improves the system** — the maintenance and
   improvement loop runs automatically after the sweep.

## Folders

- `_processed/` — files already ingested, archived by sweep date. Safe to
  prune once you trust the wiki.

## Schedule the walk (optional)

```bash
# Nightly inbox sweep at 02:00
schedule create wiki-inbox --cron "0 2 * * *" --command "procesa el inbox"
```

You don't have to wait for the schedule — say *"procesa el inbox"* anytime.
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