AF paper-reading-workspace-presentation
Create a React/Vite Workspace Presentation from one paper-reading source workspace or source chain. Use when the user wants to package, present, review, hand off, reread, or browse generated paper-reading artifacts in an interactive frontend.
Create a React/Vite Workspace Presentation from one paper-reading source workspace or source chain.
As a process F 53/100 · Will not run — References files that are not bundled: references/presentation-display-map.md, templates/react-vite/, references/manifest-schema.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/presentation-display-map.md - warning
missing-refreference to a missing file: templates/react-vite/ - warning
missing-refreference to a missing file: references/manifest-schema.md - warning
missing-refreference to a missing file: references/source-index-schema.md - warning
missing-refreference to a missing file: references/summary-schema.md - warning
missing-refreference to a missing file: references/ui-guidelines.md
Process rating: all ten parameters 53/100
- 0Tools and files. 6 referenced file(s) missing: references/presentation-display-map.md, templates/react-vite/, references/manifest-schema.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (paper-reading-workspace-presentation) differs from the folder (workspace-presentation)
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 875 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 242: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.