SKILLEMALL.ai
GitHub ↗ RU Sign in

CD deepline-gtm

GTM leads, enrichment, outreach, Plays, developer signals/Reo.dev. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,buyercaddy,cbinsights,clay,clickhouse,cloudflare,contactout,contextdev,crunchbase,crustdata-v3,customer_db,databricks,dataforseo,datagma,dealroom,deepline_ip_to_company,deepline_native,deeplineagent,deepseek,discolike,dnb,edges,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,fundable,generic_http,getleads,gong,google_ads_audiences,google_workspace,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,kickbox,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meerapi,meta_audiences,millionverifier,nooks,notion,openmart,opensosdata,openwebninja,outreach,parallel,particle,peopledatalabs,pitchbook,podscan,polymarket,postgres,predictleads,prospeo,quickenrich,rapidapi,….

getaero-io/gtm-eng-skills Agent Skills author: getaero-io MIT 80 files · 1 script body ≈ 3 579 tokens Open the sourcegithub.com↗ analyzed 2 d ago

GTM leads, enrichment, outreach, Plays, developer signals/Reo.dev. Providers…

As a process D 35/100 · Unfinished process — References files that are not bundled: recipes/developer-signals.md, writing-outreach.md, recipes/account-orgchart.md

ProcedureNotionPostgreSQLGoogle CloudCloudflareSales and CRMtype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
57
Run on models
none yet
Process rating
D
35/100
Unfinished process
References files that are not bundled: recipes/developer-signals.md, writing-outreach.md, recipes/account-orgchart.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: recipes/developer-signals.md
  • warning missing-ref reference to a missing file: writing-outreach.md
  • warning missing-ref reference to a missing file: recipes/account-orgchart.md
  • warning missing-ref reference to a missing file: recipes/build-tam.md
  • warning missing-ref reference to a missing file: recipes/clay-to-deepline.md
  • warning missing-ref reference to a missing file: recipes/deepline-monitors.md
  • warning missing-ref reference to a missing file: recipes/find-qualified-titles.md
  • warning missing-ref reference to a missing file: recipes/portfolio-prospecting.md
  • warning missing-ref reference to a missing file: recipes/small-business-prospecting.md

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: recipes/developer-signals.md, writing-outreach.md, recipes/account-orgchart.md
  • 0Tools and files. 9 referenced file(s) missing: recipes/developer-signals.md, writing-outreach.md, recipes/account-orgchart.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 85Steps. 27 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3579 tokens
  • low The response is described with custom markup (5 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 1014: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 27 items
  • +4Has examples (6 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.