CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codex-ppt

Generate visually unified image-based PPT/PPTX decks from articles, reports, papers, notes, or outlines.

Quality

71%

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 ./skills/codex-ppt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 well-sequenced orchestration contract with excellent validation gates and checklists, but its progressive-disclosure design collapses in practice because the docs/ and prompts/ files it delegates all commands and detailed rules to are missing from the bundle, leaving the body itself without executable commands. Shipping the referenced files or inlining the essential script invocations would resolve both weaknesses.

Suggestions

Include the referenced 'docs/' and 'prompts/slide-worker.md' files in the skill bundle — the body delegates all commands and detailed rules to them, and their absence makes every 'read docs/...' instruction a dead reference.

Inline at least the minimal executable invocations for the bundled scripts (e.g. how to call record_slide_result.py, prepare_slide_prompts.py, assemble_ppt.py with their arguments) so the workflow is executable without the docs/ layer.

Consolidate the repeated subagent-mandate and backend-fixity statements (currently restated in Hard Constraints, workflow steps, Subagent Dispatch, and Acceptance Criteria) into one authoritative section to trim tokens.

DimensionReasoningScore

Conciseness

The body is imperative and dense with no explanation of concepts Claude already knows — no padding about what PPT or image generation is. It sits at 4 ('minor instances of over-explanation that could be trimmed') rather than 5 because the same constraints are restated across sections: the subagent mandate appears in Hard Constraints, steps 8-9, Subagent Dispatch, and Acceptance Criteria; backend fixity and 'don't mark complete from chat alone' are each repeated three-plus times.

4 / 5

Actionability

Concrete artifacts are named throughout ('scripts/prepare_slide_prompts.py', 'record_slide_result.py', 'origin_image/slide_XX.png', state values 'pending/dispatched/recorded/accepted'), but the body contains no executable command or invocation syntax for any script — all commands are delegated to 'docs/slide-generation-and-subagents.md' and other docs/ files that are absent from the bundle. That is 'some concrete guidance but incomplete; missing key details', not the mostly-executable level of score 4.

3 / 5

Workflow Clarity

The 13-step workflow is clearly sequenced with explicit validation gates ('If any slide is pending, dispatched, or blocked, stop'), a QA feedback loop (inspect every slide, regenerate severe failures, validate edited output before replacing), a user-visible progress checklist tied to real file evidence, and blocker reporting with slide id and evidence. This matches the score-5 anchor: explicit validation steps, error-recovery loops, and checklists for a complex batch process.

5 / 5

Progressive Disclosure

The structure is well designed — a Reference Map with per-file descriptions and read-timing guidance ('read only when config is needed'), one level deep — but scoring against the actual bundle, the 10 referenced 'docs/*.md' files and 'prompts/slide-worker.md' do not exist, so the primary detailed content the body defers to is unreachable dead references. Only 'references/*.md' and 'scripts/' are actually present. Good signaling with broken navigation lands at 3, above 'references buried' (2) but below the reliable one-level-deep organization of 4-5.

3 / 5

Total

15

/

20

Passed

Description

61%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 a clear 'what' and a distinctive image-based niche, but it lacks any explicit 'when to use' trigger guidance and undersells the skill's full capability set. Adding a 'Use when...' clause with natural trigger phrases would lift both completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user wants a presentation/PPT/slides built from an article, report, paper, or outline and accepts full-slide generated images.'

Mention the other concrete capabilities (speaker notes, PPTX assembly, reusable style library) so the 'what' is comprehensive rather than a single action.

Include the synonyms 'presentation', 'PowerPoint', and 'slides' as trigger terms to reduce overlap ambiguity with editable-pptx skills.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — 'Generate visually unified image-based PPT/PPTX decks' — with a good range of input types ('articles, reports, papers, notes, or outlines'), but it is a single action: capabilities the skill actually has (speaker notes, style library, sample approval, assembly) are not mentioned. It matches 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 'Lists several specific actions' (score 4), since only the generate action is stated.

3 / 5

Completeness

The 'what' is clear (generate image-based PPT decks from source material), but there is no 'Use when...' clause or equivalent explicit trigger guidance — when to use it is at best weakly implied by the input list. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3; it cannot reach 4 ('when' could be more explicit) because 'when' is entirely unstated, not just under-specified.

3 / 5

Trigger Term Quality

Natural terms include 'PPT', 'PPTX', 'decks', and the source-material keywords 'articles, reports, papers, notes, outlines', which users would plausibly say. It falls short of score 5 because common synonyms like 'presentation', 'PowerPoint', and 'slides' are absent, leaving a few natural trigger phrases missing.

4 / 5

Distinctiveness Conflict Risk

'Visually unified image-based PPT/PPTX decks' carves out a fairly distinct niche (full-slide images, not editable shapes), so it is 'mostly distinct' like the score-4 anchor. It does not reach 5 because a generic 'make me a presentation' request would also match general editable-pptx skills, and the description offers no trigger phrasing to disambiguate when to prefer this one.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

ningzimu/codex-ppt-skill

Path

skills/codex-ppt/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.