CtrlK
BlogDocsLog inGet started
Tessl Logo

rock-esque-observational-standup

Generate an original, high-energy observational stand-up bit — a routine built on one bold contrastive claim ("there's a difference between X and Y") about society, relationships, race, gender, class, money, respectability politics, media hypocrisy — escalating through rhythmic repetition, rising volume, a voiced-then-defeated imagined objector, a sharpened recurring refrain, toward a tight, quotable, unhedged aphoristic closing line, in the tradition of Chris-Rock-style observational stand-up. Trigger on requests to write a stand-up bit, comedy routine, observational monologue with escalating examples building to a punchline. This skill is not for scripted sketch comedy, character-based sketches, mockumentary bits, confessional storytelling comedy, flat one-liner lists lacking escalation, or requests to reproduce a real comedian's actual material verbatim.

68

Quality

82%

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

77%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 a well-structured, highly actionable guide with an explicit workflow, validation checklist, feedback-style troubleshooting, and clean one-level-deep references to real bundle files. Its main weakness is token efficiency: core ideas (claim framing, refrain handling) are restated across three or four sections and could be consolidated.

Suggestions

Consolidate the claim-framing guidance: Mindset, Prerequisites, Workflow step 1, and the first Core Mechanics bullet all restate 'an obvious truth the audience was too polite to say' — state it once and cross-reference.

Merge refrain guidance into one place: it currently appears in Workflow step 4, Core Mechanics, Example 3, and Troubleshooting; a single treatment with the example would cut significant tokens.

Replace the five isolated technique snippets with one complete short bit annotated by technique, plus 1-2 fragments — this both tightens the Examples section and closes the actionability gap of never showing a full assembled routine.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain guidance Claude would not produce unprompted (contrastive framing, escalation ordering, objector handling), but the same points recur across sections: the 'obvious truth the audience was too polite to say' framing appears in Mindset ("the audience already half-believed the claim"), Workflow step 1, and Core Mechanics' opening bullet; refrain guidance is repeated in Workflow step 4, Core Mechanics, Examples, and Troubleshooting ("check whether they're actually escalating or just restating"). This fits anchor 3 ('mostly efficient but could be tightened') better than anchor 4, since the repetition is more than minor.

3 / 5

Actionability

Concrete, executable guidance throughout: an 8-step Workflow ("Draft 3-5 escalating examples... ordered so each one is more pointed than the last"), three BAD/GOOD example pairs with SYMPTOM and CONSEQUENCE, and five tagged example snippets each with a '*What it demonstrates*' note. This is mostly anchor 4-5 territory for an instruction-only skill; it falls short of anchor 5 because no complete end-to-end example bit is shown — all demonstrations are fragments in isolation, leaving the assembly (especially pacing across a full routine) to be inferred.

4 / 5

Workflow Clarity

The Workflow section gives a clearly numbered 8-step sequence with an explicit validation step — "Check the draft. Run through the checklist in ## Troubleshooting" — and the Troubleshooting section closes the loop with symptom→fix guidance ("If the closing line's edge is missing, check for a hidden qualifier and cut it") plus a four-item delivery checklist. Prerequisites even adds an early user check ("Read back the claim in one sentence before drafting examples, so the user can redirect early"), matching anchor 5's explicit validation and feedback loops.

5 / 5

Progressive Disclosure

The body is a well-organized overview and both referenced files exist and are one level deep, clearly signaled in a When-to-Use table ([Refrain and Escalation Techniques], [Subject Selection and Framing]) plus targeted inline links from Troubleshooting ("see [Subject Selection and Framing](references/subject-selection-and-framing.md)"). The deep-dive material (refrain mechanics, subject framing) is appropriately split out rather than inlined, matching anchor 5; the only blemish is that the refrain reference is linked twice in the References section (bullet plus table row), which is cosmetic.

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 strong description: it states exactly what the skill produces, gives explicit trigger phrases, and pre-empts conflict with adjacent comedy formats through a concrete exclusion list. The only deductions are for a single action verb padded with heavy structural detail and a few missing natural trigger synonyms.

DimensionReasoningScore

Specificity

Quotes a single primary action ("Generate an original, high-energy observational stand-up bit") but elaborates it with several concrete structural features — "one bold contrastive claim ('there's a difference between X and Y')", "escalating through rhythmic repetition, rising volume, a voiced-then-defeated imagined objector, a sharpened recurring refrain", "tight, quotable, unhedged aphoristic closing line". This matches anchor 4 (several specifics, minor gaps) rather than 5, which expects multiple distinct concrete actions; it is well above anchor 3's '1-2 concrete actions' given the comprehensive structural inventory.

4 / 5

Completeness

Explicitly answers both questions: what — "Generate an original, high-energy observational stand-up bit — a routine built on one bold contrastive claim..."; when — "Trigger on requests to write a stand-up bit, comedy routine, observational monologue...", plus an explicit when-not clause ("This skill is not for scripted sketch comedy..."). This matches anchor 5 (clear what AND when with concrete trigger phrases); anchor 4's weaker 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural trigger phrases are explicit: "Trigger on requests to write a stand-up bit, comedy routine, observational monologue with escalating examples building to a punchline" — covering 'stand-up bit', 'comedy routine', 'monologue', 'punchline', plus the disambiguating 'Chris-Rock-style observational'. Good coverage but a few common variations users would say are missing (e.g., 'jokes', 'write me a set', 'open mic'), so anchor 4 rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (observational stand-up in a named tradition) with distinct triggers, and the exclusion list actively prevents misfires against adjacent skills: "not for scripted sketch comedy, character-based sketches, mockumentary bits, confessional storytelling comedy, flat one-liner lists". Minimal conflict risk — a clean anchor-5 match; it is far more differentiated than anchor 4's 'minor overlap risk with closely related skills'.

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.