sales-script
When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks. Activate for sales calls, demo prep, talk tracks, bid responses, competitor comparisons, or pre-sales engineering.
83
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/sales-script/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger term coverage and specificity, listing numerous concrete deliverables and natural keywords a user would mention. Its main weakness is that it blurs the 'what it does' and 'when to use it' together—it reads more like two 'when' clauses rather than clearly stating what the skill produces followed by when to activate it. Adding an explicit capability statement (e.g., 'Generates sales enablement materials including...') would strengthen it.
Suggestions
Add an explicit 'what this does' statement at the beginning, e.g., 'Generates sales enablement materials and pre-sales deliverables for founders' before listing the trigger conditions.
Restructure to separate capabilities from triggers more clearly, e.g., 'Creates demo scripts, discovery call frameworks, objection handling guides, RFP/RFI responses, competitive matrices, POC plans, and closing playbooks. Use when a founder needs sales call prep, bid responses, competitor comparisons, or pre-sales engineering support.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, and closing playbooks. | 3 / 3 |
Completeness | The description effectively communicates 'when' via 'When a founder needs...' and 'Activate for...', but the 'what does this do' is only implied through listing deliverables—it never explicitly states what the skill produces or how it helps (e.g., 'Generates sales enablement materials'). The what and when are somewhat blurred together. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'sales calls', 'demo prep', 'talk tracks', 'bid responses', 'competitor comparisons', 'pre-sales engineering', 'RFP', 'RFI', 'objection handling', 'discovery call', 'POC planning', 'closing playbooks'. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around sales enablement and pre-sales activities for founders. The specific trigger terms like 'RFP/RFI', 'POC planning', 'demo scripts', and 'competitive feature matrices' make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable sales skill with clear workflows, concrete frameworks, and useful examples. Its main weakness is length — it packs extensive framework detail inline that could be split into referenced files, and some content (general objection handling, closing techniques) represents common sales knowledge that Claude likely already possesses. The workflow sequencing and validation checkpoints are strong.
Suggestions
Move detailed frameworks (discovery call timing table, demo script structure, objection handling table, closing techniques) into separate referenced files to reduce the main skill's token footprint.
Trim general sales knowledge Claude already knows (e.g., basic closing techniques, generic objection categories) and focus inline content on startup-specific or non-obvious guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some content that could be tightened — e.g., the closing techniques and objection handling tables contain general sales knowledge Claude likely already knows. The frameworks are useful but verbose for a skill file; some could be referenced externally. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific scoring formulas (Full 100%, Partial 50%, etc.), bid/no-bid thresholds, timing breakdowns for calls and demos, the LAER model with example objections and responses, and concrete output examples including a demo opening script and RFP coverage analysis. | 3 / 3 |
Workflow Clarity | The four-phase workflow is clearly sequenced with numbered steps, each phase building on the previous one. Validation checkpoints are present — e.g., scoring requirement coverage before proceeding, pre-demo checklists, POC success criteria with a >60% threshold, and demo recovery procedures for when things go wrong. | 3 / 3 |
Progressive Disclosure | The skill references related skills (cold-outreach, proposal-generation) and startup-context, which is good. However, the file itself is quite long and monolithic — the detailed frameworks (discovery call, demo structure, objection handling tables, closing techniques) could be split into referenced sub-files rather than inlined, making the main skill leaner. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- shawnpang/startup-founder-skills
- Commit
4ad31b4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.