CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-scoring

Use when discovering niche signals, auditing ICP or won/lost evidence, rescoring accounts, or building account and lead scoring Plays. Triggers on fit scoring, engagement scoring, backtesting, holdout evaluation, predictive lift, external proxies, and scoring leakage. Skip pure outreach copy or contributor skill installation tasks.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 exceptionally lean and rigorous skill body: executable commands with exact flags, precise input schemas, and a nine-step workflow with explicit freezing, quality-gate, and holdout checkpoints. The only structural weakness is minor bundle hygiene — one orphaned reference file, some dense inline input-format material, and unpathed cross-skill references.

DimensionReasoningScore

Conciseness

The body is densely packed with non-obvious domain constraints ("Reviews are not calls, openings are not hires", "The miner... does not understand negation or generate synonyms") and teaches nothing Claude already knows; every line carries skill-specific rules, matching the lean anchor 5.

5 / 5

Actionability

Provides copy-paste-ready commands with real flags ("python3 scripts/analyze_signals_v2.py --input accounts.csv --discover-phrases --max-phrases 500"), exact CSV schemas ("domain,status,website,jobs"), manifest fields ("analyzer_sha256", "config_sha256"), and JSON payload shapes, covering the common cases per anchor 5.

5 / 5

Workflow Clarity

The 9-step workflow is clearly sequenced with explicit validation checkpoints for batch operations ("Pilot one or two rows and pass the quality gate... before scaling", "Freeze extraction rules, aliases, model and reference artifacts before validation", "preserve an untouched holdout"), satisfying the feedback-loop requirements of anchor 5.

5 / 5

Progressive Disclosure

The task-to-reference routing table is excellent and all 19 referenced files exist one level deep, but references/pitfalls.md is an unreferenced orphan in the bundle, the CSV-format and source-adapter payload sections inline dense operational detail, and "deepline-gtm"/"deepline-plays" are named without paths, placing this just below anchor 5.

4 / 5

Total

19

/

20

Passed

Description

78%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, trigger-rich description with an explicit use/skip boundary and a well-defined niche. Its main weakness is that the capability list stays abstract and jargon-heavy, so a user unfamiliar with terms like ICP or Plays may not immediately grasp what the skill concretely produces.

Suggestions

Add one concrete deliverable statement (e.g., produces feature matrices, scorecards, backtest reports, and runnable scoring Plays) so the 'what' is explicit rather than implied by domain jargon.

Broaden trigger coverage with common user phrasings such as 'win/loss analysis', 'account/lead propensity', and 'score my accounts' to complement the existing technical terms.

Spell out at least one acronym or jargon term (e.g., ICP) inline so the description remains parseable to users outside the GTM domain.

DimensionReasoningScore

Specificity

Lists several specific in-domain actions ("discovering niche signals, auditing ICP or won/lost evidence, rescoring accounts, or building account and lead scoring Plays") but keeps them at an abstract activity level without naming concrete deliverables, matching anchor 4 rather than the comprehensive concreteness of 5.

4 / 5

Completeness

The "when" is explicit and well-developed ("Use when...", "Triggers on...", "Skip..."), and the "what" is present via the activity list, but the what-side relies on jargon and never states concrete outputs, fitting anchor 4 rather than the fully explicit anchor 5.

4 / 5

Trigger Term Quality

"Triggers on fit scoring, engagement scoring, backtesting, holdout evaluation, predictive lift, external proxies, and scoring leakage" gives good natural keyword coverage, though common user variations like "win/loss analysis", "propensity", or "score my accounts" are missing, so it stops short of the synonym-complete anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Skip pure outreach copy or contributor skill installation tasks" explicitly disambiguates adjacent skills, and niche triggers like "holdout evaluation" and "scoring leakage" define a clear, low-conflict trigger surface matching anchor 5.

5 / 5

Total

17

/

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

getaero-io/gtm-eng-skills

Path

skills/deepline-scoring/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.