CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

golden-pptx-kw

Use when testing keyword categorization

Quality

42%

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

Fix and improve this skill with Tessl

tessl review fix ./tests/golden/phase2/pptx_kw/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

32%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 serviceable index with genuinely good progressive disclosure — real, clearly signaled, one-level-deep reference files — but everything else is weak: it is padded with duplicated statistics and a broken truncated code example, gives no instruction on what to do with the material, and presents no workflow. As a skill it reads as an auto-generated scrape rather than actionable guidance.

Suggestions

Cut the duplicated Presentation Statistics block and the restated description line; keep one compact overview and remove the truncated 50-line code example (or replace it with one short, complete, runnable example).

Add explicit instructions for the skill's single action, e.g. 'To find content, open references/index.md, pick the matching section file, and read that section for slides, notes, and code.'

Move the full code examples and tables into the section reference files, leaving only a one-line pointer per category in SKILL.md so the overview stays lean.

DimensionReasoningScore

Conciseness

The body is noticeably padded: statistics are stated twice ('Total Slides: 8 / Total Sections: 3' in Section Overview and again in Presentation Statistics), the description line is repeated verbatim, and a 50-line scraped code example is inlined and even truncated mid-line with '...'. This matches 'noticeably verbose; several unnecessary explanations or padded sections', and the broken inlined example keeps it well below 3.

2 / 5

Actionability

Concrete artifacts exist (bash and python blocks, a table, file paths) but they are scraped presentation fragments with zero instruction on how to use them — 'pip install thing', 'print(\'hello\')', and a truncated function teach nothing. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute'; it cannot reach 3 because no example is complete or purposeful.

2 / 5

Workflow Clarity

There is no sequence of steps at all — the body is a content index, and the one implied action (consult the reference files) is buried under redundant sections. This sits between 'steps missing or incoherent' (1) and 'rough sequence present but many gaps' (2); the presence of a coherent Navigation section lifts it to 2, but there is no task guidance or error handling to justify 3.

2 / 5

Progressive Disclosure

The Navigation section clearly signals real, verified, one-level-deep references ('references/section_s1-s1.md - Setup', etc., plus 'See references/index.md for complete presentation structure'), and index.md links directly to the section files. It does not reach 5 because content that belongs in the references (the long code examples and tables) is inlined in the overview, and the split between the summary and the reference files is partially redundant.

4 / 5

Total

10

/

20

Passed

Description

25%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.

The description is a bare trigger clause with no statement of capabilities. It neither tells Claude what the skill does nor distinguishes it from other skills, and its keywords are too generic to fire reliably. It needs a concrete action statement plus presentation-specific trigger terms.

Suggestions

Add a concrete 'what' statement, e.g. 'Indexes and retrieves content from a Golden_Pptx_Kw presentation (slides, speaker notes, code examples, tables). Use when testing keyword categorization against presentation content.'

Include natural trigger terms users would actually say — 'presentation', 'pptx', 'slides', 'speaker notes', 'keyword categorization' — so the skill fires on real requests.

Tie the description to the artifact type (presentation/.pptx content) to reduce conflict with other keyword-matching or testing skills.

DimensionReasoningScore

Specificity

The description 'Use when testing keyword categorization' names a domain but states no concrete action whatsoever — there is no 'what' the skill does, only a when-clause. It falls between the entirely-vague anchor (1) and the domain-with-minimal-actions anchor (2); because a domain is named, 2 fits better than 1, but the total absence of any action keeps it below 3.

2 / 5

Completeness

Only a 'when' is present ('Use when testing keyword categorization') with no description of what the skill does — exactly matching the anchor-2 example 'Use when working with documents'. It cannot score 3 because the 'what' is entirely missing, not merely weakly implied.

2 / 5

Trigger Term Quality

Only two generic keywords appear ('testing', 'keyword categorization'), and no natural user phrasing, synonyms, or related terms are present. This matches 'one or two generic keywords; missing the natural phrases users say' and clearly lacks the keyword coverage of level 3+.

2 / 5

Distinctiveness Conflict Risk

The phrase is extremely broad and would overlap with any keyword-matching, categorization, or testing skill, matching 'very broad; high overlap risk with many similar skills'. It does not reach 3 because nothing anchors it to a specific artifact or task (the name 'golden-pptx-kw' hints at presentations, but the description never mentions them).

2 / 5

Total

8

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

yusufkaraaslan/Skill_Seekers

Path

tests/golden/phase2/pptx_kw/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.