Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior. Guides through gathering the right details (skill name, prompt used, actual vs expected output, context files present) and generates a properly formatted GitHub issue. Use when users say: 'this skill gave wrong advice', 'report a bug', 'file an issue', 'skill isn't working', 'wrong output', 'skill didn't activate', 'bad recommendation', 'incorrect behavior', or 'something is broken'.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.
This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.
Help users report problems with GTM skills clearly and completely so maintainers can fix them fast.
Ask the user what went wrong. Determine:
seo-and-aeo-strategy, copywriting-core)If the user is vague ("it gave bad advice"), ask specifically what was incorrect and why.
Check the user's project for context that helps diagnose the issue:
Check if these exist and note their presence:
strategy/brand.md — brand positioning, messaging, audienceabout/me.md — personal voice, writing styleCLAUDE.md — AI instructionsMissing context files are the most common cause of "wrong advice" bugs. If strategy/brand.md or about/me.md are missing, tell the user:
"The skill may have given generic advice because your brand context files are missing. Run
/bootstrapto set them up. If the skill still gives wrong advice after that, then it's a real bug worth reporting."
Check .claude-plugin/plugin.json for the current version number.
Ask how they installed the plugin (Claude Code, Cowork, Skills CLI, git clone, submodule).
Categorize into one of these types:
| Type | Description | Common cause |
|---|---|---|
| Wrong advice | Skill produced incorrect or harmful recommendations | Outdated framework, wrong domain assumptions |
| Not activating | Skill should have triggered but didn't | Description mismatch, trigger phrase gap |
| Wrong activation | Skill triggered when it shouldn't have | Overly broad description |
| Missing context | Brand/voice not applied to output | Context files missing or not read |
| Bad format | Output structure is wrong | Skill template issue |
| Crash/error | Skill fails mid-execution | Syntax error in skill, bad reference path |
Compose a GitHub issue using the bug report template. Format it so the user can copy-paste or click through:
Direct link (pre-fills the template):
https://github.com/manojbajaj95/claude-gtm-plugin/issues/new?template=bug_report.yml
Formatted issue body (if they prefer to paste manually):
**Skill**: [skill-name]
**Type**: [category from Step 3]
**Plugin Version**: [version]
**Installation**: [method]
### What I asked
[exact prompt]
### What happened
[actual output — include relevant excerpt]
### What I expected
[expected behavior]
### Context files present
- [ ] strategy/brand.md
- [ ] about/me.md
- [ ] CLAUDE.md
### Steps to reproduce
1. [step-by-step if applicable]
### Impact
[Critical / High / Medium / Low]
After generating the issue:
https://github.com/manojbajaj95/claude-gtm-plugin/issues/new?template=bug_report.yml/bootstrap firstまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see data-and-funnel-analytics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, managing, or optimizing paid advertising campaigns across any platform. Covers ad copy generation, ad creative strategy, campaign management, and competitive intelligence. Triggers on: ad copy, ad creative, paid ads, paid advertising, Facebook ads, LinkedIn ads, Google ads, Meta ads, ad campaign, ad strategy, ad testing, competitive ads, competitor ads, ad library, ad analysis, ad creative generation, campaign management, ROAS, CPC, CTR. Use this skill whenever the user mentions ads, paid channels, ad campaigns, ad copy, ad performance, or wants to analyze competitor advertising.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when optimizing app store listings, researching keywords, or tracking mobile app performance on Apple App Store and Google Play Store.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. Use when: (1) writing, editing, or proofreading a blog article or post, (2) transforming unstructured brain dumps into polished posts, (3) writing in specific personal voices (Jarad, Nick Nisi), (4) creating category-aware technology/company/product posts, (5) building tutorials, deep dives, postmortems, benchmarks, or architecture posts, (6) writing engineering blogs, dev blogs, programming blogs, coding tutorials, or documentation posts. Triggers: blog post, blog writing, technical blog, dev tutorial, brain dump, article, content writing, developer article, engineering blog, programming blog, coding tutorial, documentation post, technical writing, blog editing, proofreading, developer content
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive brand messaging, positioning, and value proposition development using proven frameworks including Peep Laja Message Layers, Osterwalder Value Proposition Canvas, Geoffrey Moore positioning, April Dunford's Five Components, StoryBrand SB7, Andy Raskin Strategic Narrative, and Messaging House. Use when developing brand identity, brand messaging architecture, positioning statements, value propositions, messaging hierarchies, brand pillars, taglines, one-liners, elevator pitches, brand guidelines, visual identity systems, or creating Positioning & Messaging Packs. Triggers include: messaging framework, brand positioning, value prop, messaging architecture, brand pillars, brand identity, StoryBrand, positioning statement, brand guidelines, design system, messaging house, corporate identity, brand voice, visual standards.
日本語の概要は準備中です。原文の説明を表示しています。