CtrlK
BlogDocsLog inGet started
Tessl Logo

browser

Open, inspect, navigate, and interact with public web pages using Kun's bounded structured browser.

64

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 ./resources/bundled-skills/browser/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a tight, well-structured instruction skill with a clear workflow and observe-after-act validation loop. Its only gaps are implicit error recovery and the absence of concrete copy-paste examples.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes Claude's competence — a compact routing table, numbered workflow, and bullet gates with no padding or explanation of concepts Claude already knows, matching 'every token earns its place'.

5 / 5

Actionability

Concrete instructional guidance names the tool, the expectedTarget identity, and ref-from-latest-snapshot usage; as an instruction-only skill code absence isn't penalized, but it lacks copy-paste-ready examples covering common cases, fitting 'mostly executable; minor gaps'.

4 / 5

Workflow Clarity

A clear five-step sequence pairs each interaction with a fresh snapshot and an explicit observe-state checkpoint ('Do not claim an action succeeded without observing the resulting page state'), but error-recovery feedback is only implicit, so it sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) with no need for external references; under 50 lines, so the simple-skill exception lets well-organized sections score 5.

5 / 5

Total

18

/

20

Passed

Description

66%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 specific and distinct, naming four concrete browser actions on public web pages with a clear niche. Its main weakness is the missing 'Use when...' trigger guidance, which caps completeness at 3.

Suggestions

Append a 'Use when...' clause with natural trigger phrases, e.g. 'Use when the user asks to open, browse, inspect, or interact with public web pages or fill public forms.'

Add common synonyms/extensions such as 'browse', 'click', 'type', and 'fill forms' to broaden trigger-term coverage toward anchor 5.

Mirror the body's richer action list (click, type, select, press, scroll, manage tabs) in the description to raise specificity to comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Open, inspect, navigate, and interact') on a clear object (public web pages), matching the 'several specific actions; minor gaps' anchor rather than 5's comprehensive coverage or 3's 1-2 actions.

4 / 5

Completeness

The 'what' is clear but there is no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3 (clear 'what', missing 'when').

3 / 5

Trigger Term Quality

Natural user phrases ('open', 'navigate', 'interact with web pages') are present, but common synonyms like 'browse', 'scrape', 'click', or 'fill forms' are missing, fitting 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

The 'Kun's bounded structured browser' framing restricted to public pages gives a clear niche with minimal conflict risk, but the absent explicit triggers keep it just below the fully distinct anchor 5.

4 / 5

Total

15

/

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
KunAgent/Kun
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.