CtrlK
BlogDocsLog inGet started
Tessl Logo

monty-python-esque

Generate an original British surrealist comedy sketch, script, or comic bit in the Monty Python tradition, built on absurd literalism, escalating internally-consistent illogic, bureaucratic pedantry, semantic argument, deadpan seriousness amid impossible premises, sudden non sequiturs, abrupt anticlimactic endings. Use this when a user asks for a new sketch, script, dialogue bit, or scene built on a mundane premise pushed to logical extremes. Do NOT use this to reproduce, quote, paraphrase, reword any actual Monty Python sketch, character, catchphrase (e.g. Dead Parrot, Spanish Inquisition, Ministry of Silly Walks, Argument Clinic); this is a generative skill for fresh original material, not a lookup, quotation, transcription tool. Not for slapstick, observational stand-up, roast comedy, American-style sitcom writing, where the humour depends on delivery, timing, rather than an escalating internally-consistent premise.

68

Quality

83%

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 strong instruction-only skill body: it adds only what Claude wouldn't already know (the mechanism discipline, anti-patterns with contrastive examples) and delegates depth cleanly to two well-scoped reference files. The main costs are mild redundancy in the anti-pattern rationale blocks and the absence of one complete worked sketch demonstrating the full workflow.

Suggestions

Merge each anti-pattern's WHY and CONSEQUENCE into a single one-line rationale — they currently restate the same point twice across four patterns, the body's largest source of padding.

Add one short complete example sketch (or a pointer to one in references/) that shows the full workflow applied: ordinary premise, engine choice, escalation beats, and anticlimax ending.

Trim overlap between 'When to Use' / 'When NOT to Use' and the frontmatter description, which already states both scopes, and keep the body's bullets to conditions not covered there.

DimensionReasoningScore

Conciseness

The body assumes Claude's intelligence (no explaining what Monty Python is or how comedy works) and stays tight in the Mindset section ("escalate the logic, don't escalate the randomness"). Minor over-explanation remains: each anti-pattern carries both a WHY and a CONSEQUENCE block that partially restate each other, and "When to Use"/"When NOT to Use" repeat material already in the description — efficient, but with trimmable padding.

4 / 5

Actionability

Concrete, executable guidance throughout: named premise examples ("a planning committee, a returns desk, a job interview"), specific directives ("interpret it with total, humourless literalness"), and BAD/GOOD dialogue pairs for each anti-pattern. It falls short of fully executable coverage because there is no complete worked example applying the whole workflow end-to-end, and some steps hedge ("consider", "you might blend two").

4 / 5

Workflow Clarity

The 9-step workflow is clearly sequenced and includes an explicit recovery checkpoint ("If the escalation fails to build past the opening exchange, stop and revisit the premise, or fall back to a different comic engine") plus a confirmation step for sensitive topics. Minor gaps keep it below 5: the recovery loop covers only escalation failure, and intermediate checkpoints (e.g. verifying tone or engine choice mid-draft) are implicit.

4 / 5

Progressive Disclosure

The body is a well-organized overview (Mindset, When to Use, When NOT to Use, Workflow, Anti-Patterns, References) with two clearly signaled, one-level-deep references presented in a table with topic and "When to Use" conditions; both referenced files exist in references/ and contain no further nesting. This matches the anchor of a clear overview with well-signaled one-level-deep references.

5 / 5

Total

17

/

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 highly effective description: third-person, concrete about both capability and triggers, with unusually good boundary guidance (explicit do-NOT-use clause and named exclusions). Its only weakness is length — the negative-scope material is somewhat redundant ("reproduce, quote, paraphrase, reword... not a lookup, quotation, transcription tool"), which keeps it from being maximally tight.

DimensionReasoningScore

Specificity

"Generate an original British surrealist comedy sketch, script, or comic bit" names the domain and several concrete output forms and mechanisms ("absurd literalism, escalating internally-consistent illogic, bureaucratic pedantry, semantic argument"), which is several specific actions with minor gaps. It stops short of a 5 because these are variations of one generative capability rather than multiple distinct comprehensive actions.

4 / 5

Completeness

It explicitly answers both: what ("Generate an original British surrealist comedy sketch... built on absurd literalism...") and when ("Use this when a user asks for a new sketch, script, dialogue bit, or scene built on a mundane premise pushed to logical extremes"), with concrete trigger phrases plus explicit negative scope. This matches the anchor that clearly and explicitly answers both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural user phrases are well covered — "sketch", "script", "dialogue bit", "scene", "Monty Python" — matching how users would actually phrase these requests. A few natural synonyms (e.g. "comedy sketch", "funny scene", "parody" framing) are missing, keeping it below the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Python-esque premise-escalation comedy) with distinct triggers and explicit do-not-use boundaries separating it from reproduction requests, slapstick, stand-up, roast, and sitcom writing. Conflict risk with other skills is minimal.

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.