node-lynx

Use this skill when a task needs to run Lynx bundles with the node-lynx CLI, capture screenshots, open a macOS preview window, use DebugRouter OpenCard, inspect rendered content through CDP, or integrate node-lynx through JavaScript or TypeScript APIs.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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 content is well-structured, executable, and concise, with complete code examples and clear decision guidance between the CLI and API paths. It would benefit only marginally from tighter prose and, since no bundle files exist, cannot offload detail to references.

Dimension	Reasoning	Score
Conciseness	The body is efficient and avoids explaining concepts Claude already knows, presenting mostly runnable examples and terse rules; a few sentences (e.g. justifying preview-on-macOS twice) could still be trimmed, so it is just below fully lean.	4 / 5
Actionability	Provides copy-paste-ready CLI commands and complete TypeScript examples with imports, try/finally cleanup, and realistic arguments covering the common cases (remote URL, local bundle, CDP inspection, OpenCard).	5 / 5
Workflow Clarity	Clear sequencing and guidance (prefer CLI vs API, when to use --no-debug-router, always destroy() in finally), and the screenshot/settle guidance acts as a pragmatic checkpoint; it lacks an explicit validate-then-retry loop, but no destructive batch operation is involved so it stays above 3.	4 / 5
Progressive Disclosure	Well-organized into clear sections (CLI, TypeScript API, Windowed API, DebugRouter OpenCard, Operational Notes) with the right amount inline for a self-contained skill; no bundle files exist to offload detail, so it appropriately stays single-file with minor room for tighter sectioning.	4 / 5
	Total	17 / 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.

The description is strong: it opens with an explicit 'Use when' trigger, enumerates concrete capabilities, and occupies a distinct niche. It is comprehensive enough to score at the top of the scale with only minor wording polish needed.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (run Lynx bundles, capture screenshots, open a macOS preview window, use DebugRouter OpenCard, inspect rendered content through CDP, integrate via JS/TS APIs); the only gap is that a couple of actions are phrased slightly generically ("integrate"), keeping it just below comprehensive.	4 / 5
Completeness	Opens with an explicit "Use this skill when..." trigger clause and enumerates the concrete capabilities (what), clearly answering both what the skill does and when Claude should use it.	5 / 5
Trigger Term Quality	Strong natural trigger terms ("run Lynx bundles", "capture screenshots", "preview window", "DebugRouter OpenCard", "CDP") that users would naturally say; a few common phrasings or synonyms (e.g. "automate", "render", "smoke test") are referenced only indirectly.	4 / 5
Distinctiveness Conflict Risk	The node-lynx / Lynx / DebugRouter OpenCard niche is highly specific with distinct triggers, so it is unlikely to fire for the wrong skill.	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: lynx-family/lynx
Path: oliver/node-lynx/skills/node-lynx/SKILL.md
Commit: c17426b

Reviewed: 5 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.