CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-todo

Compatibility alias for the canonical GTD task-management entry point

Quality

71%

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 ./.agents/skills/moai-todo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 model of token-efficient delegation: one unambiguous, executable instruction with zero padding. Its only weakness is the unexpanded '$ARGUMENTS' placeholder with no example of a valid gtd command, which slightly limits copy-paste readiness. Since the skill is a pure alias, it needs no workflow, validation, or bundle structure beyond what it has.

DimensionReasoningScore

Conciseness

The body is a single line ('Use Skill("moai") with arguments: gtd $ARGUMENTS') with zero padding and no explanation of concepts Claude already knows, matching 'Lean and efficient; every token earns its place'. It cannot score higher than the top anchor and clearly is not anchor 4, which requires trimmable over-explanation.

5 / 5

Actionability

The instruction is a concrete, exact command — the target skill name ('moai'), the subcommand ('gtd'), and the argument-passing convention — which is directly executable. It falls short of anchor 5 because '$ARGUMENTS' is an unexpanded placeholder and no example of a valid gtd invocation is given, a minor gap.

4 / 5

Workflow Clarity

This is a simple single-purpose skill whose one action (delegate to moai with the gtd subcommand) is completely unambiguous, so the simple-skill exception applies and a 5 is warranted. There are no destructive or batch operations, so no validation checkpoint is required; anchor 4's 'minor validation gaps' does not apply.

5 / 5

Progressive Disclosure

The body is well under 50 lines and needs no bundle files; it defers all detail one level deep to the clearly signaled target skill ('moai'), which is the appropriate structure for an alias. This matches 'Clear overview with well-signaled one-level-deep references... easy navigation'; there is no inline content that belongs elsewhere.

5 / 5

Total

19

/

20

Passed

Description

36%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 terse and honest about being an alias, but it scores poorly on the rubric because it states no concrete capabilities and gives no usage guidance whatsoever. A user or Claude reading only the description would not know when to invoke it or what happens beyond delegation. Adding an explicit 'Use when...' clause and naming the underlying capabilities (e.g., capturing, listing, and completing tasks) would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user mentions GTD, todos, to-do lists, or task management', to address the missing 'when' that currently caps completeness.

State the concrete capabilities being aliased (e.g., 'adds, lists, and completes tasks via the moai gtd command') instead of only describing the alias relationship.

Include natural synonyms users would actually say ('todo', 'to-do list', 'tasks', 'GTD') so the alias triggers on the same phrases as the canonical skill.

DimensionReasoningScore

Specificity

The description names the domain ("GTD task-management" aliasing) but lists no concrete actions the skill performs, matching 'Names the domain but actions are minimal or generic'. It does not reach anchor 3 because no actual capability is stated, and is above anchor 1 because the domain is named specifically.

2 / 5

Completeness

The 'what' is vague ("Compatibility alias for the canonical GTD task-management entry point" tells what it delegates to, not what it does) and the 'when' is entirely absent — there is no 'Use when...' clause, which also caps completeness at 3 per the guidelines. This matches anchor 2 ('Has a vague what and no when') rather than anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

It includes some relevant keywords ("GTD", "task-management") but misses common variations users would naturally say such as 'todo', 'to-do list', or 'tasks'. It is more specific than the generic one-or-two-keyword anchor 2 ('Works with files') but lacks the synonym coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Compatibility alias for the canonical GTD task-management entry point" identifies a specific niche but by design overlaps with the canonical entry point it aliases and with any other task-management skill, matching 'Somewhat specific but could still overlap with similar skills'. It is not mostly distinct (anchor 4) because the alias and the canonical skill share the same trigger surface.

3 / 5

Total

10

/

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

modu-ai/moai-adk

Path

.agents/skills/moai-todo/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.