ericrisco/rsc-harness / skills/prompt-engineering
prompt-engineering
VerifiedUse when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is `building-agents`), NOT a standing CI eval harness (that is `agent-eval`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.3 KB |
| evals/README.md | markdown | 806 B |
| evals/cases.yaml | config | 4.1 KB |
| references/eval-templates.md | markdown | 3.6 KB |
| references/output-contracts.md | markdown | 4.4 KB |
| scripts/verify.shexecutable | script | 3.5 KB |
evals/README.md
View on GitHub# Evals for prompt-engineering
These cases are illustrative routing and capability checks, not an automated pass/fail
gate. To run them, read `cases.yaml` and judge by hand: for each `should_trigger` prompt,
ask whether this skill's description and body would plausibly fire; for each
`should_not_trigger` prompt, confirm it routes to the named sibling instead. For the
`capability` scenario, draft a real answer and check it hits every `must_include` rubric
item (ordered skeleton, explicit output contract with the strict-vs-JSON-mode note, three
deliberately different few-shot examples, ≥5 inline cases incl. an adversarial one, the
iterate-one-variable note, no banned hedges, and the building-agents pointer). If an
answer misses an item, the skill body — not the case — is what needs fixing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |