CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brooker-esque-media-satire

Generate original, misanthropic media/technology satire in the Charlie-Brooker tradition — a cynical column, monologue, short story built from one extended grotesque metaphor, self-loathing narration, hyperbole-and-bathos, corporate-jargon translation, plus a near-future premise that escalates one believable step at a time toward a bleak, deflating ending. Use for a satirical takedown of a TV show, app, gadget, news format, or social-media trend, plus dystopian near-future short stories about a plausible technology/social mechanic. Do NOT use for mockumentary/character-voice sketches, deadpan two-hander political interviews, observational stand-up; also not for reproducing a real writer's actual column, script, episode — this skill only generates new material inspired by the technique, never a copy.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction-only skill: lean body, concrete BAD/GOOD examples that teach the technique, a sequenced workflow with a final anti-pattern check, and exemplary conditional references. The main weakness is the fabricated 'make check-draft' command — non-executable content that weakens both actionability and the escalation-validation step — plus the lack of any error-recovery guidance after the final check fails.

Suggestions

Delete the illustrative bash block and its disclaimer ('make check-draft FILE=draft.md' / 'That command is illustrative only — this skill ships no such script'); replace step 6's escalation test with a concrete inline check, e.g., 'For each step in the chain, ask: could a real company do this under an existing terms-of-service clause? If not, rewrite the step'.

Add one-line recovery guidance after the step-9 final check (e.g., 'If a beat matches an anti-pattern, rewrite that beat against the paired GOOD example and re-check — do not restart the draft'), turning the final check into a genuine feedback loop.

Trim the opening paragraph, which restates the frontmatter description ('a cynical column, monologue, short story... one sustained, escalating metaphor'), to a single sentence of unique framing.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — technique guidance is delivered through compact BAD/GOOD example pairs rather than explanations of what satire is. Not 5: the illustrative-only bash block ('make check-draft FILE=draft.md' followed by 'That command is illustrative only — this skill ships no such script') spends tokens on a command that cannot be run, and the opening paragraph partially restates the frontmatter description.

4 / 5

Actionability

Guidance is mostly executable for a writing skill: concrete mechanics ('PREFER a single scaling metaphor system... AVOID a second unrelated joke'), worked text examples ('The app doesn't send notifications, it triages you...'), and specific BAD/GOOD drafts for each anti-pattern. Not 5: the only 'command' in the skill is explicitly non-existent, and the workflow steps ('Add a jargon-mockery beat', 'Return to the centre near the end, worse') are directives without a worked mini-example for the story branch's escalation.

4 / 5

Workflow Clarity

A clear 9-step numbered sequence with explicit branch selection (step 2: rant vs story branch) and a final validation checkpoint (step 9: 'Run a final check against the anti-patterns below to verify the draft before calling it done'). Not 5: validation is a one-shot final check rather than a feedback loop — there is no guidance on what to do when a check fails (e.g., rewrite the offending beat vs restart), and the escalation-logic test points to a command that does not exist.

4 / 5

Progressive Disclosure

Clear overview in SKILL.md with well-signaled, one-level-deep references: the References table maps each topic to a real file (both references/extended-metaphor-and-voice.md and references/dystopian-escalation-structure.md exist) with precise conditional load guidance ('Load only when writing a rant/column/monologue and the metaphor is drifting...'). Matches the anchor-5 structure exactly.

5 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities in third person, explicit 'Use for'/'Do NOT use for' triggers covering both the column and story forms, and clear differentiation from neighboring comedy formats and from reproduction of real copyrighted material. Dense but every clause carries capability or trigger information.

DimensionReasoningScore

Specificity

Lists multiple specific concrete outputs and techniques — 'a cynical column, monologue, short story built from one extended grotesque metaphor, self-loathing narration, hyperbole-and-bathos, corporate-jargon translation, plus a near-future premise that escalates one believable step at a time toward a bleak, deflating ending' — comprehensive coverage with no vague filler. Not 4: coverage is complete across both forms (rant and story) plus named comedic mechanics, not 'several actions with minor gaps'.

5 / 5

Completeness

Explicitly answers both questions: the 'what' is the full capability list above, and the 'when' is 'Use for a satirical takedown of a TV show, app, gadget, news format, or social-media trend, plus dystopian near-future short stories about a plausible technology/social mechanic' — with additional 'Do NOT use for...' boundary triggers. Matches the anchor-5 example's structure exactly.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered: 'satirical takedown of a TV show, app, gadget, news format, or social-media trend', 'dystopian near-future short stories', 'cynical column', 'monologue', plus named-tradition cues ('Charlie-Brooker tradition'). These are the phrases a user would actually say when requesting this; only irrelevant file-extension synonyms are absent, which don't apply to this domain.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Brooker-tradition misanthropic satire) with distinct triggers, and the explicit exclusions ('Do NOT use for mockumentary/character-voice sketches, deadpan two-hander political interviews, observational stand-up; also not for reproducing a real writer's actual column, script, episode') sharply reduce conflict with adjacent writing skills. Third-person voice throughout; no penalty applies.

5 / 5

Total

20

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

pantheon-org/tekhne

Path

skills/comedy/brooker-esque-media-satire/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.