CtrlK
BlogDocsLog inGet started
Tessl Logo

sn-ppt-doctor

Use when diagnosing PPT Skill setup or failures involving source parsing, Playwright or Chromium rendering, HTML-to-PPTX export, Workbench startup, or bundled search and image-tool configuration.

60

Quality

73%

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

Quality

Content

75%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 content is well-structured, actionable, and concise with a clear diagnostic procedure and copy-paste commands; it stops just short of top marks due to minor over-explanation and implicit rather than explicit verification checkpoints.

DimensionReasoningScore

Conciseness

The body is dense and mostly efficient, using lists, a status table, and ini/bash blocks with little padding; only minor explanatory prose (e.g., restating that the skill is read-only) could be trimmed, keeping it just below a 5.

4 / 5

Actionability

It provides concrete, mostly copy-paste-ready commands ("python3 \"$SKILL_DIR/ppt_doctor/check_environment.py\" --probe-search") with specific flags and an env config example, with only minor gaps such as the unset $SKILL_DIR convention and omitted probe-output-dir default.

4 / 5

Workflow Clarity

A clear diagnostic procedure is sequenced (status table -> native tool inspection steps 1-5 -> call commands) with status-based decision points; the skill is explicitly non-destructive/read-only, so the destructive-cap does not apply, though explicit verification checkpoints before reporting are only implicit.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections (配置, 检查内容, 原生工具有效性, 调用) with appropriately placed code and tables; no bundle reference files exist to navigate, and the body is a single self-contained doc that could split detail but is already well-structured, landing above the midpoint.

4 / 5

Total

16

/

20

Passed

Description

71%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 specific and distinct with a clear what/when structure, but its trigger terms lean technical and miss natural user phrasings, keeping it just below the top tier.

Suggestions

Add natural-language trigger phrases users would actually say (e.g., "PPT generation broken", "PPT report fails", "deck export error") alongside the technical terms.

Consider mentioning the Chinese trigger ("ppt 体检") or a plain synonym in the description so non-English or casual phrasings are covered.

DimensionReasoningScore

Specificity

The description names the diagnostic action and enumerates several concrete failure areas ("source parsing, Playwright or Chromium rendering, HTML-to-PPTX export, Workbench startup, or bundled search and image-tool configuration"), with only minor gaps in coverage rather than comprehensive enumeration.

4 / 5

Completeness

It has an explicit "Use when..." trigger and states the what ("diagnosing PPT Skill setup or failures"), answering both; the when lists concrete scenarios but is fairly technical rather than phrased as natural user utterances, so it falls just below a 5.

4 / 5

Trigger Term Quality

Relevant keywords like "PPT", "setup", "failures", "export", and "search" are present, but the terms skew toward technical jargon (Playwright, Chromium, Workbench) and lack common natural-language variations or synonyms a user would casually say.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (PPT Skill diagnostics) with distinct, specific triggers that are unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
OpenSenseNova/SenseNova-Skills
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.