Skip to content

ericrisco/rsc-harness / skills/sales-funnel

sales-funnel

Verified

Use when planning the steps from an offer to purchase or booking: pages, transitions, recovery paths and measurement handoffs. NOT writing one page (that is `landing-copy`), running deals (that is `sales-pipeline`) or implementing payment (that is `stripe`).

FileKindSize
SKILL.mdskill md7.2 KB
evals/README.mdmarkdown1.9 KB
evals/cases.yamlconfig3.6 KB

evals/README.md

View on GitHub
# Sales funnel evaluation

Run routing in fresh sessions using only the skill description. Repeat each positive and negative
prompt three times; require at least 90% correct majority decisions across the cases. Check that
each negative case's owner exists in the catalog. Structural eval-lint does not measure routing.

For capability, give the complete scenario to independent agents with and without the skill.
Both arms receive the same source facts and have separate temporary output directories. The
baseline must not read any skill or this rubric. Randomize output labels and have an independent
grader score every rubric item with quoted evidence and quality on completeness, actionability,
correctness and grounding. Use the catalog behavioral scorer; require absolute >= 8.5 and lift >= 1.0.
Repeat three times for a stable estimate and retain all outputs, scores and failed runs.

These are model/human judgments, not deterministic CI. Record run count and uncertainty. No
behavioral result is claimed by these case definitions. Re-run after description or method changes.
No shell checker is provided: planning truth and payment-path adequacy need the supplied scenario
and semantic review, not a grep for headings.

## Initial evaluation — 2026-10-31

One capability scenario, one fresh execution per arm, independently blind-graded:
with skill **9.8/10**, without **9.8/10**, difference **+0.0**.
The catalog scorer requires absolute >=8.5 and improvement >=1.0. This run
passed absolute quality but did not meet the improvement threshold.
This is a single-trial result, not the repeated-trial protocol above or evidence of conversion gains.
Arms used separate contexts and files; the scorer reported transcript integrity **not checked**.
The owner authorized release 3.7.0 with the pack’s incomplete behavioral evidence documented.
The thresholds remain unchanged; release authorization is not an evaluation pass.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall