manage-github-tickets

Create and manage GitHub issues using the GODS framework. Use when creating, updating, or triaging GitHub issues.

Quality

81%

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

Quality

Content

75%Weight 40%Scale 1-5

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

A well-structured, actionable skill body with a clear workflow and a verification step. The main weaknesses are mild redundancy between the step-2 structure and the GODS summary, and a relatively soft validation checkpoint.

Suggestions

Consolidate the GODS structure: keep the guiding questions in "GODS Framework Summary" and reference them from step 2 rather than restating all four elements in both places.

Strengthen the Verify step into an explicit validate-then-retry gate (e.g., re-confirm the GODS sections are present before creation, and on failure attempt a fix before falling back to manual creation).

Add one fully filled `gh issue create` command (with a real title/body derived from the example) so the executable path is copy-paste ready end to end.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and no concept over-explanation, but the GODS structure in step 2 is restated in the "GODS Framework Summary" section, a minor redundancy that could be trimmed.	4 / 5
Actionability	Provides executable commands (`gh issue create --title "..." --body "..."`), named MCP tools (`create_issue`, `update_issue`), and a full worked example; minor gaps are the placeholder title/body and absence of an end-to-end filled command.	4 / 5
Workflow Clarity	A clear four-step sequence ends with a Verify checkpoint and an error-recovery fallback, but validation is relatively light ("confirm created") and GODS-format compliance is not explicitly re-checked, leaving a minor gap versus a full validate-then-retry gate.	4 / 5
Progressive Disclosure	Well-organized into labeled sections with one-level-deep, clearly signaled references to `write-gods-tasks`; no bundle files exist, and the inlined GODS summary is reasonable for a skill of this size, with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

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

A tight, third-person description that clearly states the skill's purpose and trigger conditions with concrete action verbs. Only minor gaps in synonym coverage prevent a perfect score.

Dimension	Reasoning	Score
Specificity	Names the domain (GitHub issues) and several concrete actions — "Create", "manage", and the trigger list "creating, updating, or triaging" — giving good coverage with only the generic "manage" as a minor gap.	4 / 5
Completeness	Explicitly answers both what ("Create and manage GitHub issues using the GODS framework") and when ("Use when creating, updating, or triaging GitHub issues") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"GitHub issues" plus "creating, updating, or triaging" are natural phrases users say, but synonyms like "tickets" (used in the skill name) and broader phrasings are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The GODS-framework framing carves a clear niche around GitHub issue management with distinct triggers, keeping conflict risk with generic GitHub skills minimal.	5 / 5
	Total	18 / 20 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: korchasa/flowai-plugins
Path: plugins/flowai-engineering/skills/manage-github-tickets/SKILL.md
Commit: b4ba256

Reviewed: ~21 hours 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.