CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

business-growth-skills

Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP').

71

Quality

89%

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

The canonical home for this skill is business-growth-skills in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary router body: lean, well-sectioned, and immediately actionable via a signal-to-path routing table with concrete example commands. The only flaws are cosmetic — a placeholder path in the load instruction and a minor path-prefix inconsistency between the table and the quick start.

DimensionReasoningScore

Conciseness

The ~28-line body is lean and functional with zero padding — a signal-to-path routing table, two copy-paste commands, and three terse rules. It assumes Claude's competence with no explanation of known concepts, matching anchor 5 exactly.

5 / 5

Actionability

Concrete executable commands ('cat business-growth/skills/customer-success-manager/SKILL.md', 'python3 …/health_score_calculator.py --help') plus a request-signal table. Minor gaps keep it below anchor 5: the '<skill>' placeholder in the load instruction and table paths ('skills/customer-success-manager/') that omit the 'business-growth/' prefix used elsewhere.

4 / 5

Workflow Clarity

The routing action is unambiguous: match request signals, ask one clarifying question if multiple rows match (an explicit checkpoint), load the matched SKILL.md, and follow that skill's workflow with the rule 'Route to exactly one skill'. No destructive or batch operations, so the validation cap does not apply.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Routing table, Quick start, Rules), and its external references — the four sibling SKILL.md paths — are one level deep and clearly signaled in the table, which is ideal index/router structure per the simple-skill note.

5 / 5

Total

19

/

20

Passed

Description

83%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 router-style description: it names all four bundled skills with concrete capabilities, uses third-person voice, and includes an explicit 'Use when…' clause with realistic example triggers. The only gaps are the undescribed contract-and-proposal-writer and some missing natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions per skill ('health scoring, churn risk, expansion', 'RFP analysis, competitive matrices, PoC planning', 'pipeline, forecast accuracy, GTM efficiency'), but 'contract-and-proposal-writer' is named with no capability detail — a minor coverage gap that keeps it below anchor 5 and well above the 1-2-action anchor 3.

4 / 5

Completeness

Explicitly answers both 'what' (router/index for the 4 bundled skills with their capabilities) and 'when' via an explicit 'Use when a growth/revenue request doesn't obviously match one skill…' clause with concrete trigger phrase examples — a clear anchor 5 match.

5 / 5

Trigger Term Quality

Good natural keyword coverage including example user phrasings ('which accounts are at risk', 'should we bid on this RFP'), churn risk, RFP, pipeline, forecast accuracy. Common synonyms like 'customer success', 'retention', or 'renewals' are missing, so it falls short of anchor 5's comprehensive synonym coverage but clearly exceeds anchor 3.

4 / 5

Distinctiveness Conflict Risk

The trigger is scoped to ambiguity ('doesn't obviously match one skill'), but the router's keywords inherently overlap with its four child skills (e.g., a proposal request matches both the router and contract-and-proposal-writer) — mostly distinct with minor overlap risk, anchor 4 rather than a clear niche with minimal conflict.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/business-growth-skills/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.