ericrisco/rsc-harness / skills/marketing
marketing
VerifiedUse when the words span a marketing surface — value proposition, section copy, microcopy, launch and email sequences, channel adaptation, SEO-aware structure — grounded in the brand study, which it stops and builds if missing. NOT one conversion page (that is `landing-copy`), NOT tone rules (that is `brand-voice`), NOT pixels (that is `design`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.2 KB |
| evals/README.md | markdown | 3.0 KB |
| evals/cases.yaml | config | 7.0 KB |
| references/brand-grounding.md | markdown | 9.3 KB |
| references/campaigns-and-channels.md | markdown | 7.2 KB |
| references/copy-frameworks.md | markdown | 8.2 KB |
| references/landing-copy.md | markdown | 8.6 KB |
| references/seo-geo.md | markdown | 19.9 KB |
| scripts/seo_audit.pyexecutable | script | 5.6 KB |
| scripts/verify.shexecutable | script | 10.2 KB |
evals/README.md
View on GitHub# Eval harness — `marketing` skill
These evals check two things: that the skill **triggers** on the right prompts
(and stays quiet on near-misses), and that it **measurably improves** copy/SEO
output. Cases live in `cases.yaml`. There is no pure shell runner — grading is
done by an **agent harness** (a Claude Code agent with skills loaded) plus a
human spot-check, because triggering and copy quality are judgment calls.
## What's in `cases.yaml`
- `should_trigger` — prompts that MUST load `marketing`.
- `should_not_trigger` — near-misses that must route elsewhere (`route_to`).
- `capability` — scenarios with a `must_include` rubric to grade with vs without.
## Triggering eval
Goal: the skill fires when it should and never on a near-miss.
1. Configure an agent with the **full catalog of skill descriptions** available
for routing (marketing + design, nextjs, postgresdb, security-audit, go,
flutter, presentations, course-storytelling, building-agents, deployment,
harness, init) so routing competes realistically.
2. For each `should_trigger` prompt: feed it cold, record whether `marketing`
is the skill the agent loads. Run **3-5 trials** per prompt (fresh context).
3. For each `should_not_trigger` prompt: confirm `marketing` does NOT load, and
that the chosen skill matches `route_to` (or that it correctly declines when
`route_to: none`). Same 3-5 trials.
4. Score: `triggered_correctly / total_trials` across both lists.
**Pass bar: >= 90% trigger accuracy** over all prompts and trials, with **zero
systematic false-positives** on the `design`/`nextjs` near-misses (those are the
known traps — a landing-page prompt about pixels or the build must not pull in
marketing).
## Capability eval
Goal: prove the skill changes the answer, not just the routing.
1. For each `capability` scenario, run it **twice**:
- **WITHOUT** the skill (base agent, no `marketing` loaded).
- **WITH** the `marketing` skill loaded.
2. Grade each output against that scenario's `must_include` checklist — one
point per checkable item covered. A human or a grading agent marks each
item present / absent.
3. Compute coverage = `items_covered / total_items` for each run.
**Pass bar: WITH the skill covers >= 80% of `must_include`; WITHOUT clearly
lower** (target a >= 30-point gap). The skill must demonstrably add the
brand-grounding STOP, specificity-over-adjectives, single-CTA discipline, the
ban-list, `[[NEEDS PROOF]]`, and the SEO/GEO + JSON-LD spec. If the base answer
already scores ~80%, the case isn't discriminating — tighten the rubric.
## Notes on honesty
- Trials are stochastic; report the raw fraction, not a rounded "pass".
- Brand-gate behavior is the highest-signal capability check: a correct answer
refuses to write grounded copy with no brand study and interviews instead.
Treat a confident, ungrounded full-page draft as a **capability failure** even
if the prose reads well.
- Re-run after any edit to `SKILL.md` or its `references/` — wording changes
shift both triggering and rubric coverage.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |