CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sn-proactive-agent

安装、启动和使用 Proactive Agent,记录项目进展并在合适时机提醒下一步。

Quality

70%

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/sn-proactive-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 body is a well-structured operational overview: lean, policy-dense guidance with concrete commands, flags, and data paths, a clearly sequenced task-based routing table, and a verified one-level-deep reference bundle that matches the links in the text. The only notable deductions are the inline version pin and minor duplication of acceptance-caveat sentences, plus the delegation of full command lines to the referenced install docs (appropriate for this design).

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows — every section carries routing rules, command flags, or data-path facts. It is not a 5 because of the inline version pin "目标运行包版本为 `0.1.4`" (time-sensitive information not placed in a deprecated/old-patterns section, which the guidelines penalize) and a few near-duplicate policy sentences such as "安装包验收不等于真实接入验收。Windows 说明是安装参考,不代表完整接入已验收。"

4 / 5

Actionability

For an instruction-only skill the guidance is concrete: exact reference paths in a condition table, real command flags ("serve --web-only", "doctor --session-id"), env vars ("SN_PROACTIVE_AGENT_DATA_ROOT"), and precise data layouts ("projects/<project-id>/items/<item-id>/events.md", "runtime.jsonl"). It is not a 5 because full copy-paste command lines are delegated to the reference files, leaving minor gaps at this level; it is well above anchor 3 since nothing is pseudocode or vague.

4 / 5

Workflow Clarity

The reading flow is explicitly sequenced ("先读通用流程,再按实际运行环境读取一份系统说明", read-only checks for status questions, one connector doc per harness), and validation semantics are stated concretely: "doctor --session-id 读取指定窗口的实际证据", "unverified 不等于通过", "安装包验收不等于真实接入验收". It is not a 5 because the step-by-step install/validation loop lives in overview.md rather than being fully spelled out here, leaving minor checkpoint gaps at the SKILL.md level; no destructive or batch operations are performed inline, so no cap applies.

4 / 5

Progressive Disclosure

SKILL.md is a ~65-line overview whose condition table ("安装、运行与维护服务 | install/overview.md", "macOS | install/macos.md", etc.) signals exactly when to read each of the five bundle files, and all five referenced paths were verified to exist. References are one level deep — cross-links inside the reference files (e.g., overview.md → macos.md, hermes.md → ../install/overview.md) are sibling navigation, not nested 'see X for the real content' chains — matching anchor 5 (clear overview, well-signaled one-level-deep references, easy navigation).

5 / 5

Total

17

/

20

Passed

Description

50%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 communicates a recognizable what (install/start a proactive agent that records project progress and reminds next steps) but is missing any when-to-use trigger guidance, which caps completeness at 3 and weakens trigger-term quality. Its action phrasing also overlaps with generic progress-tracking and reminder skills, giving it moderate conflict risk. All four dimensions land at the midpoint of the scale.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Proactive Agent, wants project progress tracked across conversations, or asks for next-step reminders' — this would lift completeness and trigger_term_quality simultaneously.

Replace the filler verb '使用' with the concrete capabilities the body already documents (e.g., conversation ingestion via connectors, Web workbench suggestions, resuming accepted suggestions in the original session) to raise specificity.

Include common variations and synonyms of the trigger terms (进展记录, 项目跟踪, 下一步建议, proactive agent) so natural user phrasings match this skill instead of competing reminder/notes skills.

DimensionReasoningScore

Specificity

The description names the domain ("Proactive Agent") and two concrete capabilities ("记录项目进展", "在合适时机提醒下一步"), but "安装、启动和使用" are generic lifecycle verbs where "使用" adds no information, and coverage is incomplete (no mention of conversation ingestion, the Web workbench, or connector-based resumption). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, whose example lists several equally specific actions without a catch-all filler verb.

3 / 5

Completeness

The 'what' is reasonably clear (install/start/use the agent, record project progress, remind next steps), but 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 3 per the judging guidelines. It is not a 2 because the 'what' half is concrete rather than vague.

3 / 5

Trigger Term Quality

Phrases like "安装", "启动", "记录项目进展", "提醒下一步" plus the product name are terms a user could plausibly say, but there are no variations or synonyms (e.g., 项目跟踪, 进展记录, 下一步建议, proactive/proactive agent in English) and no explicit trigger framing. This fits anchor 3 ('some relevant keywords but missing common variations or synonyms'); it is above anchor 2 because the keywords present are domain-relevant rather than purely generic like 'Works with files'.

3 / 5

Distinctiveness Conflict Risk

The named product "Proactive Agent" creates a niche, but the action phrases "记录项目进展" and "提醒下一步" overlap heavily with generic progress-tracking, memory, and reminder skills, so a user asking to record progress or remind them of next steps without naming the product could trigger the wrong skill. This sits between anchor 3 (somewhat specific, overlap possible) and anchor 4; it lands at 3 because the overlap risk extends beyond just 'closely related' skills.

3 / 5

Total

12

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

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

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository

OpenSenseNova/SenseNova-Skills

Path

skills/sn-proactive-agent/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.