deepline-gtm

GTM prospecting, enrichment, outreach, and Deepline Play work/audits. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,browserbase,builtwith,clay,clickhouse,cloudflare,contactout,contextdev,crustdata-v3,customer_db,databricks,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,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,leadmagic,lemlist,limadata,linkedin_ads_audiences,linkedin_scraper,lusha,meta_audiences,nooks,openmart,opensosdata,openwebninja,outreach,parallel,peopledatalabs,podscan,postgres,predictleads,prospeo,quickenrich,redshift,rocketreach,salesforce,salesforge,salesloft,scrapecreators,searchbug,sec_edgar,sentrion,serper,slack,smartlead,snowflake,socrata,sumble,….

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

66%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 content is a well-sequenced, validation-rich meta-skill with strong executable guidance, but it is held back by verbosity and a serious progressive-disclosure failure: its routing tables point to files absent from the bundle while the real bundle files go unreferenced.

Suggestions

Make referenced paths match the bundle: either ship recipes/, provider-playbooks/, finding-companies-and-contacts.md, enriching-and-researching.md, writing-outreach.md, or repoint routing to the existing references/ and scripts/ files.

Consolidate the repeated bare-command and preflight/env-var rules into one stated-once block to trim restated padding.

Collapse the giant provider-playbook link wall into a pointer to a single index file rather than an inline dump of ~100 links.

Dimension	Reasoning	Score
Conciseness	Mostly assumes Claude's competence with no basic-concept padding, but several rules are restated (bare-command, preflight env-var) and the provider-playbook line is a dense wall of links that pads the body.	3 / 5
Actionability	Abundant copy-paste-ready commands (plays run/export, billing, csv show) cover common cases, though several 'execute this' routings point to referenced files that do not exist in the bundle.	4 / 5
Workflow Clarity	Clear sequenced workflows with explicit validation checkpoints and feedback loops for batch/paid operations (pilot -> price -> fix -> scale, 'Only when valid' gating, strict approval gate).	5 / 5
Progressive Disclosure	The body is structured as an overview pointing one level deep to recipes/, provider-playbooks/, and sub-docs, but none of those referenced files exist; the actual references/ and scripts/ files are unreferenced, so navigation is broken and orphaned.	2 / 5
	Total	14 / 20 Passed

Description

53%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 Deepline-specific GTM niche but relies on domain labels and provider jargon instead of concrete actions or natural trigger phrases. It lacks a 'Use when...' clause, capping completeness at 3.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases (e.g., 'Use when building lead lists, finding emails/LinkedIn profiles, enriching a CSV, writing cold outreach, or auditing Deepline plays').

Replace domain labels with concrete actions (e.g., 'find contacts at target companies', 'run email/phone waterfalls', 'write and sequence cold emails').

Trim the giant provider list or move it to a reference; keep 2-3 natural keywords the user would actually say.

Dimension	Reasoning	Score
Specificity	It names the domain ("GTM prospecting, enrichment, outreach, and Deepline Play work/audits") and a long provider list, but describes activity labels rather than concrete actions like 'find contacts' or 'enrich a CSV'; sits just above minimal-generic.	3 / 5
Completeness	The "what" is clear (GTM prospecting/enrichment/outreach/Play work), but there is no "Use when..." trigger clause, so per the rubric 'when' is missing and completeness caps at 3.	3 / 5
Trigger Term Quality	"GTM prospecting, enrichment, outreach" are somewhat natural, but the bulk is provider-name jargon and common variations ("lead gen", "cold email", "find emails") and file extensions are missing.	3 / 5
Distinctiveness Conflict Risk	The Deepline-specific framing ("Deepline Play work/audits") plus an explicit provider list carves a clear niche with minimal overlap risk against generic skills.	4 / 5
	Total	13 / 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: 120 missing	Warning

	Total	15 / 16 Passed

Repository: getaero-io/gtm-eng-skills
Path: skills/deepline-gtm/SKILL.md
Commit: 3bb8968

Reviewed: 3 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.