CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-browser-module

OneKey Browser/Discovery development for WebView tabs, bookmarks, history, search, URL risk checks, DApp connections, and JSBridge behavior.

63

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-browser-module/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 content is a tight, well-structured navigation skill that routes Claude to one-level-deep reference files with concrete identifiers and a sequenced workflow including a verification checkpoint. The only notable gap is the lack of an explicit fix-retry feedback loop around the destructive/risky operations it guards against.

Suggestions

Add an explicit feedback loop after step 6, e.g. 'If verification fails, re-read the relevant rule file, fix, and re-verify before proceeding.'

Consider one short inline copy-paste example for the single most common task (e.g., a validateUrl/buildWebTabs snippet) to lift actionability from concrete-guidance to fully-executable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanation of what WebView/DApp/SimpleDB is — and every section (Quick Reference table, workflow, hard rules) earns its tokens without padding.

5 / 5

Actionability

Concrete, actionable guidance via specific identifiers (uriUtils.validateUrl, parseDappRedirect, buildWebTabs, useBrowserTabActions) and real file paths; as an instruction-only navigation skill it has no copy-paste code, which is acceptable but leaves minor gaps versus fully executable examples.

4 / 5

Workflow Clarity

Six clearly sequenced Default Workflow steps with a final verification checkpoint (step 6) and platform-suffix guardrails (step 4); lacks an explicit validate-then-fix-retry feedback loop for the risky operations named in Hard Rules.

4 / 5

Progressive Disclosure

A clean overview SKILL.md with a well-signaled Quick Reference table pointing to six real, one-level-deep reference files in references/rules/, with content appropriately split between overview and detail files.

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 well-keyworded for the OneKey Browser domain, naming concrete capability areas and natural trigger terms. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when working on OneKey Browser/Discovery WebView tabs, bookmarks, history, search, URL risk checks, or DApp connections.'

Reframe the capability list as concrete actions (e.g., 'Implements and debugs WebView tabs, bookmarks, history...') to strengthen the specificity framing.

Include a few natural synonyms or file/feature variants a user might say (e.g., 'MultiTabBrowser', 'in-app browser') to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('WebView tabs, bookmarks, history, search, URL risk checks, DApp connections, and JSBridge behavior'), but they are framed as noun-list features under 'development for' rather than explicit verbs, leaving minor coverage framing gaps.

4 / 5

Completeness

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

3 / 5

Trigger Term Quality

Good keyword coverage including natural terms ('bookmarks', 'history', 'search', 'tabs') alongside domain terms ('WebView', 'DApp connections', 'JSBridge'); a few natural synonyms or variants a user might say are missing.

4 / 5

Distinctiveness Conflict Risk

Tied to a specific niche ('OneKey Browser/Discovery') with distinct feature triggers, giving minimal conflict risk, though some overlap remains with generic browser/web-dev and the listed related skills.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 7 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 7 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.