CtrlK
BlogDocsLog inGet started
Tessl Logo

gervais-esque-cringe-satire

Generate original cringe comedy and provocateur stand-up material in two modes — (1) character-based cringe scenes/sketches with an oblivious, self-important figure (boss, host, celebrity) surrounded by uncomfortable onlookers, mockumentary-style; (2) direct-address stand-up bits, monologues, roast lines that state a taboo truth bluntly, without hedging, then escalate. Trigger for requests for an original sketch, scene, monologue, roast bit, cringe scene, blunt stand-up line, built on oblivious self-delusion, awkward silence, escalating humiliation, mock self-congratulation, flippant treatment of solemn subjects. Do NOT use this skill for gentle observational humor, warm sitcom banter, wordplay/puns with no discomfort element, requests to reproduce/paraphrase a real comedian's actual routine, script, special — this skill generates new material; it does not mimic an existing performance.

73

Quality

90%

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.

A strong, well-structured body: the two-mode workflow is explicit with verification checkpoints and troubleshooting feedback loops, and the examples are genuinely instructive rather than filler. The main weakness is redundancy — the Core Mechanics section and some examples repeat both the workflow steps and material delegated to the reference files, which costs tokens without adding guidance.

Suggestions

Cut or merge the Core Mechanics Reference section: its bullets restate the numbered Workflow steps for both modes, and its topics are already covered in references/character-cringe-craft.md and references/provocateur-standup-craft.md per the References table — keeping one canonical statement (the workflows) would remove the largest duplication.

Deduplicate examples: the 'honorary member of every minority' scene appears three times and the wedding-registry bit twice; keep each in the single section where it teaches most (Anti-Patterns) and drop the repeats from Core Mechanics/Examples.

Trim the Anti-Patterns 'Consequence of skipping this rule' lines, which restate the WHY paragraph immediately above them in each entry.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it teaches craft mechanics Claude does not already have — but there is real duplication: the "honorary member of every minority" example appears three times (Core Mechanics example, Anti-Patterns BAD and GOOD), the wedding-registry example appears twice (Examples and Anti-Patterns), and the Core Mechanics Reference largely restates the numbered Workflow steps for both modes. This fits the anchor 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the level-4 anchor, whose over-explanation would be only minor.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: numbered per-mode workflows ("Build the authority figure around one specific, nameable delusion", "Write the opening line as one unhedged sentence... strip qualifiers"), six before/after text examples showing exact lines, and symptom→fix Troubleshooting entries. Per the rubric's code-vs-instruction note, absence of code is not penalized when guidance is this concrete and example-covered — matching the top anchor.

5 / 5

Workflow Clarity

Both mode workflows are clearly sequenced (prerequisites → numbered steps → Verification), the Verification section is an explicit five-item checklist with a re-read pass ("Read it back once more start to finish: does the discomfort stay unresolved..."), and Troubleshooting provides feedback loops for error recovery. This matches the anchor with explicit validation steps, feedback loops, and checklists; level 4 would require missing checkpoints, which are present.

5 / 5

Progressive Disclosure

Structure is good: two real, one-level-deep reference files (character-cringe-craft.md, provocateur-standup-craft.md) linked inline at the exact workflow steps that need them, plus a References table with per-reference "When to Use" guidance including when to skip them. It falls short of the 5 anchor because the ~60-line Core Mechanics Reference and several of the six worked examples overlap content the reference files already cover (the table itself lists "delusion design, onlooker roster, escalation ladder, comeuppance sizing" as reference-file material), so a modest amount of content that belongs in the bundle is inlined.

4 / 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: it states what the skill generates in two concretely-described modes, gives explicit natural-language triggers, and closes with a do-not-use clause that both prevents mis-triggering against gentle-humor or parody requests and reinforces the originality constraint. The only minor cost is length, but every clause is functional rather than padded.

DimensionReasoningScore

Specificity

The description lists multiple concrete generative actions across both modes — "character-based cringe scenes/sketches with an oblivious, self-important figure (boss, host, celebrity) surrounded by uncomfortable onlookers, mockumentary-style" and "stand-up bits, monologues, roast lines that state a taboo truth bluntly, without hedging, then escalate" — with comprehensive coverage of the skill's output types. This matches the anchor for multiple specific concrete actions with comprehensive coverage; the level-4 anchor would require minor gaps in coverage, but both modes and their structural ingredients are fully enumerated.

5 / 5

Completeness

It explicitly answers both questions: what ("Generate original cringe comedy and provocateur stand-up material in two modes — (1)... (2)...") and when ("Trigger for requests for an original sketch, scene, monologue, roast bit...") with concrete trigger phrases, plus an explicit when-not clause. This is the anchor-5 pattern; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Trigger terms are natural user phrasings with synonyms across both modes: "original sketch, scene, monologue, roast bit, cringe scene, blunt stand-up line, ... awkward silence, escalating humiliation, mock self-congratulation, flippant treatment of solemn subjects" — matching the comprehensive-coverage anchor. Not below it at 4, since a user asking for a sketch, roast, monologue, or cringe scene would naturally use one of these exact terms.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined (cringe/provocateur satire with named structural devices) and the exclusion clause — "Do NOT use this skill for gentle observational humor, warm sitcom banter, wordplay/puns..., requests to reproduce/paraphrase a real comedian's actual routine" — actively separates it from adjacent comedy-writing skills. Clear niche with distinct triggers and minimal conflict risk, matching the 5 anchor rather than the 4 anchor's 'minor overlap risk'.

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.

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.