CtrlK
BlogDocsLog inGet started
Tessl Logo

github-action-review

Review fallow's GitHub Action, shell scripts, jq filters, annotations, review comments, and workflow integration. Use when changes touch action/, action.yml, GitHub review formatting, or CI shell/jq behavior.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, well-structured instruction-only review skill with excellent token efficiency and a clear verdict contract. Its main weakness is that the prioritized concerns are stated as abstract categories rather than concrete, executable review checks, and it leans on external .agents/ files that are not part of the skill bundle.

Suggestions

Convert each prioritized concern into a concrete check, e.g. 'shell safety: flag unquoted expansions, missing set -euo pipefail, and unchecked cd' instead of the bare category 'shell safety'.

Number the workflow (1. Read the listed files, 2. Review changed artifacts against each priority, 3. Emit APPROVE/CONCERN/BLOCK) and add an explicit checkpoint that all five priorities were assessed before producing the verdict.

Clarify that the 'Read:' paths are external repo files (or move the methodology into a references/ file within the bundle) so the skill is self-contained and the references resolve predictably.

DimensionReasoningScore

Conciseness

Lean ~15-line body that assumes Claude's competence and omits all concept explanation; every line (Read list, review directive, priorities, verdict contract) earns its place.

5 / 5

Actionability

Provides a concrete read list, specific review targets, and a concrete output contract ('End with APPROVE, CONCERN, or BLOCK'), but the priorities ('shell safety', 'token handling') are categories rather than executable checks, leaving minor how-to gaps.

4 / 5

Workflow Clarity

A clear implied sequence (read reference files, review changed artifacts against the priorities, emit a verdict) for a single-purpose review skill, but it is unnumbered and lacks an explicit checkpoint confirming all priorities were addressed before the verdict.

4 / 5

Progressive Disclosure

Well-organized lean overview with a clearly signaled one-level-deep 'Read:' reference list, but the references point to external '.agents/' paths outside the skill bundle rather than bundle files, a minor organization gap since the body heavily relies on those unverified external files.

4 / 5

Total

17

/

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 strong, third-person description that clearly states what the skill reviews and when to invoke it, with concrete file-path and CI-behavior triggers tied to a specific project's GitHub Action. Minor specificity gains are possible by expanding the single 'Review' verb into distinct review actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete review targets ('shell scripts, jq filters, annotations, review comments, and workflow integration'), but the single verb 'Review' leaves minor coverage gaps versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly answers both 'what' (review the action, scripts, jq filters, annotations, comments, workflow integration) and 'when' ('Use when changes touch action/, action.yml, GitHub review formatting, or CI shell/jq behavior') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage including concrete triggers users would say ('GitHub Action', 'action.yml', 'CI shell/jq behavior', 'changes touch action/'), with only a few natural synonyms missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'fallow's GitHub Action' with niche-specific triggers (action.yml, jq filters, CI shell behavior), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

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
fallow-rs/fallow
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.