CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-foundation-core

Provides MoAI-ADK foundational principles including TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, agent catalog reference, and token budget management (absorbed from moai-foundation-context). Use when referencing TRUST 5 gates, SPEC workflow, or context window optimization.

Quality

69%

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 ./.claude/skills/moai-foundation-core/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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-organized, largely concrete reference with a clearly sequenced three-phase workflow and explicit checkpoints, but it is let down by material redundancy across the three token-budget sections and — most seriously — a progressive-disclosure architecture that is claimed but not shipped: nine of its module references are broken within the provided bundle.

Suggestions

Ship the referenced modules/ directory (or prune the pointers): every 'Detailed Reference: modules/*.md' link currently resolves to a nonexistent file, breaking the skill's own navigation model.

Consolidate the three separate token-budget treatments (sections 2 and 4 plus the closing 'Token Budget' section) into a single phase-budget table with the /clear strategy stated once.

Remove the unverifiable improvement percentages ('40 percent task success', '70 percent fewer escalations', '2-3x larger projects') and the trailing rationale sentences on each TRUST pillar — they pad tokens without adding executable guidance.

DimensionReasoningScore

Conciseness

The body is mostly dense, useful reference material, but includes unnecessary explanation and clear redundancy: phase token budgets (30K/180K/40K/250K) are stated three times (sections 2, 4, and the closing 'Token Budget' table), /clear guidance is repeated in sections 2, 4, and the closing section, and each TRUST pillar closes with a rationale sentence Claude does not need (e.g. 'Clear naming improves code comprehension, team collaboration, and maintenance velocity'). This fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than 2, since padding is confined to duplicated token sections rather than pervasive prose.

3 / 5

Actionability

The guidance is largely concrete and executable: specific commands (/moai plan, /clear, moai spec lint --strict), thresholds (85% coverage, 150K context), file paths (.moai/specs/SPEC-XXX/spec.md, progress.md), a copy-paste resume-message template, and fully quoted GEARS clause patterns. It stops short of 5 because several claims are unverifiable marketing ('improves task success rate by 40 percent', 'Enables 2-3x larger projects', 'Reduces escalations by 70 percent') and key steps defer to module files that are not present.

4 / 5

Workflow Clarity

The three-phase workflow (plan → run → sync) is clearly sequenced with per-phase budgets, explicit /clear checkpoints, guard conditions ('Never use /clear when: In the middle of an agent task...'), a numbered multi-agent handoff procedure, and a closing verification checklist. TRUST 5 gates even specify failure actions ('Block merge and generate missing tests on failure'). Not 5 because error-recovery loops for the SPEC/DDD phases themselves (e.g. what to do when lint or coverage fails mid-run) are only pointed at via 'Detailed Reference' links rather than stated inline.

4 / 5

Progressive Disclosure

Judged against the actual bundle: the body repeatedly points to nine 'modules/*.md' files (trust-5-framework.md, spec-first-ddd.md, delegation-patterns.md, token-optimization.md, progressive-disclosure.md, modular-system.md, agents-reference.md, commands-reference.md, execution-rules.md), none of which exist in the bundle — only references/examples.md and references/reference.md are present. On top of the dangling references, deep content that the skill's own rules say belongs in modules (the full GEARS spec, the closing Token Budget section duplicating modules/token-optimization.md) is inlined into SKILL.md. This matches anchor 2 ('content that clearly belongs in separate files is inlined') better than 3, since most navigation pointers lead nowhere within the bundle.

2 / 5

Total

13

/

20

Passed

Description

67%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.

A solid description: it names the domain, enumerates its six components, and includes an explicit 'Use when' clause with concrete trigger phrases. Its main weaknesses are jargon-only trigger terms with no natural synonyms, and trigger coverage that spans only half of the advertised capabilities.

Suggestions

Extend the 'Use when' clause to cover all six capabilities, e.g. add delegation/agent selection, progressive disclosure structure, and token budget planning as explicit triggers.

Add plain-language synonyms alongside the jargon (e.g. 'quality gates', 'specification workflow', 'context window / token budget') so users outside the MoAI project can still match the description.

Drop the migration note '(absorbed from moai-foundation-context)' from the description; it consumes trigger space without describing a capability.

DimensionReasoningScore

Specificity

The description enumerates concrete components — "TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, agent catalog reference, and token budget management" — giving several specific items with only minor gaps. It falls short of 5 because the only action verb is the generic "Provides ... principles" (what it contains, not what it does), and the parenthetical "(absorbed from moai-foundation-context)" is migration noise rather than capability; it is above 3 because coverage of the skill's contents is comprehensive rather than 1-2 actions.

4 / 5

Completeness

Both parts are explicit: the what ("Provides MoAI-ADK foundational principles including ...") and the when ("Use when referencing TRUST 5 gates, SPEC workflow, or context window optimization"). Not 5 because the trigger phrases cover only half the listed capabilities, so the 'when' is explicit but narrower than the 'what' promises; clearly above 4's anchor-3 profile where 'when' is missing or merely implied.

4 / 5

Trigger Term Quality

The when-clause offers some relevant keywords — "TRUST 5 gates, SPEC workflow, or context window optimization" — but these are project-internal jargon with no natural synonyms or plain-language variants (e.g. quality gates, delegation, agent selection, token budget). It also omits triggers for three of the six listed capabilities (delegation patterns, progressive disclosure, agent catalog), matching anchor 3 ('some relevant keywords but missing common variations or synonyms') rather than 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The MoAI-ADK namespace plus specific artifacts (TRUST 5, SPEC-First DDD, moai-foundation-context) gives it a clear niche with minimal conflict against generic skills. Not 5 because the frontmatter names closely related sibling skills (moai-foundation-cc, moai-foundation-thinking) and terms like "SPEC workflow" and "context window optimization" plausibly overlap with the moai-workflow-spec and token-optimization territory — 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

15

/

20

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

Validation for skill structure

CriteriaDescriptionResult

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

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

modu-ai/moai-adk

Path

.claude/skills/moai-foundation-core/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.