team-collaboration-issue

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 an

Quality

36%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/team-collaboration-issue/SKILL.md

Quality

Content

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is brief and uses some structure, but its guidance is generic and non-executable, the multi-step issue-resolution workflow lacks concrete sequencing and validation, and its sole resource reference points to a file that is not bundled.

Suggestions

Replace abstract instructions with concrete, executable commands and examples (e.g., `gh issue view <id>`, a branch/commit naming convention, a PR body template).

Spell out a sequenced investigation workflow with explicit validation checkpoints (reproduce -> diagnose -> fix -> run tests -> verify -> open PR) rather than vague bullets.

Either add the referenced `resources/implementation-playbook.md` bundle file or remove the dangling reference so progressive disclosure points to real content.

Dimension	Reasoning	Score
Conciseness	The file is short, but the "Context" section ("The user needs comprehensive GitHub issue resolution that goes beyond simple fixes...") and the near-empty "Use this skill when / Do not use this skill when" sections are boilerplate framing Claude already understands and could be tightened.	2 / 3
Actionability	The instructions are abstract directives ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") with no concrete commands or code (e.g., gh issue view, git checkout -b); it describes rather than instructs.	1 / 3
Workflow Clarity	Steps are vague bullets with no real sequence or validation checkpoints for the risky operations involved (branch management, PR creation); "validate outcomes" is generic rather than an explicit checkpoint.	1 / 3
Progressive Disclosure	It signals a one-level reference to `resources/implementation-playbook.md` in both Instructions and Resources, but no `references/`, `scripts/`, `assets/`, or `resources/` directory exists, so the referenced file is a dangling path.	2 / 3
	Total	6 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description covers a coherent domain with several named actions, but it is truncated mid-word ("root cause an") and contains no explicit "Use when..." trigger, capping every dimension at 2.

Suggestions

Complete the truncated description and keep it under the 1024-char limit rather than cutting off mid-word.

Add an explicit "Use when..." trigger clause naming natural phrases a user would say (e.g., "Use when resolving GitHub issues, fixing bug reports, or preparing pull requests").

Add concrete action verbs the skill performs (e.g., "triage issues, reproduce bugs, implement fixes, open pull requests") rather than relying on abstract phrases like "collaborative development workflows".

Dimension	Reasoning	Score
Specificity	It names a domain and several actions ("systematic bug investigation, feature implementation, and collaborative development workflows", "issue triage, root cause an..."), but the field is literally truncated mid-word, cutting off the action list and leaving it incomplete.	2 / 3
Completeness	It states what the skill does ("GitHub issue resolution expert specializing in...") but never gives an explicit "when to use it" trigger, and the sentence is truncated mid-clause, so the "when" is missing.	2 / 3
Trigger Term Quality	"GitHub issue resolution expert" and "bug investigation"/"issue triage" are natural terms, but there is no explicit "Use when..." clause and common variations (bug report, pull request, fix an issue) are absent, worsened by the truncation.	2 / 3
Distinctiveness Conflict Risk	"GitHub issue resolution" is a fairly specific niche, but it could still overlap with generic git/PR workflow skills, and the mid-sentence truncation weakens how distinct the trigger reads.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/team-collaboration-issue/SKILL.md
Commit: e63f7dd

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.