CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

opencli

Operate websites and Electron apps through CLI commands, reusing Chrome login sessions. Prefer over browser_task for supported sites (GitHub, Bilibili, Twitter/X, YouTube, etc.) — deterministic commands with structured JSON output.

Quality

77%

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 ./skills/system/opencli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured, concise, actionable skill body with a clear tool-selection decision path and executable examples. All dimensions land at 4 rather than 5 due to small gaps: no error-recovery guidance, undescribed JSON output shape, and no external reference file for the adapter list.

DimensionReasoningScore

Conciseness

The body is lean — comparison tables, short code blocks, a decision tree — and assumes Claude's competence without explaining known concepts, matching the 'efficient; minor instances of over-explanation' anchor. It isn't 5 because the '核心优势' (core advantages) section partially repeats the description's claims in a promotional tone ('比 browser_task 的 "让 LLM 猜" 可靠得多') and could be trimmed.

4 / 5

Actionability

It provides concrete, copy-paste-ready calls (`opencli_run(command="zhihu hot list")`, `npm install -g @jackwener/opencli`, `opencli_doctor()`) plus the command format, matching 'mostly executable guidance with minor gaps'. It isn't 5 because the `args` parameter is shown once without explanation, output JSON structure is never described, and `opencli_doctor` is listed with no guidance on interpreting its result.

4 / 5

Workflow Clarity

The 决策路径 decision tree, prerequisites checklist, and tool-discovery flow (opencli_list → opencli_run → opencli_doctor) give a clear sequence with most checkpoints present, matching the anchor for 'clear sequence with most checkpoints'. It isn't 5 because there is no error-recovery guidance (what to do when a command fails or doctor reports a missing Browser Bridge), though the operations shown are read-heavy rather than destructive so the destructive-cap rule doesn't apply.

4 / 5

Progressive Disclosure

The skill is self-contained with well-organized sections and no nested references (no bundle files exist), matching 'good structure; most content is appropriately placed'. It isn't 5 because at ~65 lines it exceeds the under-50-line simple-skill threshold, and the growing supported-site/adapter list plus error-handling detail would be better placed in a one-level-deep reference file.

4 / 5

Total

16

/

20

Passed

Description

71%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.

A specific, well-differentiated description that clearly states what the skill does and how it differs from browser_task. Its main weaknesses are the missing natural-language trigger phrasing (no explicit 'Use when...' clause with user-recognizable scenarios) and limited keyword variations beyond the site list.

Suggestions

Add an explicit 'Use when...' clause with concrete user-facing triggers, e.g. 'Use when operating on GitHub, Bilibili, Twitter/X, or YouTube accounts, or when a task needs the user's existing Chrome login session.'

Include natural keyword variations users would actually say — e.g. 'browser automation', 'scrape/upvote/comment on posts', 'logged-in session' — to improve trigger recall.

Briefly state the kinds of operations supported (read lists, fetch video/post info, account actions) so the 'what' is comprehensive rather than implied.

DimensionReasoningScore

Specificity

The description names several concrete capabilities — 'Operate websites and Electron apps through CLI commands', 'reusing Chrome login sessions', 'deterministic commands with structured JSON output' — which matches the anchor for several specific actions with minor gaps. It falls short of 5 because it doesn't enumerate what kinds of operations are supported per site, and isn't below 3 since it goes well beyond naming the domain.

4 / 5

Completeness

The 'what' is clearly answered (operate websites/Electron apps via CLI, reuse Chrome sessions, structured JSON output) and a when-signal exists via 'Prefer over browser_task for supported sites', which functions as equivalent explicit trigger guidance so the 3-cap doesn't apply. It isn't 5 because the when-clause is framed as tool preference rather than explicit 'Use when...' triggers tied to user requests.

4 / 5

Trigger Term Quality

Site names like 'GitHub, Bilibili, Twitter/X, YouTube' and 'Chrome login' are relevant natural keywords, but common variations users would say ('browser automation', 'scrape posts', 'logged-in session', 'post comments') are absent. This matches the 'some relevant keywords but missing common variations or synonyms' anchor — not 4 because coverage of natural phrasing beyond the site list is thin.

3 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — CLI adapters for a named set of sites reusing Chrome login state — and explicitly disambiguates against the closest competing skill ('Prefer over browser_task'), matching the 'clear niche with distinct triggers; minimal conflict risk' anchor. It is not below 5 because no other skill would plausibly claim this trigger.

5 / 5

Total

16

/

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/opencli/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.