Review Shared Context Engineering plans and identify the next ready task.
92
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities (identifying next tasks, surfacing blockers, producing readiness verdicts), provides explicit trigger guidance with natural user phrases, and carves out a distinct niche around SCE plan file review. It uses proper third-person voice throughout and balances detail with conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: reviews an existing plan file, identifies the next unchecked task, surfaces blockers or ambiguous acceptance criteria, and produces an explicit readiness verdict. Also specifies the file format (Markdown checklist) and location (`context/plans/`). | 3 / 3 |
Completeness | Clearly answers both 'what does this do' (reviews plan files, identifies next unchecked task, surfaces blockers, produces readiness verdict) AND 'when should Claude use it' with an explicit 'Use when...' clause containing multiple trigger scenarios and example phrases. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'continue the plan', 'what's next?', 'resume work on the plan', 'review my plan and prepare the next task', 'continue a plan', 'resume work', 'pick the next step', 'check what remains'. These cover a wide range of natural phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it targets a very specific niche (SCE plan files in `context/plans/`, Markdown checklists, readiness verdicts before implementation). The specific file path, format, and workflow context make it unlikely to conflict with general task management or code review skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with strong actionability and workflow clarity. The structured output example with realistic blockers and the explicit readiness verdict pattern are particularly effective. Minor improvements could be made in conciseness by reducing redundancy between the example output and the bullet-point restatement of the same requirements.
Suggestions
Remove the bullet list after the expected output examples ('Explicit readiness verdict...', 'If not ready...', etc.) since these points are already clearly demonstrated in the example output blocks above them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy — the expected output section repeats concepts already stated in the rules (e.g., readiness verdict, blocker categories). The bullet list at the end of 'Expected output' restates what the example already shows. However, it avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, specific guidance: exact file paths to read, a clear plan file format with example, a structured output template with realistic example content, and explicit decision trees (e.g., missing context/ directory handling). Everything is copy-paste ready and unambiguous. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced: read context files → resolve plan target → collect task status → identify blockers → prompt for resolution → confirm scope → produce readiness summary. Validation is explicit via the ready_for_implementation verdict and the rule to block implementation until decisions are aligned. Error recovery is addressed (stale context, missing context/). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's somewhat long for a single file with no references to supplementary materials beyond the related skill. The expected output section with two example blocks could potentially be split out, though the overall length is manageable. The reference to sce-bootstrap-context is well-signaled. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents