CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deal-qualify

MEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/ai-agency/tonone/bundle/revenue-team/skills/deal-qualify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a well-sequenced, actionable qualification workflow with a concrete scoring rubric and output template. Its weaknesses are re-explaining MEDDPICC concepts Claude already knows and depending on external files (docs/output-kit.md, /atlas-report) that are absent from the bundle, which undermines both token efficiency and navigation.

Suggestions

Drop or compress the Definition column in the MEDDPICC worksheet (e.g., keep only component names plus Status/Evidence/Gap columns) — Claude already knows the framework, and the definitions are the largest source of redundant tokens.

Resolve the dangling references: either inline the essential output-format rules from docs/output-kit.md (line budget, severity indicators, box-drawing skeleton) or actually include that file in the bundle, since the skill's output format currently depends on an unreachable document.

Add an explicit validation checkpoint before Step 4 — e.g., 'confirm all 8 components have a status and one-line evidence before writing the card' — to close the workflow-clarity gap.

DimensionReasoningScore

Conciseness

The body is mostly tight (terse tables, no filler paragraphs), but the worksheet's Definition column re-explains standard MEDDPICC concepts Claude already knows (e.g., 'Champion — Internal advocate with influence who sells on your behalf when you're not in the room', 'Economic Buyer — Person with budget authority who can sign'). Eight rows of known-framework definitions is more than the 'minor instances' of the 4 anchor, but each is a single terse line and the rest of the body is lean, so it stays above 2.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: explicit status levels ('CONFIRMED (evidence in hand), PARTIAL (some signal, gaps remain), MISSING'), a score-to-verdict-to-action table ('7-8 CONFIRMED → Strong — pursue → Advance to proposal stage'), and a copy-paste qualification card template. It misses 5 because there is no worked example of a completed card, and exceeds 3 because the guidance is fully specified rather than pseudocode or high-level hints.

4 / 5

Workflow Clarity

Steps 0-4 are clearly sequenced, Step 0 acts as an input-gathering checkpoint ('Ask for any missing inputs'), and the verdict table drives an explicit decision. It falls short of 5 because there is no validation checkpoint (e.g., confirming all 8 components are scored or the card is complete before output), and stays above 3 because the sequence is explicit with most checkpoints present — this is an analysis skill, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Sections are well organized (numbered steps, clear headers) and the reference is clearly signaled ('Follow the output format defined in docs/output-kit.md'), but that file does not exist in the bundle — no references/, scripts/, assets/, or docs/ directories are present — leaving the promised output format (box-drawing skeleton, severity indicators) unreachable; '/atlas-report' is likewise referenced without bundle support. This keeps it below 4 (a critical reference is dangling), but above 2 because the structure is not minimal and nothing is buried or inlined.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states what the skill does in concrete terms, provides explicit natural-language trigger phrases, and occupies a distinct niche. The only notable gap is missing common trigger variants such as 'MEDDIC' or 'deal review', which keeps trigger coverage just short of comprehensive.

DimensionReasoningScore

Specificity

The description names concrete actions and outputs — 'guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action' — going beyond a bare domain label. It falls short of 5 because it omits several capabilities the skill actually has (component scoring with CONFIRMED/PARTIAL/MISSING, verdict tiers, gap-closing plans), and is above 3 because it lists several specific actions rather than just 1-2.

4 / 5

Completeness

It clearly answers 'what' ('MEDDPICC-based deal qualification worksheet... produce a filled card + recommended next action') and 'when' with an explicit 'Use when asked to...' clause containing four concrete trigger phrases. This directly matches the anchor for a complete what+when description with concrete triggers; nothing is merely implied.

5 / 5

Trigger Term Quality

The quoted triggers 'qualify this deal', 'run MEDDPICC on this opportunity', 'should we pursue this', and 'is this deal real' are phrases a user would naturally say, with synonym coverage of 'deal'/'opportunity'. Not 5 because common variants like 'MEDDIC' (the frequent shorter spelling) and adjacent phrasings like 'deal review' or 'sales qualification' are missing; not 3 because the natural terms users actually say are present and explicit.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — MEDDPICC-based sales deal qualification — and the triggers ('run MEDDPICC', 'should we pursue this') are distinctive to that domain, giving minimal overlap risk with unrelated skills. Voice is consistent with the rubric's good examples (imperative verb forms, no first/second-person framing), so no specificity penalty applies.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/bundle/revenue-team/skills/deal-qualify/SKILL.md

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.