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

90%

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

92%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.

A well-structured, highly actionable body with concrete file paths, a real JSON schema, worked examples, and robust validation/staleness guidance. Only minor conciseness redundancy between the frontmatter and the re-read section prevents a perfect content score.

Suggestions

Trim the redundancy between the frontmatter's re-read instruction and the 'Re-read on every deictic turn' section — keep the detailed bulleted cases in the body but avoid restating the headline rule verbatim.

Add the explicit 'Check updatedAt is recent' step to the element-level example to match the page-level example and make the validation checkpoint consistent across both workflows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with every section earning its place (custom JSON format docs, field semantics), but the 'Re-read on every deictic turn' section restates the frontmatter's re-read instruction, a minor redundancy that could be trimmed.	4 / 5
Actionability	Fully executable: gives the exact path 'node_modules/.open-slide/current.json', the Read tool, a real JSON example, and concrete numbered examples ('Read pagePath, jump to selection.line, and find the JSX opening tag near that line/column').	5 / 5
Workflow Clarity	Clear numbered sequences with explicit validation — a dedicated 'Staleness — verify before acting' section, missing-file handling, and a null-selection fallback ('If selection is null, fall back to the page-level flow') provide feedback loops for the destructive act of editing slides in place.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no bundle files needed; peer-skill references ('Consult the slide-authoring skill') are one level deep and clearly signaled, and all inline content is appropriately cohesive for a single-file skill.	5 / 5
	Total	19 / 20 Passed

Description

87%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.

A strong, specific description that explicitly states both what it does and when to use it, with natural trigger phrases and a well-scoped niche. Minor gaps in trigger-term synonyms and the single-purpose scope keep specificity and trigger quality just below full marks.

Dimension	Reasoning	Score
Specificity	Names the domain ('open-slide dev server') and several concrete actions — 'Resolve which slide, page, and (optionally) selected element' plus 'Re-read node_modules/.open-slide/current.json' — going beyond 1-2 actions, though it is a single-purpose skill so coverage is narrow rather than comprehensive.	4 / 5
Completeness	Clearly answers 'what' ('Resolve which slide, page, and (optionally) selected element the user is currently viewing') and 'when' ('Consult this whenever the user references...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Enumerates natural deictic phrases users say ('this page', 'this slide', 'this element', 'the slide I'm on', 'the current page') plus the general 'deictic reference to slide content', but a few common variants like 'here' or 'what I'm working on' are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (the open-slide dev server's current.json cursor) with distinctive triggers, so conflict with other skills is minimal.	5 / 5
	Total	18 / 20 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: dad4c24

Reviewed: 6 days 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.