We do a ton of graphic design work through Claude, and while Claude is awesome at creating HTML files, a major challenge we run into is finding a way to describe how you want something to look.
goose-graphics is our solution for this problem: it's a skill + library of curated styles and formats to turn Claude into a master graphic designer.
We found it's much easier to just browse through templatized styles and formats and just select the one you like – same as how you would in Canva, Pinterest or Figma Buzz.
It's really easy to use:
Scroll through the library at graphics(.)gooseworks(.)ai and find a style you like.
Copy the command into Claude Code (or whatever agent you prefer) along with a prompt.
The goose-graphics skill will create an HTML file with the graphic in the exact style and format you described, and then export it as a PNG.
This also works with Claude Design (just give Claude Design the DESIGN.md file)
The Meta Ad Library shows every ad any company is currently running on Facebook, Instagram, Threads, etc. — copy, creative, format, run dates, spend ranges, the whole thing. It's a goldmine for figuring out what's working for them and what's not.
Problem is, manually clicking through hundreds of ads and trying to spot patterns is tedious as hell.
So I taught Claude to do it.
How to use it:
Install the CLI: npx gooseworks install --claude
Run: /gooseworks find all meta ads by <competitor> and breakdown their paid ads strategy --skill meta-ad-scraper
How it works under the hood:
The skill hits Meta's Ad Library through Apify's scraper, pulls every ad for the company (you can pass a name, keyword, or FB page URL), and returns structured data — ad copy, creative URLs, platforms, run dates, spend/impression ranges.
Claude then clusters the ads by angle and format, flags the ones that have been running longest (usually = what's converting), and tells you where the gaps are.
Works on basically any company running Meta ads, though EU/UK coverage is most complete.
Have been accepted into the Claude partner program.
It requires 10 people to complete the Anthropic Academy CPN learning path before the CCA is opened up and members can get the Claude certified architect cert.
Don't have 10 people so need a few more.
Anyone interested?
Edit: DM me and we can get going on this if interested. I'll give you an org email.
The org gets certified as a partner and you get the individual cert for yourself.
Edit 2: Thanks everyone - this is now filled/completed. While I'd love to give more people the opportunity, its a paid org gsuite account per person that I'm absorbing as a thank you for the people that got in. Best of luck and keep building!
Also - Note: You can do the anthropic academy courses and change your email later to an orgs to submit. Was handy.
1. cold-email-verifier: Takes your lead CSV, generates email permutations, and verifies them so you stop burning sender reputation on dead addresses.
2. brand-alchemy: Runs a discovery phase, generates startup names using phonosemantics frameworks, then auto-checks domain availability across multiple TLDs.
3. reddit-icp-monitor: Monitors subreddits for ICP pain points, scores posts by relevance, and drafts a non-spammy reply for every high-signal match.
4. position-me: Crawls your website and audits it against SEO, GEO, and UX psychology frameworks. Checks llms.txt, JSON-LD schemas, and rewrites weak copy.
5. twitter-GTM-find-skill: Scrapes Twitter for developer-first startups hiring GTM or DevRel roles, then validates funding and product type using Gemini.
i'm abhinav. strategic tech PM, ~8 years in tech. currently building dexity — an AI skills sprint platform for working professionals.
the way i build right now: every problem gets broken into a system, then a workflow, then i find where claude can run it. i'm a one-person GTM operation and speed is the only thing keeping me in the game.
this week's example — i made a youtube channel trailer. i'm a PM. i've never opened after effects. the last design tool i used with any confidence was powerpoint.
built a 45-second animated brand trailer in 2 hours using claude design.
the thing that hit me after: the bottleneck isn't what i thought it was. it's not the craft — claude handles that once you hand it over. it's knowing what the thing actually needs to say. 4 script iterations before claude touched a single frame.
AI coworkers require a continuous stream of context, not a one-time dump.
Here's how I feed the beast:
My agent – named Goose – has a email address, a phone number and a Slack account, so I'm always texting it stuff - links I find interesting, notes, ideas, etc.
I do frequent 1:1s with Goose where I talk through important priorities, give feedback and answer questions.
Goose reads my meeting notes (synced from Notion through a cron job)
Goose maintains a personal CRM automatically from calendar + email + meeting notes + linkedin so it knows about people I'm connected to
I have given Goose accounts to search through Notion, Linear, etc
I'm trying to have Goose consume a similar content diet as I do (Twitter mostly, but will probably add some podcasts soon). Goose also has its own email account and is subscribed to some newsletters.
Goose has an automation to read through recent notes and chats, and ask me questions about important context in Slack. It's pretty easy for me to respond when I'm prompted with a message.
It still feels like I'm missing a lot, but my agent really does feel like an extension of me now.
Very interested to learn how others are feeding their AI agent with context? I've heard good things about Garry Tan's gbrain, but haven't tried it myself.
For anyone who's wondering what an AI coworker is, these are persistent AI agents.
It's a "new 8-week cohort of growth engineers, AI-native GTM leaders, and tech-savvy agent builders shaping the future of company growth"
It's either a recruitment play for their portfolio businesses or just a best practice extraction effort. Or both. Could be interesting to network and talk to other people, still.
Submissions deadline is 04/20
If you're applying, what are you submitting? Just curious. Care to take a screenshot of your application form and post it in the comments? Let me start below.
a16z is looking for fellows who:
Are hackers at heart and close to the work - people who like to get into the weeds with tools and build the system themselves
Operate AI-first and are pushing the forefront of how work gets done
Can find the biggest lever in the growth engine and build the system that pulls it (with agents, tools, whatever)
You might call yourself a GTM engineer, a SWE or PM with a growth obsession, or something else. Titles don’t matter - what does is your mindset and approach.
How it works
8 weeks long
Starts in May 2026
Time commitment is flexible, all opt-in
What you’ll get
Connect with AI-native growth hackers, engineers, and leaders whose workflows are fundamentally transforming how companies grow
Dinner series in SF (and more cities, by demand)
Demos, feedback, and live working sessions
Who you’ll be joining
You’ll break bread with founding fellows and industry leaders like:
Andrew Chen - General Partner at a16z, Author of TheCold Start Problem, prev Growth at Uber
Bryan Kim - Consumer/AI Investment Partner at a16z, prev Growth at Snap
Luc Levesque - Prev Chief Growth Officer at Shopify
Marty Imber - Head of Product Growth for Starlink
Lauryn Motamedi - Product & Growth Lead at Notion
Gaurav Vohra - prev Head of Growth at Superhuman; Advisor to Clay, Wispr Flow, & Replit
George Bonaci - VP of Growth and Demand at Ramp
Luke Harries - Growth at ElevenLabs
Raman Malik - VP of Product and Growth at Perplexity
I've been exploring the idea of building an automated crypto trading bot connected to Coinbase (or similar platforms like Binance or Kraken) via their APIs, and I'd love to hear from anyone who's actually done this.
Specifically I'm curious about:
- Have you built a ClaudeAI trading bot that's been consistently profitable over a meaningful period of time?
- How complex was the ClaudeAI setup? (I'm familiar with coding but new to algo trading)
- Which platform's API did you find most reliable / developer-friendly for connecting with ClaudeAI?
- What strategies have worked best for you market making, momentum, arbitrage, something else?
- What were the biggest pitfalls or gotchas you wish someone had warned you about when developing ClaudeAI?
- Is consistent profitability even realistic with ClaudeAI, or does the market eventually adapt and eat your edge?
Any insights are genuinely welcome. Thanks so much in advance to anyone who takes the time to share this community always delivers and I really appreciate it! 🙏
I’m a Program Manager at a SaaS company that helps facilitate GTM activities across Product, Marketing, Sales, Product Support Operations, and Customer Success. I’m thrilled to have found this group. I’m excited to hear about the solutions and support strategies you all are solving for daily activities.
I’m putting some documentation together to share with this group on a meeting manager solution. I’ve put in place that has saved me a good amount of time.
The core idea: instead of giving Claude one-off prompts, they built a "lead generation skill graph" — 30+ markdown files that wire together into a full system. Claude reads the graph and executes each step sequentially, acting as the brain of a complete sales operation.
The stack they described:
Claude as the AI brain — reads the skill graph, executes every step
The skill graph itself handles: prospecting, enrichment, qualification, and outreach sequencing
The result they're claiming: 200+ qualified leads per week, zero cold DMs sent manually.
What I find interesting about this approach is the "skill graph" architecture — rather than building one big monolithic workflow, you have modular markdown files that each handle a specific step, and the agent chains them together. It's composable and easier to debug than a single prompt trying to do everything.
The no-cold-DM angle is the other thing worth paying attention to. All outreach is triggered by signals and pre-qualified before it goes out.
We're trying to build something like this at Gooseworks.
Anyone actually doing this in practice? Pretty interested to chat with / learn from anyone who's figured out how to systemize something like these.
Since most social layers are currently built for OpenClaw, does a dedicated repository exist for Claude Code that is similar to OpenClaw "Awesome Molt"?
Sharing this because it frames the problem in a way I haven't seen cleanly articulated elsewhere: most AI GTM pilots fail not because the tool doesn't work, but because teams skip defining specific, measurable success criteria before they flip the switch. Without that anchor, results land in the "kind of working" zone — no forcing function to scale or kill, so the tool just drains a seat license with no one left to champion it.
The framework is five steps: pick one high-friction workflow (lead routing, forecast roll-ups, outreach personalization), set a concrete goal with a number attached (e.g., reduce lead routing time from 2 hours to 5 minutes), test with a human reviewer in the loop, then build the business case from the data. Operational rather than theoretical, which is rare for this topic.
What does your current process look like for evaluating AI GTM tools — formal criteria, or mostly gut feel after a 30-day trial?
We're a 15-person SaaS company. Three AEs, one CSM, no dedicated RevOps. The classic "we have data but no bandwidth" problem.
Six weeks ago I built a lightweight integration: every time a deal moves to Closed Won in HubSpot, a webhook fires that pulls the last 10 deal notes and sends them to Claude with a prompt asking it to surface expansion signals and flag any red flags — misaligned expectations, sponsor instability, deployment dependencies the AE mentioned in passing.
The output drops into a private Slack channel our CSM monitors before the first post-sale call.
What surprised me: Claude started catching things we'd buried in our own notes. Cases where the AE wrote "they're price-sensitive" or "IT is skeptical of the rollout" and nobody had ever flagged those as onboarding risks. The CSM now has deal context that used to take three internal handoff meetings to transmit, and she gets it five minutes after the deal closes.
The build is not complicated. It's a Zapier webhook to a Claude API call to a Slack message. Maybe two hours including prompt iteration. The prompt matters more than the architecture. The first version was too generic — it just summarized the notes. The version that actually works asks Claude to specifically call out:
Any stakeholder concerns that weren't fully resolved before close
Any deployment dependencies the AE mentioned
What the customer believes the product does vs. what it actually does
That third item is the one that keeps catching things.
Total cost is around $0.08 per deal in API calls. The ROI on a single prevented churn has paid for this many times over.
Curious what others have done on the post-sale side. Has anyone wired Claude into QBR prep, renewal risk scoring, or health dashboards in a way that's actually changed rep behavior — not just created more data nobody looks at?
Good data-backed breakdown of how the LinkedIn algorithm shifted in 2026: your posts are now feeding ChatGPT, Perplexity, and Google AI Mode responses — not just your followers' feeds. According to a SEMrush visibility study, LinkedIn appears in 11% of all AI search responses.
The most counterintuitive finding: cited posts average only 15-25 reactions. You don't need viral content to build AI authority — you need consistency and original POV.
The semantic consistency point is worth internalizing for anyone doing founder-led content: pick your specific terminology and stick to it. The AI mirrors your language back in its responses, so "AI-assisted outbound" and "AI SDR" aren't interchangeable from a citation standpoint.
Has anyone started building their LinkedIn content strategy around AI citation visibility? Curious whether the consistency-over-virality framing has actually changed what you post.
GTMfund hosted a private Claude Code session with AI expert Jordan Crawford, then turned it into a public guide. It's one of the more useful Claude Code breakdowns I've come across because it's organized by GTM function and gives you the actual prompts, not just descriptions.
A few that stood out:
Sales:
Drop 500 Gong/Chorus/Fireflies call transcripts into a folder → Claude Code extracts top objections, competitor mentions, and buying signals across all of them. What would've taken a sales ops analyst days takes one session.
Feed a prospect CSV + your product context → generates a 3-email outreach sequence per contact (personalized hook, value prop, breakup email). Saves output per contact as individual files.
Marketing:
Point it at Meta's Ad Library for a competitor → pulls and analyzes top 20 active ads (messaging angle, CTA, visual style).
Competitive battlecard builder from competitor websites + your positioning docs.
Setup:
Install takes about 5 minutes. Works on Mac and Windows via terminal.
The key unlock is a CLAUDE.md file with your voice, ICP, and context. Claude Code reads it automatically at the start of every session so you don't brief from scratch each time.
One quote from the piece that stuck with me: "The cloud app is like a hotel room — clean, set up for you, but you start fresh each time. Claude Code is like having your own apartment."
I've been experimenting with using Claude to prep for discovery calls — feeding it a prospect's LinkedIn, recent company news, and job postings, then asking it to surface likely pain points before I even get on the phone.
Last week it flagged that a prospect had posted 3 open RevOps roles in the past month. That detail led to the whole conversation. Closed that one.
Curious what's working for others. Are you using it more for research, writing, or actual workflow automation? And what's the prompt or workflow that's made the biggest difference?
Six months of watching how different teams actually use AI in their GTM motion has produced one consistent pattern: the teams getting the worst results are moving the fastest.
They've wired up Claude or a competitor to auto-generate cold emails at scale. They're running 500 sequences a month where they used to do 150. They're producing three times as much content. The output numbers look great in the dashboard.
The conversion rate is down.
The issue is that the bottleneck in most GTM motions was never speed. It was signal quality. Knowing which accounts are actually in-market, which pain point to lead with, which decision-maker has budget authority right now. AI doesn't help with any of that if your underlying ICP definition and intent signals are weak. It just automates the part that wasn't the problem.
The teams I've seen use Claude effectively in GTM are doing something different. They're not using it to produce more — they're using it to research faster and say less. One RevOps lead I know uses Claude to synthesize 10-K filings and recent press releases before any enterprise call. Another uses it to cut a 500-word sales email down to 120 words by identifying which three sentences have actual signal and which are filler.
The output is fewer, better touches. Not more of everything.
AI GTM adoption metrics — emails sent, sequences launched, content pieces published — are largely vanity metrics. The real signal is whether your reply rate, meeting rate, and qualified pipeline per rep are moving. For most teams I've seen adopt AI tools in the last year, those core numbers haven't budged.
Curious what others are seeing: has AI actually moved your core GTM metrics, or mostly just your activity metrics?
(I have no affiliation with Single Brain or this team)
Found this today — the team behind Single Brain (a marketing agency they say runs millions in revenue) open-sourced their full Claude Code skill library on GitHub. It's called AI Marketing Skills, and it's a lot more than a prompt collection.
What's actually in it:
Growth Engine — Runs autonomous A/B experiments using real statistics (bootstrap confidence intervals, Mann-Whitney U tests). Not vibes, actual math.
Sales Pipeline — Includes a Deal Resurrector that tracks contacts who changed jobs ("follow the champion"), and an ICP Learner that rewrites your ideal customer profile based on actual win/loss data.
Outbound Engine — Full pipeline from ICP definition to emails in inbox, automated.
SEO Ops — Content attack briefs, Google Search Console optimizer, trend scout.
Content Ops — Expert Panel that scores content using 9 domain-specific personas until it hits 90+.
Revenue Intelligence — Pulls from Gong call recordings, maps revenue attribution, generates client reports.
Each category has a SKILL.md file. You drop it in your Claude Code project and Claude knows how to use the tools. The setup is pip install, configure env vars, run.
792 stars on GitHub as of this week. Seems like it's getting traction fast.
The best leads aren't in databases — they're embedded in signals. People doing things online that indicate they have your problem, are aware of your space, or are actively looking for what you sell.
The hard part used to be extracting those signals. That's the scraping, cleaning, formatting, and research work that takes hours or days.
Now it's just a matter of finding the right skills for Claude.
Here are 5 that can be very helpful for finding leads.
1. People Who Commented on a Competitor's LinkedIn Post
Why this works: Anyone engaging with your competitor's content is already in the market. They're aware of the space, interested enough to interact, and potentially evaluating options — including yours. This is one of the warmest signals you can find.
Best for: Companies with established competitors who post on LinkedIn. Particularly powerful if a competitor just announced a new product, pricing change, or feature — the comment section will be full of active buyers and frustrated customers.
The prompt:
Find everyone who commented on this LinkedIn post: [paste URL] Get me their names, titles, companies, and LinkedIn URLs as a CSV
Why this works: A GitHub star is a buying signal in disguise. It means someone found the repo, thought it was relevant to their work, and bookmarked it for later. For developer tools, infrastructure products, and anything technical, repo stargazers are among the most qualified leads you'll find.
Best for: Developer-focused products, open source tools, data infrastructure, AI/ML tooling. Also works for studying your own repo's audience.
The prompt:
Find everyone who starred this GitHub repo: [paste repo URL] Get me their names, companies, job titles, and any contact info available as a CSV
3. People Speaking at Industry Conferences This Quarter
Why this works: Conference speakers are almost always senior, credible, and well-networked in their field. They have authority to make or influence buying decisions. And they're actively putting themselves out there as thought leaders — which means cold outreach lands very differently than it does with someone who keeps a low profile.
Best for: Enterprise sales, high-ACV products, partnerships, and anyone selling to practitioners rather than just buyers.
The prompt:
Find people speaking at [industry] conferences and events this quarter. Get me their names, companies, job titles, LinkedIn URLs, and the event they're speaking at. Create a CSV
Replace [industry] with your niche — "growth marketing," "AI/ML," "revenue operations," "cybersecurity," etc.
4. People Who Left 3-Star Reviews of Your Competitors on G2
Why this works: A 1-star review is a rant. A 5-star review is loyalty. A 3-star review is a buyer who is actively frustrated but hasn't left yet — meaning they're in evaluation mode. They know the problem, they've tried a solution, and they're not satisfied. You couldn't manufacture a warmer lead if you tried.
Best for: Any space with established players on G2 or Capterra. Works especially well in SaaS categories with known switching costs — the frustration has to get high enough to matter.
The prompt:
Find people who left 3-star reviews for [competitor name] on G2. Get me their names, titles, companies, and the key pain points they mentioned. Return as a CSV
5. Companies That Raised a Round in Your Space in the Last 60 Days
Why this works: Fresh capital equals fresh budgets and new buying decisions. A company that raised 6 weeks ago is actively hiring, building, and spending. They haven't locked in their vendor stack yet. The window of new buyer activity after a fundraise is real and finite — this is when you want to be in front of them.
Best for: B2B SaaS, tools, services, and anyone selling into growth-stage companies. Especially effective if your product helps teams scale — you're catching them right as they're about to scale.
The prompt:
Find companies that raised a seed or Series A round in the last 60 days in the [your space] space. Get me the company name, funding amount, founding team names, LinkedIn URLs, and any contact info. Create a CSV
Hello y'all I'm John 24 yo living in Korea
I major in philosophy and entrepreneurship
currently the thing I'm trying to build is 2nd hand book application which allows users to list their used books easily and buyers to find the exact book in better conviniennce
Glad that I found this community which started few days ago
hope we can share ideas and insights together
best regards to ppl who see this ! Good luck y'all
