web-form-fill

网络表单填报技能 — 从信息搜集到浏览器填报的完整工作流，确保框架受控组件正确写入、页面切换前暂存、最终提交由用户确认。

Quality

68%

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/web-form-fill/SKILL.md

Quality

Content

77%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 highly actionable with executable commands, clear sequencing, and strong validation/feedback loops for a risky multi-page form-filling task. Its main weaknesses are moderate verbosity from duplicated instructions and a monolithic single-file structure with no progressive disclosure to reference bundles.

Suggestions

Move the 常见问题与对策 and 速查操作模板 sections into a separate reference file (e.g., references/templates.md) and link to it, reducing duplication and the main-file token load.

De-duplicate the focus/clear/type/verify cycle between §3-B, the 速查 templates, and 常见问题 so each control flow appears once.

Trim explanatory prose that restates the same guarantee multiple times (e.g., the repeated 'type 走真实输入管线' rationale) to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and task-focused, but it is long (~310 lines) and repeats the type/focus/clear/snapshot cycle across the main section, 速查 templates, and 常见问题, which could be tightened.	3 / 5
Actionability	It provides fully executable camoufox-cli commands (open/type/click/upload/snapshot/close) with concrete refs, per-control fill methods in leveled tables, and copy-paste-ready template blocks covering text/select/radio/datepicker/upload.	5 / 5
Workflow Clarity	The four-step workflow is clearly sequenced with explicit validation checkpoints (3-C 填写验证, 3-D 页面切换暂存, Step 4 提交前确认) plus feedback loops (verify→clear→retry→record-as-unfillable), satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Structure is well sectioned, but there are no bundle files and everything lives inline in SKILL.md; the 常见问题/速查 templates and per-control tables could plausibly be split into reference files, so it is organized but monolithic rather than progressively disclosed.	3 / 5
	Total	16 / 20 Passed

Description

58%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 concretely names the form-filling domain and several specific technical guarantees, but it lacks an explicit 'Use when...' trigger clause and could include more natural synonyms (报名/登记/申请) to improve trigger coverage.

Suggestions

Add an explicit 'Use when...' clause listing trigger scenarios (e.g., 申报系统、比赛报名、补贴申请、信息登记) so Claude knows when to invoke the skill.

Include natural synonyms users say (报名、登记、申请、填报) alongside '网络表单' to broaden trigger-term coverage.

Consider third-person action verbs at the start (e.g., '采集信息并逐页填报在线表单') to match the rubric's preferred voice.

Dimension	Reasoning	Score
Specificity	Names the domain (网络表单填报) and lists several concrete actions: 信息搜集, 浏览器填报, 框架受控组件正确写入, 页面切换前暂存, 最终提交由用户确认 — but the phrasing is more about guarantees than a comprehensive action list.	4 / 5
Completeness	It clearly states what the skill does (a full workflow from information gathering to browser filling), but there is no explicit 'Use when...' / 'when to use' clause — the trigger guidance is only implied, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It contains the natural phrase 网络表单填报 (web form filling) users would say, plus terms like 申报/填报, but lacks common synonyms/variations (e.g., 报名, 登记, 申请) that broaden trigger coverage.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct — controlled-component form filling with a draft-before-switch-page and human-confirmed-submit protocol — with only minor overlap risk against a general browser-guide skill.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: TeamWiseFlow/xiaobei
Path: skills/web-form-fill/SKILL.md
Commit: fdc03d6

Reviewed: 11 days 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.