Skip to content
Back to search

gtm-coding-agent

Build your go-to-market engine with coding agents instead of a $2K/mo tool stack. 21 chapters, nine forkable starters, four installable skills, GTM-OS skeleton, and Python scripts. Includes the Clearbox Reddit buyer-signal engine: find buyers without getting banned.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/shawnla90/gtm-coding-agent with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/shawnla90/gtm-coding-agent'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/shawnla90--gtm-coding-agent/badge.svg)](/listings/shawnla90--gtm-coding-agent)

HTML

<a href="/listings/shawnla90--gtm-coding-agent"><img src="/api/listings/shawnla90--gtm-coding-agent/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

# 1. Clone the repo
git clone https://github.com/shawnla90/gtm-coding-agent.git
cd gtm-coding-agent

# 2. Open in Claude Code
claude

# 3. Type this
> help me set up

Claude reads the CLAUDE.md, asks you 6 questions about your GTM, then: - Recommends whether to start with Cursor or Claude Code - Picks your mode (solo founder, agency, etc.) - Builds your folder structure - Copies the right templates - Gives you a 3-5 chapter learning path

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 343 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # GTM Coding Agent Starter Kit
  2. **Build your go-to-market engine with coding agents, Python scripts, and structured context.**
  3. Open this repo in [Claude Code](https://claude.ai/code) and type `help me set up`. The AI walks you through building a personalized GTM workspace — ICP, positioning, outbound sequences, content, automation — all from your terminal.
  4. Structured context + coding agents + Python scripts. Build alongside the tools you already use.
  5. ---
  6. ## New: build the Reddit client pack end to end
  7. <p align="center"><a href="https://github.com/shawnla90/ClearboxGTM/releases/latest"><img src="https://raw.githubusercontent.com/shawnla90/ClearboxGTM/main/assets/gallery/client-pack-tour.gif" alt="ClearboxGTM client value pack: API dispositions to eleven-view Sheet and guided Notion brief" width="100%"></a></p>
  8. Chapters 18 and 19 now teach the current contract: Clearbox owns the source disposition and exact Reddit permalink; Freckle, Base Loop, or Clay may add analysis; the client receives one eleven-view working Sheet and one guided Notion brief; and retrieval, observed AI appearance, exact citation, engagement, and business outcomes remain separate receipts.
  9. This repo carries the broader GTM curriculum and portable starter. The complete maintained Reddit-growth implementation lives in **[ClearboxGTM](https://github.com/shawnla90/ClearboxGTM)**. See the **[latest ClearboxGTM release](https://github.com/shawnla90/ClearboxGTM/releases/latest)** for the live synthetic Sheet and Notion demo, visual walkthrough, agency skill, multi-account guide, attribution scorecard, fixtures, and builder.
  10. ---
  11. ## Anatomy of This Repo
  12. ```
  13. gtm-coding-agent/
  14. │
  15. ├── CLAUDE.md # interactive onboarding ← START HERE
  16. ├── README.md # you are here
  17. │
  18. ├── chapters/ # 25 educational chapters
  19. │ ├── 01-coding-agents-vs-editors.md # agents vs cursor vs chatgpt
  20. │ ├── 02-context-engineering.md # CLAUDE.md, structured context
  21. │ ├── 03-token-efficiency.md # 200K context, cost, subagents
  22. │ ├── 04-oauth-cli-apis.md # 3 ways tools connect
  23. │ ├── 05-automation-agents.md # cron, n8n, trigger.dev
  24. │ ├── 06-local-first-gtm.md # your mac as a GTM server
  25. │ ├── 07-python-for-gtm.md # APIs, CSVs, enrichment
  26. │ ├── 08-tools-ecosystem.md # apollo, clay, exa, firecrawl
  27. │ ├── 09-voice-dna-content.md # voice extraction, anti-slop
  28. │ ├── 10-terminal-mastery.md # tmux, SSH, multiplexing
  29. │ ├── 11-build-your-dashboard.md # Next.js + Supabase signals dashboard
  30. │ ├── 12-competitive-intel-engine.md # SQLite-in-git + d3-force + Claude subprocess
  31. │ ├── 13-crm-automation-slash-commands.md # HubSpot + Salesforce + /stale-opportunities
  32. │ ├── 14-voice-invocation.md # transcript → voice-drift + content fan-out to Discord
  33. │ ├── 15-meta-ad-intelligence.md # Meta Ad Library scraper + Claude taxonomy + dashboard
  34. │ ├── 16-programmatic-landing-pages-hubspot-cms.md # HubSpot CMS Pages API + subagent columns
  35. │ ├── 17-client-onboarding-miro-boards.md # Miro onboarding boards + client docs package
  36. │ ├── 18-reddit-buyer-signals.md # Reddit buyer signals + GEO/competitor/content
  37. │ ├── 19-lead-unmasking-and-slack-digest.md # company-evidence gate + client packs + digest
  38. │ ├── 20-podcast-to-shorts.md # one recording → captioned vertical clip drafts
  39. │ ├── 21-student-gtm.md # campus network → public GTM track record
  40. │ ├── 22-headless-linkedin-outreach.md # self-hosted Playwright outreach + SQLite ledger
  41. │ ├── 23-reachability-grading.md # Moltsets A-F grades → route by grade → color-coded sheet, next to your verifier (+ the Apollo overlap, said plainly)
  42. │ ├── 24-enrichment-on-the-go.md # your own Prospeo key, from Claude Code or a Grok agent, verified mobiles
  43. │ └── 25-stream-deck-command-center.md # Stream Deck+ profile generated from Python: project keys, Claude Code keys, content kickoffs, MCP
  44. │
  45. ├── skills/ # installable Claude Code skills (Reddit, reachability, reply loop, re-find)
  46. │ ├── clearbox-onboard/ # domain → researched Clearbox offer pack + pastable prompt
  47. │ ├── reddit-onboard/ # personalized route through the public playbook → Notion
  48. │ ├── reddit-engage/ # value-first replies, approve-each-one human gate
  49. │ ├── reddit-agency/ # 11-view Sheet + guided brief + multi-account scorecard
  50. │ ├── reply-engine/ # gated ≤18-word reply templates + rules-pinned sheet tab
  51. │ ├── moltsets-reachability/ # grade every email A-F, route the bad ones, read it in a sheet (Ch 23)
  52. │ ├── instantly-hubspot-replies/ # log Instantly replies into HubSpot and reply from the sending mailbox (Ch 26-28)
  53. │ └── dead-address-refind/ # a retired mailbox is not a departure (Ch 29)
  54. │
  55. ├── starters/ # runnable starter folders (CLI + data)
  56. │ ├── apollo-prospecting/ # Apollo waterfall: 5 intent gates → color-coded sheet (v0.8.0)
  57. │ ├── instantly-hubspot-replies/ # reply-loop rules, webhook shape, HubSpot card (Ch 26-28)
  58. │ ├── moltsets-reachability/ # Moltsets employment check + A-F grade → route by grade → 11-tab sheet, delta vs your verifier (Ch 23)
  59. │ ├── reddit-buyer-signals/ # Reddit signals + GEO/competitor/unmask/digest (Ch 18-19)
  60. │ ├── hubspot-landing-engine/ # brief → subagent columns → HubSpot CMS DRAFT pages (Ch 16)
  61. │ ├── market-scoring-sheet/ # CSV → color-coded 1-5 scored Google Sheet
  62. │ ├── client-onboarding-miro/ # Miro board templates (Ch 17)
  63. │ ├── podcast-shorts/ # recording → word-timed captioned vertical drafts (Ch 20)
  64. │ ├── stream-deck-command-center/ # generated Stream Deck profile, project launchers, kickoffs (Ch 25)
  65. │ └── student-gtm/ # interview → your own build-in-public repo (Ch 21)
  66. │
  67. ├── engine/ # tool documentation (living, updated regularly)
  68. │ ├── apify.md # Apify CLI: scraping, actors, follower lists
  69. │ ├── apollo.md # Apollo: batch enrichment, job change detection
  70. │ ├── claude-subprocess.md # Claude CLI as a subprocess — batch analysis pattern
  71. │ ├── hubspot-cms.md # HubSpot CMS Pages API v3 + HubL templates
  72. │ └── _tool-template.md # template for adding new tools
  73. │
  74. ├── gtm-os/ # operational skeleton
  75. │ ├── CLAUDE.md # GTM-OS operating instructions
  76. │ ├── demand/ # ICP, positioning, competitors
  77. │ ├── messaging/ # attack angles, value props
  78. │ ├── segments/ # target account segments
  79. │ ├── engine/ # tool integrations + docs
  80. │ │ └── prompts/ # reusable AI prompts
  81. │ ├── campaigns/active/ # live campaign tracking
  82. │ ├── content/ # content pipeline
  83. │ ├── status.md # current GTM status
  84. │ └── log.md # decision log
  85. │
  86. ├── modes/ # persona-based starter configs
  87. │ ├── solo-founder.md # one person, full stack GTM
  88. │ ├── agency.md # multiple clients
  89. │ ├── single-client.md # GTM eng at one company
  90. │ └── abm-outbound.md # target account pipeline
  91. │
  92. ├── templates/ # reusable templates
  93. │ ├── claude-md/ # 3 CLAUDE.md variants
  94. │ ├── voice/ # voice DNA, anti-slop rules
  95. │ ├── content/ # blog, content drop, SEO brief
  96. │ └── partner/ # per-client folder structure
  97. │
  98. ├── examples/ # worked examples (anonymized)
  99. │ ├── voice-dna/ # filled-in voice profile
  100. │ ├── icp/ # example ICP for B2B SaaS
  101. │ ├── prompts/ # qualification, gap analysis
  102. │ └── scripts/ # Python enrichment patterns (prospeo_enrich.py, Ch 24)
  103. │
  104. ├── prompts/ # ready-to-use AI prompts
  105. │ ├── icp-builder.md # define ideal customer profile
  106. │ ├── positioning-workshop.md # positioning & differentiation
  107. │ ├── competitor-analysis.md # competitive landscape
  108. │ ├── signal-mapping.md # buying signals → actions
  109. │ ├── email-sequence.md # outbound email sequences
  110. │ └── content-repurpose.md # 1 piece → 5 formats
  111. │
  112. ├── starters/ # deployable starter projects
  113. │ ├── signals-dashboard/ # Next.js + Supabase signals dashboard (Chapter 11)
  114. │ │ ├── schema/ # SQL schemas + seed data
  115. │ │ ├── pipeline/ # Python signal scoring pipeline
  116. │ │ └── src/ # dashboard app (5 pages, dark theme)
  117. │ ├── nexus-intel/ # SQLite-in-git competitive intel engine (Chapter 12)
  118. │ │ ├── src/ # Next.js app with d3-force Nexus graph
  119. │ │ ├── scripts/ # Apify CLI scrapers + Claude subprocess analyzers
  120. │ │ └── data/ # SQLite schema, public seed, committed intel.db
  121. │ ├── crm-automation/ # HubSpot stale-opportunity engine (Chapter 13)
  122. │ │ ├── stale_opportunity_check.py # surface 60-day deals, re-enrich, write custom props
  123. │ │ ├── .claude/commands/ # /stale-opportunities slash command
  124. │ │ └── README.md # setup + HubSpot custom property schema
  125. │ └── instantly-hubspot-replies/ # reply-loop rules, webhook shape, HubSpot card (Ch 26-28)
  126. │
  127. └── social/ # launch content
  128. ├── reddit-post.md
  129. ├── linkedin-post.md
  130. └── carousel-slides.md
  131. ```
  132. ### Chapters 26 to 29
  133. Numbering starts at 26 so Chapter 25 can be the Stream Deck command center without colliding with Chapter 24 (Enrichment on the Go).
  134. | Chapter | File | You'll be able to |
  135. |---|---|---|
  136. | 26 - Cold Email Replies into the CRM | `chapters/26-replies-into-the-crm.md` | Log Instantly replies as HubSpot email engagements and open an unowned MQL deal only for an interested reply or the card's MQL button |
  137. | 27 - Going Live on the Reply Loop | `chapters/27-reply-loop-go-live.md` | Mint a service key and a personal access key without a seat, deploy the webhook and the cron, and prove 401 and 200 |
  138. | 28 - Reply from the Sending Mailbox | `chapters/28-reply-from-the-sending-mailbox.md` | Add a private HubSpot card that replies through Instantly from the campaign mailbox, and treat an empty thread as a 200 |
  139. | 29 - Dead Address versus Departed | `chapters/29-dead-address-versus-departed.md` | Treat a retired mailbox as a re-find, not a resignation, and swap the address only after a human yes |
  140. The production gotchas for that loop (campaign-name guard, `vercel env pull` placeholders, the User-Agent on `GET /api/v2/emails?lead=`, the legacy secondary-email PUT, workflow triggers, the blocklist) are the Build and Gotchas sections in `skills/instantly-hubspot-replies/SKILL.md`. A dead-address auto-reply that fills Instantly's reply status is `skills/dead-address-refind/SKILL.md`.
  141. ---
  142. ## How It All Connects
  143. | | |
  144. |---|---|
  145. | **Interactive Onboarding** | **Educational Chapters** |
  146. | `CLAUDE.md` asks 6 questions, then builds your workspace. Recommends tools, mode, and learning path — all personalized. | 25 chapters from "what is a coding agent" to a Stream Deck command center, including holding your own enrichment key and calling it from the terminal or a phone agent. Read in order or jump to what you need. |
  147. | **GTM-OS Skeleton** | **Modes** |
  148. | A working folder structure for ICP, positioning, segments, campaigns, and content. Fork it. Fill it in. Run GTM from it. | 5 personas: solo founder, agency, single-client, ABM outbound, student. Each mode configures the skeleton differently. |
  149. | **Templates** | **Prompts** |
  150. | CLAUDE.md variants, voice DNA, content formats, partner structures. Copy into your projects, fill in the blanks. | 6 battle-tested AI prompts for ICP building, positioning, competitor analysis, signal mapping, email sequences, and content repurposing. |
  151. | **Starter Projects** | |
  152. | Ten forkable starters. **Apollo prospecting** (v0.8.0) grows a seed list through five intent gates, deepest intent first, and ships a color-coded Google Sheet; searches are free, credits only on reveal. **Reddit buyer signals** (Ch 18-19) preserves Clearbox dispositions and exact permalinks, measures Exa retrieval without calling it an AI citation, and enriches only exact company domains self-disclosed on the author's Reddit profile; search, thread, and handle matches stay in manual review. **Signals dashboard** (Ch 11) is Next.js + Supabase with 5 operational pages. **Nexus Intel** (Ch 12) is a Clay-companion intel engine with SQLite-in-git, d3-force graph, Apify CLI scrapers, and Claude subprocess analysis. **CRM Automation** (Ch 13) re-enriches 60-day-old HubSpot deals and writes the verdict back as custom properties. **Podcast to Shorts** (Ch 20) turns one recording into captioned vertical clips staged as drafts, cut against a word-timestamped transcript. **Student GTM** (Ch 21) interviews a student and scaffolds their own repo, weekly recording loop, gotchas log, and campus client offer. **Instantly to HubSpot** (Ch 26-28) is the reply-loop rules module, the webhook and cron shape, and the card that replies from the sending mailbox. Deploy any of them in minutes. | |
  153. ---
  154. ## Read the Web Guide
  155. Prefer reading to forking? The full playbook is available as a book-style web guide:
  156. **[The GTM Coding Agent Playbook on shawnos.ai](https://shawnos.ai/guide/gtm-coding-agent)**
  157. 23 chapters, expanded with narrative, examples, and Shawn's perspective. The web version is for reading cover to cover. This repo is for forking and building.
  158. ---
  159. ## Powered by Clearbox
  160. 🟧 The Reddit buyer-signal engine in this kit (Chapters 18 and 19) runs on **Clearbox**. Clearbox reads what your market is actually asking across Reddit, classifies each thread by buying intent, and hands you the leads, the competitor mentions, and the conversations worth joining. The kit is the open-source how. Clearbox is the engine that makes it live.
  161. The full Reddit motion has its own repo: **[ClearboxGTM](https://github.com/shawnla90/ClearboxGTM)**. It contains the maintained buyer-signal engine, client-pack builder, Freckle/Base Loop/Clay analysis path, public agency skills, multi-account controls, evidence scorecard, generated proof, and the visual client delivery system you can hand to a client or run for your own.
  162. **See your market. Move first.** Start a 7-day free trial at **[clearbox.to](https://clearbox.to)**.
  163. ---
  164. ## See It In Action
  165. **Chapters 18–19 - Reddit client value pack:**
  166. [![ClearboxGTM client pack walkthrough](https://raw.githubusercontent.com/shawnla90/ClearboxGTM/main/assets/gallery/client-pack-tour-poster.png)](https://github.com/shawnla90/ClearboxGTM/releases/latest)
  167. *Clearbox API dispositions → optional Freckle, Base Loop, or Clay analysis → eleven-view Sheet → guided Notion brief. The demo uses synthetic fixtures.*
  168. **Chapter 11 - Signals Dashboard (Supabase + Recharts):**
  169. https://github.com/user-attachments/assets/295f3b1b-37e1-4686-8de3-9b2b9219c8cb
  170. *The signals dashboard running against a live Supabase database. 5 pages, dark theme, real-time polling.*
  171. **Chapter 12 - Nexus Intel (SQLite + d3-force, 2x speed):**
  172. ![Nexus Intel demo](https://raw.githubusercontent.com/shawnla90/gtm-coding-agent/main/assets/videos/nexus-intel-demo-2x.gif)
  173. *The competitive intel engine. Clone, seed, boot, see signals.*
  174. ---
  175. ## Quick Start
  176. ```bash
  177. # 1. Clone the repo
  178. git clone https://github.com/shawnla90/gtm-coding-agent.git
  179. cd gtm-coding-agent
  180. # 2. Open in Claude Code
  181. claude
  182. # 3. Type this
  183. > help me set up
  184. ```
  185. Claude reads the CLAUDE.md, asks you 6 questions about your GTM, then:
  186. - Recommends whether to start with Cursor or Claude Code
  187. - Picks your mode (solo founder, agency, etc.)
  188. - Builds your folder structure
  189. - Copies the right templates
  190. - Gives you a 3-5 chapter learning path
  191. ---
  192. ## Who This Is For
  193. **You should use this if:**
  194. - You're a founder, GTM engineer, or agency operator
  195. - You want to use coding agents (Claude Code, Cursor, Codex) for GTM — not just chat
  196. - You want to understand what's happening under the hood of your GTM stack
  197. - You want a system you can build on, not just configure
  198. **You probably don't need this if:**
  199. - You have a 50-person marketing team with established tooling
  200. - You're looking for a no-code solution
  201. - You want a pre-built product, not a learning system
  202. ---
  203. ## The Philosophy
  204. A GTM tool usually sells you a dashboard. This gives you a workspace.
  205. The difference: a workspace is files you control, prompts you can edit, scripts you can modify, and context an AI agent can read. When your ICP, positioning, voice, and tooling all live in structured markdown files, a coding agent becomes your GTM co-pilot.
  206. I still use HubSpot and Instantly. This is not about replacing tools. It's about understanding how things work and being able to build the pieces that don't exist yet. You'll learn how it works, then make it yours.
  207. ## This Is a Living Repo
  208. This repo gets updated with real workflows I'm actively using and stress testing. Apify CLI scraping patterns, Apollo batch enrichment, Instagram growth automation, terminal multiplexing setups. If it's in here, I've run it. If it broke, I documented how.
  209. New commits land regularly as I discover better patterns, new CLI tools ship, or existing workflows evolve. The `engine/` folder has detailed tool documentation (Apify, Apollo, and more coming) with working scripts you can run today.
  210. If you learn from this and want to help it grow, star it, fork it, open a PR. This is how we build a GTM coding agents community. Not through courses. Through shared systems that actually work.
  211. ## Get notified when new chapters drop
  212. New chapters and starters ship as tagged **[Releases](https://github.com/shawnla90/gtm-coding-agent/releases)**. Because everything here is code and version-controlled, each release is something you can fork and build on the same day. To catch them: **star** the repo (releases from repos you star surface in your GitHub home feed), and **Watch → Custom → Releases** for an email on each drop.
  213. ---
  214. ## What You'll Learn
  215. | Chapter | You'll Be Able To |
  216. |---------|-------------------|
  217. | 01 - Coding Agents vs Editors | Choose the right AI tool for your GTM workflow |
  218. | 02 - Context Engineering | Structure CLAUDE.md files that make agents 10x more useful |
  219. | 03 - Token Efficiency | Manage context windows without burning money |
  220. | 04 - OAuth, CLI, and APIs | Connect any GTM tool to your agent |
  221. | 05 - Automation Agents | Set up scripts that run your GTM on autopilot |
  222. | 06 - Local-First GTM | Turn your Mac into a GTM server |
  223. | 07 - Python for GTM | Write enrichment scripts, API calls, CSV pipelines |
  224. | 08 - Tools Ecosystem | Evaluate and integrate Apollo, Apify, Clay, Exa, Firecrawl |
  225. | 09 - Voice DNA & Content | Extract your voice, kill slop, create content that sounds like you |
  226. | 10 - Terminal Mastery | tmux, SSH, multiplexing for running multiple agent sessions |
  227. | 11 - Build Your Dashboard | Build and deploy a real-time GTM dashboard with Next.js, Supabase, and signal intelligence |
  228. | 12 - Competitive Intel Engine | Build a Clay-companion intel engine: SQLite-in-git, Apify CLI scrapers, Claude-as-subprocess analysis, d3-force Nexus graph |
  229. | 13 - CRM Automation & Slash Commands | Wire HubSpot and Salesforce to your agent, build `/stale-opportunities`, and mine the nurture graveyard AEs abandoned |
  230. | 14 - Voice-Invocation | Auto-run voice-drift on every meeting transcript, fan out content + signals to typed Discord channels for review |
  231. | 15 - Meta Ad Intelligence | Scrape the Meta Ad Library, classify creatives via Claude subprocess, pair declared strategy with demand signals |
  232. | 16 - Programmatic Landing Pages | Brief + subagent columns + HubSpot CMS Pages API v3. Personalized DRAFT landing pages, one command, controlled list |
  233. | 17 - Client Onboarding Miro Boards | Build a client-visible GTM engine map, docs package, and screenshot QA loop before kickoff |
  234. | 18 - Reddit Buyer Signals | Preserve classified buyer signals and exact permalinks, add Freckle/Base Loop/Clay analysis, build the eleven-view client pack, and measure each evidence level separately |
  235. | 19 - Company Evidence, Client Packs & Digest | Separate direct Reddit-profile disclosure from candidates and lookup errors, enrich only verified companies, then deliver stable client surfaces and the daily queue |
  236. | 20 - Podcast to Shorts | Turn one recording into captioned vertical clips staged as drafts, cut against a word-timestamped transcript |
  237. | 21 - Student GTM | Build a public go-to-market track record in one semester with no budget, no title, and the campus network you already have |
  238. | 22 - Headless LinkedIn Outreach | Run outreach from your own account with a Playwright sender, a SQLite ledger, and a read-only observer — and see why the connection note, not the follow-up, is the campaign |
  239. | 23 - Reachability Grading | Grade every address A-F with Moltsets, confirm the person is still there from the LinkedIn URL, and route the rows a suppress-only tool deletes: D to LinkedIn then phone, not-found to a second pass, all in a color-coded sheet. Lay the grades next to the verifier you already run (10,088 rows: 6,776 agreements, 819 corrected addresses, 793 job changes the verifier passed), with the Apollo overlap stated plainly |
  240. | 24 - Enrichment on the Go | Hold your own Prospeo key and call it from Claude Code or a Grok agent: verified email, verified mobile, search, then a cleared-to-call or email-only route |
  241. | 25 - Stream Deck Command Center | Generate a Stream Deck profile from Python, put each repo on a key that opens Claude Code with the right model, effort, and GitHub account, and run a draft, critique, render content pipeline with a human gate |
  242. ---
  243. ## Built With
  244. - [Claude Code](https://claude.ai/code) — AI coding agent (primary)
  245. - [Cursor](https://cursor.com) — AI code editor (recommended for beginners)
  246. - Python 3.10+ — scripting and automation
  247. - Markdown — everything is structured text
  248. - [Next.js](https://nextjs.org) + [React](https://react.dev) — dashboard starters
  249. - [Supabase](https://supabase.com) — Postgres for the signals dashboard
  250. - [better-sqlite3](https://github.com/WiseLibs/better-sqlite3) + [d3-force](https://d3js.org/d3-force) — Nexus Intel starter
  251. - [Apify CLI](https://apify.com) — scraping actors for both starters
  252. - [Recharts](https://recharts.org) + [shadcn/ui](https://ui.shadcn.com) — charts and components
  253. ---
  254. ## Contributing
  255. This is a living educational repo. If you've built GTM workflows with coding agents and want to contribute:
  256. 1. Fork the repo
  257. 2. Add your example to `examples/` or your tool doc to `engine/` (anonymize client data)
  258. 3. Open a PR with context on what GTM problem it solves
  259. 4. Star the repo if it helped you. That's how others find it.
  260. ---
  261. ## License
  262. MIT — use it, fork it, make it yours.
  263. ---
  264. <p align="center">
  265. <em>Stop renting GTM tools. Start building GTM systems.</em>
  266. <br/><br/>
  267. 🟧 <strong>Clearbox</strong> &middot; See your market. Move first. &middot; <a href="https://clearbox.to">clearbox.to</a>
  268. </p>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.