current-slide

Resolve which slide, page, and (optionally) selected element the user is currently viewing in the open-slide dev server. Consult this whenever the user references "this page", "this slide", "this element", "the slide I'm on", "the current page", or any deictic reference to slide content without naming it. Re-read `node_modules/.open-slide/current.json` at the start of every such turn — the user navigates between turns, so a value you read earlier in the conversation is almost certainly stale.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and the workflows are clearly sequenced with validation checkpoints, but it is verbose in its repeated staleness messaging and monolithic in structure with no progressive disclosure to separate reference files. Tightening the redundancy and splitting the field reference would lift the two middle dimensions.

Suggestions

Consolidate the re-read/staleness guidance: it currently appears in the description, the "Re-read on every deictic turn" section, and the "Staleness" section — merge the duplicates so the critical point is stated once and cross-referenced.

Move the full "What you get" JSON field reference into a separate references/ file (e.g. CURRENT_JSON_FIELDS.md) and keep SKILL.md as a lean overview, since the body exceeds 50 lines and the field schema is the bulk of the length.

Dimension	Reasoning	Score
Conciseness	Assumes Claude's competence (no explaining of JSON or dev servers) and is substantive, but the re-read/staleness message is reinforced three times — in the description, the "Re-read on every deictic turn" section, and the "Staleness" section — so not every token earns its place; could be tightened.	2 / 3
Actionability	Provides the exact file path, the Read tool, a complete JSON example with per-field semantics, and copy-paste-ready numbered procedures for both page- and element-level references.	3 / 3
Workflow Clarity	Both worked examples are clearly sequenced with validation checkpoints — check `updatedAt` freshness, confirm the selection snippet/tagName, fall back to page-level flow if selection is null — plus an explicit staleness tier list (fresh/older/hours).	3 / 3
Progressive Disclosure	Well-organized into clearly headed sections, but the body is a ~110-line monolithic file with no bundle references, exceeding the 50-line simple-skill threshold where inline-only structure scores 3.	2 / 3
	Total	10 / 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 precise, action-oriented, and rich with the exact deictic phrases a user would say, while explicitly covering both what the skill does and when to invoke it. It sits in a distinctive niche with low conflict risk. No changes needed.

Dimension	Reasoning	Score
Specificity	Names concrete actions — "Resolve which slide, page, and (optionally) selected element" and "Re-read `node_modules/.open-slide/current.json`" — matching the anchor for multiple specific concrete actions; voice is third-person imperative with no first/second-person penalty.	3 / 3
Completeness	Explicitly answers what (resolve the current slide/page/element) and when ("Consult this whenever the user references...") with an explicit Use-when-style trigger clause.	3 / 3
Trigger Term Quality	Quotes the natural phrases users actually say — "this page", "this slide", "this element", "the slide I'm on", "the current page" — giving good coverage of deictic trigger variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — resolving the current location in the open-slide dev server via a specific file — with distinct deictic triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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: 1weiho/open-slide
Path: packages/core/skills/current-slide/SKILL.md
Commit: 35dc46c

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.