survey
Home base for development work. Navigate the work graph, see what's ready, blocked, or stalled, reflect on where the team is, and decide what to pick up next.
42
43%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./develop/skills/survey/SKILL.mdQuality
Discovery
9%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 too abstract and metaphorical ('home base', 'work graph') to serve as an effective skill selector. It lacks explicit trigger guidance, concrete technical actions, and natural user keywords. Without a 'Use when...' clause and with vague language throughout, Claude would struggle to reliably select this skill from a pool of alternatives.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms like 'what should I work on next', 'project status', 'blocked tasks', 'backlog', 'priorities', or 'sprint planning'.
Replace abstract phrases like 'navigate the work graph' and 'home base' with concrete actions such as 'Lists open tasks by status, identifies blocked work items, and recommends next tasks based on priority and dependencies'.
Clarify the specific domain and tooling (e.g., does this work with GitHub issues, Jira, a local task file?) to make the skill distinctly identifiable and reduce conflict risk with other development workflow skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names some actions like 'navigate the work graph', 'see what's ready, blocked, or stalled', 'reflect on where the team is', and 'decide what to pick up next', but these are somewhat abstract and not concrete technical operations. The domain is loosely defined as 'development work'. | 2 / 3 |
Completeness | While it loosely describes what it does, there is no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is entirely missing, which per the rubric should cap completeness at 2, and the 'what' is also vague enough to warrant a score of 1. | 1 / 3 |
Trigger Term Quality | The description lacks natural keywords a user would actually say. Terms like 'home base', 'work graph', and 'stalled' are not typical user trigger phrases. Missing common terms like 'task board', 'backlog', 'sprint', 'status', 'priorities', 'what should I work on', or 'project status'. | 1 / 3 |
Distinctiveness Conflict Risk | 'Home base for development work' is extremely generic and could overlap with project management, task tracking, sprint planning, or any number of development workflow skills. There are no distinct triggers to differentiate it. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
77%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 instruction skill that provides concrete, scenario-based guidance for a read-only survey activity. Its strengths are clear actionability through specific trigger phrases, prioritized signal lists, and explicit transition points to other skills. Minor weaknesses include some verbosity in framing/stance sections and inline content that could potentially be split for better progressive disclosure.
Suggestions
Trim the 'Your Stance' section — the behavioral framing ('receptive, observational, honest') is implicit from the instructions and doesn't need a dedicated section.
Consider moving the detailed scenario response patterns (re-entry, direction-seeking, reflection, stale sweeps) into a separate reference file, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally well-written but includes some unnecessary framing ('You are the home base of development work') and stance descriptions that Claude doesn't need explained at length. The 'What Survey Does NOT Do' section is useful but slightly verbose. The example trigger phrases are helpful but add bulk. | 2 / 3 |
Actionability | Despite being an instruction-only skill (no code), the guidance is highly concrete and specific. Each scenario has clear trigger phrases, explicit response strategies with prioritized signal lists, specific patterns to scan for, and named transitions to other skills. The signal priority list and staleness signals are actionable checklists. | 3 / 3 |
Workflow Clarity | The skill clearly sequences the survey workflow: read the graph → identify the relevant scenario → respond with the appropriate pattern → suggest a transition when the thought crystallizes. For a non-destructive, read-only skill, this is appropriately clear. The transitions section provides an explicit decision tree for handoffs. | 3 / 3 |
Progressive Disclosure | References to model.md and guidelines.md are clear and one-level deep, which is good. However, the skill itself is moderately long (~100 lines) and could benefit from separating the detailed scenario responses into a reference file, keeping the SKILL.md as a leaner overview. The inline content is well-organized with headers but borders on being a monolithic document. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- audenaert/etak
- Commit
632c389
- 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.