CtrlK
BlogDocsLog inGet started
Tessl Logo

pryor-esque-confessional-standup

Generate an original, autobiographical confessional stand-up bit/story/monologue built from a genuinely painful personal anecdote, using techniques like multi-voice character embodiment (switching voice mid-story to become a parent/cop/friend/animal/younger-self), rhythmic escalating repetition, self-implicating honesty, vivid sensory specificity, plus a blunt closing truth in place of a tidy moral. Use it when a user wants to write, punch up, workshop, critique such a piece before it gets tested at an open mic. Do not use it for observational one-liners with no personal narrator, absurdist/surreal sketches, character-only sketch writing, requests to reproduce, quote, transcribe, imitate a real performer's actual routine.

72

Quality

88%

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 exemplary instruction-only skill: a sequenced workflow with validation and troubleshooting loops, concrete worked examples for every mechanic, and well-signaled references to real one-level-deep deep-dive files. Its one weakness is token efficiency — core rules (voice-switching, blunt endings, self-implication) are each restated two to three times across the Workflow, Core Mechanics, and Anti-Patterns sections.

Suggestions

Consolidate the repeated blunt-truth-ending guidance: Workflow step 7, Mechanic #6, and Anti-Pattern #4 all restate the same rule. Keep one full treatment (Mechanic #6 with its example) and have the workflow step and anti-pattern reference it briefly instead of re-explaining it.

Similarly, the unannounced voice-switch rule is fully spelled out in Mechanic #2, Anti-Pattern #3, and the reference-table description; keep the WHY/SYMPTOM/EXAMPLE structure in the anti-pattern and trim the restated rationale in Mechanic #2 to a one-line pointer.

The self-implication rule appears in Workflow step 2, Mechanic #3, and the second anti-pattern with overlapping rationale; merge the 'why' explanation into a single location and cross-reference it from the others to cut roughly 15-20 lines without losing guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but the same craft rules are restated across sections: the blunt-truth-ending rule appears in Workflow step 7, Mechanic #6, and Anti-Pattern #4; the unannounced voice-switch rule appears in Mechanic #2, Anti-Pattern #3, and the reference table; self-implication likewise recurs three times. That is the 'could be tightened' anchor rather than the 'minor instances of over-explanation' of a 4 — the redundancy is structural, not incidental.

3 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: an 8-step workflow, six mechanics each demonstrated by a short freshly invented example with a note on what it demonstrates, and four anti-patterns with explicit ❌ BAD / ✅ GOOD example pairs. The examples are complete and cover the common drafting cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

The 8-step sequence is clearly ordered with an explicit validation step ('Check the draft against the anti-patterns below'), a read-aloud check before finishing, and a Troubleshooting section with error-recovery loops ('If a draft still fails to implicate the narrator, revisit step 2... Run the anti-pattern checklist again'). This is a generative writing skill, not a destructive or batch operation, so the validation cap does not apply.

5 / 5

Progressive Disclosure

SKILL.md functions as an overview, with the two deep-dive topics (voice embodiment, structuring the turn) split into real, substantive one-level-deep files that exist in the bundle, surfaced through a table giving topic, path, and 'When to Use' conditions. Navigation is easy and the split is appropriate, matching the clear-overview-with-well-signaled-references anchor.

5 / 5

Total

18

/

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.

This is a strong description: it states concrete capabilities with the key techniques named, gives an explicit 'Use it when...' trigger clause plus a do-not-use boundary list, and stays in third-person imperative voice throughout. The only weakness is moderate synonym coverage — a few natural user phrasings ('comedy set', 'jokes about my life') are not represented.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Generate an original, autobiographical confessional stand-up bit/story/monologue', 'write, punch up, workshop, critique' — and names the specific techniques involved (multi-voice character embodiment, rhythmic escalating repetition, self-implicating honesty, vivid sensory specificity, blunt closing truth), matching the comprehensive-coverage anchor. It is not a 4 because coverage shows no real gaps in what the skill does.

5 / 5

Completeness

It explicitly answers both questions: the 'what' is stated up front ('Generate an original, autobiographical confessional stand-up bit/story/monologue...') and the 'when' is explicit with concrete trigger phrases ('Use it when a user wants to write, punch up, workshop, critique such a piece before it gets tested at an open mic'), plus an explicit do-not-use list. It is not a 4 because the 'when' clause is fully explicit rather than only partially specified.

5 / 5

Trigger Term Quality

Natural user-facing terms are well covered ('stand-up', 'bit', 'story', 'monologue', 'personal anecdote', 'punch up', 'workshop', 'critique', 'open mic', 'confessional'), but a few common phrasings a user might actually say are missing (e.g. 'comedy set', 'jokes about my life', 'funny story about something that happened to me'). This fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (autobiographical confessional stand-up storytelling) with distinct triggers and explicitly enumerates exclusions ('Do not use it for observational one-liners with no personal narrator, absurdist/surreal sketches, character-only sketch writing, requests to reproduce, quote, transcribe, imitate a real performer's actual routine'), minimizing conflict risk with adjacent comedy-writing skills.

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.