ericrisco/rsc-harness / skills/proposals
proposals
VerifiedUse when writing the document a buyer reads to say yes — a commercial proposal or Statement of Work, turning discovery notes into a scoped and priced document, adding tiers so the middle one wins, or diagnosing a proposal that will not close. NOT the binding legal agreement with its liability and IP clauses (that is `contracts`), NOT deciding the number or the margin (that is `pricing`), NOT the deck that pitches the vision to a room (that is `pitch-deck`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.8 KB |
| evals/README.md | markdown | 869 B |
| evals/cases.yaml | config | 3.3 KB |
| references/proposal-skeleton.md | markdown | 4.5 KB |
| references/sow-skeleton.md | markdown | 3.5 KB |
| scripts/verify.shexecutable | script | 8.7 KB |
evals/cases.yaml
View on GitHubskill: proposals
should_trigger:
- prompt: "Write a commercial proposal for the Acme website redesign."
why: Core job — the persuasive, scoped, priced document a buyer reads to commit.
- prompt: "Draft a statement of work for the 8-week data-migration engagement."
why: The SOW is this skill's second artifact (scope, exclusions, acceptance criteria, terms).
- prompt: "Add Good/Better/Best tiers to this offer so the middle one wins."
why: Tiered presentation and anchoring — the three-tier pattern that lifts close rate ~23%.
- prompt: "Esta propuesta no cierra, ¿por qué? Haz que cierre."
why: Non-obvious + Spanish — diagnosing a non-closing proposal is a proposals job (exec summary, tiers, close), not pipeline tracking.
- prompt: "Scope this so the client can't keep adding work for free."
why: Non-obvious — the request is really for explicit exclusions + a change-order clause, the scope-creep defense.
- prompt: "Turn these discovery-call notes into a proposal."
why: Discovery-to-proposal is the canonical intake-to-artifact flow.
- prompt: "Necessito redactar l'abast del projecte i la proposta comercial per al client."
why: Catalan — SOW (abast) + commercial proposal, squarely this skill.
should_not_trigger:
- prompt: "Draft the MSA and add liability and IP-assignment clauses."
route_to: contracts
why: Binding, enforceable legal terms — not the persuasive scoped doc.
- prompt: "What should we charge for this engagement and what's our margin?"
route_to: pricing
why: Deciding the number and the model, not presenting it in a proposal.
- prompt: "Build the slide deck to pitch this to their board."
route_to: pitch-deck
why: Visual narrative for a room, not a scoped/termed document.
- prompt: "The deal closed — send the invoice."
route_to: invoicing
why: Billing after the win, downstream of the proposal.
- prompt: "Set up follow-up reminders and move this deal to the negotiation stage."
route_to: sales-pipeline
why: Tracking and cadence, not authoring the document.
- prompt: "Write a cold email to get a first meeting with this prospect."
route_to: cold-outreach
why: First-touch messaging — there's no discovered need to scope yet.
capability:
- scenario: >
Given short discovery notes — buyer problem ("support drowning in ~200
password/order-status tickets a week"), a rough budget band (~$30–60k), and a
6-week window — produce a complete proposal plus the SOW that annexes it.
must_include:
- Personalized executive summary structured problem -> solution -> outcome -> investment, using the buyer's own words, not a feature dump.
- Three outcome-named pricing tiers with the middle marked recommended.
- A scope section with an explicit EXCLUSIONS subsection naming what is out.
- Deliverables each with acceptance criteria a third party can judge pass/fail.
- A change-order clause requiring written approval with updated cost and dates.
- A payment schedule tied to milestones, not the calendar.
- A mutual-action-plan close with dated next steps, one concrete CTA, and a validity window.
- No weasel words (etc., as needed, and more, TBD, unbounded ongoing).
- No smuggled binding-legal clauses, with a note that those route to contracts and the MSA governs.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |