CtrlK
BlogDocsLog inGet started
Tessl Logo

oh-my-ppt-source-reading

Source-document reading workflow for Oh My PPT. Read before generating slides from reference documents or retrieved snippets.

64

Quality

75%

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 ./resources/skills/oh-my-ppt-source-reading/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a highly actionable, well-sequenced reading workflow with concrete tool calls, a worked example, and an explicit refine-and-repeat feedback loop. Its main weakness is moderate redundancy of the anti-fabrication guidance and a single-file structure with no progressive disclosure references.

Suggestions

Consolidate the repeated no-invention / keep-the-page-full guidance into one canonical section and cross-reference it instead of restating it in Evidence rules, the thin-material section, and Output discipline.

Consider extracting the worked example and the "When the inspected material is thin" expansion playbook into a short reference file (e.g. EXAMPLES.md) to bring progressive disclosure to one level deep.

Add a one-line "Stop condition" checklist at the end of the workflow summarizing when a slide has enough source-grounded evidence to stop reading.

DimensionReasoningScore

Conciseness

Efficient and instruction-dense with no padding about concepts Claude already knows, but the no-invention / keep-the-page-full rule is restated across Evidence rules, the "thin material" section, and Output discipline and could be tightened.

4 / 5

Actionability

Gives concrete, executable tool signatures (grep(pattern, path, glob), glob(pattern, path), read_file(path, offset, limit)) with a fully worked example including specific parameters; absence of literal code is not penalized for this instruction-only skill.

5 / 5

Workflow Clarity

The 8-step Reading workflow is clearly sequenced with an explicit feedback loop (step 6: refine search terms and repeat grep -> targeted read) and grounding checks (steps 7-8); the operation is read-only so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Boundary, When to use / not to use, Reading workflow, Evidence rules, etc.) with easy navigation, but it is a single ~80-line file with no reference structure, slightly above the under-50-line simple-skill exception.

4 / 5

Total

18

/

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.

The description clearly scopes a niche workflow and gives one concrete action, but it lacks an explicit "Use when..." trigger clause and only weakly implies when to invoke it. Trigger-term coverage is good but could add common synonyms.

Suggestions

Add an explicit trigger clause, e.g. "Use when the host prompt provides sourceDocumentPaths or retrieved snippets to preserve facts from a reference document."

Expand the action list beyond the single "Read" verb to name the concrete sub-actions (grep within source paths, targeted read_file, expand thin material into an argument).

Add natural synonyms such as "source material", "reference docs", or "reading" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ("Source-document reading workflow for Oh My PPT") and one concrete action ("Read before generating slides from reference documents or retrieved snippets"), but coverage is a single action rather than comprehensive.

3 / 5

Completeness

Has a clear "what" but no explicit "Use when..." trigger clause; the "when" is only weakly implied by "Read before generating slides", so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural-term coverage ("reference documents", "retrieved snippets", "slides", "source-document") that a user would plausibly say, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The "Oh My PPT" + source-reading niche is mostly distinct with minimal conflict risk, though minor overlap exists with a sibling slide-generation skill in the same family.

4 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
arcsin1/oh-my-ppt
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.