CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-core-efficient

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

66

Quality

78%

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

100%

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 that gives concrete tool-and-parameter guidance with a clear default loop and escalation branches, with no wasted tokens.

DimensionReasoningScore

Conciseness

The ~46-line body is lean with no concept-explanation fluff (no 'what a browser is' padding) and every bullet earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor; it is not level 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

It names concrete tools with concrete parameters and flags (browser_act, browser_find detail=compact, include_page_text=true, download_started, browser_evaluate) plus explicit escalation branches; per the code-vs-instruction note, absence of code is not penalized when guidance is this actionable, matching the fully executable/specific guidance anchor.

3 / 3

Workflow Clarity

The numbered 'Default Loop' sequences steps 1-5 with an explicit re-read/orientation feedback checkpoint (step 5) and the 'Escalation Rules' section provides clear decision branches; this is not a destructive/batch operation so the validation cap does not apply, matching the clear-sequence-with-feedback anchor.

3 / 3

Progressive Disclosure

The body is under 50 lines, needs no external references, and is organized into well-signaled sections (Goals, Default Loop, Tool Selection, State Discipline, Wait Discipline, Escalation Rules), matching the simple-skills note that well-organized sections alone can score 3; no bundle files exist to verify further.

3 / 3

Total

12

/

12

Passed

Description

57%

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 has an explicit trigger and a clear, low-conflict niche, but its 'what' is abstract and its trigger terms skew technical, so it conveys intent without naming concrete capabilities.

Suggestions

Add concrete capabilities to the description (e.g., 'click, type, locate, and read page state with the fewest tool calls') to lift specificity and completeness toward level 3.

Include natural-language trigger terms users would actually say (e.g., 'browser', 'click a button', 'fill a form', 'read a page') alongside 'embedded browser' to improve trigger term coverage.

Reframe the 'what' as a capability statement rather than a quality goal so the description answers 'what does this do' concretely, not just 'how well it does it'.

DimensionReasoningScore

Specificity

It names the domain ('embedded browser') and an abstract behavior class ('cheapest reliable interaction loop') but lists no concrete actions, matching the anchor that names a domain and some actions without being comprehensive; it is above level 1 because it does more than 'Helps with documents' but lacks the multiple specific concrete actions required for level 3.

2 / 3

Completeness

An explicit 'Use when...' clause is present ('Use when working in the embedded browser and you want the cheapest reliable interaction loop'), but the 'what' side is vague/abstract ('cheapest reliable interaction loop') rather than a concrete capability statement; because the explicit trigger keeps it off level 1 but the weak 'what' prevents level 3, it sits at level 2.

2 / 3

Trigger Term Quality

The phrase 'when working in the embedded browser' is a genuine trigger, but the keywords ('embedded browser', 'interaction loop') lean technical and omit common natural variations users would say (e.g., 'browser', 'click', 'page'); this matches the anchor with some relevant keywords missing common variations rather than the full coverage of level 3.

2 / 3

Distinctiveness Conflict Risk

'embedded browser' paired with the efficiency framing ('cheapest reliable interaction loop') carves a clear niche unlikely to trigger the wrong skill; this matches the clear-niche-with-distinct-triggers anchor rather than the overlapping level 2.

3 / 3

Total

9

/

12

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.