CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

67%

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

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured conceptually but verbose, descriptive rather than executable, and critically has broken progressive disclosure: it references nonexistent module files and never links the real reference bundle.

Suggestions

Fix progressive disclosure: replace the six dangling 'modules/*.md' links with links to the actual references/examples.md and references/reference.md (or create the modules), so navigation targets exist.

Trim redundancy: merge the three overlapping 'When to Use' sections into one and condense the 'Common Rationalizations' table, which argues concepts Claude already knows.

Add concrete, executable guidance (specific commands, code snippets, or copy-paste handoff package templates) in the body rather than describing patterns abstractly.

DimensionReasoningScore

Conciseness

Mostly efficient per-section but padded overall: redundant 'When to Use' lists appear in Quick Reference, Implementation Guide, and Best Practices, and the 'Common Rationalizations' table debates strawmen Claude already understands; token-percentage breakdowns add length without proportional value.

2 / 3

Actionability

Gives some concrete guidance (150K/180K thresholds, /clear points, 30K buffer) but the body is predominantly descriptive prose ('Concept:', 'Use Case:') with no executable code or commands; the concrete examples live only in the unreferenced references/examples.md.

2 / 3

Workflow Clarity

Multi-step SPEC-First and monitoring workflows are sequenced with a verification checklist, but validation feedback loops are implicit and one-line ('Verify agent compatibility') for operations that warrant a validate-fix-retry loop, leaving checkpoints mostly implicit.

2 / 3

Progressive Disclosure

Scored against the actual bundle: the body's 'Advanced Documentation' section points to six modules/*.md files that do not exist, while the real references/examples.md and references/reference.md are never linked — broken navigation plus a monolithic body matches the monolithic/deeply-broken-references anchor.

1 / 3

Total

7

/

12

Passed

Description

92%

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 states concrete capabilities and includes an explicit 'Use for ...' trigger clause covering natural terms. Its main weakness is moderate overlap risk with generic context/memory skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions within a defined domain: 'Manages context window optimization, session state persistence, and token budget allocation', matching the anchor for listing multiple specific concrete actions; not a 2 because it goes beyond naming a domain plus some actions.

3 / 3

Completeness

Explicitly answers both what ('Manages ... optimization, ... persistence, and ... allocation for multi-agent workflows') and when ('Use for token budget management, context limits, or session handoff'), with an explicit 'Use for' trigger clause.

3 / 3

Trigger Term Quality

The 'Use for token budget management, context limits, or session handoff across agents' clause supplies natural terms a user would say; some jargon ('context window optimization') keeps it from being perfect but coverage is strong.

3 / 3

Distinctiveness Conflict Risk

The multi-agent context/session niche is fairly specific, but 'context' and 'memory' triggers overlap with general context-management and memory skills, so it could still trigger for the wrong skill.

2 / 3

Total

11

/

12

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.

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