stage

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

1.00x

Quality

83%

Does it follow best practices?

Impact

67%

1.00x

Average score across 1 eval scenario

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

The content is a tight, fully executable workflow with clear sequencing, an explicit validation loop, and well-organized sections appropriate for a simple skill.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding and no explanation of concepts Claude already knows; every line is an instruction or command that earns its place.	3 / 3
Actionability	It provides fully executable commands — 'git status', 'git add', 'pre-commit run --all-files', 'git diff --cached --name-only' — with a concrete exclusion list, copy-paste ready.	3 / 3
Workflow Clarity	Steps are clearly sequenced with an explicit validation checkpoint (pre-commit pass/fail), a feedback loop (fix -> re-stage -> retry), and a bounded 5-iteration cap with a fallback report.	3 / 3
Progressive Disclosure	This is a simple, under-50-line single-task skill with no need for external references; its well-organized sections satisfy progressive disclosure per the simple-skills note.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 lacks an explicit 'Use when' trigger clause and only covers a narrow set of natural trigger terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when staging changes before a commit or when pre-commit hooks are failing.'

Broaden trigger terms to include natural user phrasings like 'commit', 'git add', 'lint', or 'hooks'.

Keep the current concrete action list but pair it with the 'when' guidance to lift completeness to 3.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions — 'Stage files, run pre-commit, fix failures, loop until clean' — each tied to an actual operation rather than abstract language.	3 / 3
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Terms like 'stage files', 'pre-commit', and 'fix failures' are natural, but common variations a user might say ('commit', 'git add', 'lint', 'hook') are missing, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The pre-commit staging loop is a distinct niche with specific triggers unlikely to collide with other skills.	3 / 3
	Total	10 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PaloAltoNetworks/shifter
Path: .claude/skills/stage/SKILL.md
Commit: 9c0fe10

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