Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with a real, well-documented extraction script and a clear two-step workflow, but it carries some redundancy in restating the schema and lacks a final verification checkpoint for the batch review. Tightening the schema restatement and adding a completion check for step 2 would lift it.
Suggestions
Remove or consolidate the trailing bullet list that re-explains the JSON schema fields already documented in the schema block.
Add a verification checkpoint to step 2, e.g. confirm every locale in `locales` and every file in `files` has been reviewed before finishing.
De-duplicate the script usage command, which appears both in the Workflow section and the Extraction Script section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient, but the trailing bullet list re-explains the JSON output schema fields (e.g. "locales.*.added", "files[].english") already shown in the schema block, which could be tightened. | 2 / 3 |
Actionability | It gives an exact, copy-paste-ready command ("python3 scripts/extract_pr_strings.py <pr-number> --output /tmp/pr-strings.json"), a concrete output schema, and a named downstream skill (/translation-review). | 3 / 3 |
Workflow Clarity | Step 1 has an explicit completion checkpoint ("This step is complete when the output includes..."), but this is a batch operation over many locales/files with no final verification that all were reviewed and no checkpoint on step 2, capping clarity at 2. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections (Workflow, Extraction Script, output schema) with a single one-level-deep, real bundle reference ("scripts/extract_pr_strings.py") that is clearly signaled. | 3 / 3 |
Total | 10 / 12 Passed |