CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-surf-knowledge-graph

Search, read, traverse, and write connected HTML pages in your html.surf knowledge graph.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/html-surf-knowledge-graph/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 clean, token-efficient overview that is well-organized and needs no bundle files, but it reads more like a capability brochure than an operational guide: no tool names, no invocation examples, and no explicit step sequence with a concrete validation step before saving. Adding a short numbered workflow and one or two example MCP tool calls would make it fully actionable.

Suggestions

Add a short numbered workflow (connect via OAuth → search/locate pages → read and follow links → validate HTML → save only when the user authorizes writes) so the sequence and checkpoints are explicit rather than implied.

Name the key MCP tools (search, read, link/backlink traversal, validate, save) with one or two example invocations and expected responses, so usage guidance is executable rather than purely descriptive.

Specify what 'Validate generated HTML before saving it' concretely means (which tool or check to run, and what to do on failure), since that is the critical checkpoint before the destructive save operation.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes Claude's competence: the MCP endpoint, auth protocol details ("Streamable HTTP and OAuth with PKCE and Dynamic Client Registration"), a compact capability list, and four example prompts. Nothing explains concepts Claude already knows, and every section carries non-obvious information — matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete setup guidance exists (connect URL, auth flow, public-vs-private distinction) and the example prompts are specific, but there is no executable usage guidance: no MCP tool names, no example tool invocations or parameters, and no response formats — leaving key details missing, which matches the 'some concrete guidance but incomplete' anchor. It is not 4 because, beyond the connection step, the body describes capabilities ('Search accessible html.surf pages') rather than instructing how to perform them.

3 / 5

Workflow Clarity

A rough sequence is implied (connect/OAuth → search/read → validate → save with authorization) and validation is named ("Validate generated HTML before saving it"), but there is no explicitly ordered workflow and the validation checkpoint is unspecified (which tool, what checks). Since page writes are destructive and validation is only implied, workflow clarity is capped at 3 per the destructive-operations guideline. It is not 2 because the sections do convey the correct order of connection before use and authorization before writes.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, and the body is organized into clear, well-labeled sections (MCP Server, What Claude Can Do, Example Prompts, User Guidance). Per the simple-skill guideline this matches the top anchor: nothing is inlined that belongs in a separate file, and navigation is trivial.

5 / 5

Total

16

/

20

Passed

Description

70%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 concise, distinctive description with concrete verbs and a clear niche, but it lacks the 'when to use' trigger clause entirely, which is the single biggest gap. Adding a 'Use when...' clause naming natural user phrases would lift completeness and trigger quality simultaneously.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions html.surf, their html.surf pages or notes, or wants to search, browse, or edit linked HTML pages in a knowledge graph.'

Include a few more natural user phrasings as trigger terms (e.g. 'pages', 'notes', 'links', 'backlinks', 'browse') to broaden keyword coverage.

Optionally mention validation and page management (bookmarks, share links, permissions) to close the coverage gap between description and body capabilities.

DimensionReasoningScore

Specificity

The description lists four concrete actions — "Search, read, traverse, and write" — on a named domain ("connected HTML pages in your html.surf knowledge graph"), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because capabilities the body documents (backlinks, bookmarks, validation, permissions, themes) are absent, and 'traverse' is less concrete than the other verbs.

4 / 5

Completeness

The 'what' is clear (search, read, traverse, write HTML pages in html.surf), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Good keyword coverage with distinctive natural terms users would say: "Search", "read", "write", "HTML pages", "html.surf", "knowledge graph". It misses a few natural variations a user might say ("pages", "notes", "links", "backlinks", "browse"), so it sits at the 'good coverage; a few natural terms missing' anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and distinct: the product name "html.surf" and "knowledge graph" anchoring make it unlikely to trigger for the wrong skill. A user mentioning html.surf or their knowledge-graph pages would unambiguously match this; minimal conflict risk with generic HTML or web-development skills.

5 / 5

Total

16

/

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

stukennedy/html-surf-claude-skill

Path

skills/html-surf-knowledge-graph/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.