disqualification-handling

Handles disqualified and near-miss inbound leads gracefully. Drafts polite rejection emails, referral requests (right company wrong person), and nurture routing (future fit). Ensures no inbound lead gets ignored and every disqualification preserves the relationship. Tool-agnostic.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sales/composites/disqualification-handling/SKILL.md

Quality

Content

71%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 is highly actionable with complete templates, concrete rules, and a well-sequenced workflow that includes human-review checkpoints for this batch operation. Its main weaknesses are length/conciseness and the total absence of progressive disclosure via separate reference files.

Suggestions

Move the four detailed email template frameworks into a references/ file (e.g., references/email-templates.md) and link to them one level deep, keeping only a brief summary inline in SKILL.md.

Trim redundant per-category 'Goal:'/'Objective:' lines and the ASCII architecture diagram, or condense them, to reduce token overhead.

Add an explicit self-check step that verifies each draft against the Email Hard Rules list before routing to human review, strengthening the validation feedback loop.

Dimension	Reasoning	Score
Conciseness	The ~365-line body is mostly actionable, but includes tightening opportunities such as per-category 'Goal:'/'Objective:' lines, an ASCII architecture diagram, and verbose inline template frameworks that pad the token budget.	3 / 5
Actionability	Provides fully executable, copy-paste-ready email templates for all four categories, concrete rules (word limits, banned words), explicit sub_verdict triggers, a routing table, and a concrete markdown output format covering the common cases.	5 / 5
Workflow Clarity	A clear Step 0→1→2→3 sequence is present with validation checkpoints ('Draft ready for human review & send'), an Email Hard Rules checklist, and edge-case routing; minor gaps keep it just below a 5.	4 / 5
Progressive Disclosure	The skill is well-sectioned but ships as a single 365-line monolithic SKILL.md with no bundle files or one-level references, and the four detailed email templates are inlined where they could be split into reference files.	3 / 5
	Total	15 / 20 Passed

Description

71%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.

The description is specific and action-oriented with a clear, distinct niche, but it lacks any explicit 'Use when...' trigger guidance, which caps its completeness. Trigger-term coverage is good though not exhaustive.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g., 'Use when handling disqualified or near-miss inbound leads, drafting rejection emails, or routing leads to nurture.'

Include a few more natural synonyms users might say ('rejected leads', 'what do we do with the ones that didn't qualify') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Drafts polite rejection emails, referral requests (right company wrong person), and nurture routing (future fit)' — giving comprehensive coverage of the skill's handling paths.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('rejection emails', 'referral requests', 'nurture routing', 'disqualified', 'near-miss', 'inbound leads') that a sales/outreach user would say, though a few synonyms (e.g., 'rejected leads', 'follow-up') are absent.	4 / 5
Distinctiveness Conflict Risk	The post-qualification disqualification-handling niche is distinct and unlikely to trigger for the wrong skill, with only minor overlap risk against general outreach/email-drafting skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/sales/composites/disqualification-handling/SKILL.md
Commit: 2523432

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.