CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-stage3-concepts

Builds a numbered, categorized concept catalogue from the talk summary and timeline, scoring each concept HIGH / MEDIUM / LOW for talk potential with optional repo enrichment. Use when you need a structured inventory of concepts before choosing a talk angle, or when assessing which ideas have the strongest presentation potential.

68

Quality

85%

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.

A well-crafted, highly actionable instruction skill: concrete file contracts, a complete output template, calibrated scoring criteria, and a validation checklist. Remaining improvements are minor — deduplicate Tips vs. Anti-patterns content and consider splitting the output template into a reference file.

DimensionReasoningScore

Conciseness

The body is efficient — lean tables, bullet criteria, and no explanations of concepts Claude already knows — but has minor redundancy: 'merge very similar concepts' and the value of LOW concepts each appear in both the Anti-patterns and Tips sections, so it falls at anchor 4 rather than a fully lean 5.

4 / 5

Actionability

Fully concrete instructional guidance: exact input/output path patterns ('talks/{YYYY}-{slug}-concepts.md'), a complete markdown output template, per-level scoring criteria with concrete indicators, a 12-category table, and hard thresholds ('Minimum 15 concepts (20+ for REX with repo)', 'Max 30% HIGH'). This is copy-paste-ready guidance for an instruction-only skill.

5 / 5

Workflow Clarity

A clear numbered 7-step sequence is backed by a validation checklist and scoring-discipline rule, but there is no explicit validate-then-fix loop after the checklist — matching anchor 4 (most checkpoints present, minor validation gap) rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist, and the ~155-line body is well organized with clear section headers and appropriate single-file placement; the output template and category table could arguably move to a reference file, keeping this at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

83%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 explicitly states what the skill does and when to use it, with domain-specific trigger phrases and concrete scoring language. Its only weaknesses are minor: slightly incomplete action coverage and a small overlap in trigger phrasing with the downstream positioning stage.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Builds a numbered, categorized concept catalogue', 'scoring each concept HIGH / MEDIUM / LOW for talk potential', 'optional repo enrichment'), but stops short of the full pipeline (extraction, categorization, output writing) that would make coverage comprehensive — matching anchor 4 rather than 5.

4 / 5

Completeness

It clearly answers both questions: the 'what' is explicit ('Builds a numbered, categorized concept catalogue... scoring each concept HIGH / MEDIUM / LOW') and the 'when' is an explicit 'Use when...' clause with two concrete trigger situations ('before choosing a talk angle, or when assessing which ideas have the strongest presentation potential').

5 / 5

Trigger Term Quality

Good natural keyword coverage ('concept catalogue', 'talk angle', 'presentation potential', 'structured inventory of concepts', 'summary', 'timeline'), but a few natural variations users might say (e.g., 'speech', 'outline', 'presentation ideas') are missing.

4 / 5

Distinctiveness Conflict Risk

The concept-catalogue/talk-potential-scoring niche is mostly distinct with clear triggers, but 'before choosing a talk angle' slightly overlaps the sibling Stage 4 (Position) skill's role, creating minor conflict risk within its own skill family.

4 / 5

Total

17

/

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: 4 suspicious

Warning

Total

14

/

16

Passed

Repository

FlorianBruniaux/claude-code-ultimate-guide

Path

examples/skills/talk-pipeline/stage-3-concepts/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.