do-nothing-buster
Skill1 starsChanged 47 days agoLicence not identifiedView on GitHub
Diagnoses no-decision risk in a live deal: checks the nine status-quo causes from handbook 20.1 against your deal notes, scores the risk, and builds a status-quo battle plan with cost of inaction, compelling event, champion actions and next steps. Use on \"they might do nothing\", \"no decision risk\", \"status quo is our competitor\", \"why won't they decide\", \"no urgency to buy\". Siblings: competitive-battlecard (a named competitor is in the deal), presales-coach (stuck deal, constraint not yet known), win-loss-analyzer (deal already closed as no-decision). SKIP for named-competitor positioning.
In this repository42 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brandSkill
- business-case-stress-testerSkill
- capability-mapperSkill
- champion-healthSkill
- competitive-battlecardSkill
- confidence-taggerSkill
- critical-business-issue-finderSkill
- deal-prequalSkill
- demo-dryrun-coachSkill
- demo-storyboardSkill
- diagramSkill
- discovery-ftdSkill
- discovery-salesSkill
- discovery-transformerSkill
- docx-generatorSkill
- exec-briefing-prepSkill
- field-comms-writerSkill
- humanizeSkill
- integration-complexitySkill
- knowledge-captureSkill
- learning-planSkill
- linkedin-postSkill
- negotiation-prepSkill
- osd-architectSkill
- osd-scoperSkill
- pptx-generatorSkill
- presales-coachSkill
- presales-leaderSkill
- presales-metricsSkill
- pricing-positioningSkill
- rag-markdownSkill
- rfx-navigator-presalesSkill
- second-brainSkill
- security-questionnaireSkill
- solution-architectureSkill
- tactical-empathy-coachSkill
- tfqSkill
- toc-bbit-expertSkill
- video-demo-creatorSkill
- win-loss-analyzerSkill
- workshop-agenda-builderSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.