AF non-annoying-news
Create, configure, and render a source-grounded personal newspaper/news digest from URLs, bookmarks, X/Twitter bookmarks, browser reading lists/bookmarks, read-later apps, feeds, newsletters, web research, or pasted notes. Use for first-run onboarding, recurring digest setup, personal newspaper naming/design/cadence customization, source/signal configuration, magazine-style PDF/HTML issues, bookmark/news roundups, editorial QA, rendering, and release-quality layout proofing. On first setup, require a personalized onboarding interview before creating a config, cron, or personal issue.
As a process F 45/100 · Will not run — References files that are not bundled: assets/newspaper-template/base.css
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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/newspaper-template/base.css
Process rating: all ten parameters 45/100
- 0Tools and files. 1 referenced file(s) missing: assets/newspaper-template/base.css
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 85Steps. 45 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1544 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 590: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (6 of 6)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.