skill-deck

Generate slide deck presentations from briefs — use when you need slides, pitch decks, or visual summaries

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/skill-deck/SKILL.md

Quality

Content

63%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 content delivers a clear, actionable 4-step pipeline with an explicit outline-approval gate and concrete prompts, commands, and templates. Its weaknesses are padding from generic presentation best practices, a dangling reference to a non-existent host-adapter file, and no progressive disclosure into bundle files.

Suggestions

Trim or move the 'Slide Structure Best Practices' and 'By Audience Type' sections — most of that guidance (one idea per slide, 5-7 bullets, define technical terms) is knowledge Claude already has — into a short reference file or a few lines.

Fix or remove the reference to 'skills/blocks/codex-host-adapter.md' — no such file exists in the bundle, so the pointer is dead.

Add a post-render validation step after Step 4 (confirm the .pptx exists and is non-empty, offer to reopen/inspect it) to complete the workflow's checkpoint coverage.

Dimension	Reasoning	Score
Conciseness	The pipeline steps are tight and procedural, but sections like 'Slide Structure Best Practices' ('One idea per slide', '5-7 bullets max', 'Balance detail with accessibility') restate presentation knowledge Claude already has, and the audience-type subsections could be trimmed. Mostly efficient with some unnecessary explanation — anchor 3, not 4, because the generic best-practices block is a meaningful chunk of the file.	3 / 5
Actionability	Concrete, executable guidance throughout: exact AskUserQuestion option sets, a plugin-check command with the exact install command, a markdown outline template, and an example filename. Falls short of anchor 5 because actual PPTX rendering is delegated to an external skill with no code/spec of its own, and the reference to 'skills/blocks/codex-host-adapter.md' points at a file that does not exist in the bundle.	4 / 5
Workflow Clarity	The 4-step pipeline is clearly sequenced with a prerequisites check (including the exact failure message to show) and an explicit approval gate ('the user MUST approve the outline structure before PPTX generation'). Missing a post-render validation step (verify the PPTX was created/opens) keeps it at anchor 4 rather than 5; no destructive/batch cap applies.	4 / 5
Progressive Disclosure	The body is well-sectioned but monolithic — no bundle files exist (no references/, scripts/, or assets/), while the body references 'skills/blocks/codex-host-adapter.md', a path that is neither clearly signaled nor present in the bundle. Content like the audience-type guidance and example workflows could live in reference files; some structure present but organization could be better — anchor 3.	3 / 5
	Total	14 / 20 Passed

Description

65%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 concise, well-scoped description that clearly answers what the skill does and when to use it. Its main weaknesses are the thin capability list (only one action named) and second-person phrasing in the trigger clause, plus missing common synonyms like PowerPoint/presentations.

Suggestions

Expand the 'what' clause to name the full pipeline: e.g. 'Generate slide deck presentations from briefs with optional research, outline approval, and PPTX export'.

Rewrite the trigger clause in third person and add common synonyms: 'Use when the user asks for slides, pitch decks, presentations, PowerPoint (.pptx) files, or visual summaries'.

Avoid second-person phrasing ('use when you need') to match the third-person voice used by high-quality descriptions.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — 'Generate slide deck presentations from briefs' — but omits the skill's other capabilities (optional research, outline approval, PPTX export). The trigger clause 'use when you need slides' is second person, which per the judging guidelines reduces the score by one from an anchor-3 base.	2 / 5
Completeness	Both parts are present: what ('Generate slide deck presentations from briefs') and when ('use when you need slides, pitch decks, or visual summaries'). The when-clause is explicit but could be more specific — it omits 'presentations', 'PowerPoint', and the PPTX output format, keeping it at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	'slides, pitch decks, or visual summaries' are natural user phrases with good coverage, but common variations like 'PowerPoint', 'presentation', and '.pptx' are missing from the trigger list. Not the comprehensive synonym coverage of anchor 5, but clearly above anchor 3's partial coverage.	4 / 5
Distinctiveness Conflict Risk	'slide deck presentations from briefs' carves a clear niche with distinct triggers (slides, pitch decks, visual summaries). Minor overlap risk with generic presentation/.pptx document skills keeps it below anchor 5's minimal-conflict bar.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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: nyldn/claude-octopus
Path: skills/skill-deck/SKILL.md
Commit: 0093dab

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.