Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/roast
Constructive critique via 5 HackerNews personas with claim validation.
Passed 12 of 19 test cases with the skill, and 7 of 19 without it.
and 8 more in the full report
8 fixed7 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
During Phase 4 claim verification, an agent claims line 45 has no error handling, but reading line 45 shows a try-catch block wrapping the entire async call. What verdict must be assigned to this claim?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns the UNFOUNDED verdict when evidence contradicts a claim. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill produces evidence-based constructive critique through 5 specialized HackerNews commenter personas: Skeptical Senior, Well-Actually Pedant, Enthusiastic Newcomer, Contrarian Provocateur, and Pragmatic Builder. The workflow spawns these personas in parallel, validates all claims against actual files and lines, and synthesizes findings into an improvement-focused report.
Key constraints baked into the workflow:
read-only-ops skill invocation| When | Load | Content |
|---|---|---|
| Phase 5: writing the synthesized report | references/report-template.md | Full report template with tone transformation rules |
Goal: Establish guardrails before any analysis begins.
Call the Skill tool with read-only-ops.
skill: read-only-ops
This ensures no modifications can occur during the analysis workflow.
Allowed operations:
Read tool for file contentstest cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.