agent-github-modes

Agent skill for github-modes - invoke with $agent-github-modes

1.07x

Quality

Does it follow best practices?

Impact

86%

1.07x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-github-modes/SKILL.md

Quality

Discovery

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

This is an extremely weak description that fails on all dimensions. It provides no information about what the skill does, when it should be used, or what specific capabilities it offers. It reads more like an internal label than a functional description.

Suggestions

Describe the specific actions this skill performs (e.g., 'Switches between GitHub workflow modes such as PR review, issue triage, and branch management').

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user wants to change GitHub workflow mode, review PRs, manage issues, or switch between GitHub operational contexts').

Remove the invocation command ('invoke with $agent-github-modes') from the description and replace it with concrete capability details that help Claude distinguish this skill from other GitHub-related skills.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for github-modes' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an 'agent skill' and provides an invocation command, with no explanation of functionality or usage triggers.	1 / 3
Trigger Term Quality	The only keyword is 'github-modes' which is a technical/internal term, not something a user would naturally say. There are no natural trigger terms like 'pull request', 'branch', 'merge', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could overlap with any GitHub-related skill. 'github-modes' is undefined and provides no clear niche or distinct triggers.	1 / 3
	Total	4 / 12 Passed

Implementation

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

This skill is a catalog of mode descriptions rather than actionable instructions. It lists 10+ GitHub integration modes with abstract metadata bullet points but provides no concrete workflows, executable commands, validation steps, or real examples. The content is extremely verbose while simultaneously lacking substance—it describes capabilities without teaching Claude how to perform any of them.

Suggestions

Replace abstract mode descriptions with concrete, step-by-step workflows showing actual gh CLI commands and their expected outputs for the most common operations (e.g., creating a PR, managing a release).

Add validation checkpoints to workflows—e.g., after creating a PR, check its status with `gh pr view`; after merging, verify the branch was deleted.

Reduce the 10+ mode catalog to a concise reference table, and move detailed instructions for each mode into separate files with clear cross-references.

Replace pseudocode examples (the batch operations JavaScript block, swarm integration block) with actual executable commands or remove them entirely.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with repetitive structure across 10+ modes that all follow the same template pattern. Most content is descriptive metadata (bullet points like 'Review Quality: Deep', 'Security Analysis: Yes') that provides no actionable value. The overview sentence explains what the document is, which is unnecessary.	1 / 3
Actionability	Despite listing many modes and tools, there is no concrete, executable guidance for any workflow. The 'usage' lines reference a `$github` command pattern that is never defined or explained. Code examples are pseudocode-like (the batch operations JavaScript block is not real executable code), and the swarm integration example uses undefined syntax.	1 / 3
Workflow Clarity	No multi-step workflows are defined anywhere. Each mode is described with abstract bullet points but never shows a sequence of steps to accomplish a task. There are no validation checkpoints, error handling, or feedback loops for any of the complex operations described (PR management, releases, CI/CD).	1 / 3
Progressive Disclosure	The entire content is a monolithic wall of repetitive mode descriptions with no references to external files. All 10+ modes are listed inline with identical formatting, making it hard to navigate. No content is split into separate reference files despite the document being very long.	1 / 3
	Total	4 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: 398f7c2

Reviewed: 2 days 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.