Content
76%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, highly actionable skill: concrete copy-paste commands and a sensible state-preservation workflow for local repos. The main gap is unvalidated state restoration around the git stash round-trip, plus mild redundancy between the structure/paths sections and the example usage section.
Suggestions
Add a verification step after restoring state, e.g. check `git stash pop` output for conflicts and confirm `git branch --show-current` matches $ORIGINAL_BRANCH before declaring the work done; alternatively prefer a non-destructive reference method (e.g. `git worktree add` or `git fetch` + `git show origin/main:<file>`) over stashing untracked changes.
Merge "GitHub Details" into the "Repository Structure" section and fold "Example Usage" into the finding steps to remove the duplicated paths and workflow.
Clarify what to do when a repo exists neither locally nor remotely (e.g. report back to the user) so the decision flow has an explicit terminal branch.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean executable commands with no padding or explanations of concepts Claude already knows. However, the "GitHub Details" section repeats paths already shown in the structure tree and commands, and "Example Usage" re-walks the finding steps, so minor trimming is possible — matching the level-4 anchor rather than the every-token-earns-its-place level 5. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout: "ls ~/repos/github/dwmkerr/<repo-name>", "gh repo view dwmkerr/<repo-name> --json name,url", the git clone commands, and the complete stash/branch state-preservation blocks. Concrete examples cover the common cases (existing local repo, remote-only repo, searching content). | 5 / 5 |
Workflow Clarity | The finding sequence is clearly numbered (check local → preserve state → fetch → restore; else check GitHub → clone) and the ORIGINAL_BRANCH record/restore pattern is a real checkpoint. But the "git stash --include-untracked" / "git stash pop" round-trip is a state-altering operation with no verification that the restore succeeded (no stash-pop conflict handling, no post-restore check), and per the destructive-operation cap this holds workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | The skill is a single well-sectioned file (~105 lines) with no bundle files, and the content appropriately stays in one file at one level deep. It exceeds the under-50-line simple-skill exception and has minor organization gaps — the redundant "GitHub Details" and "Example Usage" sections could be consolidated — so it matches the level-4 anchor rather than level 5. | 4 / 5 |
Total | 16 / 20 Passed |