AGENT SKILLBY MANOJBAJAJ95
Issue reporting
AT A GLANCE
Issue reporting is a general marketing agent skill from manojbajaj95. Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior. It is published in the manojbajaj95/claude-gtm-plugin GitHub repository (74 stars) under the MIT license. Install it with: npx skills add manojbajaj95/claude-gtm-plugin --skill issue-reporting
- SOURCE REPOSITORY
- manojbajaj95/claude-gtm-plugin (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- CATEGORIES
- SKILL.MD SIZE
- 5.1 KB141 LINES
QUICK ANSWER
- WHAT IT IS01
- Helps users report issues with GTM skills, incorrect advice, broken activation, missing context, or unexpected behavior. It stands out by giving issue reporting a defined shape, so the agent asks for better context and returns a more usable result.
- INPUTS02
- Context the agent needs: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add manojbajaj95/claude-gtm-plugin --skill issue-reportingREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 13
Issue Reporting#
Workspace Context#
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.
Operating Contract#
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.
When This Skill Activates#
- User says a skill gave wrong or harmful advice
- User says a skill isn't activating when it should
- User says their brand context wasn't applied
- User says output format is wrong or unexpected
- User wants to report a bug or file an issue
- User says "something is broken" about a skill
Step 1 — Identify the Problem#
Ask the user what went wrong. Determine:
- Which skill — get the exact skill name (e.g.
seo-and-aeo-strategy,copywriting-core) - What they asked — the exact prompt or task they gave Claude
- What happened — the actual output or behavior
- What they expected — what should have happened instead
If the user is vague ("it gave bad advice"), ask specifically what was incorrect and why.
Step 2 — Gather Context#
Check the user's project for context that helps diagnose the issue:
Context files#
Check if these exist and note their presence:
strategy/brand.md— brand positioning, messaging, audienceabout/me.md— personal voice, writing styleCLAUDE.md— AI instructions
Missing 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."
Plugin version#
Check .claude-plugin/plugin.json for the current version number.
Installation method#
Ask how they installed the plugin (Claude Code, Cowork, Skills CLI, git clone, submodule).
Step 3 — Classify the Issue#
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 |
Step 4 — Generate the Issue#
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.ymlFormatted 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]Step 5 — Offer Next Steps#
After generating the issue:
- Give them the direct link to file it:
https://github.com/manojbajaj95/claude-gtm-plugin/issues/new?template=bug_report.yml - If the problem is missing context files, suggest running
/bootstrapfirst - If it's clearly a skill bug, encourage them to file it — it helps improve the plugin for everyone
- Thank them for reporting — contributors who file clear issues are invaluable
Important#
- Never dismiss user frustration — if they think the advice is wrong, take it seriously
- Don't try to fix the skill yourself — this skill is for reporting, not patching
- Be specific in the issue — vague reports like "it didn't work" are hard to act on
- Include the actual output when possible — maintainers need to see what went wrong
Supporting file: .claude-plugin/plugin.json#
{
"name": "gtm-skills",
"version": "2.6.0",
"description": "Go-to-market skills for Claude Code — SEO, content, outbound, sales, growth, analytics, strategy, ads, social, and CRM",
"author": {
"name": "mbajaj"
}
}FAQ
07 QUESTIONS
01What is the Issue reporting agent skill?
Helps users report issues with GTM skills, incorrect advice, broken activation, missing context, or unexpected behavior. It is listed under general marketing in the 100xLab agent skills directory.
02How do I install Issue reporting in Cursor, Claude Code, or Codex?
Run npx skills add manojbajaj95/claude-gtm-plugin --skill issue-reporting in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Issue reporting, not every skill in the repository.
03What does the Issue reporting SKILL.md cover?
The SKILL.md includes sections on Workspace Context, Operating Contract, When This Skill Activates, Step 1 — Identify the Problem, Step 2 — Gather Context and Context files. Read the full text on this page or in plain markdown at /resources/agent-skills/manojbajaj95-claude-gtm-plugin--issue-reporting--1l8yj4e/raw.
04Which agents can use Issue reporting?
Issue reporting installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Issue reporting under?
The manojbajaj95/claude-gtm-plugin repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is Issue reporting free to use?
Reading, copying and installing Issue reporting costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of Issue reporting?
Issue reporting comes from https://github.com/manojbajaj95/claude-gtm-plugin, which has 74 GitHub stars. The SKILL.md is at https://github.com/manojbajaj95/claude-gtm-plugin/blob/HEAD/skills/issue-reporting/SKILL.md. The author is manojbajaj95.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Issue reporting was written by its original authors and is published in manojbajaj95/claude-gtm-plugin (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.