deepline-gtm

GTM prospecting, enrichment, outreach, and plays. Discovery: deepline-pre-research. Providers: adyntel,affinity,ai_ark,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bloomberry,bluesky,bounceban,browserbase,builtwith,clickhouse,cloudflare,contactout,contextdev,crustdata-v3,customer_db,dataforseo,datagma,deepline_ip_to_company,deepline_native,deeplineagent,discolike,dropleads,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,generic_http,gong,google_ads_audiences,google_workspace,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kernel,leadmagic,lemlist,limadata,linkedin_ads_audiences,linkedin_scraper,lusha,meta_audiences,nooks,openmart,opensosdata,openwebninja,outreach,parallel,peopledatalabs,podscan,predictleads,prospeo,quickenrich,redshift,rocketreach,salesforce,salesforge,scrapecreators,sentrion,serper,slack,smartlead,snowflake,sumble,theirstack,trestle,twitterapi,upcell,versium,wiza,zerobounce.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/deepline-gtm/SKILL.md

Quality

Content

65%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 highly actionable with clearly sequenced workflows and explicit validation gates, but it is verbose with repetitive justification and its progressive-disclosure structure is undermined because every linked sub-doc and provider playbook is missing from the bundle.

Suggestions

Trim repeated rationale and ALL-CAPS emphasis (e.g. the 'important' line, restated 'single most common failure mode' phrases) to tighten conciseness.

Ship the referenced Level 2/2.5 docs and provider-playbooks so the routing table and provider-link wall resolve to real files.

Move the 80+ provider-playbook inline link wall out of SKILL.md into an index file so the overview stays navigable.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose (430+ lines) with repeated imperatives, restated rationales ('This has happened repeatedly', 'The single most common failure mode'), and an ALL-CAPS 'important' line that pad without adding novel guidance; it explains behavior Claude could infer from the commands themselves.	2 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (Quick Start install block, 'deepline plays run ... --input', billing commands, approval template, grep recipe-discovery command) with concrete examples covering the common cases.	5 / 5
Workflow Clarity	Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops: the iterate loop (pilot -> price -> fix -> scale), the mandatory pilot-before-approval gate, the AWAIT_APPROVAL/FULL_RUN state contract, and 'validate -> fix -> re-run' for batch operations.	5 / 5
Progressive Disclosure	Structure and one-level-deep links are present (doc hierarchy, routing table, recipe table), but every referenced target file (finding-companies-and-contacts.md, enriching-and-researching.md, recipes/.md, provider-playbooks/.md) is absent from the bundle, so the navigation points to nothing and a large provider-link wall is inlined in SKILL.md.	3 / 5
	Total	15 / 20 Passed

Description

56%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 states a clear domain and surfaces useful trigger vocabulary, but it lacks an explicit 'Use when...' trigger clause and pads the field with an enormous provider list instead of concrete capabilities. Completeness is capped by the missing trigger guidance.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when building lead lists, enriching contacts, writing cold outreach, or running GTM plays').

Replace or compress the 100+ provider enum with 2-3 concrete capability actions to lift specificity.

Trim the raw provider list from the description into a separate reference so the field reads as a capability summary, not a manifest.

Dimension	Reasoning	Score
Specificity	The description names the domain ('GTM prospecting, enrichment, outreach, and plays') plus a discovery pointer, but the actions are high-level categories rather than concrete operations, and the bulk of the text is a 100+ provider list rather than capability detail.	3 / 5
Completeness	It gives a clear 'what' (prospecting/enrichment/outreach/plays) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It surfaces natural GTM vocabulary users would say ('prospecting', 'enrichment', 'outreach', 'plays') with reasonable synonym coverage, though it lacks common phrasings like 'lead list' or 'cold email' and is not exhaustive.	4 / 5
Distinctiveness Conflict Risk	The Deepline GTM framing plus the provider list carves a fairly distinct niche with low overlap risk against generic skills, though 'enrichment' and 'outreach' could collide with sibling deepline skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 110 missing	Warning

	Total	15 / 16 Passed

Repository: getaero-io/gtm-eng-skills
Path: skills/deepline-gtm/SKILL.md
Commit: 869569c

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.