CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ppt-creator

Deprecated presentation entry retained as a compatibility notice. Use to check the retirement status of ppt-creator or identify a legacy installation. This package does not generate PPTX files.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

For what it is — a retirement notice rather than a capability skill — the body is efficient, honest, and actionable, covering the status, the compatibility constraint, the removal timeline, and a conditional redirect to the successor. The only real weakness is the underspecified fallback redirect, which leaves the model to improvise when deck-creator is absent.

DimensionReasoningScore

Conciseness

The body is lean — every paragraph conveys status, compatibility, or redirect information — and the date and version number are appropriate in a notice that is itself a deprecation section; minor tightening is possible (the "do not promise access to a private edition" clause is cryptic and "builder, templates or creation workflow" slightly restates the retirement).

4 / 5

Actionability

It gives mostly concrete, executable guidance — "Keep the existing `daymade-docs:ppt-creator` identity", "use `deck-creator` only when it is already installed", "Do not use it to generate a slide deck" — with one minor gap: the fallback branch "select a presentation workflow actually available in the current host" says what to do but not how to find one.

4 / 5

Workflow Clarity

As a single-purpose notice it lays out a clear response: state the retirement, preserve the identity, and redirect with an explicit two-branch conditional; it is not fully unambiguous because the fallback branch leaves workflow selection to judgment, so it sits below the simple-skill 5 anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, entirely self-contained with no bundle files (no references/, scripts/, or assets/ directories exist), and nothing here needs external material; a clear heading plus three focused paragraphs satisfies the well-organized-structure standard for the simple-skill case.

5 / 5

Total

17

/

20

Passed

Description

73%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 well-crafted deprecation description: it is honest about the skill's retired state, provides explicit trigger guidance for legitimate residual uses (status checks, legacy-install identification), and actively disclaims the former capability to avoid mis-triggering. Its main limitation is inherent to a retirement notice — few concrete actions to enumerate — which caps specificity.

Suggestions

Raise specificity by naming the concrete actions a model should take when invoked, e.g., "Explains the 2026-08-07 retirement, keeps the daymade-docs:ppt-creator identity for installed-plugin compatibility, and redirects new presentation requests to deck-creator."

Add one or two user-side trigger phrases (e.g., "Use when the user asks what happened to ppt-creator or why slide generation fails") to push completeness from purpose-phrasing to explicit trigger phrasing.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("check the retirement status of ppt-creator", "identify a legacy installation") plus an explicit negative capability ("does not generate PPTX files"), but does not list several specific actions as anchor 4 requires.

3 / 5

Completeness

It clearly answers both what ("Deprecated presentation entry retained as a compatibility notice... does not generate PPTX files") and when ("Use to check the retirement status of ppt-creator or identify a legacy installation"); the trigger guidance is explicit but phrased as purpose rather than concrete user-moment trigger phrases, so it falls short of anchor 5.

4 / 5

Trigger Term Quality

Good keyword coverage for this niche — "Deprecated", "ppt-creator", "retirement status", "legacy installation", "PPTX" — matching what a user checking on this skill would naturally say, though a few synonyms (e.g., "removed", "presentation") are missing, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — the retirement status of one specifically named skill — and the explicit "This package does not generate PPTX files" disclaimer minimizes conflict risk with any active presentation-creation skill, matching anchor 5.

5 / 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

daymade/claude-code-skills

Path

daymade-docs/ppt-creator/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.