reverse-skill
reverse-skill: análisis desde routing.json a un caso reproducible
Sigue reglas, precondiciones, case-init, índice, fixity y generación de informes con una fixture inocua.
Qué aprenderás
- Navigate reverse-skill routing and case scripts
- Verify evidence and report boundaries
- Design safe regression contributions
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
- Start source reading from routing.json and a harmless fixture.
- Trace route preconditions, case writes, hashes, retries, and report references.
- Prefer regression, schema, idempotency, and cross-platform fixes over broad risky changes.
Begin with a harmless fixture
Fija commit y fixture pública, confirma normalización, regla R0–R44, precondiciones, archivos, hashes, reintentos y referencias del informe; prioriza regresiones y pruebas de schema/idempotencia.
Search from `skills/config/routing.json`, `skills/scripts/master-route.ps1`, `case-init.ps1`, regression cases, and the selected scenario `SKILL.md`. Treat README tables as navigation hints, then confirm symbols, parameters, and tests in the checkout.
Follow the route decision
Record how a natural-language hint is normalized, which R0–R44 rule matches, what preconditions are checked, and how the selected skill and tool list are emitted. Compare the route with the expected regression case and explain any ambiguity or fallback.
Inspect failure behavior: missing tool, unknown scenario, invalid scope, disallowed network profile, or malformed configuration should stop with an actionable error rather than silently selecting a more powerful path.
Trace case and evidence writes
Follow `case-init` into scope, timeline, workitems, and field-journal files, then trace how a scenario skill records command, artifact, timestamp, hash, and analyst note. Identify whether retries are idempotent and whether partial artifacts are marked incomplete.
Next inspect case-review and report generation. A report should reference immutable evidence and distinguish observation, finding, path, confidence, limitations, and remediation; avoid copying raw secrets or sensitive samples into logs.
Turn findings into safe contributions
Good contribution-sized changes include a new routing regression fixture, an explicit precondition, a redacted evidence schema test, an idempotent case-init check, or a cross-platform script fix. Run routing, coherence, smoke, and index drift checks before proposing it.
Keep active exploitation or bypass experimentation outside article fixtures. The source-analysis goal is to make authorized methodology selection and evidence handling more reliable, not to publish operational abuse recipes.
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
Pin a commit and create a public toy fixture.
- 2
Trace hint normalization, rule match, preconditions, and selected skill.
- 3
Inspect case-init, evidence, fixity, review, and report generation.
- 4
Add a narrow regression or schema test and run every documented gate.
Ejemplo para copiar
hint -> routing.json rule -> precondition -> skill/tool list
fixture -> case-init -> timeline/evidence/hash
-> case-review -> report with Finding/Path referencesPreguntas frecuentes
Can a README table prove a script's exact behavior?
No. Confirm parameters, symbols, tests, and failure paths in the pinned checkout.
What is a low-risk first contribution?
A harmless routing fixture, precondition error, evidence schema, idempotency test, or platform script fix.
Fuentes
- reverse-skill README (captured 2026-08-31)Fuente verificada 2026-08-31
- reverse-skill repositoryFuente verificada 2026-08-31