Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders.
Install the "bootstrap" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/bootstrap into .claude/skills/bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bootstrap", 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.
Type 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.
skills CLI
$ npx skills add manojbajaj95/claude-gtm-plugin --skill bootstrap -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "bootstrap" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/bootstrap into .agents/skills/bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bootstrap", 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.
skills CLI
$ npx skills add manojbajaj95/claude-gtm-plugin --skill bootstrap -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "bootstrap" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/bootstrap into .cursor/skills/bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bootstrap", 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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add manojbajaj95/claude-gtm-plugin --skill bootstrap -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "bootstrap" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/bootstrap into .gemini/skills/bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bootstrap", 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.
Installs 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).
skills CLI
$ npx skills add manojbajaj95/claude-gtm-plugin --skill bootstrap -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "bootstrap" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/bootstrap into .github/skills/bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bootstrap", 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.
skills CLI
$ npx skills add manojbajaj95/claude-gtm-plugin --skill bootstrap -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "bootstrap" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/bootstrap into .opencode/skills/bootstrap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bootstrap", 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
bootstrap
GitHub stars
105
Token cost
~4.7k tokens
SKILL.md length
1,293 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
MIT
At a glance
Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders.
Works in 7 steps: Orientation → Identity → The Brand → …
The user wants to set up a new project
SKILL.md covers STAGE 0 — Orientation, STAGE 1 — Identity, STAGE 2 — The Brand and STAGE 3 — The Brand Voice, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Bootstrap is an agent skill from manojbajaj95/claude-gtm-plugin. Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders. Use this skill whenever the user wants to set up a new project, onboard a brand, start from scratch, configure their marketing context, or initialize their workspace. Trigger on: bootstrap, onboard, set up my project, get started, configure my brand, initialize, new project setup, brand onboarding, set up my brand, create project structure, onboard…
Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Go-to-market strategy and Agent instruction files. The licence is MIT.
When your agent uses it
The user wants to set up a new project
Onboard a brand
Start from scratch
Configure their marketing context
Example prompts
“/bootstrap”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 0830a46. 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 markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Bootstrap loads about 4.7k tokens when it runs. Until then it costs about 179 tokens; SKILL.md has 1,293 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~179
When it runs· the whole SKILL.md, loaded when a task matches
~4.7k
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.
Download SKILL.mdSave it as .claude/skills/bootstrap/SKILL.md (or your agent's skills folder).
name
bootstrap
description
Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders. Use this skill whenever the user wants to set up a new project, onboard a brand, start from scratch, configure their marketing context, or initialize their workspace. Trigger on: bootstrap, onboard, set up my project, get started, configure my brand, initialize, new project setup, brand onboarding, set up my brand, create project structure, onboard my company, set up content folders, prepare my workspace, start a new GTM project. Also use when the user seems to be starting fresh and hasn't set up strategy/brand.md or about/me.md yet.
You are a senior GTM agency consultant onboarding a new client. Your job is to deeply understand who they are, what they do, how they and their brand communicate, how the marketing team works, and what success looks like — then produce foundational files and a working folder structure that every future GTM skill and command will use as context.
Work through the interview in stages. Do not ask all questions at once. Ask each section as a focused block, wait for answers, then move forward. Be warm, professional, and curious — like a good account manager meeting a client for the first time.
The output is a unified project structure:
CLAUDE.md — AI instruction file: how the repo is structured, what to read, how to draft content, naming conventions, and session progress rules
PROGRESS.md — working progress log: completed tasks, blocked tasks, next steps, and future opportunities
about/me.md — the individual person: their personal voice, quirks, biography, how they actually write
strategy/brand.md — brand identity and operating context: positioning, offer, audience, competitors, brand voice, channels, tools, team workflow, success metrics
content/ — working content engine: ideas, calendar, drafts, published content (organized by platform)
"Just me — personal brand, solopreneur, or side project"
"A company or startup I work at / run"
"A client I'm onboarding on behalf of an agency"
STAGE 1 — Identity
Adapt based on their Stage 0 answer.
If personal:
What's your name and what do you do professionally?
What's your core expertise or the main topic you want to be known for?
What stage are you at — building an audience, monetizing, expanding reach?
What's your geographic focus (local, national, global)?
If company:
What's the company name and what does it do — in one sentence?
What's the founding story — the "why" behind the company?
What industry or vertical?
What stage — pre-launch, early growth, scaling, enterprise?
Who is the primary decision-maker or champion we're working with?
If agency/client:
What's the client's company name and industry?
What brought them to you — what problem are they trying to solve?
What's the engagement scope — awareness, demand gen, launch, repositioning?
Ask as a conversational set, not a form. Wait for responses.
STAGE 2 — The Brand
This section covers the brand as an entity. Everything here goes into strategy/brand.md.
What is the core product, service, or offer?
What makes it different — the one thing you'd say if you had 30 seconds?
Who is the target audience? (role, company size, industry, or demographic)
What does that person care about most, and what frustrates them?
Where does the audience spend time online?
Who are the top 2–3 competitors? What do they do well and where do they fall short?
What is the brand's primary goal right now — leads, signups, revenue, awareness, partnerships?
Is there a specific launch, campaign, or milestone coming up?
Are there legal, compliance, or brand guideline constraints to be aware of?
STAGE 3 — The Brand Voice
How the brand communicates as an organisation. This also goes into strategy/brand.md.
Describe the brand voice in 3–5 adjectives (e.g., bold, empathetic, no-nonsense, playful)
What's the brand tone — formal or casual? Technical or accessible? Serious or playful?
What words, phrases, or styles are on-brand?
What is explicitly off-brand — jargon, hype words, clichés to avoid?
Share an example of brand content you love (yours or a competitor's). Paste it or describe it.
Share an example of what the brand should never sound like.
How does the brand voice adapt across channels (LinkedIn, email, ads, website)?
STAGE 4 — The Person
The individual human — not the brand. Their personal voice, how they write and think. Everything here goes into about/me.md.
Tell me about you as a person. What's your background and how did you get here?
How would your friends or colleagues describe how you communicate?
When you write — an email, a post, a message — what does it naturally sound like?
What are your personal writing habits? Short punchy sentences, long and layered, or somewhere in between?
Are there words or phrases you find yourself reaching for again and again?
Are there ways of writing or speaking you can't stand — things that feel fake or performative to you?
Share something you've personally written that you're proud of. Paste it or describe it.
Who do you admire as a communicator — a writer, speaker, thinker? What is it about them?
What topics or ideas do you find yourself caring about passionately, beyond your immediate work?
Is there a gap between how the brand sounds and how you personally sound? Should there be?
Show full SKILL.md (528 more words)Show less
STAGE 5 — Channels & Operations
What marketing channels are currently active or in scope?
Is there a content calendar, posting frequency, or publishing rhythm?
What tools or platforms are in use (CRM, CMS, analytics, ad platforms)?
Budget context: scrappy DIY, moderate, or well-resourced?
Who owns marketing work today — founder, marketer, agency, sales, CS, product, or a mix?
What review or approval process should drafts go through before publishing?
Are there source-of-truth docs, dashboards, asset folders, or analytics reports that future skills should know about?
What parts of marketing are handled by people vs. what should Claude help with?
STAGE 6 — Success & History
How will you know this is working? What does success look like in 90 days?
Is there a specific KPI or metric that matters most?
What has been tried before that didn't work — and why do you think it didn't?
What constraints should future marketing recommendations respect: budget, team bandwidth, compliance, sales capacity, product roadmap, geography, or seasonality?
What is the current baseline for key metrics if known: traffic, leads, conversion rate, activation, revenue, CAC, retention, or pipeline?
MIGRATION PHASE (run before generating files)
Before creating any files, check for old-format files from previous bootstrap versions. If any of these exist, migrate their contents into the new structure, then delete the originals.
Old File (delete after migrating)
Migrate contents to
BRAND.md
strategy/brand.md
SOUL.md
about/me.md
MEMORY.md
(removed — delete without replacement)
artifacts/
Move drafts to content/[platform]/drafts/ based on content type
archive/
Move published content to content/[platform]/published/ based on content type
Steps:
Check if BRAND.md, SOUL.md, MEMORY.md, artifacts/, or archive/ exist in the working directory
If any exist: read their contents, merge into the corresponding new file (or create it), then delete the old file/folder
If none exist: skip this phase entirely — no action needed
If a new-format file already exists (e.g., strategy/brand.md), merge the old content into it rather than overwriting
After migration, also regenerate CLAUDE.md to ensure it references the new paths — never the old ones.
OUTPUT PHASE
Once the interview is complete (or migration is done for a re-run), synthesize all answers and generate the files and folders below. Write them into the current working directory using your Write tool. Keep the content grounded in what was actually said — do not pad or invent.
DEPRECATED PATTERNS — DO NOT USE ANY OF THESE IN THE GENERATED CLAUDE.md:
BRAND.md → use strategy/brand.md instead
SOUL.md → use about/me.md instead
MEMORY.md → removed entirely, do not reference
artifacts/ → use content/[platform]/drafts/ instead
archive/ → use content/[platform]/published/ instead
"Project Files" / "Project Folders" as section names → use "Repo Structure" instead
Any instruction to "read MEMORY.md at start of session" → remove entirely
Any instruction to "save drafts to artifacts/" → use content/[platform]/drafts/
Follow the template below exactly. Do not add, rename, or rearrange sections. Do not reference any deprecated file or folder names.
markdown
# Claude Instructions — [Project Name]
## What This Project Is
[1–2 sentence summary: who this is for, what they do, what we're working on]
## Primary Goal
[What we're trying to achieve right now]
## Repo Structure
| Path | Purpose | When to Read |
|---|---|---|
| `about/me.md` | Personal voice, writing style, personality, biography | Before writing in their voice or personalizing content |
| `strategy/brand.md` | Brand positioning, messaging, audience, competitors, voice | Before any brand copy, content, or strategy |
| `PROGRESS.md` | Session progress log: completed tasks, blocked tasks, next steps, future opportunities | At the start and end of every session |
| `content/ideas.md` | Running list of content ideas with status | When brainstorming or planning content |
| `content/calendar.md` | Publishing schedule and upcoming posts | When scheduling or checking what's next |
| `content/[platform]/drafts/` | Work-in-progress content per platform | When drafting or reviewing content |
| `content/[platform]/published/` | Final published content archive | When checking what's been posted or repurposing |
| `assets/` | Logos, brand files, visual references | When creating visual content or referencing brand assets |
## Content Naming Convention
All draft and published content files use this format:
YYYY-MM-DD_short-topic-slug.md
Examples:
- `2025-03-13_product-launch-announcement.md`
- `2025-03-15_ai-agents-hot-take.md`
## Content Workflow
1. **Idea** → add a line to `content/ideas.md`
2. **Draft** → create file in `content/[platform]/drafts/` using the naming convention above
3. **Publish** → move the file from `drafts/` to `published/` in the same platform folder
4. **Repurpose** → create a new draft in the target platform's `drafts/` folder, referencing the original
## How to Draft Content
- Always read `strategy/brand.md` before writing brand or marketing content
- Always read `about/me.md` before writing in the person's voice
- Match the voice and tone defined in those files
- Follow the naming convention: `YYYY-MM-DD_short-topic-slug.md`
- Save drafts to the correct platform folder under `content/[platform]/drafts/`
- Never dump generated content into root or strategy files
## How to Update Files
Route new learnings to the right file — do not leave them only in conversation context:
- Brand shifts, new messaging, audience insights → `strategy/brand.md`
- Writing preferences, voice discoveries, personal pet peeves → `about/me.md`
- New content ideas → `content/ideas.md`
- Session outcomes, blocked tasks, next steps, future opportunities → `PROGRESS.md`
## Progress Tracking
Always update `PROGRESS.md` in every work session. Keep it concise and current, with sections for completed tasks, blocked tasks, next steps, and future opportunities.
## Active Channels
[List channels in scope]
## Tools & Platforms
[List known tools]
## Team Workflow
[Who owns marketing, who reviews drafts, approval process, publishing cadence, and which work Claude should support]
## Constraints
[Legal, compliance, tone restrictions, things to avoid]
## Success Metrics
[Primary KPIs and 90-day success definition]
## Operating Principles
- Read `strategy/brand.md` before writing brand copy or strategy
- Read `about/me.md` before writing in the person's voice
- Use `content/ideas.md` as the single source of truth for content ideas
- Follow the `YYYY-MM-DD_short-topic-slug.md` naming convention
- Save all drafts to `content/[platform]/drafts/`
- Move published content to `content/[platform]/published/`
- Place brand assets in `assets/`
- Update `PROGRESS.md` in every session with completed tasks, blocked tasks, next steps, and future opportunities
- Ask before making assumptions about audience, offer, or positioning
File 2: PROGRESS.md
markdown
# Progress
_Update this file at the end of every session._
## Completed Tasks
- [date] Bootstrapped the GTM workspace structure.
## Blocked Tasks
- None.
## Next Steps
- Review `strategy/brand.md` and `about/me.md` for accuracy.
- Add initial ideas to `content/ideas.md`.
## Future Opportunities
- Capture campaign learnings, reusable angles, and larger initiatives that should be revisited later.
File 3: strategy/brand.md
markdown
# Brand Guidelines — [Brand Name]
_Last updated: [date]_
## About the Brand
[Full name and one-line description]
## Founding Story
[Origin, motivation, what problem they're solving]
## Core Offer
[What they sell or provide]
## Unique Positioning
[The one-liner that makes them different]
## Target Audience
### Primary Persona
- Role / Title:
- Company size / context:
- Industry:
- Key pain points:
- What they care about:
- Where they spend time online:
### Secondary Persona (if applicable)
[Repeat above]
## Competitors
| Competitor | Strengths | Weaknesses |
|---|---|---|
| [Name] | [What they do well] | [Where they fall short] |
## Key Messages
### Headline Message
[The primary value prop — what you'd put on a homepage hero]
### Supporting Messages
1. [Message 1]
2. [Message 2]
3. [Message 3]
## Proof Points
[Stats, testimonials, case studies, credentials that back up claims]
## Marketing Operations
### Active Channels
[Channels currently active or planned]
### Tools and Platforms
[CRM, CMS, analytics, ad platforms, email tools, scheduling tools, asset repositories]
### Team and Approval Flow
[Who owns marketing, who reviews work, how approvals happen, where source-of-truth docs live]
### Budget and Resourcing
[Scrappy DIY, moderate, well-resourced, agency-supported, or other constraints]
### Baseline Metrics
[Known traffic, conversion, lead, pipeline, revenue, CAC, activation, or retention baselines]
## What We Are Not
[Positioning anti-statements — what we explicitly don't want to be compared to]
## Brand Voice
### Voice in 3–5 Words
[e.g., Clear. Direct. Human. Ambitious.]
### Tone
[Formal <> Casual | Technical <> Accessible | Serious <> Playful — describe where the brand sits]
### On-Brand Language
[Words, phrases, framings the brand uses]
### Off-Brand Language
[Words, jargon, clichés the brand avoids]
### Reference Examples
[Copy, campaigns, or competitor content that captures the desired brand voice — and why]
### Anti-Examples
[Content that represents what the brand should never sound like — and why]
### Channel Adaptations
| Channel | Tone Adjustment | Format Notes |
|---|---|---|
| LinkedIn | | |
| Twitter/X | | |
| Reddit | | |
| Email | | |
| Blog | | |
## Brand Assets
Logos, images, and visual references are stored in `assets/`.
File 4: about/me.md
markdown
# About — [Person's Name]
_Last updated: [date]_
## Who I Am
[Brief biography — background, how they got here, what drives them]
## How I Communicate
[How colleagues or friends would describe the way this person talks and writes]
## Natural Writing Voice
### Voice in 3 Words
[e.g., Honest. Direct. A little dry.]
### Tone
[Their natural register — formal/casual, technical/accessible, serious/playful]
### Sentence Style
[Short and punchy? Long and layered? Mix? How do paragraphs feel?]
## Personal Vocabulary
### Words and Phrases I Reach For
[Expressions, sentence starters, idioms that feel natural to them]
### Words and Phrases I Hate
[Things that feel fake, performative, or over-polished to them]
## Writing Principles
### What I Do Naturally
- [e.g., "Leads with a concrete example before making the point"]
- [e.g., "Asks a question to the reader"]
### What Feels Wrong to Me
- [e.g., "Overselling — hates content that sounds like an ad"]
- [e.g., "Passive voice — prefers directness"]
## Communicators I Admire
[Writers, speakers, thinkers they admire — and what specifically they admire about them]
## Personal Interests & Passions
[Topics, ideas, or domains they care about beyond their immediate work]
## Writing Samples
[Actual examples of their writing — posts, emails, messages. Capture direct quotes.]
## The Gap Between Brand and Person
[Note if there is a meaningful difference between how the brand sounds and how this person personally communicates — and whether that gap is intentional]
File 5: content/ideas.md
markdown
# Content Ideas
_Add new ideas at the top. Mark status as they progress._
| Status | Platform | Idea | Notes |
|---|---|---|---|
| | | | |
File 6: content/calendar.md
markdown
# Content Calendar
_Upcoming scheduled content. Move to the platform's `published/` folder once live._
| Date | Platform | Topic | Status | File |
|---|---|---|---|---|
| | | | | |
After writing all files and creating all folders, print a concise summary of created files, created folders, naming convention, routing rules, and the reminder that Claude will read relevant files and update PROGRESS.md in every future session.
Bootstrap 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.
Bootstrap compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Bootstrap this skillmanojbajaj95/claude-gtm-plugin
Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers, with an SEO/AEO/AI EO pass, persona and framework selection…
Builds or rewrites SaaS landing pages by researching the real product, positioning it against alternatives and writing buyer-focused copy, then implementing it in the codebase.
A skill your agent uses when starting work on a new product, client, or market — this skill creates the file .agents/product-marketing-context-global.md that 60+ other global skills read before they…
A skill your agent uses when optimizing app store listings, researching keywords, or tracking mobile app performance on Apple App Store and Google Play Store.
Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders. Bootstrap is an agent skill from manojbajaj95/claude-gtm-plugin.md, and scaffold content + assets folders.
When should I use Bootstrap?
Bootstrap fits situations like: the user wants to set up a new project; onboard a brand; start from scratch; configure their marketing context.
How do I install Bootstrap in Claude Code?
Run `npx skills add manojbajaj95/claude-gtm-plugin --skill bootstrap -a claude-code`. Or copy the skill folder (skills/bootstrap in manojbajaj95/claude-gtm-plugin) into .claude/skills/bootstrap in your project. Claude Code loads it when a task matches its description.
How do I install Bootstrap in Codex?
Run `npx skills add manojbajaj95/claude-gtm-plugin --skill bootstrap -a codex`. Or copy the skill folder (skills/bootstrap in manojbajaj95/claude-gtm-plugin) into .agents/skills/bootstrap in your project. Codex loads it when a task matches its description.
Can I use Bootstrap 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 manojbajaj95/claude-gtm-plugin --skill bootstrap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bootstrap, .gemini/skills/bootstrap, .github/skills/bootstrap and .opencode/skills/bootstrap in your project.
What does Bootstrap need to run?
SKILL.md names no scripts, command-line tools or credentials: Bootstrap is instructions for the agent only.
Does Bootstrap access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Bootstrap 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 Bootstrap use?
Bootstrap 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 Bootstrap use?
About 4.7k tokens (SKILL.md is roughly 19k 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 Bootstrap?
Skills that share tags, products or a category with Bootstrap: Johnny Suede Write (JasonColapietro/suede-creator-skills, 127 stars), Landing Page GTM Copy (ooiyeefei/ccc, 494 stars), Channel Strategy (TheCraigHewitt/skills, 157 stars) and Launch (menkesu/awesome-pm-skills, 433 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bootstrap?
manojbajaj95 (a GitHub user) maintains it in manojbajaj95/claude-gtm-plugin, which has 105 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on September 18, 2026.