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.

59

Quality

67%

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

85%Weight 40%Scale 1-3

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 well-structured, actionable reading workflow with concrete tool calls, a refine-retry feedback loop, and clean sectioning; its main weakness is repeated restatement of the no-fabrication rule across sections. It scores at the top anchor on actionability, workflow clarity, and progressive disclosure.

Suggestions

Consolidate the repeated 'do not invent exact facts/metrics/dates/names' guidance into one authoritative statement and reference it from the other sections to reduce redundancy.

Consider trimming the overlapping restatements between 'Evidence rules', 'When the inspected material is thin', and 'Output discipline' since several points (omit or state qualitatively, trust inspected source) recur.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the 'do not invent exact facts' rule is restated four or more times across Evidence rules, step 8, the thin-material section, and Output discipline, so it could be tightened rather than rated fully lean.

2 / 3

Actionability

It gives complete, concrete tool signatures (grep(pattern, path, glob), glob(pattern, path), read_file(path, offset, limit)) plus a fully worked Q3 example with actual calls like read_file(path='/source.md', offset=118, limit=60); this is actionable, specific guidance with no pseudocode, meeting the top anchor for an instruction-only skill.

3 / 3

Workflow Clarity

The reading workflow is a clear 8-step sequence with an explicit refine-and-repeat feedback loop (step 6), a stop condition ('Stop reading once the current slide has enough source-grounded evidence'), and conflict-resolution rules, satisfying the clear-sequence-with-feedback-loops anchor.

3 / 3

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clear, well-labeled sections (Boundary, When to use, Reading workflow, Evidence rules, Long-document discipline, Output discipline) with no nested references, matching the well-organized-sections top anchor for a self-contained skill.

3 / 3

Total

11

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 competent and on-domain but not exemplary: it identifies the niche and an embedded use context yet lacks an explicit 'Use when…' trigger clause and broader natural trigger variations. All dimensions land at the middle anchor.

Suggestions

Add an explicit 'Use when…' clause naming concrete triggers (e.g., 'Use when generating slides from reference documents, retrieved snippets, or source pages provided by the host').

Broaden trigger terms to natural user phrasing such as 'PPT', 'presentation', 'deck', and 'make slides from this document'.

List a couple more concrete actions (e.g., 'grep source paths, read targeted sections, verify facts against inspected passages') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('source-document reading workflow for Oh My PPT') and actions ('Read before generating slides from reference documents or retrieved snippets') but does not list multiple concrete actions, matching the 'names domain and some actions' anchor rather than the comprehensive multi-action level.

2 / 3

Completeness

It states what the skill does and embeds a when-context ('before generating slides from reference documents or retrieved snippets'), but there is no explicit 'Use when…' trigger clause, which the guidelines cap at 2 rather than the clearly-answered-both level.

2 / 3

Trigger Term Quality

Relevant natural terms like 'reference documents', 'generating slides', and 'source documents' are present, but 'retrieved snippets' is technical and common variations users would say ('PPT', 'presentation', 'deck') are missing, so it sits at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The 'Oh My PPT' qualifier gives it a recognizable niche, but the source/reference-document reading framing could still overlap with general document skills, matching 'somewhat specific but could still overlap'.

2 / 3

Total

8

/

12

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.