Skills team-collaboration-issue

📦

team-collaboration-issue

Name: team-collaboration-issue
Author: sickn33

Content revision r1 Safe ⚙️ External commands🌐 Network access

Resolve GitHub Issues With Team Workflow

Issue work often stalls when investigation, fixes, tests, and pull requests are handled separately. This skill guides a structured workflow from triage to verification.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "team-collaboration-issue" from https://skillstore.io/skills/sickn33-team-collaboration-issue.md and its manifest at https://skillstore.io/api/skills/sickn33-team-collaboration-issue/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-team-collaboration-issue.md Signed manifest GET /api/skills/sickn33-team-collaboration-issue/manifest Signed lockfile GET /api/skills/sickn33-team-collaboration-issue/lockfile

Test it

Using "team-collaboration-issue". A bug report says login fails after token expiry.

Expected outcome:

The skill returns a triage summary, reproduction plan, likely root cause areas, test targets, implementation steps, and pull request guidance.

Using "team-collaboration-issue". A feature request needs profile customization with backend and frontend changes.

Expected outcome:

The skill breaks the request into phases, suggests ownership boundaries, identifies tests, and prepares review-ready delivery notes.

Using "team-collaboration-issue". A slow query issue affects a high-traffic page.

Expected outcome:

The skill guides measurement, query investigation, optimization validation, regression tests, deployment checks, and rollback planning.

Security Audit

Safe

v5 • 7/7/2026 Open versioned report

All static findings appear to be false positives in documentation examples, not executable skill code. The files contain GitHub, git, npm, and curl examples for normal issue-resolution workflows, with no prompt injection or exfiltration intent found.

Files scanned

679

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (5)

resources/implementation-playbook.md:92-96 resources/implementation-playbook.md:611-619 resources/implementation-playbook.md:376-388 SKILL.md:33 SKILL.md:37

🌐 Network access (2)

resources/implementation-playbook.md:320 resources/implementation-playbook.md:452

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-team-collaboration-issue/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-team-collaboration-issue/security.svg)](https://skillstore.io/skills/sickn33-team-collaboration-issue?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-team-collaboration-issue?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-team-collaboration-issue/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-team-collaboration-issue.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). team-collaboration-issue security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-team-collaboration-issue/audits/5

BibTeX citation

@techreport{sickn33-sickn33-team-collaboration-issue-2026,
  author = {sickn33},
  title = {team-collaboration-issue security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-team-collaboration-issue/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "team-collaboration-issue security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-team-collaboration-issue/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-team-collaboration-issue:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Triage incoming bug reports

Maintainers can classify severity, gather missing context, and find related issues before assigning implementation work.

Implement verified fixes

Engineers can move from reproduction to root cause, tests, code changes, and pull request evidence.

Coordinate release follow-up

Technical leads can plan verification, deployment monitoring, closure comments, and rollback notes for critical issues.

Try These Prompts

Start Issue Triage

Use this skill for GitHub issue #123. Summarize the report, classify priority, list missing context, and suggest next steps.

Plan a Bug Fix

Use this skill to plan a fix for issue #123. Include likely root causes, files to inspect, tests to add, and branch naming.

Prepare a Pull Request

Use this skill to prepare the pull request for issue #123. Draft the summary, testing evidence, risk notes, and reviewer checklist.

Coordinate Critical Resolution

Use this skill for a critical production issue. Create a triage plan, hotfix workflow, verification checklist, communication plan, and rollback notes.

Best Practices

Start with issue facts, reproduction steps, linked work, and clear acceptance criteria.
Add tests that prove the fix and protect the affected workflow from regressions.
Include concise pull request evidence, verification steps, and known risks for reviewers.

Avoid

Starting code changes before confirming the expected behavior and reproduction path.
Closing issues without test evidence, reviewer context, or a clear pull request reference.
Copying example commands without adapting them to repository tooling and permissions.

Frequently Asked Questions

Does this skill require GitHub CLI access?

No, but many examples use GitHub CLI. Users can adapt the workflow to browser or API-based issue management.

Can it fix issues automatically?

It can guide investigation, implementation, tests, and pull request preparation. The user still controls repository changes and approvals.

Is it only for bugs?

No. It also supports feature requests, performance work, release follow-up, and documentation updates tied to issues.

Does it choose the final priority?

It suggests priority using impact, severity, and workaround signals. Team policy should decide the final classification.

Can it work with Claude, Codex, and Claude Code?

Yes. The workflow is written for agent-assisted development across Claude, Codex, and Claude Code.

What inputs produce the best results?

Provide the issue URL, repository context, expected behavior, reproduction notes, test commands, and project constraints.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/team-collaboration-issue

Ref

9f814fc6a43fd99946f2da5e0df231c65a38bc76

Maintenance freshness

7/18/2026

Usage

7 downloads · 86 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md