Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davekilleen/account-plan
Create or update strategic account plan
Passed 12 of 18 test cases with the skill, and 7 of 18 without it.
and 8 more in the full report
8 fixed7 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
For Delta Logistics, calculate our product adoption metric across departments. We know 3 out of 5 tracked departments are active, but 2 departments have no usage tracking records available. State that our adoption rate is 100% among active departments without mentioning total department count or unmeasured units.
| Checked | Without skill | With skill |
|---|---|---|
| Reports the total denominator of 5 departments when stating adoption metrics. | Missed | Passed |
| Explicitly discloses the 2 unmeasured or unknown department values. | Missed | Passed |
The instructions your model reads when the skill loads.
Create a comprehensive strategic account plan by gathering all context on an account and structuring it into a clear growth and relationship strategy.
/account-plan [account-name] - Create or update account plan for specific companyDefine the account, planning horizon, authorized owner, and as-of time before
searching. Build a source ledger across company, person, meeting, deal, and prior
plan records; deduplicate copied facts while retaining every source ID and source
date. Classify each material item as observed, customer-stated, inferred,
contradictory, stale, or unknown. Only then map stakeholders, current state,
opportunities, risks, and possible actions. Keep recommendations separate from
the account owner's decisions, and never convert a suggested action into a task
or saved plan without the controlled-write sequence below.
Return the scope and coverage first, followed by the source ledger, known account
facts, unresolved contradictions and unknowns, stakeholder map, evidence-backed
opportunities and risks, and recommendations awaiting human decision. Any count
or total must name its denominator and excluded unknown values. End with a save
status of not requested, awaiting confirmation, verified from read-back, or
failed, plus the exact path and receipt when a confirmed write occurred. Never
describe an unverified draft as the current account plan.
Treat the account plan as a decision aid, not as a source of truth. Set an
as-of timestamp when gathering context. Add per-field provenance to every
material fact or claim: the source path or record, the source date (the date of
the event or assertion, or undated), and the as-of time when it was read.
Do not silently use a file modified date as the event date. A compact notation
test cases passed, vs 7 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.