CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-research

Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or build custom language/messaging from buyer, competitor, community, and CRM evidence. Triggers: pre-research, source discovery, provider strategy, research data sources, ScrapeCreators, X/Twitter data, Reddit comments, public and private datasets, CRM data, workflow data, custom language, messaging language, pain language.

Quality

90%

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

81%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 highly actionable, well-sequenced operational skill body with strong validation gates and a verified one-level-deep reference bundle. Its main weakness is token efficiency: the artifact-resolution mandate and report-format rules are repeated across multiple sections, and the full report template could live in a reference file.

Suggestions

State the artifact-resolution requirement once (in §4.55) and reference it from Non-Negotiables, §3, and Finish Criteria instead of restating the five required fields in each place.

Move the ~75-line §7 report template to a reference file (e.g. references/report-template.md) and keep only the section skeleton and cleanup rules inline.

Add the missing THIRD_PARTY_NOTICES.md to the bundle or remove the instruction to keep it with the skill when packaging.

DimensionReasoningScore

Conciseness

The body is dense with Deepline-specific operational knowledge Claude would not know, but the artifact-resolution rule is stated four times (Non-Negotiables, §3's "record why it matters; the exact artifact", §4.55, and Finish Criteria) and the §7 report template runs roughly 75 lines inline. This fits anchor 3 (mostly efficient but some unnecessary repetition that could be tightened) better than anchor 4's "minor instances".

3 / 5

Actionability

Guidance is fully executable throughout: concrete `deepline search "topic -> recent web and news sources" --categories research` examples, complete curl calls to the planning endpoint with headers and payload, a copy-paste SKILL_ROOT resolution loop plus `python3 "$SKILL_ROOT/scripts/query_design.py" "$OBJECTIVE" --depth default`, and `--dry-run` price checks before paid probes. This matches anchor 5 (copy-paste ready commands covering common cases).

5 / 5

Workflow Clarity

The Standard Flow is clearly sequenced (1–7 with explicit gates §4.25, §4.5, §4.55, §4.6), includes validation checkpoints (standalone billing check first, describe-before-pricing, coverage gate over every source family, approval gate with exact question before any full paid run) and an error-recovery feedback loop ("A cell filled from memory instead of a live result is not verified. Search for it."). This matches anchor 5's explicit validation and feedback loops.

5 / 5

Progressive Disclosure

The "Start Here" section clearly signals four real one-level-deep references (source-map.md, last30days-gtm-corpus.md, query-design.md, fanout-consolidation.md, all verified present with substantial content) and three real scripts. Minor gaps keep it at anchor 4 rather than 5: THIRD_PARTY_NOTICES.md is referenced in the Attribution section but absent from the bundle, and the long §7 report template is inlined in SKILL.md rather than split out.

4 / 5

Total

17

/

20

Passed

Description

96%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 description: concrete multi-action capability statement, an explicit "Use when" clause, and a rich natural-language trigger list. The only weakness is mild overlap risk with sibling GTM/personalization skills via broad trigger terms like "CRM data" and "messaging language".

DimensionReasoningScore

Specificity

The description lists five concrete actions across named data domains ("discover the critical public, private, CRM, workflow, social, and web data sources", "compare provider coverage", "estimate Deepline credit cost", "recommend the source plan", "build custom language/messaging"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It explicitly answers both "what" (discover sources, compare coverage, estimate cost, recommend plan, build messaging) and "when" ("Use when the user wants a last30days-style pre-research pass in Deepline" plus a dedicated "Triggers:" list with concrete phrases), exactly matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

The explicit trigger list covers 14 natural terms with synonyms and variations ("pre-research, source discovery, provider strategy, ScrapeCreators, X/Twitter data, Reddit comments, public and private datasets, CRM data, workflow data, custom language, messaging language, pain language"), which a user needing this skill would plausibly say. It is above the 4 anchor because common variations and community phrasings are included, not just a few keywords.

5 / 5

Distinctiveness Conflict Risk

The Deepline pre-research framing ("last30days-style pre-research pass", "recommend the source plan before building or running the workflow") carves a clear niche, but broad triggers like "CRM data", "custom language", and "messaging language" overlap with closely related GTM/personalization skills. This fits anchor 4 (mostly distinct, minor overlap risk with closely related skills) rather than 5 (minimal conflict risk).

4 / 5

Total

19

/

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-research/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.