reverse-skill
reverse-skill: futuro y proyecto de un workbench auditable
Manifiesto de caso, autorización, capacidades, grafo de evidencia, regresiones e informes accesibles.
Qué aprenderás
- Design a case/evidence manifest
- Plan fixture-driven routing governance
- Add capability and authorization gates safely
Antes de empezar
- Basic Git and command-line usage
- Comfort reading a project README
You can explain the project, run its documented first step, and decide what to verify before adopting it.
Conclusiones clave
- A case manifest can connect authorization, route, tools, evidence, findings, and report.
- Public fixtures and capability manifests make cross-platform behavior testable.
- Accessible text/SVG remains canonical even when interactive lineage views are added.
Make the contract measurable
Conserva hash de routing, regla, cliente, índice, autorización, objetivo, red, capacidades, artefactos e informe. Markdown/SVG son canónicos; Three.js solo una vista opcional del grafo.
Treat new scenarios, tools, MCP servers, and active-action helpers as proposals until their authorization, permissions, failure modes, and fixtures are reviewed.
Design the case manifest
Record repository commit, routing.json hash, matched rule, client/host, tool-index snapshot, authorization reference, target/sample hash, network profile, allowed actions, skill versions, artifact hashes, timeline, findings, reviewer, retention, and report checksum. Keep secrets and sensitive samples outside the manifest but bind them by controlled identifiers.
Generate JSON plus accessible Markdown/HTML. A local SVG can show route and evidence lineage; an optional Three.js view may explore large case graphs, but text must remain the canonical searchable representation.
Ship bounded milestones
Milestone one adds public APK/ELF/PCAP fixtures and route regression receipts. Milestone two validates case-init idempotency, evidence fixity, redacted logs, and cross-platform parity. Milestone three adds capability manifests and policy checks for MCP/client permissions. Milestone four canaries active-action workflows only in explicitly authorized sandboxes.
Publish the 173-case baseline, skipped-tool reasons, route latency, analyst review time, and known limitations. Start report-only, then advisory, then enforce missing authorization or evidence gates after teams can reproduce them.
Success criteria
A learner or analyst should be able to replay a harmless case, explain the route, inspect every permission and artifact, produce a defensible report, and recover from a tool or client failure. That is more durable than adding more commands to a catalog.
Cómo elegir
| Criterio | Opción A | Opción B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Pasos de implementación
- 1
Define the case and capability manifest schema.
- 2
Add harmless fixtures, route receipts, idempotency, fixity, and redaction tests.
- 3
Validate client/MCP permissions and cross-platform parity.
- 4
Move from report-only to advisory/enforced authorization and evidence gates.
Ejemplo para copiar
case:
commit: <sha>
routing_sha256: <hash>
matched_rule: R12
authorization_ref: owner-ticket-001
target_sha256: <hash>
network_profile: offline
evidence: [artifacts/a.bin, timeline.json]
report_sha256: <hash>Preguntas frecuentes
Should case manifests include target contents?
No. Store hashes and controlled references; keep sensitive samples in an access-managed evidence store.
Is Three.js part of the core router?
No. It is an optional presentation layer; accessible Markdown/HTML and local SVG should remain complete without it.
Fuentes
- reverse-skill README (captured 2026-08-31)Fuente verificada 2026-08-31
- reverse-skill repositoryFuente verificada 2026-08-31