Gingiris Opensource
Gingiris/gingiris-opensource
🇺🇸 Open Source Marketing Playbook — How to get 10k+ GitHub stars.
Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior.
Install Issue Reporting
$ npx skills add manojbajaj95/claude-gtm-plugin --skill issue-reporting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin issue-reporting --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/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/issue-reporting .claude/skills/issue-reporting && 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 "issue-reporting" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reporting into .claude/skills/issue-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporting", 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/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reportingType 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 manojbajaj95/claude-gtm-plugin --skill issue-reporting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin issue-reporting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/issue-reporting .agents/skills/issue-reporting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-reporting" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reporting into .agents/skills/issue-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporting", 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 manojbajaj95/claude-gtm-plugin --skill issue-reporting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin issue-reporting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/issue-reporting .cursor/skills/issue-reporting && 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 "issue-reporting" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reporting into .cursor/skills/issue-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporting", 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/manojbajaj95/claude-gtm-plugin.git --path skills/issue-reporting--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 manojbajaj95/claude-gtm-plugin --skill issue-reporting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin issue-reporting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/issue-reporting .gemini/skills/issue-reporting && 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 "issue-reporting" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reporting into .gemini/skills/issue-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporting", 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 manojbajaj95/claude-gtm-plugin issue-reportingInstalls 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 manojbajaj95/claude-gtm-plugin --skill issue-reporting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/issue-reporting .github/skills/issue-reporting && 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 "issue-reporting" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reporting into .github/skills/issue-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporting", 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 manojbajaj95/claude-gtm-plugin --skill issue-reporting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install manojbajaj95/claude-gtm-plugin issue-reporting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/issue-reporting .opencode/skills/issue-reporting && 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 "issue-reporting" agent skill from https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/issue-reporting into .opencode/skills/issue-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-reporting", 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
issue-reporting- GitHub stars
- 105
- Token cost
- ~1.4k tokens
- SKILL.md length
- 601 words
- Files
- 1
- Skills in repo
- 52
- Repo updated
- First seen
- Licence
- MIT
At a glance
Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior.
- Works in 5 steps: Identify the Problem → Gather Context → Classify the Issue → …
- Users say: this skill gave wrong advice
- SKILL.md covers Workspace Context, Operating Contract, When This Skill Activates and Step 1 — Identify the Problem, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Issue Reporting is an agent skill from manojbajaj95/claude-gtm-plugin. 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'.
Its SKILL.md is about 1.4k 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. It works with GitHub. The licence is MIT.
When your agent uses it
- Users say: this skill gave wrong advice
- Skill isnt working
- Skill didnt activate
- Bad recommendation
Example prompts
- “this skill gave wrong advice”
- “report a bug”
- “file an issue”
- “/issue-reporting”
Workflow steps
5 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 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
Issue Reporting loads about 1.4k tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 601 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 manojbajaj95/claude-gtm-plugin at commit 0830a46, republished under its MIT licence (© manojbajaj95). 601 words, ~1,356 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-reporting/SKILL.md (or your agent's skills folder).- name
- issue-reporting
- description
- 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'.
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).
Show full SKILL.md (243 more words)Show less
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
© manojbajaj95, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/issue-reporting of manojbajaj95/claude-gtm-plugin.
Open the folder on GitHubat commit 0830a46
Compare with similar skills
Issue Reporting 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 |
|---|---|---|---|---|---|---|
| Issue Reporting this skillmanojbajaj95/claude-gtm-plugin | 105 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Gingiris OpensourceGingiris/gingiris-opensource | 256 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Yalc OrientationOthmane-Khadri/YALC-the-GTM-operating-system | 317 | — | ~1k | Automated safety check: Notes | MIT | |
| Landing Page GTM Copyooiyeefei/ccc | 494 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Metadata Checkjdevalk/skills | 105 | — | ~1k | Automated safety check: Pass | MIT | |
| Channel StrategyTheCraigHewitt/skills | 157 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Yalc Orientation
Othmane-Khadri/YALC-the-GTM-operating-system
First-touch onboarding for someone who just opened the YALC repo.
Landing Page GTM Copy
ooiyeefei/ccc
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.
Metadata Check
jdevalk/skills
Reviews short high-value strings — page titles, meta descriptions, schema description fields, FAQ answers, GitHub repo taglines, profile bios, social-card copy, and other metadata where Flesch and…
Channel Strategy
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
Launch
menkesu/awesome-pm-skills
Builds a launch plan, launch story and press/distribution plan, then drafts the pitch emails and announcement copy.
More from manojbajaj95/claude-gtm-plugin
All 52 skills in this repoApp Store Optimization
manojbajaj95/claude-gtm-plugin
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.
Market Research Analysis
manojbajaj95/claude-gtm-plugin
Comprehensive market research and analysis skill. An agent skill from manojbajaj95/claude-gtm-plugin.
Pitch Deck Creation
manojbajaj95/claude-gtm-plugin
Create professional investor pitch decks with structured content and visual design.
Qr Code Generator
manojbajaj95/claude-gtm-plugin
Generate QR codes with URLs and UTM tracking. An agent skill from manojbajaj95/claude-gtm-plugin.
SEO And Aeo Strategy
manojbajaj95/claude-gtm-plugin
SEO, AEO (Answer Engine Optimization), and GEO strategy for search engines and AI visibility.
Linkedin
manojbajaj95/claude-gtm-plugin
LinkedIn profile optimization and content creation. An agent skill from manojbajaj95/claude-gtm-plugin.
Related
Works with
Categories
Questions about Issue Reporting
What does Issue Reporting do?
Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior. Issue Reporting is an agent skill from manojbajaj95/claude-gtm-plugin. Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior.
When should I use Issue Reporting?
Issue Reporting fits situations like: users say: this skill gave wrong advice; skill isnt working; skill didnt activate; bad recommendation.
How do I install Issue Reporting in Claude Code?
Run `npx skills add manojbajaj95/claude-gtm-plugin --skill issue-reporting -a claude-code`. Or copy the skill folder (skills/issue-reporting in manojbajaj95/claude-gtm-plugin) into .claude/skills/issue-reporting in your project. Claude Code loads it when a task matches its description.
How do I install Issue Reporting in Codex?
Run `npx skills add manojbajaj95/claude-gtm-plugin --skill issue-reporting -a codex`. Or copy the skill folder (skills/issue-reporting in manojbajaj95/claude-gtm-plugin) into .agents/skills/issue-reporting in your project. Codex loads it when a task matches its description.
Can I use Issue Reporting 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 issue-reporting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-reporting, .gemini/skills/issue-reporting, .github/skills/issue-reporting and .opencode/skills/issue-reporting in your project.
What does Issue Reporting need to run?
SKILL.md names no scripts, command-line tools or credentials: Issue Reporting is instructions for the agent only.
Does Issue Reporting 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 Issue Reporting 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 Issue Reporting use?
Issue Reporting 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 Issue Reporting use?
About 1.4k tokens (SKILL.md is roughly 5.4k 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 Issue Reporting?
Skills that share tags, products or a category with Issue Reporting: Gingiris Opensource (Gingiris/gingiris-opensource, 256 stars), Yalc Orientation (Othmane-Khadri/YALC-the-GTM-operating-system, 317 stars), Landing Page GTM Copy (ooiyeefei/ccc, 494 stars) and Metadata Check (jdevalk/skills, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Reporting?
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.
Source: manojbajaj95/claude-gtm-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.