wayfinder

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

Quality

67%

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

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 a well-structured, actionable planning skill with clear sequenced workflows and validation checkpoints. Its main weaknesses are conceptual verbosity and a monolithic layout with no progressive disclosure via reference files.

Suggestions

Tighten the fog-of-war and out-of-scope sections to their operational rules, trimming the philosophical rationale that does not change what Claude does.

Extract the map-body and ticket markdown templates into a reference file (e.g. references/templates.md) and link to it, so the overview stays lean and navigable.

Consider moving the detailed Ticket Types table into a reference file referenced one level deep, keeping the core workflow in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of basic-concept fluff Claude already knows, but it carries substantial conceptual/philosophical elaboration (fog-of-war metaphor, plan-don't-do and out-of-scope rationale) that could be tightened without losing operational clarity.	2 / 3
Actionability	It provides copy-paste-ready markdown templates for the map body and tickets, concrete labels (wayfinder:map, wayfinder:<type>), named sub-skills (/grilling, /domain-modeling, /research, /prototype), and specific claim/resolve procedures — concrete and actionable for an instruction-only skill.	3 / 3
Workflow Clarity	Both invocation modes are laid out as clearly numbered sequences with explicit checkpoints: stop-and-ask if no fog (charting step 2), claim-before-work concurrency guard, the 'Fog or ticket?' test, and rule-out-of-scope handling for the destructive close-ticket action.	3 / 3
Progressive Disclosure	The skill is a single monolithic file with well-organized sections but no bundle files and no one-level-deep references; at ~125 lines, material such as the map-body template and ticket-type detail is all inline and could be split out for easier navigation.	2 / 3
	Total	10 / 12 Passed

Description

57%

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, distinctive niche but is held back by metaphor-heavy phrasing and the absence of an explicit use-when trigger. It answers 'what' well but only implies 'when'.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrasing, e.g. 'Use when a task is too large for one agent session and needs to be broken into issue-tracker decision tickets before execution.'

Reduce metaphor in favor of concrete user-sayable terms (e.g. 'break into tickets' instead of 'find the way to the destination') to improve trigger term quality.

List the concrete operations briefly (create a map issue, file decision tickets, resolve them one per session) to lift specificity toward multiple concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain (oversized work, issue tracker, decision tickets, shared map) and actions (plan into tickets/map, resolve one by one), but relies on a single conceptual action wrapped in metaphor ('destination', 'way') rather than listing multiple concrete operations; not comprehensive.	2 / 3
Completeness	It states what the skill does, but the 'when' is only weakly implied (work that does not fit in one session) and there is no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant terms like 'agent session', 'issue tracker', 'decision tickets' appear, but the phrasing is metaphor-laden ('destination', 'shared map') and a user needing this skill would more naturally say 'this is too big for one session' or 'break this into tickets'; common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The combination of oversized-work decomposition into issue-tracker decision tickets and a shared map is a clear niche with distinct triggers, unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: vinvcn/mattpocock-skills-zh-CN
Path: skills/engineering/wayfinder/SKILL.md
Commit: f2b2464

Reviewed: 1 day 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.