CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-stage6-revision

Produces revision sheets with quick navigation by act, a master concept-to-URL table, Q&A cheat-sheet with 6-10 anticipated questions, glossary, and external resources list. Use when preparing for a talk with Q&A, creating shareable reference material for attendees, or building a safety-net glossary for live delivery.

70

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

82%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 instruction template with quantified construction rules and a validation checklist. Its main weaknesses are the monolithic inline output template and a validation step that lives only at the end of the workflow rather than as inline checkpoints.

Suggestions

Move the full output-format template to a referenced file (e.g., references/revision-template.md) and keep a brief section summary in SKILL.md, improving progressive disclosure and token efficiency for the ~135-line template block.

Embed validation inline in the 8-step workflow — e.g., after building the master table, cross-check it against pitch/slides concepts and fix gaps before continuing — rather than relying solely on the end-of-run checklist.

Trim the Tips section and the duplicated opening paragraph, and reconcile the metric format ("value -> context" in the template vs "{value} ({context})" in the Construction rules).

DimensionReasoningScore

Conciseness

The body is domain-specific with no explanations of concepts Claude already knows, but the opening paragraph duplicates the frontmatter description and the Tips section adds motivational rationale ("you pull up the master table in 5 seconds") that could be trimmed. Not 5: minor padding remains; not 3: the bulk of the content (template, rules, checklist) earns its tokens.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: exact input/output file paths ("talks/{YYYY}-{slug}-pitch.md"), a complete copy-paste output template, and quantified constraints ("6 questions minimum, 10 maximum", "20 seconds max", "Always with units"). Not 4: there are no gaps a reader would hit when executing — only a trivial metric-format wording inconsistency between the template and the rules.

5 / 5

Workflow Clarity

The "What this skill does" section lists a clear 8-step sequence and a dedicated validation checklist closes the workflow, but validation appears only as an end-of-run checklist — there are no inline checkpoints or validate-then-fix feedback loops within the sequence. Not 5: the anchor requires explicit validation steps and feedback loops embedded in the workflow; not 3: the sequence itself is coherent and a checklist does exist.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and the only outbound links (Related stage-5/orchestrator skills) are one level deep and clearly signaled, but the 135-line output-format template is inlined wholesale in a ~230-line SKILL.md where a references/ split would keep the overview lean. Not 5: the skill exceeds the size where inline-only structure is ideal; not 3: what is inline is the core instruction, not misfiled reference material.

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: it enumerates concrete deliverables in third person and pairs them with an explicit, multi-scenario "Use when" clause. The only gap is keyword coverage, which lacks common synonyms a user might naturally say (e.g., "presentation", "public speaking").

DimensionReasoningScore

Specificity

"Produces revision sheets with quick navigation by act, a master concept-to-URL table, Q&A cheat-sheet with 6-10 anticipated questions, glossary, and external resources list" names five concrete deliverables in third person, comprehensively covering the skill's outputs. Not 4: no coverage gaps — the deliverable list is exhaustive and each action is specific.

5 / 5

Completeness

The first sentence explicitly states what the skill produces, and "Use when preparing for a talk with Q&A, creating shareable reference material for attendees, or building a safety-net glossary for live delivery" gives explicit trigger guidance with three concrete scenarios. Not 4: the "when" is specific and multi-scenario, not merely present.

5 / 5

Trigger Term Quality

"talk", "Q&A", "revision sheets", "glossary", "reference material for attendees", "live delivery" are natural phrases a user would say. Not 5: common synonyms like "presentation", "public speaking", or "conference talk" are missing, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The talk-revision niche with triggers like "preparing for a talk with Q&A" and "safety-net glossary for live delivery" is clearly distinct from other skill domains with minimal conflict risk. Not 4: the overlap with sibling talk-stage skills is resolved by the explicit "revision sheets / Q&A prep" framing.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository

FlorianBruniaux/claude-code-ultimate-guide

Path

examples/skills/talk-pipeline/stage-6-revision/SKILL.md

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.