AC proposal-writing
Write winning proposals and quotes for a solopreneur business. Use when putting together a proposal for a potential client, structuring a sales document, pricing a project scope, or improving proposal win rates. Covers proposal structure, scoping, pricing presentation, objection pre-emption, and the psychology of persuasive proposals. Trigger on "write a proposal", "proposal template", "sales proposal", "quote for client", "how to structure a proposal", "proposal writing", "win more proposals", "client proposal".
Write winning proposals and quotes for a solopreneur business.
As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (proposal-writing) differs from the folder (proposal-writing-2)
- 70When it triggers. States when to use, but not when not to
- 85Steps. 37 steps, 3 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 2122 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 518: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.