Content
78%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 strong, highly actionable skill body: every step is executable, the sequence is clear with a verify step, and the pitfalls capture real non-obvious failure modes. The main weaknesses are the inlined (and diverged) proxy script duplicating the unused `scripts/proxy.mjs` bundle file, and a few missing validation checkpoints around the patch/build and cleanup steps.
Suggestions
Replace the inline proxy code in Step 4 with a reference to the bundled script, e.g. "Copy `scripts/proxy.mjs` to `$GITNEXUS_DIR/proxy.mjs`" — the inline copy has already diverged from the (better) bundle version, which is exactly the drift risk progressive disclosure prevents.
Add a validation checkpoint after Step 2's build (e.g., confirm `npx vite build` exits 0 / `dist/index.html` exists) and before the cleanup's `rm -rf .claude/` and `gitnexus clean`, which are destructive and currently unvalidated.
Add a short failure-feedback note for step 5 (e.g., if the curl check returns 502, confirm `npx gitnexus serve` is running) to complete the error-recovery loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-first with no explanations of concepts Claude already knows; every section earns its place (e.g., the cloudflared `--config /dev/null` pitfall is genuinely non-obvious). Not 5: the ~45-line inline proxy script and a few asides ("same origin, no CORS issues, no sudo, no nginx") could be trimmed or moved out of the main file. | 4 / 5 |
Actionability | Every step is copy-paste executable: complete bash blocks, an exact patch shown as before/after TypeScript, the full proxy script, and a curl verification command. This matches the anchor for fully executable guidance covering the common case. | 5 / 5 |
Workflow Clarity | A clear 7-step sequence with an explicit verification checkpoint ("Verify: `curl -s http://localhost:8888/api/repos` should return the indexed repo(s)") and a dedicated cleanup section. Not 5: there is no validation after the source patch/build step and no feedback loop if the tunnel or proxy fails; the destructive `rm -rf .claude/` and `gitnexus clean` cleanup steps run without a pre-check. | 4 / 5 |
Progressive Disclosure | Section structure is good (When to Use, Prerequisites, Size Warning, Steps, Pitfalls), but the body inlines ~45 lines of proxy code as "Write this to a file" while `scripts/proxy.mjs` exists in the bundle and is never referenced — and the two copies have diverged (the inline version lacks the host-header fix, `.ttf`/`.map` MIME entries, and stricter SPA fallback present in the bundle file). This matches "content that should be separate is inline". Not 2: the rest of the document is well organized with no buried references. | 3 / 5 |
Total | 16 / 20 Passed |