Loading...
Loading...
Found 440 Skills
Build enriched prospect lists from ICP criteria - find targets, enrich contacts, score accounts, detect trigger signals
Build and configure the GTM tech stack - tool selection, integrations, and data flows that power prospecting, outbound, and analytics
Comprehensive analytics audit of website codebase to identify trackable elements and assess analytics readiness. Use when users want to "audit my analytics", "scan for trackable elements", "find what I can track", "analyze my website for tracking opportunities", or before implementing GTM tracking. Scans HTML/JSX/TSX/Vue for all clickable elements (buttons, links, forms, etc.), identifies existing tracking code, evaluates DOM structure for analytics, and provides recommendations. Acts as senior frontend engineer with GA4 expertise.
Use when planning or drafting search-optimized content that balances keyword intent with GTM messaging.
Promote a quick-and-dirty prototype to an lgtm-hq-standard repo - commit WIP lint-clean, grill the design, spec the backlog as milestone/epic/issue tree, then implement issue by issue. Use when asked to properize, productionize, or turn a prototype into a proper project.
Audit the OpenSSF Scorecard rating for py-lintro. Use when asked to check the scorecard, understand the rating, or find what's missing. Specific to github.com/lgtm-hq/py-lintro.
Comprehensive market research and analysis skill. Use when sizing markets, conducting competitive analysis, generating professional market research reports, analyzing consumer behavior, or identifying market opportunities. Activates for: market research, market analysis, market report, TAM SAM SOM, market sizing, industry analysis, market landscape, competitive landscape, market trends, consumer research, Porter's Five Forces, PESTLE, SWOT, BCG Matrix, McKinsey-style report, consulting report, market opportunity, industry report, due diligence, M&A analysis, GTM market analysis, product-market fit validation.
Before showing the founder any substantive GTM deliverable (positioning, value prop, homepage, launch post, pricing, sales script, the brief or roadmap), stress-test it against the standard as an independent critic, because the agent that wrote it is the worst judge of whether it is good. Use as a gate right before presenting work, or when the founder asks whether something is actually strong.
Interview the founder once and write a docs/gtm-cofounder/founder-brief.md that every other skill reads first, so the advice is about their real business, not a textbook. Use this before anything else, or whenever the agent lacks context on the founder's product, ICP, market, or stage, or is giving generic GTM advice.
After the founder brief, turn it into an honest diagnosis and a prioritized, stage-aware GTM roadmap saved as docs/gtm-cofounder/gtm-roadmap.md. This is the hub the founder returns to every session to see where they are and the single next move. Use right after start-here, whenever the founder doesn't know what to work on next, wants a plan instead of a one-off task, or is drowning in disconnected tactics.
Refresh the founder's competitive and market context. Re-scan named rivals and the category for what changed since the brief was written (rebrands, repositioning, new entrants, pricing shifts, renamed categories) and update docs/gtm-cofounder/founder-brief.md and the roadmap with anything that moves positioning. Use on a cadence, or whenever a competitor rebrands, a new tool appears, or the founder senses the market has shifted under them.
Turn developer love into revenue by enabling champions and choosing a GTM model. Use when developers adopt the free tier but nobody pays, when the founder is cold-selling the VP instead of arming the developer, or when picking between open-source, PLG, inbound, and sales-led.