Marketing Os
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
Research a company's ideal customer profiles and build detailed synthetic buyer personas.
Install Buyer Persona Generator
$ npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gooseworks-ai/goose-skills buyer-persona-generator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/research/capabilities/buyer-persona-generator .claude/skills/buyer-persona-generator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "buyer-persona-generator" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/research/capabilities/buyer-persona-generator into .claude/skills/buyer-persona-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buyer-persona-generator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gooseworks-ai/goose-skills/tree/main/skills/research/capabilities/buyer-persona-generatorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gooseworks-ai/goose-skills buyer-persona-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/research/capabilities/buyer-persona-generator .agents/skills/buyer-persona-generator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "buyer-persona-generator" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/research/capabilities/buyer-persona-generator into .agents/skills/buyer-persona-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buyer-persona-generator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gooseworks-ai/goose-skills buyer-persona-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/research/capabilities/buyer-persona-generator .cursor/skills/buyer-persona-generator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "buyer-persona-generator" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/research/capabilities/buyer-persona-generator into .cursor/skills/buyer-persona-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buyer-persona-generator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gooseworks-ai/goose-skills.git --path skills/research/capabilities/buyer-persona-generator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gooseworks-ai/goose-skills buyer-persona-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/research/capabilities/buyer-persona-generator .gemini/skills/buyer-persona-generator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "buyer-persona-generator" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/research/capabilities/buyer-persona-generator into .gemini/skills/buyer-persona-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buyer-persona-generator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gooseworks-ai/goose-skills buyer-persona-generatorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/research/capabilities/buyer-persona-generator .github/skills/buyer-persona-generator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "buyer-persona-generator" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/research/capabilities/buyer-persona-generator into .github/skills/buyer-persona-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buyer-persona-generator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gooseworks-ai/goose-skills buyer-persona-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/research/capabilities/buyer-persona-generator .opencode/skills/buyer-persona-generator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "buyer-persona-generator" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/research/capabilities/buyer-persona-generator into .opencode/skills/buyer-persona-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "buyer-persona-generator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
buyer-persona-generator- GitHub stars
- 1.2k
- Used in
- 1 other repo
- Token cost
- ~2.2k tokens
- SKILL.md length
- 675 words
- Files
- 2
- Skills in repo
- 273
- Repo updated
- First seen
- Licence
- MIT
At a glance
Research a company's ideal customer profiles and build detailed synthetic buyer personas.
- Works in 4 steps: Company Research → Identify ICP Segments → Build Synthetic Personas → …
- You need to understand who your buyers are at a deep level — their motivations
- SKILL.md covers Quick Start, Inputs, Process and Output Summary, plus 2 more sections
- Reaches acme.com
What it does
Buyer Persona Generator is an agent skill from gooseworks-ai/goose-skills. Research a company's ideal customer profiles and build detailed synthetic buyer personas. Identifies 4-6 distinct buyer segments through web research, then creates rich, realistic personas with demographics, motivations, skepticism profiles, decision criteria, and language patterns. Use when you need to understand who your buyers are at a deep level — their motivations, objections, and how they evaluate solutions.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).
It sits in Marketing & SEO, covering Positioning and messaging. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.
When your agent uses it
- You need to understand who your buyers are at a deep level — their motivations
- How they evaluate solutions
Example prompts
- “/buyer-persona-generator”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c650c6d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
acme.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Buyer Persona Generator loads about 2.2k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 675 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 675 words, ~2,172 tokens.
Download SKILL.mdSave it as
.claude/skills/buyer-persona-generator/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- buyer-persona-generator
- description
- Research a company's ideal customer profiles and build detailed synthetic buyer personas. Identifies 4-6 distinct buyer segments through web research, then creates rich, realistic personas with demographics, motivations, skepticism profiles, decision criteria, and language patterns. Use when you need to understand who your buyers are at a deep level — their motivations, objections, and how they evaluate solutions.
- tags
- research
ICP Persona Builder
Research a company's buyer segments and build detailed synthetic personas that model their ideal customers. These personas become a reusable client asset — once built, any skill can load them to evaluate content, messaging, websites, or campaigns through buyer eyes.
Quick Start
Build ICP personas for [company]. Their site is [url].With known ICPs:
Build personas for [company]. Their ICPs are: [ICP 1], [ICP 2], [ICP 3].Inputs
| Input | Required | Source |
|---|---|---|
| Company name | Yes | User provides |
| Company URL | Recommended | Helps with research |
| Known ICPs | No | User provides, or discovered via research |
| Client context file | No | Any existing company context file, if available |
Process
Phase 1: Company Research
Understand what the company does and who they serve:
- WebFetch their website — homepage, product/solutions pages, pricing, "who it's for" pages
- WebSearch for:
- "[company] customers" / "[company] case studies"
- "[company] reviews" (G2, Capterra, TrustRadius)
- "[company] vs" (comparison searches reveal buyer segments)
- "[company] jobs" (who they're hiring to sell to / support)
- Extract signals:
- What problem do they solve?
- What's their pricing/packaging? (Signals ACV and buyer type)
- What industries/verticals do they serve?
- What company sizes do they target?
- What roles/titles appear in case studies and testimonials?
- What's their go-to-market motion? (Self-serve, sales-led, hybrid)
Phase 2: Identify ICP Segments
From the research, identify 4-6 distinct buyer segments. Each segment should represent a meaningfully different type of buyer — different role, different company profile, or different buying motivation.
For each segment, define:
| Attribute | Description |
|---|---|
| Segment name | Short label (e.g., "Enterprise IT Leader", "Startup Founder", "Agency Operator") |
| Role/titles | Typical job titles in this segment |
| Company profile | Size, stage, industry, tech stack |
| Core pain point | The #1 problem driving them to look for a solution |
| Buying trigger | What event makes them start searching NOW |
| Decision criteria | What matters most when evaluating (ranked) |
| Sophistication | How well they understand the problem space and solution landscape |
| Alternatives | What else they'd consider (competitors, DIY, status quo) |
| Segment size estimate | Rough sense of how big this segment is for the company (primary, secondary, emerging) |
Segment diversity rules:
- At least one technical buyer (evaluates capabilities, architecture, integrations)
- At least one business buyer (evaluates ROI, outcomes, competitive advantage)
- At least one skeptical profile (has been burned before, hard to convince)
- At least one junior/researcher (doing initial research for a decision-maker)
- Try to cover different company sizes if the company serves multiple tiers
Phase 3: Build Synthetic Personas
For each segment, create a detailed synthetic persona. The persona should feel like a real, specific person — not a marketing abstraction.
Persona structure:
{
"id": "persona-slug",
"name": "Jordan Chen",
"segment": "Enterprise IT Leader",
"title": "VP of Engineering",
"company": {
"type": "Mid-market SaaS company",
"size": "200-500 employees",
"stage": "Series B, scaling fast",
"industry": "Financial services technology"
},
"demographics": {
"experience_years": 12,
"reports_to": "CTO",
"team_size": 35,
"budget_authority": "$50K-200K without board approval"
},
"situation": "Jordan's team is growing faster than their tooling can support. They've been using a patchwork of internal scripts and are losing engineering hours to maintenance. The CTO has asked Jordan to evaluate modern solutions before next quarter's planning cycle.",
"pain_points": [
"Team productivity is dropping as they scale",
"Current tools don't integrate well",
"Onboarding new engineers takes too long"
],
"buying_trigger": "CTO mandate to evaluate solutions before Q3 planning",
"decision_criteria_ranked": [
"Enterprise security and compliance (SOC2, SSO)",
"Integration with existing stack (GitHub, Jira, Datadog)",
"Scalability — will this work at 2x team size?",
"Total cost of ownership, not just sticker price",
"Implementation timeline — needs to be live in 6 weeks"
],
"skepticism_profile": {
"trust_level": "Low — has been burned by vendor promises before",
"research_style": "Deep dive. Reads docs, checks GitHub issues, asks peers in Slack communities",
"key_objections": [
"Will this actually scale or will we outgrow it in a year?",
"What's the real implementation cost beyond the license?",
"How good is the support when things break at 2am?"
]
},
"technical_sophistication": "High — understands the technical landscape well, can evaluate architecture decisions, wants to see under the hood",
"language": {
"describes_problem_as": "We need to consolidate our toolchain and reduce operational overhead",
"searches_for": ["engineering productivity platform", "developer tools consolidation", "[competitor] alternative enterprise"],
"red_flag_words": ["revolutionary", "AI-powered", "seamless" — overpromising triggers skepticism],
"trust_signals": ["SOC2 badge", "customer logos in their industry", "transparent pricing", "public changelog"]
},
"evaluation_behavior": {
"first_visit": "Scans headline, checks if it's for their company size, looks for enterprise/security page",
"deep_evaluation": "Reads docs, checks integrations list, looks for case studies from similar companies",
"social_proof_needs": "Wants to see companies their size in their industry, not just FAANG logos",
"deal_breakers": ["No SSO/SAML", "No self-hosted option", "Pricing only available via sales call"]
}
}Show full SKILL.md (281 more words)Show less
Phase 4: Save Persona Assets
Save to the client directory as reusable assets:
personas.json — Machine-readable, all personas in an array. Save to the current working directory or wherever the user prefers:
{
"company": "Acme Corp",
"url": "https://acme.com",
"created": "2026-02-26",
"segment_count": 5,
"personas": [ ... ]
}personas.md — Human-readable Markdown with all personas written out in prose form, easy to review and share.
segments.md — Summary table of all segments with key attributes, useful as a quick reference.
Output Summary
After building, present:
- Segment overview table — All segments with key attributes at a glance
- Persona summaries — 2-3 sentence summary of each persona
- Coverage check — Confirm diversity rules are met (technical, business, skeptical, researcher)
- Next steps — Suggest running
icp-website-auditor other skills that can use the personas
Tips
- Research depth matters. Spend real time in Phase 1. The better you understand the company's actual customers, the more realistic the personas. Don't just read the homepage — dig into reviews, case studies, job postings.
- Make personas specific. "Marketing Manager" is too generic. "Sarah, Senior Demand Gen Manager at a 50-person B2B SaaS startup who just lost her SDR team to budget cuts" tells you exactly how she'll evaluate a tool.
- Include the language dimension. How the persona describes their problem is often completely different from how the vendor describes their solution. This gap is where messaging fails.
- Skepticism is the most important trait. Every persona needs a clear skepticism profile. What would make them NOT buy? What's their default assumption about vendors?
- This skill has no code script. It's agent-executed using WebSearch and WebFetch. The structured process above guides the research and persona creation.
Dependencies
- Web search capability (for company and ICP research)
- Web fetch capability (for reading website pages)
- No API keys or paid tools required
© gooseworks-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/research/capabilities/buyer-persona-generator of gooseworks-ai/goose-skills.
- SKILL.md
- skill.meta.json
Open the folder on GitHubat commit c650c6d
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Buyer Persona Generator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Buyer Persona Generator this skillgooseworks-ai/goose-skills | 1.2k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 540 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Positioningferdinandobons/startup-skill | 1.2k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Stanley Druckenmiller Investmenttradermonty/claude-trading-skills | 3k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| B2b Playbookweilun88313/B2B-Playbook | 203 | — | ~3.1k | Automated safety check: Pass | Proprietary |
Similar skills
Revenue Centric Design
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
Startup Positioning
ferdinandobons/startup-skill
Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test.
Stanley Druckenmiller Investment
tradermonty/claude-trading-skills
Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener)…
B2b Playbook
weilun88313/B2B-Playbook
Turn B2B marketing work into evidence-aware outputs using market, positioning, demand, account-program, lifecycle, and tool-selection guidance.
Research Brand
onvoyage-ai/gtm-engineer-skills
Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.
More from gooseworks-ai/goose-skills
All 273 skills in this repoReddit Post Finder
gooseworks-ai/goose-skills
Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.
Create Image Fal
gooseworks-ai/goose-skills
Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.
Render Hook Replacement
gooseworks-ai/goose-skills
Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.
Blog Feed Monitor
gooseworks-ai/goose-skills
Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.
Competitor Post Engagers
gooseworks-ai/goose-skills
Find leads by scraping engagers from a competitor's top LinkedIn posts.
Render Chatgpt Chat
gooseworks-ai/goose-skills
Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…
Related
Categories
Questions about Buyer Persona Generator
What does Buyer Persona Generator do?
Research a company's ideal customer profiles and build detailed synthetic buyer personas. Buyer Persona Generator is an agent skill from gooseworks-ai/goose-skills. Research a company's ideal customer profiles and build detailed synthetic buyer personas.
When should I use Buyer Persona Generator?
Buyer Persona Generator fits situations like: you need to understand who your buyers are at a deep level — their motivations; how they evaluate solutions.
How do I install Buyer Persona Generator in Claude Code?
Run `npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a claude-code`. Or copy the skill folder (skills/research/capabilities/buyer-persona-generator in gooseworks-ai/goose-skills) into .claude/skills/buyer-persona-generator in your project. Claude Code loads it when a task matches its description.
How do I install Buyer Persona Generator in Codex?
Run `npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a codex`. Or copy the skill folder (skills/research/capabilities/buyer-persona-generator in gooseworks-ai/goose-skills) into .agents/skills/buyer-persona-generator in your project. Codex loads it when a task matches its description.
Can I use Buyer Persona Generator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gooseworks-ai/goose-skills --skill buyer-persona-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/buyer-persona-generator, .gemini/skills/buyer-persona-generator, .github/skills/buyer-persona-generator and .opencode/skills/buyer-persona-generator in your project.
What does Buyer Persona Generator need to run?
SKILL.md names no scripts, command-line tools or credentials: Buyer Persona Generator is instructions for the agent only.
Does Buyer Persona Generator access the network?
SKILL.md names 1 domain. In commands or code: acme.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Buyer Persona Generator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Buyer Persona Generator use?
Buyer Persona Generator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Buyer Persona Generator use?
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Buyer Persona Generator?
Skills that share tags, products or a category with Buyer Persona Generator: Marketing Os (Yuzzyuk/marketing-os, 540 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Positioning (ferdinandobons/startup-skill, 1.2k stars) and Stanley Druckenmiller Investment (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Buyer Persona Generator?
gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.
Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.