CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-gtd

Canonical GTD entry point for capture, clarification, organization, review, and engagement

Quality

80%

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

The canonical home for this skill is moai-todo in modu-ai/moai-adk

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 maximally lean router stub: one unambiguous, executable instruction delegating to the "moai" skill with the "gtd" argument. It fully satisfies conciseness, workflow clarity, and progressive disclosure for a single-purpose delegation skill, with only a minor actionability gap from the absence of worked examples.

DimensionReasoningScore

Conciseness

The body is a single instruction line — "Use Skill("moai") with arguments: gtd $ARGUMENTS" — with zero padding and nothing that explains what Claude already knows. Every token is load-bearing for a router stub, matching the lean-and-efficient anchor exactly.

5 / 5

Actionability

It gives one fully concrete, executable command — the exact skill to invoke ("moai") and the exact argument pattern ("gtd $ARGUMENTS") — so it is well above anchor 3's pseudocode level. It falls short of anchor 5 only because there are no worked examples covering common invocations and the $ARGUMENTS placeholder is left unexplained.

4 / 5

Workflow Clarity

This is a simple single-purpose skill whose one action (delegate to Skill("moai") with args "gtd $ARGUMENTS") is unambiguous, so the simple-skill exception applies and workflow clarity can score 5. No destructive or batch operation is involved, so no validation checkpoint is required.

5 / 5

Progressive Disclosure

A one-line router with a single, clearly signaled one-level-deep reference to the target skill "moai" that holds all real content; nothing that belongs elsewhere is inlined. For an under-50-line skill with no need for external references, this clean delegation structure satisfies the anchor-5 pattern.

5 / 5

Total

19

/

20

Passed

Description

58%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 names the GTD domain and all five methodology stages, giving it reasonable specificity and a distinct niche. However, the actions are abstract nouns without objects, it contains no "when to use" guidance (capping completeness at 3), and trigger coverage relies on the "GTD" acronym while missing natural user phrasings like "tasks", "to-do", or "weekly review".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions GTD, Getting Things Done, inbox capture, weekly reviews, or next actions."

Include natural synonyms users actually say — "tasks", "to-do list", "Getting Things Done", "weekly review", "next actions" — instead of relying solely on the five stage nouns.

Give each action an object so capabilities read as concrete verb+object pairs, e.g. "captures items into an inbox, clarifies them into next actions, organizes by context, runs weekly reviews".

DimensionReasoningScore

Specificity

Lists several named actions covering the full GTD pipeline — "capture, clarification, organization, review, and engagement" — with minor gaps. It falls below anchor 5 because the actions are abstract nouns without objects or outcomes (cf. "Extract text and tables from PDF files"), and above anchor 3 because it names the domain plus five stages rather than only 1-2 actions.

4 / 5

Completeness

The "what" is clearly stated ("Canonical GTD entry point for capture, clarification, organization, review, and engagement") but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It does not reach anchor 4 because the "when" is entirely absent, not merely imprecise.

3 / 5

Trigger Term Quality

Includes the key term "GTD" plus stage words like "capture", "organization", and "review", but misses common user phrasings such as "tasks", "to-do list", "inbox", "next actions", "weekly review", or "Getting Things Done" spelled out. Coverage leans mainly on the GTD acronym, matching anchor 3 (some relevant keywords, missing common variations) rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

The GTD framing carves out a mostly distinct niche with a clear entry-point claim, but generic stage words ("review", "organization", "capture", "engagement") create minor overlap risk with other productivity or task-management skills. It does not reach anchor 5 because it lacks explicit distinct trigger phrases, and it is above anchor 3 because the "Canonical GTD" positioning is specific.

4 / 5

Total

14

/

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-gtd/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.