Content
96%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 an exemplary procedural skill: dense with repo-specific, non-obvious directives, fully executable commands, explicit validation checkpoints, and fallback behavior for failure paths. The only structural improvement would be sectioning the main workflow the way the final section is sectioned.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — e.g. "Never force push, unless users asks for it", "Pass their actual paths; do not assume that the repository root has a `src` directory" — with no explanations of concepts Claude already knows; every directive is project-specific and earns its place. | 5 / 5 |
Actionability | Fully executable, copy-paste-ready commands cover the common cases: `bunx oxfmt <changed-file-or-package-directory>... --write`, `bun run build`, `git push -u origin HEAD`, `gh pr create --title "..." --body-file <path>`, and the maintainer-edits remediation via `gh api --method PATCH repos/<owner>/<repo>/pulls/<number> -F maintainer_can_modify=true`. | 5 / 5 |
Workflow Clarity | A clear sequence (branch check → existing-PR check → format → build/stylecheck → commit → push → create PR → post-creation) with explicit validation ("Inspect any formatter changes before committing", build/stylecheck gates, `maintainerCanModify` check-and-fix) and error-recovery feedback loops (poll for the Vercel comment with sleep intervals; "If either the page path or the preview URL cannot be determined confidently, leave the created PR unchanged and report"). | 5 / 5 |
Progressive Disclosure | External references are well-signaled, conditional, and one level deep ("If the changes add a Remotion Element, read the [Element contribution guide]... before continuing"; the `pr-name` skill link), and nothing that belongs in a separate file is inlined. It falls short of a 5 because the ~60-line body has only one section header, leaving the main workflow as a flat, unsectioned sequence. | 4 / 5 |
Total | 19 / 20 Passed |