Skip to content

ericrisco/rsc-harness / skills/chatbot

chatbot

Unverified

Use when a support or sales bot on a live website must behave: persona/system prompt, grounding so it cannot invent prices or policy, jailbreak and injection defense, the human handoff, launch metrics and kill switch. NOT the agent loop or RAG index under it (that is `building-agents`), NOT a human answering one ticket (that is `customer-support`).

FileKindSize
SKILL.mdskill md13.1 KB
evals/README.mdmarkdown1.3 KB
evals/cases.yamlconfig4.3 KB
references/handoff-and-sales.mdmarkdown3.9 KB
references/system-prompt-and-guardrails.mdmarkdown5.3 KB
scripts/verify.shexecutablescript7.0 KB

evals/README.md

View on GitHub
# chatbot — evals

`cases.yaml` holds two kinds of checks. **Trigger cases** (`should_trigger` / `should_not_trigger`) are routing judgments: read each prompt and confirm the skill description would (or wouldn't) claim it, and that each `should_not_trigger` lands on the named sibling instead — there's no runner, it's a human/LLM judgment against the frontmatter. The **capability case** is a rubric: give a fresh agent loaded with this skill the scenario, then check the produced system prompt and operating design contain every item in `must_include`.

To exercise the artifact gate, run the verifier against a candidate system prompt:

```bash
# from your project (not the skills repo)
skills/chatbot/scripts/verify.sh path/to/system-prompt.md
skills/chatbot/scripts/verify.sh path/to/system-prompt.md --strict   # warnings fail too
```

It's read-only and dependency-free (POSIX sh + grep). It hard-fails on a leaked secret, a missing refusal/handoff/grounding section, or an unbounded-commitment phrase ("we guarantee", "any price", "always refund", "unlimited"); it warns on a missing length cap or missing injection-defense language. A clean or empty file exits 0, so it never false-fails. A good capability answer should produce a prompt that passes `verify.sh` cleanly.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall