CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-github-modes

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

52

1.07x
Quality

30%

Does it follow best practices?

Impact

86%

1.07x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-github-modes/SKILL.md

The canonical home for this skill is agent-github-modes in ruvnet/claude-flow

SKILL.md
Quality
Evals
Security

Quality

Content

36%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.

The body is an over-claimed mode catalog: well-sectioned but padded with non-actionable attributes, a duplicated frontmatter block, and invented invocation syntax, with no real workflow sequencing or validation. It reads as marketing-style enumeration rather than executable skill guidance.

Suggestions

Remove the duplicated YAML frontmatter block inside the body and the buzzword attribute lists; keep only concrete tool lists and invocation syntax.

Add at least one end-to-end sequenced workflow (e.g., PR review -> checks -> merge) with explicit validation checkpoints before destructive/batch actions.

Replace the non-executable '$github <mode>' pseudo-syntax with real, runnable gh CLI commands or document clearly that these are invocation conventions.

DimensionReasoningScore

Conciseness

The body is padded with buzzword attribute lists ('Intelligent', 'Advanced', 'Proactive', 'Automated') and a stray duplicated YAML frontmatter block that add no executable value.

2 / 5

Actionability

Usage examples and bash/mcp snippets give some concrete form, but the mode entries rely on attribute descriptors and non-executable '$github <mode>' invocation syntax rather than runnable steps.

3 / 5

Workflow Clarity

The content is a mode catalog with no sequenced workflow or validation checkpoints; the batch-operations section lacks validation, capping clarity well below 3.

2 / 5

Progressive Disclosure

Clear section headers organize the modes, but everything is inlined in one monolithic file with no references to supporting files and no bundle structure to navigate.

3 / 5

Total

10

/

20

Passed

Description

25%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.

The description is a generic, self-referential label that fails to convey concrete capabilities or explicit usage triggers. It reads as a placeholder rather than actionable skill metadata.

Suggestions

Replace the description with concrete actions (e.g., 'Orchestrate GitHub workflows, manage PRs, track issues, and coordinate releases across repositories').

Add an explicit 'Use when...' clause listing natural user triggers such as 'reviewing a PR', 'coordinating a release', or 'managing issues'.

Drop the 'invoke with $agent-github-modes' meta-instruction from the description; it is not a capability statement.

DimensionReasoningScore

Specificity

The phrase 'Agent skill for github-modes' names the domain but describes no concrete actions, leaving what the skill actually does unspecified.

2 / 5

Completeness

It offers only a tautological 'what' (an agent skill for github-modes) and no 'when' guidance, with no 'Use when...' clause present.

2 / 5

Trigger Term Quality

The only trigger cue is 'invoke with $agent-github-modes' plus the word 'github'; it lacks the natural phrases a user would say when needing this skill.

2 / 5

Distinctiveness Conflict Risk

The generic 'Agent skill for X' framing is very broad and would overlap with many other GitHub-related skills.

2 / 5

Total

8

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/ruflo
Reviewed

Table of Contents

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.