CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-core-efficient

Use when working in the embedded browser and you want the cheapest reliable interaction loop.

53

Quality

59%

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 ./runtime/harnesses/src/embedded-skills/browser-core-efficient/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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-only skill with concrete tool and parameter guidance plus a clear default loop and escalation path. Its main gap is the absence of example call syntax that would lift actionability to fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept over-explanation; minor redundancy between the Goals summary and the operational sections keeps it just below 'every token earns its place'.

4 / 5

Actionability

Guidance names specific tools and parameters (browser_act, browser_find, detail=compact, include_page_text=true, download_started) with clear when-to-use rules; not 5 because no concrete example call sequences are shown.

4 / 5

Workflow Clarity

The numbered Default Loop gives a clear sequence with conditional checkpoints ('Re-read state only if the action result is ambiguous', stale-ref re-location); not 5 because there is no full validate-then-fix feedback loop.

4 / 5

Progressive Disclosure

Under 50 lines, no external references needed, and content is organized into well-signaled sections (Goals, Default Loop, Tool Selection, State Discipline, Wait Discipline, Escalation Rules), matching the simple-skill exception for a 5.

5 / 5

Total

17

/

20

Passed

Description

40%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 provides a clear trigger context but is weak on stating concrete capabilities, leaning on a vague intent phrase instead of naming what the skill does. It is reasonably distinct but would benefit from explicit action verbs.

Suggestions

Add concrete capability verbs, e.g. 'choose the cheapest reliable browser tool calls, avoid redundant state reads and screenshots, and prefer locator-based actions'.

Replace 'cheapest reliable interaction loop' with natural user-facing phrasing or pair it with plain synonyms like 'efficient browser automation' or 'fewest tool calls'.

Make the 'what' explicit before the 'Use when' clause so both purpose and trigger are unambiguous.

DimensionReasoningScore

Specificity

Names the domain ('embedded browser') but the only action framing is the abstract 'cheapest reliable interaction loop' with no concrete capabilities listed, matching the 'names the domain but actions are minimal or generic' anchor; not 3 because no specific actions are enumerated.

2 / 5

Completeness

A clear 'when' is present ('Use when working in the embedded browser...') but the 'what' is only a vague intent rather than a stated capability, matching the 'only when is present without what' anchor; not 3 because there is no clear 'what'.

2 / 5

Trigger Term Quality

'working in the embedded browser' is a reasonably natural trigger phrase, but 'cheapest reliable interaction loop' is jargon and common synonyms/variations are missing, fitting 'some relevant keywords but missing common variations'; not 4 because coverage is thin.

3 / 5

Distinctiveness Conflict Risk

The embedded-browser plus efficiency framing carves a mostly distinct niche with only minor overlap risk against a general sibling browser skill, fitting 'mostly distinct; minor overlap risk'; not 5 because it is not maximally differentiated.

4 / 5

Total

11

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
holaboss-ai/holaOS
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.