CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-reference-deck-analysis

Use when analyzing a reference PPTX for read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection.

Quality

84%

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

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 lean, well-structured instruction-only skill body with concrete script invocations, an explicit safety section, and exemplary progressive disclosure to real bundle files. The only gaps are a missing code example for the primary python-pptx extraction path and a dangling requirements.txt reference.

Suggestions

Ship the referenced requirements.txt (or change the line to 'pip install defusedxml') so 'Install defusedxml from requirements.txt' is not a dangling reference.

Add a minimal 3–5 line python-pptx snippet for the primary extraction contract to make the main path copy-paste ready like the OOXML commands already are.

Briefly state what to do when validate_package.py reports malformed XML or broken relationships (e.g., record the exception in the manifest and fall back to targeted unpack inspection).

DimensionReasoningScore

Conciseness

The 43-line body is telegraphic and dense — 'compact prompt context: slide count and size, text summaries, shape counts, styles, brand signals' — with zero explanation of concepts Claude already knows and no padding. Every line carries actionable information.

5 / 5

Actionability

The OOXML section gives concrete, executable commands ('scripts/inspect.py <deck.pptx>', 'scripts/validate_package.py <deck.pptx> --output <report.json>', 'scripts/unpack.py <deck.pptx> <output-dir>'), but the primary 'Contract' path offers no code example for the task-local python-pptx extraction, and 'Install defusedxml from requirements.txt' references a requirements.txt that does not exist in the bundle. Not 3 because the provided commands are complete and runnable.

4 / 5

Workflow Clarity

A clear numbered 1–4 sequence exists with a validation tool (validate_package.py) and a conditional gate ('only when raw-package evidence is necessary'), plus a manifest checkpoint ('Record inspected parts and parsing exceptions'). It misses 5 because no validate-then-fix feedback loop is described for malformed XML or broken relationships; the read-only, non-destructive nature means the destructive-cap does not apply.

4 / 5

Progressive Disclosure

The body is a genuine overview that pushes output shapes, documentation-only patterns, and OOXML part maps to three real reference files (all verified to exist), each named with its purpose in a final pointer line, plus three real bundled scripts referenced inline in the workflow. References are one level deep and clearly signaled.

5 / 5

Total

18

/

20

Passed

Description

75%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, third-person description with an explicit trigger clause and a distinct read-only analysis niche. Its main weaknesses are the fused what/when structure and missing common synonyms (deck, presentation, slides, .pptx).

Suggestions

State the 'what' independently before the trigger clause, e.g., 'Analyzes a reference PPTX read-only to produce structure, theme, typography, and layout-rhythm evidence plus a derived template catalog. Use when analyzing a reference deck or .pptx for design evidence or OOXML diagnostics.'

Add natural trigger synonyms users would actually say — 'deck', 'presentation', 'slides', and the '.pptx' file extension.

Consider naming the concrete outputs (extraction report, diagnostics manifest, template catalog) to sharpen the what-clause.

DimensionReasoningScore

Specificity

The description lists several concrete analysis targets — 'read-only structure, theme, typography, layout rhythm, diagnostics, derived template catalogs, or safe OOXML package inspection' — giving specific capability coverage with only minor gaps. It falls short of a 5 because these are noun-phrase targets rather than the fully concrete, comprehensive action list of the top anchor.

4 / 5

Completeness

The explicit 'Use when analyzing a reference PPTX for...' clause clearly answers 'when', and the listed capabilities convey 'what'. It does not reach 5 because the 'what' is fused into the trigger clause rather than stated independently with concrete capability phrases (e.g., 'Analyzes ... and produces ...').

4 / 5

Trigger Term Quality

Natural terms like 'PPTX', 'theme', 'typography', 'layout', 'template', and 'OOXML package inspection' are present and would match user phrasing. Common synonyms such as 'deck', 'presentation', 'slides', and the '.pptx' extension are missing, keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Phrases like 'reference PPTX', 'read-only', 'derived template catalogs', and 'safe OOXML package inspection' carve a distinct niche apart from general pptx creation/editing skills. Minor overlap risk remains with a generic presentation-analysis skill, so it is mostly distinct rather than minimal-conflict.

4 / 5

Total

16

/

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-reference-deck-analysis/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.