Content
71%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 highly actionable, well-sequenced operational reference with exact tool names, parameters, and pitfall callouts that make workflows executable. Its weaknesses are duplicated pitfall content that inflates token cost and a monolithic single-file structure where per-domain references would improve navigation.
Suggestions
Split per-domain detail (PR workflows, issues, branches, quick-reference table) into one-level-deep reference files (e.g., references/pull-requests.md, references/issues.md) and keep SKILL.md as an overview with clearly signaled links.
Deduplicate the pitfalls: state each pitfall once (e.g., BBQL double-quoting appears in three places) and consolidate the "Known Pitfalls" section to only cross-cutting items not already covered in workflows.
Add post-operation validation steps and a validate-fix-retry loop for batch operations (e.g., verify PR state after creation, re-check pagination via the `next` URL before finishing a listing).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense reference material with no explanation of concepts Claude already knows, but contains notable redundancy: BBQL double-quoting rules appear three times, and the "irreversible delete", "assignee vs assignee_account_id", and destination_branch-default pitfalls are each duplicated between workflow sections and the "Known Pitfalls" section. This fits 'mostly efficient but could be tightened' rather than 4's 'minor instances'. | 3 / 5 |
Actionability | Fully executable, instruction-only guidance: exact tool slugs, concrete parameter names and formats (`[{"uuid": "{...}"}]`, `name~"api"`, `"on hold"`), enumerated value sets, and a per-task quick-reference table. Not 4: the common cases (create PR, comment, filter, paginate) are covered with copy-paste-ready specifics rather than having minor gaps. | 5 / 5 |
Workflow Clarity | Each workflow is a clearly numbered sequence with [Prerequisite]/[Required]/[Optional] markers, setup includes an explicit checkpoint ("Confirm connection status shows ACTIVE"), and destructive operations are gated ("Always confirm with the user before executing delete operations"). Not 5: there are no post-operation verification steps or validate-fix-retry feedback loops, and batch/rate-limit guidance lacks any loop, leaving minor validation gaps. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), so the entire ~230-line per-tool reference — five workflow breakdowns, pitfalls, and a 17-row quick-reference table — is inlined in one file. Section headers give it structure, but this is exactly the content that belongs in one-level-deep reference files, matching 'content that should be separate is inline'. | 3 / 5 |
Total | 15 / 20 Passed |