CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bird-fortune-political-satire

Generate original British political satire sketches in the pompous-establishment two-hander tradition, a formal interview, briefing, consultation scene built on faux-serious rhetoric, class pretension, institutional hypocrisy, euphemism, slow-burn escalation, self-serving reasoning concealed beneath polished language. Use this skill for an original satirical sketch script, an interview-format dialogue exchange, a briefing-scene transcript, featuring a pompous official, minister, executive, regulator, spokesperson, peer, who sincerely believes their evasive reasoning is sound. Not intended for reproducing real sketches, quoting real public figures' actual recorded words, near-verbatim programme dialogue, slapstick, absurdist non-political comedy, or monologue writing without an interview/dialogue frame.

71

Quality

89%

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

85%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-constructed creative-instruction skill: concrete workflow with a gated final check, excellent paired anti-pattern examples, a real verification checklist with feedback loops, and clean one-level-deep references. The main cost is redundancy — the escalation-preference advice is stated three times, which inflates the token budget without adding guidance.

Suggestions

State the sustained-escalation preference once (Workflow step 5) and have Core Mechanics and Troubleshooting reference it rather than restate it, trimming ~10 lines.

Replace the ALL-CAPS PREFER/AVOID/UNLESS/RECOMMENDED paragraph with one plain sentence, since the emphasis adds no guidance beyond step 5.

Consider folding one or two of the five Examples into references/euphemism-and-escalation.md to further slim the main file.

DimensionReasoningScore

Conciseness

The body is largely skill-specific craft guidance Claude would not derive itself (sincerity-preserving register, euphemism-over-insult), but there is real redundancy: sustained-escalation advice appears in Workflow step 5 ("Escalate slowly... Favour sustained escalation over rapid-fire jokes"), again in Core Mechanics ("PREFER sustained escalation over rapid-fire jokes"), and again in Troubleshooting; the ALL-CAPS PREFER/AVOID/UNLESS paragraph restates a point already made. This fits the 3 anchor ('mostly efficient but... could be tightened'). Not 2 because no section explains concepts Claude already knows; not 4 because the duplication spans multiple sections, not just minor trimmable instances.

3 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: an 8-step ordered workflow with per-step directives ("Seed the concealed weakness... The audience should be able to infer it before the character admits it"), GOOD/BAD paired dialogue examples for every anti-pattern, symptom→fix Troubleshooting entries, and worked examples of each technique. Per the scoring note for instruction skills, concrete specific guidance replaces code, and the examples cover the common cases — matching the 5 anchor.

5 / 5

Workflow Clarity

The Workflow is explicitly ordered with a mandated gate ("you MUST complete step 8 before treating any draft as finished"), and the Verification section is a named 5-item checklist with an explicit feedback loop ("if any check fails, return to the matching Troubleshooting entry above"). This matches the 5 anchor: clear sequence, explicit validation steps, feedback loops, and a checklist.

5 / 5

Progressive Disclosure

SKILL.md is a well-sectioned overview (Mindset, When to Use, Workflow, Core Mechanics, Anti-Patterns, Examples, Troubleshooting, Verification) and the two detail files — references/euphemism-and-escalation.md and references/interview-frame-and-personas.md — both exist on disk, are one level deep, and are surfaced through a table with explicit 'When to Use' conditions plus inline citations in Troubleshooting. This matches the 5 anchor: clear overview with well-signaled one-level-deep references and appropriate content split (deep-dive detail lives in the reference files).

5 / 5

Total

18

/

20

Passed

Description

87%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.

A strong description that states a concrete generative action, an explicit 'Use this skill for...' trigger clause, and sharp exclusions that delineate it from neighboring comedy skills. The only weakness is that the comma-list construction runs long and omits a few natural synonyms (parody, spoof) a user might use.

Suggestions

Add one or two natural synonyms such as 'parody' or 'spoof interview' to the trigger terms so users phrasing the request as a parody are also matched.

Break the single run-on sentence chain into two or three shorter sentences so the what/when/not-for clauses each read cleanly.

DimensionReasoningScore

Specificity

Concrete actions are named — "Generate original British political satire sketches", "a formal interview, briefing, consultation scene" — with specific formats and character types ("minister, executive, regulator, spokesperson, peer") listed, matching the 'several specific actions; minor gaps' anchor. Not 5 because the core action is a single verb (generate) with format variations, unlike the comprehensive multi-action 5-anchor example; not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

It explicitly answers what ("Generate original British political satire sketches in the pompous-establishment two-hander tradition... built on faux-serious rhetoric, class pretension, institutional hypocrisy") and when ("Use this skill for an original satirical sketch script, an interview-format dialogue exchange, a briefing-scene transcript..."), plus explicit exclusions ("Not intended for reproducing real sketches..."). Uses third person. This matches the 5 anchor: both what and when with concrete trigger phrases; nothing is merely implied.

5 / 5

Trigger Term Quality

Natural user phrasing is present: "political satire", "satirical sketch script", "interview-format dialogue exchange", "briefing-scene transcript", "minister", "spokesperson" — good keyword coverage matching the 4 anchor. Not 5 because common synonyms a user would plausibly say — "parody", "spoof", "comedy sketch", "Yes Minister-style" — are missing; not 3 because the terms present are exactly what a user requesting this would say, not jargon.

4 / 5

Distinctiveness Conflict Risk

A clear niche — the pompous-establishment two-hander interview tradition — with minimal overlap risk against generic sketch, monologue, or impersonation skills, reinforced by explicit boundary statements ("Not intended for... slapstick, absurdist non-political comedy, or monologue writing without an interview/dialogue frame"). This matches the 5 anchor's clear niche with distinct triggers.

5 / 5

Total

18

/

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/bird-fortune-political-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.