CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ppt-script-authoring

Design and build a deck as a python-pptx program: your own layout system, the source's own figures, charts you draw, and a template's design when the user gave one.

Quality

70%

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-dist/ppt-engine/raven_ppt/skill/ppt-script-authoring/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 body is an exceptionally actionable, rigorously validated workflow document: enforced ordering, feedback loops, exact measurements, and executable code throughout. Its main liability is size — ~39k tokens with signature tables and a findings catalog inlined that belong in the existing reference files, plus discursive prose that repeats rules across sections.

Suggestions

Move the §4 helper-signature tables and the §12 findings catalog into existing or new reference files (e.g. an api.md and findings.md beside charts.md), keeping one-line pointers with the existing 'open it when...' signals.

Tighten the multi-paragraph narratives (e.g. §3.5's caption/footer geometry and the §3 blank-region rules that recur in §12) to the rule plus one worked example, cutting the measured back-stories.

Either surface the five layouts-*.md sub-references from SKILL.md directly or fold their pointers into the layouts.md entry so no content sits two reference levels deep.

DimensionReasoningScore

Conciseness

The body runs ~2130 lines (~39k tokens): §4 inlines two full helper-signature tables ('Read this rather than the modules (51k tokens of source...)') while charts.md/shapes.md exist as separate files, §3.5 spends ~60 lines on caption/footer geometry including measured back-stories ('on five reference pages, three of them at 6.40in and 6.44in'), and rules recur across §3, §6.5 and §12. This is 'noticeably verbose; several unnecessary explanations or padded sections' — not 1 because it never explains basic concepts Claude already knows and nearly every passage is operational; not 3 because the sheer inlined API/ findings bulk goes beyond 'could be tightened'.

2 / 5

Actionability

Fully executable and copy-paste ready: a complete program from imports to 'prs.save(os.environ["PPT_OUTPUT"]) # the last line of every program', exact thresholds ('body copy stays at or above 14pt', 'the median is 250'), executable geometry ('assert stack(right).short_by(*PLAN, *((GUTTER,) * (len(PLAN) - 1))) == 0.0'), and per-failure remediation ('Under 1 is refused, because a cover that does not cover is fit="contain"'). Specific examples cover the common cases.

5 / 5

Workflow Clarity

The sequence is explicitly enforced, not suggested — 'ppt_build refuses until ppt_prepare has read the task', 'ppt_outline records it, and the build refuses until it exists' — with validation checkpoints at every stage and a full refusal/report catalog in §12 naming the move for each. Feedback loops are explicit: 'Fix everything a build reported before you build again, and send the edits and the build in one reply' and 'Measure every band, ask short_by, then draw' give validate-fix-retry cycles for error recovery.

5 / 5

Progressive Disclosure

Seven reference files are linked with purpose signals ('Open it now, before the first page', 'Open it when a page carries a table', 'Open it before choosing a form') and all seven exist in references/ (charts.md, design-requirements.md, formulas.md, icons.md, layouts.md, shapes.md, tables.md). Not 5: layouts.md itself links to five further files (layouts-data/figures/multiples/primitives/type.md), making those two levels deep and undiscoverable from SKILL.md, and the inlined helper API and findings catalogs are content that could live in the existing references.

4 / 5

Total

16

/

20

Passed

Description

58%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 is a specific, distinctive one-sentence capability statement for python-pptx deck authoring, stronger than most vague examples. Its weaknesses are the absent 'when to use' guidance and the missing natural trigger vocabulary (PowerPoint, presentation, slides, .pptx) that users would actually say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a presentation, deck, slides, or PowerPoint (.pptx) file, or mentions python-pptx.'

Include the natural synonyms users say — PowerPoint, presentation, slides, .pptx — rather than relying on 'deck' and the library name 'python-pptx' alone.

Consider naming the deliverable (.pptx file) so the skill triggers on file-extension mentions as well as task mentions.

DimensionReasoningScore

Specificity

"Design and build a deck as a python-pptx program" names the domain and technology, and the colon list enumerates several concrete capabilities ("your own layout system", "the source's own figures", "charts you draw", "a template's design"). This matches the anchor 'lists several specific actions; minor gaps in coverage' — not 5 because ingest, outline and review stages of the workflow are unmentioned, and not 3 because it goes beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent trigger guidance — the only 'when' ("a template's design when the user gave one") conditions a sub-feature, not skill usage. Per the judging guidelines a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Present keywords are "deck", "python-pptx", "charts", "figures", "template" — but the most natural user phrasings for this domain ("PowerPoint", "presentation", "slides", ".pptx") are absent, and "python-pptx" is a library name users rarely say. This is 'some relevant keywords but missing common variations or synonyms' rather than 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

"a deck as a python-pptx program" carves a clear niche that few skills would accidentally trigger, and the capability list is distinctive. Not 5: terms like "deck", "charts you draw" and "template" carry minor overlap risk with presentation- and charting/dataviz-adjacent skills, and no explicit triggers sharpen the boundary.

4 / 5

Total

14

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 13 missing, 13 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

EverMind-AI/Raven

Path

plugins-dist/ppt-engine/raven_ppt/skill/ppt-script-authoring/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.