CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gtm-metrics

Defining GTM metrics, pipeline efficiency, AI cost metrics, TTFV, CAC/LTV/NRR, magic number, attribution models, weekly review cadence.

Quality

65%

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 ./skills/gtm-metrics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 high-signal reference skill: nearly every table carries specific formulas, 2025 benchmarks, and actionable thresholds Claude would not reliably know. Its weaknesses are structural — a monolithic 400+ line file with no progressive disclosure, a duplicated quick-reference section, a promotional footer, and no explicit end-to-end workflow tying the nine sections together.

Suggestions

Move the stage benchmark tables (NRR by ARR band, growth rate benchmarks, attribution model comparison, funnel rates) into references/ files (e.g. references/benchmarks.md, references/attribution.md) and keep SKILL.md as an overview that links to them, cutting context cost for casual invocations.

Remove the duplicated Quick Reference table (it restates ~20 facts already in sections 1-9) and the promotional "About this skill" footer, which spends tokens on marketing rather than guidance.

Add an explicit step sequence with validation gates, e.g. 1) Gather "Before Starting" context, 2) Run the data health audit and only proceed above 70%, 3) Select tier-appropriate metrics, 4) Stand up the dashboard, 5) Institute the weekly review — so the nine sections read as one workflow rather than parallel references.

DimensionReasoningScore

Conciseness

The bulk is dense, non-obvious reference data (2025 benchmarks, formulas, targets) that earns its tokens, but the ~20-row Quick Reference table restates facts already given verbatim in sections 1-9, the persona opener is padded ("You are an expert in... You know that..."), and the "About this skill" section is a purely promotional footer with marketing links and UTM parameters. Mostly efficient but needs tightening, matching anchor 3 rather than anchor 4.

3 / 5

Actionability

Concrete, executable guidance throughout: exact scoring formulas ("Data Health Score = (Completeness * 0.35) + (Accuracy * 0.30) + (Recency * 0.20) + (Consistency * 0.15)"), numeric thresholds ("<8 months" payback, "<5 min" speed-to-lead), a minute-by-minute weekly meeting agenda, and PQL tiers with routing actions. Falls short of anchor 5 only because metric-instrumentation and dashboard-build steps are described rather than given as runnable procedures.

4 / 5

Workflow Clarity

"Before Starting" provides a context-gathering entry sequence and the Data Health grade table acts as an implicit gate ("Below 70% | F | Stop trusting pipeline reports"), but there is no explicit end-to-end sequence (gather context -> build framework -> instrument -> review) with validate-then-proceed checkpoints connecting the nine sections. Sequence is present while checkpoints remain implicit, matching anchor 3.

3 / 5

Progressive Disclosure

Section headers, numbered sections, and a quick-reference table give genuinely good navigation, but this is a 400+ line monolith with no bundle files at all: the stage-by-stage benchmark tables (NRR by ARR band, growth rates, attribution model comparison) are exactly the material that belongs in references/ files loaded on demand. Good structure with inline content that should be separate matches anchor 3; it is above anchor 2's "minimal structure" but below anchor 4's "most content appropriately placed".

3 / 5

Total

13

/

20

Passed

Description

57%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 names a clear, well-scoped domain with strong natural keywords, but it is a topic list rather than an action list and contains no trigger guidance for when to invoke it. Adding a "Use when..." clause and verb-driven capabilities would raise both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when building GTM dashboards, benchmarking CAC/NRR/magic number, choosing an attribution model, or setting up a weekly metrics review."

Convert topic nouns into concrete actions: replace "pipeline efficiency, AI cost metrics, TTFV" with verb phrases like "Calculate CAC payback and magic number, benchmark NRR by ARR stage, measure AI cost of revenue".

Sharpen distinctiveness against sibling skills in the same collection by foregrounding what only this skill does (cross-metric dashboards, benchmarks by stage, data health scoring) rather than shared topics like NRR or attribution.

DimensionReasoningScore

Specificity

Only one action verb appears ("Defining GTM metrics"); the remainder are topic nouns ("pipeline efficiency, AI cost metrics, TTFV, CAC/LTV/NRR, magic number"). The domain and deliverables are concretely enumerated (above anchor 2's generic actions) but it lists topics rather than several specific actions, so it falls short of anchor 4.

3 / 5

Completeness

The "what" is clear (defining metrics, attribution models, review cadence) but there is no "Use when..." clause or any equivalent trigger guidance, capping completeness at anchor 3. It is above anchor 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

Natural phrases the target user would say include "GTM metrics", "CAC", "LTV", "NRR", "magic number", "attribution models", and "weekly review cadence". Coverage is good but misses common variations like "KPIs", "dashboard", or "SaaS metrics", so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

GTM measurement is a recognizable niche, but the skill's own Related Skills table shows heavy overlap within its family (expansion-retention also covers NRR, content-to-pipeline also covers attribution, solo-founder-gtm also covers metric prioritization). It is somewhat specific but could still trigger for the wrong sibling skill, matching anchor 3 rather than anchor 4's "minor overlap risk".

3 / 5

Total

13

/

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

Synter-Media-AI/free-skills

Path

skills/gtm-metrics/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.