CtrlK
BlogDocsLog inGet started
Tessl Logo

deepline-gtm

Use for GTM prospecting, enrichment, qualification, CSV processing, lead/account/contact research, public/social pre-research, waterfall enrichment, email/LinkedIn lookup, personalization, scoring, campaigns, and custom Deepline plays/scripts. Providers: adyntel, ai_ark, allegrow, apify, attio, aviato, bettercontact, bloomberry, bluesky, builtwith, cloudflare, contactout, crustdata, crustdata-v2, crustdata-v3, customer_db, dataforseo, datagma, deepline_native, deeplineagent, discolike, dropleads, emailbison, enformion, exa, findymail, firecrawl, forager, fullenrich, generic_http, google_ads_audiences, hackernews, heyreach, hubspot, hunter, icypeas, instantly, ipqs, leadmagic, lemlist, limadata, linkedin_ads_audiences, linkedin_scraper, lusha, meta_audiences, openmart, opensosdata, openwebninja, parallel, peopledatalabs, predictleads, prospeo, rocketreach, salesforce, scrapecreators, serper, slack, smartlead, snowflake, tamradar, theirstack, trestle, twitterapi, upcell, wiza, wizleads, zerobounce.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 routing skill with strong workflow gates, weakened mainly by motivational verbosity and by routing-table links that point to bundle files absent from this package. The lowest dimensions are conciseness and progressive_disclosure.

Suggestions

Trim the hortatory/rationale passages in Section 2 ("STOP", "This is not optional", "distilled from hundreds of real runs...") to short imperatives; Claude already understands why reading docs helps.

Either include the referenced files (finding-companies-and-contacts.md, enriching-and-researching.md, writing-outreach.md, prompts.json, recipes/*.md, provider-playbooks/*.md) or relink the routing table to the files that do exist under references/ and scripts/.

DimensionReasoningScore

Conciseness

The bulk is lean operational guidance (commands, tables, checklists), but several passages over-explain rationale Claude already grasps — e.g. "distilled from hundreds of real runs... reading a doc for 5 seconds saves you from 10 failed tool calls" and repeated hortatory "STOP / This is not optional" blocks that could be trimmed.

2 / 3

Actionability

Throughout it gives concrete, copy-paste-ready commands with flags — `deepline csv show --csv <path> --summary`, `deepline enrich --rows 0:1`, `deepline billing balance`, plus a full approval message template and working-directory setup.

3 / 3

Workflow Clarity

Clear sequence with explicit checkpoints: one-row pilot, a strict four-section approval gate with AWAIT_APPROVAL/FULL_RUN states, a feedback loop (pilot fails -> fix and re-run), then full run, final file/playground check, and end-of-session consent.

3 / 3

Progressive Disclosure

The documentation hierarchy and task->doc routing table are well signaled and mostly one level deep, but the referenced files (finding-companies-and-contacts.md, enriching-and-researching.md, writing-outreach.md, prompts.json, recipes/, provider-playbooks/) are not present in this bundle — only references/ and scripts/ exist and go unreferenced — so navigation points to a structure that isn't there.

2 / 3

Total

10

/

12

Passed

Description

100%

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 dense, trigger-first description that clearly names both capabilities and a use-for clause, anchored to a distinct provider-specific niche. It fully satisfies all four dimensions.

DimensionReasoningScore

Specificity

Quotes many specific concrete actions — "prospecting, enrichment, qualification, CSV processing, lead/account/contact research, public/social pre-research, waterfall enrichment, email/LinkedIn lookup, personalization, scoring, campaigns, and custom Deepline plays/scripts" — going well beyond naming a domain.

3 / 3

Completeness

The explicit "Use for ..." clause answers both what (the action list) and when (the trigger), matching the anchor that requires explicit triggers; it is not merely implied.

3 / 3

Trigger Term Quality

Leads with natural GTM vocabulary users would say (prospecting, enrichment, lead/account/contact research, personalization, scoring, campaigns) before the technical provider list.

3 / 3

Distinctiveness Conflict Risk

The Deepline-specific branding plus a named provider list pins it to a clear niche, making it unlikely to fire for a generic or competing skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 82 missing

Warning

Total

15

/

16

Passed

Repository
getaero-io/gtm-eng-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.