CtrlK
BlogDocsLog inGet started
Tessl Logo

moai-foundation-cc

Canonical Claude Code authoring kit covering Skills, sub-agents, plugins, slash commands, hooks, memory, settings, sandboxing, headless mode, and advanced agent patterns. Use when creating Claude Code extensions or configuring Claude Code features.

61

Quality

73%

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-cc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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, mostly actionable reference with a clear workflow and verification checklist, but it is weighed down by redundancy, inline time-sensitive version detail, and a progressive-disclosure structure whose referenced detail files are missing from the bundle.

Suggestions

Create the referenced reference/*.md files (e.g. claude-code-skills-official.md, claude-code-hooks-official.md) or remove the dangling Documentation Index entries so progressive disclosure points to real on-demand resources.

De-duplicate the /agents-removed note and move version-specific deltas (CC 2.1.172/2.1.197/2.1.198, dated changelog notes) into a single "Deprecated / changelog" section to improve conciseness.

Add at least one complete copy-paste template (a full plugin.json and a full agent frontmatter) so the core authoring guidance is fully executable rather than described in prose.

DimensionReasoningScore

Conciseness

The ~250-line body is mostly efficient reference material, but the /agents-removed note is repeated (Quick Reference and Sub-agent Creation), inline version-specific info (CC 2.1.172/2.1.197/2.1.198, 2026-07-03) is not isolated in a deprecated section, and evolvable provenance comments add noise, fitting anchor 3.

3 / 5

Actionability

It gives concrete commands and examples ("/plugin install owner/repo", "sg -p 'class $X extends Service' --lang python", Grep/Glob patterns, -p/--allowedTools flags) plus concrete field specs, but core authoring formats are described in prose without complete copy-paste templates, leaving minor gaps.

4 / 5

Workflow Clarity

The Explore-Plan-Code-Commit workflow is a clear four-phase sequence and the Verification checklist supplies checkpoints for the risky settings.json case, but the main workflow phases stay high-level without embedded validation steps, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

Section structure and a Documentation Index signal one-level-deep references clearly, but the referenced reference/*.md files do not exist in the bundle and substantial reference content is inlined in the body, matching anchor 3 rather than the well-placed anchor 4.

3 / 5

Total

14

/

20

Passed

Description

83%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 strong: it explicitly states both what the kit covers and when to use it, with concrete trigger phrases and a distinct canonical-kit niche. The main weakness is that it lists covered topics rather than concrete actions, and its breadth introduces minor overlap risk.

DimensionReasoningScore

Specificity

The description enumerates many concrete components it covers ("Skills, sub-agents, plugins, slash commands, hooks, memory, settings, sandboxing, headless mode, and advanced agent patterns"), but they are topics/objects rather than verbs, so it stops short of the comprehensive action-listing anchor 5.

4 / 5

Completeness

It explicitly answers both what ("Canonical Claude Code authoring kit covering…") and when ("Use when creating Claude Code extensions or configuring Claude Code features") with concrete trigger phrases, matching the anchor 5 example.

5 / 5

Trigger Term Quality

"Use when creating Claude Code extensions or configuring Claude Code features" supplies natural phrases a user would say, with good keyword coverage, but lacks synonyms or variations that would reach anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Canonical Claude Code authoring kit" carves a clear niche, but the breadth across ten topics creates minor overlap risk with more specialized Claude Code skills, fitting anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 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

Total

14

/

16

Passed

Repository
modu-ai/moai-adk
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.