CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

88%

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

SKILL.md
Quality
Evals
Security

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.

A highly actionable, well-organized single-file skill: executable commands and complete code examples for every usage path, with valuable non-obvious operational details throughout. The main improvement opportunities are trimming repeated URL/flag duplication and splitting the larger API sections into reference files.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious specifics ("--screenshot-delay <ms>... defaults to 100", "PNG pixel size is width * dpr by height * dpr", "Treat waitForFrame() as 'a frame was submitted'") and explains nothing Claude already knows. It is not a 5 because the sample gallery URL is repeated five times across examples and the CLI-rules bullets partially restate flag behavior already shown in the commands, so a modest trim is possible.

4 / 5

Actionability

Every path is copy-paste ready: complete CLI invocations with all flags, and full TypeScript examples with imports, try/finally cleanup, and error callbacks covering remote URLs, local file URLs, CDP inspection, data updates, windowed input, and OpenCard managers. Specific examples cover the common cases; nothing is pseudocode.

5 / 5

Workflow Clarity

Each usage path is an unambiguous, correctly sequenced flow (construct view → load template → wait/screenshot → destroy in finally), with explicit decision guidance ("Prefer the CLI for one-off screenshots... Prefer the API when the task needs programmatic setup...") and error-recovery hooks (onCardError, try/finally). It is not a 5 because there are no verification checkpoints for the produced output (e.g., confirming the PNG was written or retrying on capture failure), leaving minor validation gaps; it is above 3 because sequences and cleanup/error checkpoints are consistently present.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the body has no dangling references, so all content is appropriately contained in a single well-sectioned file (CLI, TypeScript API, Windowed API, DebugRouter OpenCard, Operational Notes) that is easy to navigate. It is not a 5 because at roughly 250 lines the skill exceeds the under-50-line simple-skill case, and clearly separable material (the full OpenCard manager example or the CLI flag reference) could be split into one-level-deep reference files to keep SKILL.md a leaner overview.

4 / 5

Total

17

/

20

Passed

Description

88%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 description that explicitly states both capabilities and trigger conditions with domain-specific, concrete language. The only weaknesses are a few missing natural synonyms (render, headless, .lynx.bundle) and a slight overlap risk from the standalone CDP trigger phrase.

DimensionReasoningScore

Specificity

The description lists multiple concrete, specific actions: "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" — comprehensive coverage of the skill's capabilities with no vague filler. It is not a 4 because coverage spans every major capability in the body (CLI, screenshots, preview, OpenCard, CDP, programmatic API) rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both questions in one structure: "what" is the enumerated capability list (run bundles, screenshots, preview, OpenCard, CDP inspection, API integration) and "when" is the explicit trigger clause "Use this skill when a task needs to..." with concrete trigger phrases. It is not a 4 because the 'when' guidance is fully explicit and enumerated rather than merely present.

5 / 5

Trigger Term Quality

Good natural keyword coverage for the domain — "Lynx bundles", "node-lynx CLI", "screenshots", "macOS preview window", "DebugRouter OpenCard", "CDP", "JavaScript or TypeScript APIs" are terms a Lynx developer would actually say. It is not a 5 because common variations like "render", "preview a Lynx page", "headless", or the ".lynx.bundle" extension are missing.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (node-lynx / Lynx runtime tooling) with distinct triggers such as "Lynx bundles", "node-lynx CLI", and "DebugRouter OpenCard". It is not a 5 because "inspect rendered content through CDP" is joined by "or" and stands as an independent trigger, so a generic Chrome-DevTools-Protocol inspection request could plausibly surface this skill; the overlap is minor.

4 / 5

Total

18

/

20

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.

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

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.