CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gsd-capture

Capture ideas, tasks, notes, and seeds to their destination

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pi/package-skills/gsd-capture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, lean router: precise flag parsing, a clear sequence, an explicit fail-closed dispatch protocol, and clearly signaled one-level-deep references. Its main weaknesses are the triple repetition of the routing map across <objective>, <routing>, and <context>, and references that depend on an unresolved template placeholder rather than local bundle files.

Suggestions

Collapse the routing information into the single <routing> table and have <objective> and <context> reference it, removing the duplicated flag-by-flag prose.

State what happens for an unrecognized or malformed flag (e.g., treat as default add-todo argument vs. ask the user) so the parse step has its own validation checkpoint.

Add a fallback for the case where an execution_context path under __GSD_PI_ENGINE_ROOT__ cannot be read (e.g., report the unresolved path and stop), mirroring the fail-closed dispatch handling.

DimensionReasoningScore

Conciseness

The body avoids concept explanations and mostly assumes competence, but the routing information is stated three times: the mode-routing list in <objective> ("default (no flag): Capture as a structured todo ... add-todo workflow"), the <routing> table, and the first-token parsing rules in <context>. This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened'; it is above 2 because nothing explains concepts Claude already knows, and below 4 because consolidating the three routing statements would cut the body substantially.

3 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill: exact flags (--note, --backlog, --seed, --list-seeds, --list), precise parse rules ("strip the flag, pass remainder to note workflow"), the dispatch tool call signature ("call gsd_dispatch with role ... and task"), and explicit file paths to read. This fits 'Mostly executable guidance; concrete code or commands with minor gaps' — it is not 5 because the actual capture mechanics are entirely delegated to the referenced workflow files, which are only listed, not summarized.

4 / 5

Workflow Clarity

The three-step process (parse flag → load and execute workflow → preserve gates) is clearly sequenced, and the dispatch section provides an explicit fail-closed feedback loop ("If gsd_dispatch reports the role unresolved or the child failed, STOP that step and surface the error", with skip-if-optional handling). It matches 'Clear sequence with most checkpoints present; minor validation gaps' — the body delegates validation to the target workflows ("Preserve all workflow gates ... duplicate detection, commits") rather than stating its own checkpoint for, say, unrecognized flags, which keeps it below 5.

4 / 5

Progressive Disclosure

The body is a lean router that puts all detail in one-level-deep references, clearly signaled in a dedicated <execution_context> block listing six workflow files plus ui-brand.md, with explicit instructions to read them. This fits 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps' — it falls short of 5 because the referenced paths use the unresolved placeholder __GSD_PI_ENGINE_ROOT__ and no local bundle files exist, so navigation depends on an install-time substitution rather than verifiable relative paths.

4 / 5

Total

15

/

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 clear, compact 'what' with a GSD-flavored vocabulary, but it completely omits any 'use when' trigger guidance and leans on one generic action verb. It functions as a recognizable label rather than an effective router for when the skill should activate.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to save an idea, task, or note for later, mentions the backlog, or wants to plant/audit a seed in the GSD system.'

Name the concrete destinations (todos in .planning/todos/, notes, ROADMAP.md backlog, .planning/seeds/) so the 'what' covers what capture actually does, not just 'to their destination'.

Include natural user phrasings and the routing flags (--note, --backlog, --seed, --list) to improve trigger-term coverage and distinguish this from generic note-taking skills.

DimensionReasoningScore

Specificity

The description names the domain via four concrete capture types ("ideas, tasks, notes, and seeds") but relies on a single generic action ("Capture ... to their destination") with no detail on what capture entails. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it is above score 2 because the enumerated object types go beyond a bare domain label, but below 4 because there is only one action verb and 'their destination' is unspecified.

3 / 5

Completeness

The 'what' is stated clearly ("Capture ideas, tasks, notes, and seeds to their destination") but there is no 'when' guidance at all — no 'Use when...' clause or equivalent trigger phrasing, which caps completeness at 3 per the judging guidelines. It is not 4 because the trigger side is entirely absent rather than merely under-specified, and not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Terms like "ideas", "tasks", and "notes" are phrases users would naturally say, but common variations are missing: no "todo", "backlog", "save this for later", "remember this", or file/flag terms (--note, --backlog, --seed) that the skill actually routes on. This fits 'Some relevant keywords but missing common variations or synonyms' rather than 4's 'Good keyword coverage; a few natural terms missing', since several high-frequency phrasings are absent.

3 / 5

Distinctiveness Conflict Risk

"seeds" is a distinctive GSD-specific term, but "Capture ideas, tasks, notes" is broad and would overlap with generic note-taking, todo, or journaling skills. This matches 'Somewhat specific but could still overlap with similar skills'; the GSD system vocabulary keeps it above 2, while the lack of explicit trigger scoping keeps it below 4.

3 / 5

Total

12

/

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

open-gsd/gsd-core

Path

pi/package-skills/gsd-capture/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.