CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wayfinder

把单个 agent session 装不下的一大块工作规划成 issue tracker 上的 decision tickets shared map,并逐一解决,直到通往 destination 的路清晰。

Quality

71%

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/engineering/wayfinder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a well-crafted, information-dense skill body: both workflows are concretely sequenced with edge-case handling, the templates are copy-paste ready, and it assumes Claude's competence throughout without teaching known concepts. The main residual gaps are the dangling reference to a tracker doc that is not part of the bundle and decision-gate (rather than verification) checkpoints.

Suggestions

Ship the referenced "tracker doc" (e.g. references/tracker.md with the 「Wayfinding 操作」 section and the local-markdown fallback) inside the skill's references/ directory so the pointer is not dangling.

Add lightweight verification steps to the advancing workflow (e.g. confirm the issue is closed and the Decisions-so-far pointer landed before adding new tickets) to upgrade decision gates into true checkpoints.

DimensionReasoningScore

Conciseness

The body is dense and purposeful: it teaches only skill-specific concepts (fog of war, frontier, HITL/AFK, claim-by-assignee) that Claude would not already know, and never pads with background explanation. It falls short of anchor 5 due to a few sentences of motivational restatement (e.g. "想直接做工作的冲动通常表示你已经到达 map 边缘,该 hand off 了") and some repetition of the out-of-scope rules across sections.

4 / 5

Actionability

Guidance is largely executable: copy-paste-ready map and ticket body templates, exact labels (`wayfinder:map`, `wayfinder:<type>`), a concrete claim procedure (assign before any work), and specific Skill-tool invocations (`research`, `prototype`, `grilling`, `domain-modeling`) with a research-branch convention. It is not a 5 because key operations defer to external artifacts not in the bundle — the "tracker doc 的「Wayfinding 操作」小节" and `/setup-matt-pocock-skills` — leaving minor execution gaps.

4 / 5

Workflow Clarity

Both invocation modes are clearly sequenced (6-step charting, 5-step advancing) with explicit gates: stop if no fog, claim before work, one resolution per session, close-and-log out-of-scope tickets, and update/delete invalidated tickets. Anchor 5 is not reached because checkpoints are decision gates rather than verification steps — e.g. no check that the resolution comment posted, the issue closed, or blocking edges wired correctly — leaving minor validation gaps at anchor 4.

4 / 5

Progressive Disclosure

The body is well organized into clearly signaled sections (map structure, ticket types, fog of war, out of scope, two invocation modes) with templates inlined at a size where separation is unnecessary, and cross-skill references are explicit. It does not reach 5 because the "tracker doc" and local-markdown-tracker references point outside the skill with no bundled fallback files present in references/, a small navigation gap.

4 / 5

Total

16

/

20

Passed

Description

53%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 clear, fairly distinctive capability in a single sentence with a concrete "what", but it entirely lacks an explicit "Use when…" trigger clause and leans on skill-internal vocabulary (decision tickets, shared map, destination) rather than natural user phrases. Adding explicit trigger guidance and user-natural keywords would materially improve trigger quality and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when a task is too large for one agent session, when the path to the goal is unclear, or when the user asks to plan, decompose, or map out a large effort before executing it."

Replace or augment jargon terms ("decision tickets", "shared map", "destination") with natural user vocabulary such as "break down large work", "planning", "roadmap", "issue tracker tickets" so users' phrasing matches the description.

Briefly enumerate the concrete actions involved (chart the map, create and wire tickets, grill/research/prototype each decision, graduate fog into new tickets) to raise specificity from 1-2 named actions to several.

DimensionReasoningScore

Specificity

The description names its domain (oversized work, agent sessions) and 1-2 concrete actions — "规划成 issue tracker 上的 decision tickets shared map" and "逐一解决" — but coverage is not comprehensive (no mention of the charting/advancing modes or ticket types). It fits anchor 3 (domain plus 1-2 concrete actions) better than anchor 4, which expects several listed actions.

3 / 5

Completeness

The "what" is clear (decompose oversized work into a decision-ticket map on an issue tracker and resolve tickets until the path is clear), but there is no explicit "Use when…" clause or equivalent trigger guidance — the "when" is only weakly implied by "单个 agent session 装不下". Per the judging guidelines, a missing explicit trigger clause caps completeness at 3, so it cannot reach 4.

3 / 5

Trigger Term Quality

Some relevant natural terms are present ("agent session", "issue tracker", "一大块工作"/"装不下" as a natural pain phrase), but several keywords are skill-internal jargon ("decision tickets", "shared map", "destination") that users would not naturally say. It sits between anchor 3 (some relevant keywords, missing variations) and anchor 2; the genuinely natural "too big for one session" phrasing lifts it to 3.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — multi-session planning via issue-tracker decision tickets with a shared map — with limited overlap risk against generic planning or task-breakdown skills. It is not a 5 because the description does not carry distinct trigger phrases, so a user asking broadly to "plan" or "break down" large work could match other planning skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

vinvcn/mattpocock-skills-zh-CN

Path

skills/engineering/wayfinder/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.