CtrlK
BlogDocsLog inGet started
Tessl Logo

workspace-navigator

猫猫把“打开文档、代码或日志”等模糊意图解析成本地绝对路径或 worktree 相对路径,并返回 applied、queued、blocked 或 unconfirmed 的真实 Workspace 投递状态。

65

Quality

79%

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 ./cat-cafe-skills/workspace-navigator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 and well-sequenced with explicit validation and feedback loops, and it is concise for its depth. The main gap is purely structural: it is a single long file with no progressive disclosure via references.

Suggestions

Trim the 面板快捷入口 section, which partly restates guidance already covered in the scenario table, to tighten conciseness.

Consider splitting the full tool-parameter reference and the 常见问题 FAQ into a reference file linked one level deep, to strengthen progressive disclosure.

Add a brief '验证文件存在后再调用' reminder inline next to the Step 3 call examples so the validation checkpoint is co-located with the action.

DimensionReasoningScore

Conciseness

The body is dense and practical — tables throughout, no padding, no explaining of basic concepts like glob or files — with only minor trim opportunities (the panel-shortcut section partly restates earlier guidance).

4 / 5

Actionability

It gives fully executable, copy-paste-ready guidance: per-intent glob/grep patterns and concrete cat_cafe_workspace_navigate({ path, action, worktreeId, threadId, line }) calls with real example paths covering the common cases.

5 / 5

Workflow Clarity

A clear three-step sequence (intent → path search → call MCP) with explicit validation ('先 glob/grep 确认文件存在,再调 API'), a multi-result checkpoint, and a deliveryStatus → next-action feedback loop for error recovery on queued/blocked/unconfirmed.

5 / 5

Progressive Disclosure

Single self-contained file with no bundle files and clean section/table navigation; since there are no one-level-deep references to signal, it does not perfectly fit the top anchor, but the organization is strong with only minor room to split the tool reference or FAQ out.

4 / 5

Total

18

/

20

Passed

Description

70%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 is specific, distinct, and uses natural user phrasing, but it lacks an explicit 'Use when...' clause, so its completeness is capped. Adding a one-line trigger clause would lift it to the top band.

Suggestions

Add an explicit 'Use when...' / '当 operator 说「帮我打开/看看…」时' clause to the description so the 'when' is stated, not implied, lifting completeness past 3.

Broaden the action list slightly (e.g., 'reveal directories, open files, jump to a line') to push specificity toward the comprehensive anchor.

Include a synonym or two in the description text itself (e.g., '打开/查看/找…') so trigger-term quality does not rely on the separate triggers field.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions — parsing '打开文档、代码或日志' intents into local absolute paths or worktree-relative paths and returning the applied/queued/blocked/unconfirmed delivery status — but these amount to one core action plus a status taxonomy rather than a maximally broad action list, so it sits just below the comprehensive anchor.

4 / 5

Completeness

The 'what' is clear (parse vague intents into paths and return real delivery status), but there is no explicit 'Use when...' clause; the embedded example phrases only weakly imply the 'when', so per the missing-trigger-clause guidance completeness is capped at 3.

3 / 5

Trigger Term Quality

It embeds natural phrases a user would actually say ('打开文档、代码或日志'), giving good keyword coverage, though the description text alone carries only a few of those natural terms (the separate triggers field supplies the rest).

4 / 5

Distinctiveness Conflict Risk

The workspace path-navigation niche and distinctive delivery-status vocabulary (applied/queued/blocked/unconfirmed) give clear, low-conflict triggers that are unlikely to fire for the wrong skill.

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.

Validation15 / 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
zts212653/clowder-ai
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.