windows-shell-commands

Running shell commands on this Windows checkout via the PowerShell and Bash tools, and passing multi-line or quoted arguments (commit messages, PR bodies, file content) without corruption. Use when running git or gh with multi-line or quoted input, writing a commit message or PR body from the command line, reaching for a heredoc or here-string, or after a message or body comes out wrapped in stray characters such as a leading and trailing `@`.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%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 concise, highly actionable skill body that gives copy-paste examples for the real failure mode (cross-shell heredoc corruption) and a robust fallback (write a file, pass by path). The only gap is the absence of an explicit validation loop, which the single-purpose guidance nature of the skill largely excuses.

Suggestions

Consider adding a one-line verification cue after the write-a-file fallback (e.g. 'then confirm the commit/PR shows the body uncorrupted') to close the workflow loop and lift workflow_clarity to 5.

The 'Rule of thumb' restates guidance already in the section bodies; trimming it to a single sentence would tighten conciseness without losing clarity.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence: it does not explain what shells, heredocs, or here-strings are, and the 'Symptom of getting it wrong' section conveys genuinely non-obvious knowledge (the `@`-corruption cause) rather than padding. Every token earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready examples for both shells — PowerShell `git commit -m @'...'@`, Bash `git commit -F - <<'EOF'`, multiple `-m` flags, and `gh pr create ... --body-file` — covering the common multi-line and quoted-input cases.	5 / 5
Workflow Clarity	Clear decision sequence (default PowerShell → when to use Bash → symptom → per-shell solutions → write-a-file fallback → rule of thumb) with the 'Symptom of getting it wrong' section acting as a diagnostic checkpoint. Not a 5 because there is no explicit multi-step validate→fix→retry loop, though the single-purpose guidance nature of the skill does not demand one.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are empty) and none are needed; the body is a short, well-organized set of clearly-headed sections with no nested or buried references, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	19 / 20 Passed

Description

100%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 tightly-scoped, highly specific description that clearly states both what the skill does and when to use it, with natural trigger phrases including a concrete diagnostic symptom. It risks over-triggering only at the legitimate boundary of multi-line shell input.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions and artifacts — 'Running shell commands ... via the PowerShell and Bash tools' and 'passing multi-line or quoted arguments (commit messages, PR bodies, file content) without corruption' — giving comprehensive coverage of its niche.	5 / 5
Completeness	Explicitly answers both what (running Windows shell commands and passing multi-line/quoted args without corruption) and when, with a concrete 'Use when running git or gh ... writing a commit message or PR body ... reaching for a heredoc or here-string, or after a message or body comes out wrapped in stray characters'.	5 / 5
Trigger Term Quality	Uses natural trigger terms users would actually say — 'git or gh', 'commit message or PR body', 'heredoc or here-string', 'multi-line or quoted input' — plus the unusually natural symptom trigger 'wrapped in stray characters such as a leading and trailing `@`'.	5 / 5
Distinctiveness Conflict Risk	Clear niche — Windows shell quoting and heredoc/here-string corruption — with distinct triggers (heredoc, here-string, stray `@` wrapping) that are unlikely to fire for unrelated skills.	5 / 5
	Total	20 / 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: SRombauts/SQLiteCpp
Path: .claude/skills/windows-shell-commands/SKILL.md
Commit: 672a1e0

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