CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-deck-context

Use when preparing the narrative, sources, and design context for a new editable PPTX deck.

Quality

79%

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 ./plugins/pptx-deck-creation/skills/pptx-deck-context/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-structured instruction-only skill: a coherent pre-authoring decision sequence, strong rules, and a clean one-level reference to a real bundle file. The only meaningful gap is the absence of explicit validation/feedback checkpoints and any example of the `source_ref` or `summary` artifact formats.

Suggestions

Add a validation step to the decision sequence, e.g. 'Before authoring, verify every metric, quotation, and chart value has a `source_ref` in the manifest; add missing ones or drop the claim.'

Include a one-line example of a `source_ref` and a `summary.design_context` record so the recorded artifacts are unambiguous to produce.

Briefly state what `summary` is (where it lives, its role for the downstream authoring skill) since it is currently referenced without definition.

DimensionReasoningScore

Conciseness

The body is lean and directive with zero padding — every step and rule earns its place (e.g. 'Translate design signals into explicit fills, typography, spacing, and bboxes; do not rely on an automatic layout engine'), assuming Claude's competence throughout.

5 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: named frameworks (`mckinsey`, `scqa`, `pyramid`, `mece`...), a real file path (`references/design-profiles.md`), and specific fields to record. Not a 5 because the `source_ref` and `summary` formats are referenced but never exemplified, leaving minor gaps.

4 / 5

Workflow Clarity

A clear five-step 'Decision sequence' properly ordered before slide authoring, with step 5 acting as a pre-authoring checkpoint ('Record the framework, assumptions, source manifest... before authoring slides'). Not a 5 because no explicit validation or feedback loop is stated (e.g. verifying every metric has a `source_ref`).

4 / 5

Progressive Disclosure

Well-organized sections under 50 lines, with one clearly-signaled, one-level-deep reference (`references/design-profiles.md`) that exists in the bundle and is linked both inline in step 4 and in a dedicated closing line. Scored against the actual bundle structure.

5 / 5

Total

18

/

20

Passed

Description

62%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, correctly third-person description with an explicit 'Use when...' trigger and a clear niche. Its main weakness is thin keyword coverage and a 'when' clause that mirrors the 'what' rather than offering distinct natural trigger phrases like 'presentation' or 'slides'.

Suggestions

Add natural synonyms users would actually say — e.g. 'presentation', 'Powerpoint', 'slides', 'slide deck' — so the skill triggers on common phrasings rather than only 'PPTX deck'.

Replace the generic 'preparing' with more concrete verbs, e.g. 'Draft the narrative, build the source manifest, and lock the design profile before authoring a new editable PPTX deck'.

Differentiate the 'when' from the 'what' with a distinct trigger condition, e.g. 'Use when the user asks for a new deck or slide narrative, before any coordinates or PPTX objects are authored'.

DimensionReasoningScore

Specificity

The description names the domain ('a new editable PPTX deck') and the concrete objects of preparation ('the narrative, sources, and design context'), but the only action verb is the generic 'preparing' — matching the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage.

3 / 5

Completeness

It explicitly answers both what ('preparing the narrative, sources, and design context for a new editable PPTX deck') and when (an explicit 'Use when...' clause). Not a 5 because the 'when' clause largely restates the 'what' rather than adding distinct concrete trigger phrases.

4 / 5

Trigger Term Quality

'PPTX deck' and 'design context' are relevant keywords, but the most natural user phrasings — 'presentation', 'PowerPoint', 'slides' — are absent, matching the anchor for some relevant keywords missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

The pre-authoring context niche (narrative, sources, design lock vs. authoring coordinates) is mostly distinct, but it would still plausibly trigger alongside a general presentation-creation skill — minor overlap risk with closely related skills.

4 / 5

Total

14

/

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

wshobson/agents

Path

plugins/pptx-deck-creation/skills/pptx-deck-context/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.