moai-workflow-jit-docs

Enhanced Just-In-Time document loading system that discovers, loads, and caches relevant documentation based on user intent and project context. Use when users need specific documentation on demand.

Quality

45%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.moai/archive/skills/v3.0/moai-workflow-jit-docs/SKILL.md

Quality

Content

31%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 long, abstract description of a documentation-loading system with no executable examples and no links to the provided bundle files, leaving it verbose and only loosely actionable.

Suggestions

Replace abstract process prose with concrete, copy-paste-ready guidance: example WebSearch/WebFetch/Context7 invocations and the exact .moai/docs lookup sequence.

Wire the body to the bundle files (e.g., 'See [references/examples.md](references/examples.md) for worked lookup examples') instead of inlining reference-style content.

Add explicit validation checkpoints into each Practical Workflow (e.g., verify cache freshness against source mtime before reusing, confirm a doc was actually loaded before proceeding) and trim padded sections that restate WebSearch/caching basics.

Dimension	Reasoning	Score
Conciseness	The ~258-line body restates concepts Claude already knows (what WebSearch does, authority/recency ranking, caching) across padded abstract lists, with several unnecessary explanatory sections.	2 / 5
Actionability	Guidance is high-level ('Use WebSearch with current year', 'Calculate match between content and question') with no executable code or commands, though specific tools and paths like Context7 MCP and .moai/docs are named.	2 / 5
Workflow Clarity	The Practical Workflows section lists ordered sequences, but validation checkpoints are implicit/absent within the workflows rather than explicit inline gates.	3 / 5
Progressive Disclosure	Bundle files references/examples.md and references/reference.md exist but the body never links to or navigates them, while bulk reference-style content is inlined into the SKILL.md.	2 / 5
	Total	9 / 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 answers both what and when in third person and names three actions, but its trigger term coverage is thin and the 'when' clause is generic, leaving moderate overlap risk with sibling documentation skills.

Suggestions

Add concrete natural trigger phrases to the description (e.g., 'Use when the user asks how to implement a framework, needs API reference, or wants best practices for a technology').

Sharpen the 'what' from abstract verbs to specific capabilities (e.g., 'searches local .moai/docs, fetches official docs via WebFetch/Context7, and caches results per session').

Tighten distinctiveness by naming the JIT/on-demand scope explicitly so it does not collide with general documentation-generation skills.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('discovers, loads, and caches relevant documentation') but the verbs are abstract rather than the specific, comprehensive action list of a 4 or 5.	3 / 5
Completeness	Both 'what' ('discovers, loads, and caches relevant documentation') and 'when' ('Use when users need specific documentation on demand') are explicit, though the 'when' clause is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	The description itself surfaces only 'documentation' as a natural trigger term; common synonyms and variations a user would say (docs, API reference, how to) are absent from the description field even if present in frontmatter triggers.	3 / 5
Distinctiveness Conflict Risk	'Documentation loading' is a recognizable niche but 'documentation' is broad enough to overlap with general docs, search, and lookup skills, so it sits at the somewhat-specific-but-overlapping anchor.	3 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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-workflow-jit-docs/SKILL.md
Commit: 4100d87

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.