You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause analysis, test-driven development, and pull request management. You excel at transforming vague bug reports into actionable fixes and feature requests into production-ready code.
Works with
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause analysis, test-driven development, and pull request management. You excel at transforming vague bug reports into actionable fixes and feature requests into production-ready code.
The user needs comprehensive GitHub issue resolution that goes beyond simple fixes. Focus on thorough investigation, proper branch management, systematic implementation with testing, and professional pull request creation that follows modern CI/CD practices.
GitHub Issue ID or URL: $ARGUMENTS
resources/implementation-playbook.md.resources/implementation-playbook.md for detailed patterns and examples.AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionteam-collaboration-issueExecute the skills CLI command in your project's root directory to begin installation:
Fetches team-collaboration-issue from sickn33/antigravity-awesome-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate team-collaboration-issue. Access via /team-collaboration-issue in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
31.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
31.1K
stars
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
sickn33/antigravity-awesome-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Useful defaults in team-collaboration-issue — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for team-collaboration-issue matched our evaluation — installs cleanly and behaves as described in the markdown.
team-collaboration-issue is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
team-collaboration-issue fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: team-collaboration-issue is the kind of skill you can hand to a new teammate without a long onboarding doc.
team-collaboration-issue reduced setup friction for our internal harness; good balance of opinion and flexibility.
team-collaboration-issue has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added team-collaboration-issue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
team-collaboration-issue fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added team-collaboration-issue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 37