stage

Stage files, run pre-commit, fix failures, loop until clean

1.00x

Quality

75%

Does it follow best practices?

Impact

67%

1.00x

Average score across 1 eval scenario

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/stage/SKILL.md

Quality

Content

92%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 a lean, well-structured workflow with concrete commands, an explicit validation feedback loop, and clear sequencing; only minor actionability gaps keep it from a perfect actionability score.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or over-explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Provides concrete executable commands (git status, git add, pre-commit run, git diff --cached) but 'Fix the issues' and 'all relevant changed files' are mild gaps in specificity.	4 / 5
Workflow Clarity	Clear four-step sequence with an explicit validation checkpoint (pre-commit pass/fail), a fix→re-stage→retry feedback loop, and a bounded 5-attempt stop condition.	5 / 5
Progressive Disclosure	Under 50 lines, single-purpose, no external references needed, and well-organized into clearly labeled Step sections — meeting the simple-skill exception for a 5.	5 / 5
	Total	19 / 20 Passed

Description

58%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 concise and action-oriented with a clear niche, but it omits any explicit 'when to use' trigger guidance and lacks synonym coverage, limiting trigger-term and completeness scores.

Suggestions

Add a 'Use when…' clause naming concrete trigger phrases (e.g. 'Use when staging changes before a commit or when pre-commit hooks need to pass').

Include natural synonyms users say, such as 'git add' and 'commit', to broaden trigger-term coverage.

Specify what gets staged (e.g. tracked vs untracked files) to reduce the minor specificity gap.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Stage files, run pre-commit, fix failures, loop until clean') but is terse with minor coverage gaps rather than a comprehensive enumeration.	4 / 5
Completeness	The 'what' is clear (stage, pre-commit, fix, loop) but there is no 'Use when…' or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'stage' and 'pre-commit' are natural user terms, but common synonyms and variations like 'git add' and 'commit' are missing.	3 / 5
Distinctiveness Conflict Risk	The staging-plus-pre-commit niche is mostly distinct with only minor overlap risk against a general git/commit skill.	4 / 5
	Total	14 / 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: PaloAltoNetworks/shifter
Path: .claude/skills/stage/SKILL.md
Commit: c46caa4

Reviewed: 14 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.