CtrlK
BlogDocsLog inGet started
Tessl Logo

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

86%

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.

The body is an excellent, actionable instruction skill: a gated workflow, concrete examples of every core technique, checklists with a real feedback loop, and clean one-level-deep reference structure. The only notable weakness is redundancy — the sincerity and euphemism rules are each restated across four to five sections, and Core Mechanics overlaps the Workflow.

Suggestions

State the never-self-aware and euphemism-over-bluntness rules once (in Anti-Patterns, where they have the strongest rationale) and have Mindset, Workflow, Troubleshooting, and Verification reference them in a few words instead of restating the full rule.

Fold 'Core Mechanics' into the Workflow (its escalation-duration guidance belongs in step 5) or trim it to only the content that does not repeat existing steps, cutting the body by roughly 15 lines without losing guidance.

DimensionReasoningScore

Conciseness

Mostly efficient technique-specific content, but key rules are repeated many times: the character-must-never-be-self-aware rule appears in Mindset, Workflow steps 2 and 8, Anti-Pattern 2, Troubleshooting, and Verification check 4, and the euphemism-over-bluntness rule likewise recurs across three sections. 'Core Mechanics' also substantially restates Workflow steps 5 and 6.

3 / 5

Actionability

For an instruction-only generative skill, the guidance is fully concrete: 8 sequenced drafting steps, five model-dialogue examples covering the common cases (frame, class pretension, euphemism, slow-burn escalation, ending) each with an explanation of the mechanism, and symptom-to-fix troubleshooting entries pointing at specific reference sections.

5 / 5

Workflow Clarity

The 8-step workflow is clearly ordered with a mandatory completion gate ('you MUST complete step 8 before treating any draft as finished'), and the Verification section is an explicit checklist with a feedback loop — 'if any check fails, return to the matching Troubleshooting entry' — covering error recovery for each failure mode.

5 / 5

Progressive Disclosure

The body is a well-organized overview with detail appropriately split into two real, one-level-deep reference files, surfaced in a table with topic, link, and explicit 'When to Use' conditions, and also cross-linked inline from Troubleshooting. Both referenced paths exist and neither nests further references.

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.

The description clearly and explicitly states what the skill does, when to use it, and what it deliberately excludes, with strong distinctiveness. Its weaknesses are verbosity in the genre-description sentence and a few missing natural trigger terms (parody, spoof, Bird & Fortune).

DimensionReasoningScore

Specificity

Lists several concrete deliverables — 'an original satirical sketch script, an interview-format dialogue exchange, a briefing-scene transcript' — plus named formats (interview, briefing, consultation), but the first sentence is padded with genre adjectives ('faux-serious rhetoric, class pretension, institutional hypocrisy, euphemism, slow-burn escalation') that describe style rather than actions.

4 / 5

Completeness

Explicitly answers both: 'Generate original British political satire sketches in the pompous-establishment two-hander tradition... a formal interview, briefing, consultation scene' (what) and 'Use this skill for an original satirical sketch script, an interview-format dialogue exchange, a briefing-scene transcript' (when, with concrete trigger phrases), plus a clear negative-scope clause ('Not intended for...').

5 / 5

Trigger Term Quality

Good natural-keyword coverage ('political satire sketches', 'satirical sketch script', 'interview-format dialogue exchange', 'briefing-scene transcript', 'minister, executive, regulator, spokesperson, peer'), but common user phrasings like 'parody', 'spoof interview', 'comedy sketch', and 'Bird & Fortune' itself are absent — the show name appears only in the body, not the description.

4 / 5

Distinctiveness Conflict Risk

A clear niche — British establishment political-satire two-hander interviews — with explicit exclusions (no slapstick, no absurdist non-political comedy, no monologue, no real-person mimicry) that sharply reduce the chance of triggering for a wrong skill.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pantheon-org/tekhne
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.