Issue Reporting

Community

manojbajaj95

issue-reporting

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'.

Overview

Publisher	manojbajaj95
Repository	`claude-gtm-plugin`
Skill name	`issue-reporting`
Stars	109
Forks	34
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by manojbajaj95 on GitHub. Read the source before you install it.

Installation

Install the Issue Reporting AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reporting
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git /tmp/claude-gtm-plugin
mkdir -p .claude/skills
cp -r /tmp/claude-gtm-plugin/skills/issue-reporting .claude/skills/issue-reporting

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Issue Reporting in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Issue Reporting on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Issue Reporting is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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, audience
about/me.md — personal voice, writing style
CLAUDE.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 /bootstrap to 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.yml

Formatted issue body (if they prefer to paste manually):

markdown
**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 /bootstrap first
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

Frequently asked questions

What does the Issue Reporting AI skill do?

Why use Issue Reporting on TypingMind?

Because you install it once and use it with any model. Issue Reporting is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Issue Reporting in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reporting. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Issue Reporting?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Issue Reporting?

As many as you like. As long as a model supports skills, you can use Issue Reporting with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Issue Reporting AI skill free?

Yes. It is published on GitHub by manojbajaj95 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Karpathy Guidelines

multica-ai

OrganizationPopular

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define…

Create Agent

Create a custom agent (.agent.md) for a specific job.

Create Hook

Create a hook (.json) to enforce policy or automate agent lifecycle events.

Generate Run Commands

microsoft

OrganizationPopular

Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Issue Reporting

Workspace Context

Operating Contract

When This Skill Activates

Step 1 — Identify the Problem

Step 2 — Gather Context

Context files

Plugin version

Installation method

Step 3 — Classify the Issue

Step 4 — Generate the Issue

Step 5 — Offer Next Steps

Important

Frequently asked questions

Related AI Skills

Set up your own AI workspace now