Content
51%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.
The body is token-efficient and cleanly structured for a minimal skill, but it is too thin to be actionable: it only documents installation and provides no guidance for the actual version-control workflow it promises. Adding concrete usage steps and validation checkpoints is the main improvement needed.
Suggestions
Add a usage section with concrete, executable examples of the core version-control operations (commit, diff, rollback) on ArcGIS web maps.
Include a brief workflow with validation checkpoints, especially since version control can involve destructive/batch changes to web maps.
Remove the duplicated description line or replace it with substantive guidance so every token earns its place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no concept over-explanation, but it re-states the frontmatter description line, a minor redundancy that keeps it just below the 'every token earns its place' anchor. | 4 / 5 |
Actionability | It provides one concrete executable command ('npx clawhub@latest install gitmap') but gives zero guidance on how to perform the actual version-control operations the skill is named for, fitting 'minimal concrete guidance; missing specific steps.' | 2 / 5 |
Workflow Clarity | Only the install step is shown and is unambiguous, but the core version-control workflow (commit, diff, rollback, validation) is entirely absent with massive gaps rather than a clear sequence. | 2 / 5 |
Progressive Disclosure | The skill is under 50 lines, has no external references (no references/scripts/assets bundle exists), and its content is organized into clear sections, satisfying the simple-skill exception for progressive disclosure. | 5 / 5 |
Total | 13 / 20 Passed |