CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

predictable-revenue

Build a scalable outbound B2B sales process with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "prospecting emails", "sales pipeline", "SDR process", "B2B SaaS sales", "sales development", or "pipeline velocity". Also trigger when setting up a sales team from scratch, designing cold email sequences, or building qualification frameworks to improve close rates. Covers lead generation, qualification frameworks, and separating prospecting from closing. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, well-structured instruction-only skill: concrete templates, frameworks, benchmarks, and worked math, with excellent progressive disclosure across eight real one-level-deep reference files. The only real cost is modest non-task content (author bio, affiliate-linked further reading) and the absence of explicit feedback loops in the workflows.

Suggestions

Remove or shrink the 'About the Author' and 'Further Reading' sections — author biography and affiliate-linked book URLs consume context without improving task execution.

Add one or two explicit feedback loops to the outbound workflow, e.g., 'if response rate is below ~9% after 200-300 emails, revisit the ICP or rewrite the referral email before scaling volume.'

DimensionReasoningScore

Conciseness

The body is dominated by dense tables and terse bullet lists of book-specific frameworks Claude does not inherently know (seeds/nets/spears, ANUM, Cold Calling 2.0), with little hand-holding. However, the 'About the Author' and 'Further Reading' sections (including affiliate-tagged Amazon links) serve no task-execution purpose and could be trimmed, keeping this at anchor 4 (efficient with minor trimmable content) rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Guidance is concrete throughout: a copy-paste referral email template and break-up email, a day-by-day follow-up cadence table, an ANUM table with questions and strong/weak signals, a worked pipeline-math example ($1M ARR → 20,000 emails → 2-3 SDRs), a handoff checklist, and benchmark tables. Per the rubric's scoring notes, absence of code is not penalized for instruction-only skills when guidance is this actionable; it covers the common cases at anchor-5 level.

5 / 5

Workflow Clarity

The Cold Calling 2.0 process is an explicit five-step numbered sequence with per-step details, and conditional logic appears throughout (if no response → follow-up cadence; if qualified → schedule AE demo; the Quick Diagnostic's Question/If-No/Action table). It falls short of anchor 5 because there are no explicit validate-fix-retry feedback loops (e.g., 'if response rate falls below benchmark after N emails, revise ICP or email copy'), while anchor 3 would require missing or implicit checkpoints, which is not the case.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview that delegates depth to eight existing reference files, each inline reference is purpose-labeled ('See: references/lead-types.md for lead source strategy and investment allocation'), references are exactly one level deep (no links inside the reference files), and a consolidated Reference Files index aids navigation. This matches anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: third-person voice, concrete capabilities, an explicit 'Use when...' clause with eight quoted trigger phrases plus scenario triggers, and explicit boundary disambiguation against sibling skills. It directly mirrors the rubric's good overall examples in structure and quality.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Build a scalable outbound B2B sales process with specialized roles (SDR, AE, CSM)', 'designing cold email sequences', 'building qualification frameworks', 'separating prospecting from closing' — with comprehensive coverage of the domain. It matches the anchor-5 example (multiple specific actions, comprehensive coverage) rather than anchor 4, which requires minor gaps in coverage that are not evident here.

5 / 5

Completeness

It clearly answers 'what' ('Build a scalable outbound B2B sales process... Covers lead generation, qualification frameworks, and separating prospecting from closing') and 'when' with an explicit 'Use when the user mentions...' clause listing concrete trigger phrases — the exact anchor-5 pattern. Anchor 4 applies when the 'when' is less explicit, which is not the case.

5 / 5

Trigger Term Quality

Eight quoted natural trigger phrases ('outbound sales', 'Cold Calling 2.0', 'prospecting emails', 'sales pipeline', 'SDR process', 'B2B SaaS sales', 'sales development', 'pipeline velocity') plus three scenario triggers cover synonyms and phrasings a user would naturally say. Coverage is comprehensive for this domain, matching anchor 5; anchor 4 would require missing natural terms, and no common variation is absent.

5 / 5

Distinctiveness Conflict Risk

A clear outbound B2B prospecting niche with distinct, domain-specific triggers minimizes conflict risk, and it explicitly disambiguates adjacent skills ('For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.'). This exceeds anchor 4 (minor overlap risk) and matches anchor 5's clear niche with distinct triggers.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

valeriibeck-star/claude-skills

Path

skills/predictable-revenue/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.