CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

browser-type

Type text into input fields on webpage. When you need to fill forms, enter search queries, or input data. PREREQUISITE - must use browser_navigate first. May need to click field first for focus.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/system/browser-type/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tool reference: complete parameter documentation, two concrete examples, explicit prerequisites, and genuinely non-obvious notes (append behavior, Chinese input support). Only minor trims and one under-specified note keep it from full marks.

DimensionReasoningScore

Conciseness

The body is lean — a parameter table, two one-line JSON examples, and short prerequisite/notes sections — with no explanation of concepts Claude already knows. The trailing '推荐' section promoting browser_task is minor padding that could be trimmed, which keeps it at 'efficient; minor instances that could be trimmed' rather than the 5 anchor's 'every token earns its place'.

4 / 5

Actionability

Concrete, copy-paste-ready JSON examples ("{\"selector\": \"input[name='q']\", \"text\": \"OpenAkita\"}") plus a parameter table make the guidance mostly executable. Small gaps remain: the note "如需清空请先选中" (select first to clear) gives no concrete mechanism, and no full tool-call invocation syntax is shown, so it does not fully reach the 5 anchor's 'specific examples cover the common cases'.

4 / 5

Workflow Clarity

This is a simple single-action skill and the action is unambiguous; the Prerequisites section ("必须先用 browser_navigate 打开目标页面", "如果输入框没有焦点,可能需要先点击") plus Related Skills make the implicit navigate → focus → type sequence explicit. Per the simple-skill guideline, a clear single-purpose action with no destructive or batch operation warrants 5.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no external bundle files (no references/, scripts/, or assets/ exist), and all content fits inline in well-organized sections (Parameters, Examples, Prerequisites, Notes, Related Skills) with no buried references. Per the rubric guideline, a short skill with no need for external references scores 5 with well-organized sections.

5 / 5

Total

18

/

20

Passed

Description

62%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 compact and functional: it states a concrete capability, an explicit use-when clause, and practical prerequisites. Its main weakness is thin trigger-term coverage — it lacks common synonyms a user might naturally say — and it names only one core action.

Suggestions

Expand the 'when' clause with concrete trigger phrases users would naturally say, e.g. 'Use when the user asks to type into, fill in, or enter text in a search box, login field, or form on a web page.'

Add natural synonyms and variants such as 'text box', 'search bar', 'form field', 'login/username field' to improve trigger-term coverage.

Consider briefly describing additional capabilities it supports (e.g. clearing or replacing field content, handling focus) to lift specificity and completeness — but keep the same length, not padding.

DimensionReasoningScore

Specificity

"Type text into input fields on webpage" names the domain and one concrete action; the other phrases ("fill forms, enter search queries, or input data") are use contexts rather than additional capabilities. It matches 'names domain and 1-2 concrete actions' and does not reach the 4 anchor's 'several specific actions', while being clearly above the generic 2 anchor.

3 / 5

Completeness

It answers both questions: what ("Type text into input fields on webpage") and when ("When you need to fill forms, enter search queries, or input data"), plus useful prerequisites ("must use browser_navigate first", "May need to click field first"). The 'when' clause is explicit but short and could be more specific with concrete trigger phrases, so it sits at the 4 anchor rather than 5, and clearly above the 3 anchor where 'when' is missing or only implied.

4 / 5

Trigger Term Quality

"fill forms", "enter search queries", and "input data" are natural phrases, but common variations users would say — "type into", "text box", "search bar", "form field", "login" — are missing. Some relevant keywords with gaps in synonyms, matching the 3 anchor rather than the 4 anchor's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

"Type text into input fields on webpage" carves a clear niche (browser form typing) with distinct triggers, and the browser_navigate prerequisite anchors it to the browser tool family. Minor overlap risk exists with closely related skills like clicking or form submission, matching the 4 anchor rather than the 5 anchor's 'minimal conflict risk'.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

openakita/openakita

Path

skills/system/browser-type/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.