CtrlK
BlogDocsLog inGet started
Tessl Logo

web-form-fill

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

58

Quality

68%

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 ./skills/web-form-fill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with excellent workflow sequencing and validation checkpoints, scoring top marks on actionability and workflow clarity. It is held back only by some verbosity from duplicated templates and a monolithic structure with no progressive disclosure split.

Suggestions

Remove or compress the '速查:填写操作模板' section since it repeats §3 content, or replace it with a one-line pointer to the relevant subsections.

Tighten the '为什么 type 就够了' table to drop framework event-chain explanations Claude already knows, keeping only the case-specific outcomes.

Consider splitting the troubleshooting ('常见问题与对策') and operation templates into a referenced file to reduce the monolithic inline block.

DimensionReasoningScore

Conciseness

Mostly efficient and actionable, but the '速查:填写操作模板' section duplicates guidance already in §3, and the '为什么 type 就够了' table re-explains framework event mechanics Claude already knows.

2 / 3

Actionability

Provides fully executable camoufox-cli commands, ref-based flows, and per-control-type templates (select/radio/date/upload) with verification tables that are copy-paste ready.

3 / 3

Workflow Clarity

Clear 4-step sequence with explicit validation checkpoints (3-C 填写验证, 3-D 暂存-before-switch), feedback loops (verify → clear → retry → record), and an explicit safety gate in Step 4 forbidding auto-submit.

3 / 3

Progressive Disclosure

Single monolithic ~310-line file with all content inline and no bundle files; sections are well-organized, but quick-reference and troubleshooting content that could be split out is kept inline.

2 / 3

Total

10

/

12

Passed

Description

60%

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 conveys a clear, multi-phase capability with concrete actions, but lacks an explicit 'Use when...' trigger and natural scenario keywords, capping completeness and trigger quality at 2. It is specific in what it does yet only moderately distinct from a generic browser skill.

Suggestions

Add an explicit 'Use when...' clause naming natural user scenarios (e.g. 申报系统、比赛报名、补贴申请、信息登记表单).

Replace technical phrasing like '框架受控组件正确写入' with user-facing trigger terms ('填报在线表单/报名/申报').

Surface the scenario keywords currently only in the body into the description to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain (网络表单填报) and multiple concrete actions: '从信息搜集到浏览器填报的完整工作流', '框架受控组件正确写入', '页面切换前暂存', '最终提交由用户确认'.

3 / 3

Completeness

Clearly answers 'what' (完整工作流 from info gathering to browser filling) but has no explicit 'Use when...' trigger; per guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes the domain term '网络表单填报' but leans on technical jargon ('框架受控组件', '页面切换前暂存') and omits natural scenario keywords a user would say (报名/申报/补贴申请) that appear only in the body.

2 / 3

Distinctiveness Conflict Risk

The form-filling niche is somewhat specific, but without distinct explicit triggers it could still overlap with the general browser-guide skill for ordinary browser tasks.

2 / 3

Total

9

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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