bin-scripts

Use when performing git operations, running Laravel/Composer commands, managing local dev sites, or killing processes on ports. Custom scripts in your PATH provide shortcuts for common workflows.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./claude/skills/bin-scripts/SKILL.md

Quality

Content

76%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 efficient, highly actionable catalog of PATH scripts organized into clean tables with concrete invocations. Its main weakness is the absence of validation or confirmation guidance around destructive operations (git abort, brew autoremove), which caps workflow clarity.

Suggestions

Add an explicit caution/validation note for destructive scripts — e.g. for 'git abort', instruct to confirm untracked files via 'git status' before running, and note that brewdump prompts interactively.

Consider moving the detailed cpanel panel tour and solo/mux internals into a separate reference file so SKILL.md stays a lean overview.

Annotate each destructive/batch script in its table cell with a brief precondition or post-run verification step.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, purpose-dense tables (script \| usage \| purpose) that assume Claude's competence, with only minor verbose spots like the cpanel panel-by-panel listing that could be trimmed.	4 / 5
Actionability	Every script entry pairs a concrete invocation with its purpose — e.g. 'git save file1 file2 "message"', 'killport 3000', 'artisan migrate' — giving copy-paste-ready commands that cover the common cases.	5 / 5
Workflow Clarity	This is a reference catalog rather than a sequenced workflow, but it documents destructive/batch operations like 'git abort' (hard reset + clean untracked) and brewdump's 'brew autoremove' without any validation or confirmation checkpoint guidance, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no bundle files referenced and no nested references; it is a single self-contained catalog, with only minor opportunity to split the longer cpanel/solo/mux detail into separate files.	4 / 5
	Total	16 / 20 Passed

Description

75%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 well-structured with an explicit 'Use when' trigger clause and concrete action categories spanning several dev-workflow domains. It is held back from top marks by the generic 'what' clause and broad 'git operations' phrasing rather than enumerated specific actions.

Dimension	Reasoning	Score
Specificity	Names several concrete action categories — 'git operations', 'running Laravel/Composer commands', 'managing local dev sites', 'killing processes on ports' — but 'git operations' is a broad domain label rather than enumerated specific actions, leaving minor coverage gaps versus a comprehensive 5.	4 / 5
Completeness	Explicitly provides both a 'what' ('Custom scripts in your PATH provide shortcuts for common workflows') and a 'when' ('Use when performing git operations, running Laravel/Composer commands...'); the 'what' is somewhat generic, keeping it just below a 5.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('git operations', 'Laravel/Composer commands', 'killing processes on ports') with good coverage, but lacks synonyms or specific script-name triggers a user might mention.	4 / 5
Distinctiveness Conflict Risk	The mix of git, Laravel/Composer, dev-site, and port-killing shortcuts is mostly distinct, though 'git operations' could overlap with a dedicated git skill, creating minor conflict risk.	4 / 5
	Total	16 / 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: joshmanders/dotfiles
Path: claude/skills/bin-scripts/SKILL.md
Commit: 54ab5f6

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