CtrlK
BlogDocsLog inGet started
Tessl Logo

apply-comments

Apply pending @slide-comment markers written by the open-slide inspector tool. Use when the user asks to "apply comments", "process slide comments", "apply the inspector comments", or references markers left inside `slides/<id>/index.tsx`.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tightly written, fully actionable procedure with an authoritative regex, executable helper code, explicit validation, and well-handled edge cases. It assumes Claude's intelligence and stays within budget while covering destructive-operation safety. Strong result with no actionable weaknesses.

DimensionReasoningScore

Conciseness

Lean prose that assumes Claude's competence — it never explains what JSX, base64, or a regex are — and every section (procedure, decode helper, edge cases, 'Do not') earns its place in the context budget.

3 / 3

Actionability

Provides an authoritative detection regex, an executable copy-paste decode() function, a concrete node -e inspection tip, exact file paths, and a precise reverse-line-order Edit instruction — all copy-paste ready.

3 / 3

Workflow Clarity

A clear 7-step sequence includes an explicit Verify step (re-read, confirm no stray markers, run typecheck/lint/build) with a fix-what-you-broke feedback loop, appropriate for destructive batch edits across multiple slide files.

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ all absent) and none are needed; the body is cleanly sectioned (Marker format, Procedure, helper, Edge cases, Do not) with no nested reference chains, satisfying the well-organized single-file criterion.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, third-person, and clearly states both the action performed and the natural-language triggers for invocation. It avoids vague fluff and over-claims. No improvements needed.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Apply pending @slide-comment markers', 'perform the described edits', and 'delete the markers' — within a clearly scoped domain, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what the skill does (apply markers, edit, delete) and when to use it via an explicit 'Use when the user asks to...' clause with concrete triggers.

3 / 3

Trigger Term Quality

Provides natural quoted phrasings a user would actually say ('apply comments', 'process slide comments', 'apply the inspector comments') plus a concrete file-path trigger, giving strong coverage of likely variations.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow niche (open-slide inspector @slide-comment markers tied to slides/<id>/index.tsx) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
1weiho/open-slide
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.