CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-deck

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-deck/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 skill body delivers an exceptionally well-gated workflow with concrete, executable commands and thorough verification loops, but it pays for this with heavy repetition and a monolithic structure that inlines large reference-grade material. Deduplication and splitting the red-team and template content into reference files would materially improve token efficiency.

Suggestions

State each guardrail once: 'Do not invent a decision', 'include follow-up only when the brief calls for it', and 'do not claim a finished deck' are each repeated 3-4 times across Step 3, the board outline check, the audience-type sections, and Step 5. Consolidate them into a single rule where first defined and reference it by name elsewhere.

Move the ~130-line stakeholder red-team operational detail (transport exclusions, retry/budget environment variables, the seat-collection recipe) into a bundled reference file such as references/red-team.md, keeping a short summary and a one-level-deep pointer in the body.

Collapse the two overlapping markdown outline templates (the generic decision storyline and the executive/board outline) into one, keeping the decision-specific requirements and compressing the other to its distinguishing structure to cut roughly a template's worth of tokens.

DimensionReasoningScore

Conciseness

The 540-line body restates the same guardrails many times ("Do not invent a decision" appears in Step 3, the executive outline, the red-team section and the audience guidance; "include follow-up only when the brief calls for it" and "do not claim a finished deck" each recur 3-4 times) and inlines two overlapping full outline templates. The repetition goes beyond 'some tightening', matching the noticeably-verbose anchor, though it avoids explaining concepts Claude already knows.

2 / 5

Actionability

Guidance is mostly executable: a complete document-renderer.py invocation with exact flags, a copy-paste seat-collection bash script with transport guard and wait logic, exact environment variables, enumerated AskUserQuestion options, and a specified per-slide verification table. Minor gaps remain in resolving OCTO_ROOT/PLUGIN_ROOT/ORCHESTRATOR and the renderer's 'advertised host invocation', which are left to environment inference, so it sits just below the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

The 5-step pipeline is clearly sequenced with explicit validation checkpoints and feedback loops: the mandatory wireframe approval gate, the board outline check, the titles-only read, bounded repair-and-reverify rounds that re-run all checks after each rerender, and a one-row-per-slide verification table with pass/fail/unverified outcomes. This matches the anchor requiring explicit validation steps, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

The body has good internal structure (clear step and sub-section headers), but no bundle files exist: the ~130-line red-team operational section and both full outline templates are inlined content that clearly belongs in separate reference files, and the one cited reference (docs/DOCUMENT-RENDERERS.md) points into the external plugin install rather than a bundled file. This matches the anchor of some structure with content that should be separate kept inline.

3 / 5

Total

14

/

20

Passed

Description

70%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 cleanly answers both what the skill does and when to use it, with natural trigger terms and a distinct slide-deck niche. Its main limitation is that it advertises only the headline capability rather than the fuller pipeline the skill actually offers.

DimensionReasoningScore

Specificity

"Generate slide deck presentations from briefs" names the domain, the input type, and one concrete action, but omits the skill's other capabilities (research, outline approval, rendering, verification, red teaming). This matches the anchor for domain plus 1-2 concrete actions without comprehensive coverage.

3 / 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 phrased generically ("when you need") rather than with concrete user-request trigger phrasings, matching the anchor where 'when' could be more explicit or specific.

4 / 5

Trigger Term Quality

"slides", "pitch decks", "presentations" and "visual summaries" are natural terms users would say, giving good keyword coverage. Common variations like "PowerPoint", "deck" alone, and file extensions (.pptx/.ppt) are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Slide-deck and pitch-deck generation "from briefs" occupies a mostly distinct niche with named trigger objects, with only minor overlap risk against a closely related generic pptx/presentation skill. It does not fully separate from such neighbors (e.g. conversion vs. generation is not distinguished in the description itself), so it stays below the clear-niche anchor.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (563 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 3 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-deck/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.