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 captures genuinely non-obvious domain knowledge in a token-efficient way, but it reads as raw engineering notes rather than a skill: observations are not shaped into a usable workflow, key directives are garbled or buried, and no concrete implementation/debugging steps are given. The remotion.new route-tracking section is the one fully actionable piece.
Suggestions
Restructure the field observations into a sequenced workflow for the skill's stated purpose — e.g., ordered steps for tracking sequence identity via nodePath + index across hot reloads, with an explicit validation checkpoint for the expanded-state end goal.
Add concrete executable guidance: the actual API/code for fetching a nodePath once per symbolicated stack, and a specific debugging procedure for identity/remount mismatches instead of inference from raw observations.
Fix garbled sentences ("needs to be calculated asyn", "overrideId works change") and move the loose prose after the Fields list under clear section headers so every rule is scannable rather than buried in paragraph notes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence with no padding or explanations of known concepts, but the stack/nodePath/overrideId identity relationships are restated across several loose sentences ("Once nodePath is mapped to overrideId...", "If the same stack is found...", "multiple sequences can share the same stack...") and some garbled phrasing ("overrideId works change") forces re-reading, so it is not fully tight. | 4 / 5 |
Actionability | Concrete knowledge is present (field-by-field identity semantics like "overrideId -> does keep the identity the same... even if the file / line / column changes", and the explicit remotion.new checklist rule), but there is no executable guidance for the stated purpose — no code, commands, or API details for fetching a nodePath "for every stack once" or for debugging identity mismatches. | 3 / 5 |
Workflow Clarity | The body is a collection of observations with no sequenced process or checkpoints for implementing/debugging visual editing; only the remotion.new route rule is a coherent, unambiguous directive. It sits between 'steps missing or incoherent' and 'rough sequence present but many gaps', closer to the latter only because the route rule and the nodePath+index design intent give rough direction. | 2 / 5 |
Progressive Disclosure | Two section headers exist ("## Fields", "## remotion.new route tracking") and the skill is short enough to need no external files, but a block of unstructured, unheaded prose follows the Fields list and mixes design rules with observations — organization gaps beyond the 'minor' level of the next anchor. | 3 / 5 |
Total | 12 / 20 Passed |