CtrlK
BlogDocsLog inGet started
Tessl Logo

comedy-style-skill-generator

Generate a new, reusable comedy-writing SKILL.md for a requested comedic tradition — real, generic, or invented — by extracting its transferable comic mechanics (premise construction, escalation pattern, rhythm, rhetorical devices) into concrete, actionable writing rules instead of vague adjectives, and by converting any living performer's persona into technique rather than voice-imitation. Use this when a user asks to create a comedy skill for a style, or a skill "like" a comedian or show, and wants a complete SKILL.md file back. Do NOT use this to write comedic material directly (that is the generated skill's job, not this one's), for non-comedy skill generation, or to produce a skill whose body just says "be funny" or "make it absurd" without concrete mechanics.

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

81%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 exceptionally actionable and workflow-clear: a concrete analysis checklist, an explicit conversion method with BAD/GOOD pairs, a required-sections assembly spec, and a verification loop with a style-fidelity pass. Its main weakness is token efficiency — the living-performer rule is repeated across four sections and the universal-craft baseline and worked examples could move to the existing reference files. Progressive disclosure is good, with two verified one-level-deep references clearly signaled.

Suggestions

State the living-performer rule once in the 'For living performers' section and have the Workflow step 3, Anti-Pattern, and Troubleshooting entries reference it in one line each instead of restating the full rationale — this would cut noticeable token duplication across four sections.

Move the ~40-line universal-craft baseline (the six principles and pre-writing scaffold) and the five universal 'don'ts' out of Workflow steps 4 and 5 into a dedicated reference file (e.g. references/universal-craft.md), keeping a one-line pointer plus one or two seed examples in the body.

Trim the miniature worked examples in the body to the single 'deadpan corporate-memo satirist' pair and point to the already-existing references/worked-examples.md for the second tradition and the full pipeline, reducing inline bulk while preserving the demonstration of the conversion method.

DimensionReasoningScore

Conciseness

The living-performer rule is stated in four places (Workflow step 3, the 'For living performers' section, the first Anti-Pattern, and Troubleshooting), and the ~40-line universal-craft baseline plus the full worked-example walkthroughs could largely live in the already-existing reference files. Matches the 3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') — not 4 because the repetition and inlined bulk are noticeable rather than minor, though the body never explains concepts Claude already knows.

3 / 5

Actionability

Everything is executable: a 14-point analysis checklist, an explicit conversion spec with ❌ BAD / ✅ GOOD pairs ('Start with a plausible premise, interpret one key term literally, and escalate the resulting contradiction through three increasingly serious procedural responses'), a required-sections assembly list, and labeled worked examples. Fully matches the 5 anchor for an instruction-only skill — concrete, specific guidance covering the common cases.

5 / 5

Workflow Clarity

A seven-step sequenced workflow with an explicit verification checklist in step 6 and a genuine feedback loop ('If the piece misses the style, the fix belongs in the skill… Revise the skill and repeat until a fresh reader would recognise the trial piece'). Matches the 5 anchor's validate → fix → retry pattern, and the living-performer branch and Troubleshooting section handle error recovery explicitly.

5 / 5

Progressive Disclosure

Two real, one-level-deep references (references/worked-examples.md and references/living-performer-conversion.md, both verified to exist and match their descriptions) are clearly signaled in a 'When to Use' table, and the body is well-sectioned. Not 5 because a substantial amount of content that could be split out — the universal-craft baseline in step 4 and the extended worked-example material — remains inlined in the ~350-line body.

4 / 5

Total

17

/

20

Passed

Description

92%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 clearly and explicitly states both what the skill does and when to use it, with concrete actions and natural trigger phrases. The explicit negative triggers ('Do NOT use this to write comedic material directly…') make it highly distinguishable from the skills it generates. The only weakness is that trigger coverage misses a few natural phrasing variants, and the description runs long, though every clause is load-bearing rather than padded.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Generate a new, reusable comedy-writing SKILL.md', 'extracting its transferable comic mechanics (premise construction, escalation pattern, rhythm, rhetorical devices) into concrete, actionable writing rules', and 'converting any living performer's persona into technique rather than voice-imitation' — with comprehensive coverage of what the skill does. Not score 4 because there are no minor gaps: the action list covers generation, extraction, conversion, and the deliverable form.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' ('Generate a new, reusable comedy-writing SKILL.md… by extracting its transferable comic mechanics') and the 'when' ('Use this when a user asks to create a comedy skill for a style, or a skill "like" a comedian or show'), plus negative triggers ('Do NOT use this to write comedic material directly'). Matches the 5 anchor exactly; not 4 because the 'when' is fully explicit with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say are present ('create a comedy skill for a style', 'a skill "like" a comedian or show', 'wants a complete SKILL.md file back'), but a few natural variants (e.g. 'turn this style into a skill', 'make a reusable comedy skill') are not covered. Falls between the 4 and 5 anchors, noticeably above the midpoint but short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (generating comedy-style skill files, not writing comedy) with distinct triggers and explicit negative anchors that separate it from comedy-writing itself and from non-comedy skill generation. Minimal conflict risk with any other skill.

5 / 5

Total

19

/

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.