AC heuristics
Master reference for 88 psychological heuristics — the complete leverage list for sales, copywriting, offer design, cold outreach, objection handling, and persuasion. Use this skill whenever working on any stimulus meant to influence human behaviour: cold emails, DMs, VSL scripts, sales call frameworks, proposal copy, landing pages, CTAs, offer structuring, objection rebuttals, or follow-up sequences. Always trigger when the user asks how to make copy more persuasive, how to handle a specific objection, how to frame an offer, how to structure a pitch, or how to get someone to take action. If the task involves getting a human to do something — consult this skill first, every time, without exception.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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: 2. 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 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 14 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 14 branches
- 70Execution cost. Instruction body is 4909 tokens
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 707: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 9 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.