CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-foundation-context

Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.

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 ./.moai/archive/skills/v3.0/moai-foundation-context/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 well-organized with concrete thresholds, quantified budgets, sequenced workflows, and useful rationalization/red-flag/verification sections, but it is held back by structural duplication and, critically, an Advanced Documentation section whose six module references do not match the actual bundle (references/reference.md and references/examples.md are never linked). Fixing the reference paths and providing templates for the handoff package and session snapshot would lift it substantially.

Suggestions

Replace the six nonexistent modules/*.md pointers with links to the actual bundle files (references/reference.md and references/examples.md), or add the module files so the Advanced Documentation section resolves.

Deduplicate the overlapping sections — merge the two "When to Use" lists and the "Quick Reference" capabilities with the "Implementation Guide" features into a single section, and drop the abbreviated "Core Patterns" summary that is fully restated in "Core Patterns Detail".

Add concrete templates or examples for the handoff package structure (Pattern 4) and session state snapshot (Pattern 3) so the guidance is copy-paste executable rather than descriptive.

DimensionReasoningScore

Conciseness

The body is mostly list-form and avoids explaining concepts Claude already knows, but it is padded with duplicated sections: two near-identical "When to Use" lists ("Managing large codebases exceeding 150K token limits" vs "Context window approaching limits exceeding 150K tokens"), overlapping capability/feature lists in "Quick Reference" and "Implementation Guide", and "Core Patterns" summarized in the Implementation Guide then re-expanded in "Core Patterns Detail". This fits anchor 3 (mostly efficient but could be tightened) rather than 2, since the individual sections are terse and the duplication is structural rather than fluffy prose.

3 / 5

Actionability

There is genuinely concrete guidance — specific thresholds (warning at 150K, critical at 180K, clear at 85%), quantified budget breakdowns, and an itemized handoff package field list — but everything is described rather than templated: no copy-paste command sequences, no handoff package format example, no session-state snapshot template. As an instruction-only skill this lands at anchor 3 (some concrete guidance but incomplete) rather than 4, which would require mostly executable, specific instruction blocks.

3 / 5

Workflow Clarity

Multi-step processes are sequenced ("Session Initialization", "SPEC-First Workflow: Execute /moai:1-plan, then mandatory /clear to save 45-50K tokens, then /moai:2-run...") and validation is present (handoff validation checks, a Verification checklist with checkboxes, and monitoring thresholds with defined actions at 60/75/85%). This matches anchor 4 (clear sequence, most checkpoints present) rather than 5 because the workflow sequences are compressed run-on paragraphs instead of numbered steps with explicit error-recovery loops.

4 / 5

Progressive Disclosure

The "Advanced Documentation" section points to six module files (modules/token-budget-allocation.md, modules/session-state-management.md, modules/context-optimization.md, modules/handoff-protocols.md, modules/memory-mcp-optimization.md, modules/reference.md), but none of these exist in the bundle — the actual files are references/reference.md and references/examples.md, neither of which is referenced from the body. Every navigation pointer is broken, and substantial detail (the full pattern descriptions, budget tables) is inlined that belongs in those separate files. This matches anchor 2 (references buried/broken, content that should be separate is inline) rather than 3, because the structure exists on paper but resolves to nothing on disk.

2 / 5

Total

12

/

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.

A strong description: it states concrete capabilities in third person and includes an explicit "Use for..." trigger clause with domain-appropriate keywords. Its main weaknesses are mildly abstract action phrasing and a missed opportunity to include common synonyms (context window, memory, session persistence) in the trigger clause.

DimensionReasoningScore

Specificity

The description names the domain ("context window optimization, session state persistence, and token budget allocation for multi-agent workflows") and lists several specific capabilities, but the actions are somewhat abstract noun-phrases rather than fully concrete operations like the anchor-5 examples ("Extract text and tables... fill forms, merge documents"). It fits anchor 4 (several specific actions, minor coverage gaps) better than 3, since more than 1-2 actions are named, and better than 5, since the actions are less concrete and comprehensive than the top anchor.

4 / 5

Completeness

Both halves are explicit: the "what" ("Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows") and a concrete "when" clause ("Use for token budget management, context limits, or session handoff across agents"). This mirrors the anchor-5 example structure (capability list followed by "Use when...") with concrete trigger phrases, so it clearly exceeds anchor 4's "when could be more explicit".

5 / 5

Trigger Term Quality

"Use for token budget management, context limits, or session handoff across agents" supplies natural phrases a user would plausibly say (token budget, context limits, session handoff). It is not a 5 because common variations and synonyms are missing from the description itself — e.g., "context window", "memory", "session persistence", "/clear" — and not a 3 because the terms present go beyond a bare domain mention to multiple usable trigger phrases.

4 / 5

Distinctiveness Conflict Risk

The multi-agent token/session niche is fairly distinct with dedicated triggers (token budget, session handoff), but terms like "context", "state", and "session management" overlap with related memory- and configuration-management skills (the body itself lists moai-cc-memory and moai-cc-agents as neighbors). Mostly distinct with minor overlap risk among closely related skills — anchor 4, not 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

Path

.moai/archive/skills/v3.0/moai-foundation-context/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.