openviking

OpenViking 集成 — 浏览器自动化与 Web 搜索工具

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openviking/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and highly actionable, with concrete install config and copy-paste usage commands plus a single real script reference. Its main weaknesses are padding in the conceptual/themed sections and missing validation checkpoints in the install and batch-indexing workflows.

Suggestions

Add validation checkpoints: after install, run `viking.sh info` to confirm setup; after batch `add-dir`, run `list`/`info` to verify files were indexed before proceeding.

Trim the themed '朝廷集成建议' section and the '什么是 OpenViking' comparison table to the essential decision guidance to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	Installation and usage sections are efficient, but the conceptual '什么是 OpenViking' intro plus the themed '朝廷集成建议' section (兵部/户部/礼部…) add padding that could be tightened, fitting 'mostly efficient but includes some unnecessary explanation'.	2 / 3
Actionability	The install steps give fully executable commands (pip install, a complete JSON config, env-var exports) and the usage section lists copy-paste-ready `viking.sh` subcommands, matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	Installation is a numbered 4-step sequence, but there are no validation checkpoints (no verify-install or test-API-key step) and the batch `add-dir` indexing has no verification, so per the guidelines workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	Content is split into clear, well-labeled sections with a single one-level-deep reference to the real `scripts/viking.sh` bundle file; the skill is compact and self-contained, matching the simple-skills note that well-organized sections can score 3.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 names a domain and a couple of tool categories but uses the abstract verb '集成', omits any 'Use when...' trigger guidance, and mischaracterizes the skill as browser automation/web search when the body is about a memory and knowledge-base backend. It is borderline-adequate but inaccurate and untriggered.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user needs long-term memory, a knowledge base over large document sets, semantic search, or file indexing.'

Correct the framing: the skill is a context database / memory backend (indexing, embeddings, semantic search, summaries), not browser automation or web search — the current description risks triggering for the wrong skill.

Replace the abstract '集成' with concrete actions, e.g. 'Index files and directories, run semantic search, and generate multi-level summaries via OpenViking.'

Dimension	Reasoning	Score
Specificity	"OpenViking 集成 — 浏览器自动化与 Web 搜索工具" names the domain and tool categories, but the only action verb is the abstract "集成" (integration) with no concrete operations, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill is (OpenViking integration) but has no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2 ('has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	"浏览器自动化" and "Web 搜索" are somewhat natural keywords, but coverage is thin with no common variations, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The 'OpenViking' name is somewhat distinctive, but the '浏览器自动化与 Web 搜索工具' framing is generic and — worse — contradicts the body (which describes a context database / knowledge base), so it could trigger for the wrong skill.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wanikua/danghuangshang
Path: skills/openviking/SKILL.md
Commit: acea185

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.