CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-demand-gen-specialist

Demand generation and acquisition-funnel specialist orchestrating the marketing-demand-acquisition, paid-ads, and email-sequence skills. Use when building or fixing the acquisition engine — e.g., comparing channel CAC against B2B SaaS benchmarks before reallocating a $40k/month budget, scoring paid-ads account health with ad_health_scorer.py before scaling spend, or designing a nurture sequence that must score 70+ on sequence_analyzer.py before launch. Covers channel mix, CAC/ROAS math, MQL→SQL workflows, attribution, and nurture design.

76

Quality

96%

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

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.

The body is a strong, actionable orchestrator spec: concrete executable commands with flags, three sequenced workflows with verification checkpoints and retry loops, and clean one-level-deep references to sub-skill bundles. The only weakness is mild verbosity from repeated long path prefixes and narrative prose that could be tightened.

Suggestions

Define a short path alias once (e.g. 'MA=../../marketing-skill/skills') and reuse it, or list the three skill base paths up front and reference files by relative name, to cut the repeated '../../marketing-skill/skills/...' prefixes throughout the body.

Tighten the 'Lane boundaries' and 'Proactive Routing' prose into scannable bullets so the routing rules read as a lookup table rather than narrative.

The 'Skill Integration' section could collapse the per-calculator Path/Usage/Output sub-bullets into a single line each, since the Location header already gives the path.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (no definitions of CAC/ROAS/MQL), but the long repeated relative path prefixes ('../../marketing-skill/skills/...') and the narrative 'Lane boundaries' / 'Proactive Routing' prose could be trimmed. This sits at 'efficient, minor instances that could be trimmed' rather than the fully-lean 'every token earns its place' anchor.

4 / 5

Actionability

Provides copy-paste-ready commands with full flags — 'python3 .../roas_calculator.py --spend 5000 --revenue 18000 --conversions 120 --clicks 2400 --margin 70 --json', 'ad_health_scorer.py --checks checks.json --platform meta --json', 'sequence_analyzer.py --file sequence.json --json' — and documents outputs and the no-args edge case for calculate_cac.py, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Three workflows each have a numbered, sequenced step list with an explicit 'Verification' checkpoint and feedback loops ('re-run the scorer after fixes and confirm the score improved', 'fix every flag and re-run until the quality score is ≥ 70'), matching the anchor for clear sequence with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

The SKILL.md is a clear overview that delegates detail one level deep to well-signaled references — sub-skill SKILL.md files, references/*.md knowledge bases, and scoring-system.md — without inlining walls of reference content. For an orchestrator agent, pointing to the sub-skills' bundles rather than duplicating them is appropriate, well-organized navigation matching the top anchor.

5 / 5

Total

19

/

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.

The description is exemplary: it states concrete capabilities with named tools and quantitative thresholds, gives explicit 'Use when' trigger guidance with realistic examples, and carves out a distinct acquisition-funnel niche. It is concise despite its density and uses correct third-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'comparing channel CAC against B2B SaaS benchmarks before reallocating a $40k/month budget', 'scoring paid-ads account health with ad_health_scorer.py', 'designing a nurture sequence that must score 70+ on sequence_analyzer.py' — with specific tools and thresholds, plus a coverage clause naming channel mix, CAC/ROAS math, MQL→SQL workflows, attribution, and nurture design. This matches the comprehensive-coverage anchor rather than the 'several actions, minor gaps' anchor below it.

5 / 5

Completeness

Explicitly answers both 'what' ('orchestrating the marketing-demand-acquisition, paid-ads, and email-sequence skills'; 'Covers channel mix, CAC/ROAS math, MQL→SQL workflows, attribution, and nurture design') and 'when' ('Use when building or fixing the acquisition engine — e.g., ...') with concrete trigger phrases, hitting the top anchor rather than the 'when could be more specific' level below.

5 / 5

Trigger Term Quality

Covers natural phrases a marketer would say ('building or fixing the acquisition engine', 'scaling spend', 'nurture sequence', 'channel CAC') with synonyms (CAC/ROAS, paid-ads/account health, nurture) and file-extension-style references (ad_health_scorer.py, sequence_analyzer.py), matching the comprehensive-synonyms-and-extensions anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — the acquisition funnel — and names the exact sub-skills it orchestrates, so it is unlikely to trigger for adjacent skills (analytics, content, cold-email). Voice is third person ('orchestrating', 'Covers') with no first/second person, so no specificity penalty applies.

5 / 5

Total

20

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 6 missing, 8 suspicious

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.