CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-sync

Synchronize documentation, codemaps, and create pull request

Quality

70%

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 ./.agents/skills/moai-sync/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 maximally lean, unambiguous one-line delegation to the moai skill's sync command, which is ideal for token efficiency. Its weaknesses are the total absence of validation guidance for the batch doc-sync and PR-creation workflow it triggers, and the lack of any context about what "sync" does or accepts.

Suggestions

Add a brief line stating what `sync` does plus one example invocation with concrete arguments, e.g. `Skill("moai") with arguments: sync docs/ --dry-run`.

Include a verification step, e.g. "After sync, confirm the pull request was created and summarize the changed files for the user before finishing."

Add a minimal heading or one-line overview so the file has basic structure and signals what the delegation covers.

DimensionReasoningScore

Conciseness

The entire body is one line — "Use Skill(\"moai\") with arguments: sync $ARGUMENTS" — with zero padding, zero explanation of concepts Claude already knows, and nothing that could be trimmed; every token earns its place.

5 / 5

Actionability

The delegation directive is concrete and executable as written (exact skill name "moai", subcommand "sync", argument pass-through "$ARGUMENTS"), so it meets "concrete code or commands with minor gaps" (4). It falls short of 5 because no examples cover common cases — there is no sample invocation or indication of what arguments "sync" accepts or produces.

4 / 5

Workflow Clarity

The single action is unambiguous in form, but per the skill's own description it performs batch operations — "Synchronize documentation, codemaps, and create pull request" — and the body contains no validation or verification step anywhere. The rubric caps batch/destructive skills without validation at 3, and this cap explicitly takes precedence over the simple-skill exception.

3 / 5

Progressive Disclosure

The one-line body delegates to a single, clearly signaled target one level deep (Skill("moai")), and there is no bundle content to split — no references/, scripts/, or assets/ directories exist, so nothing is improperly inlined. It sits just below 5 because the file has no organizational structure at all: no heading, no overview line, and no indication of what "sync" covers.

4 / 5

Total

16

/

20

Passed

Description

50%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 names its domain and a couple of actions but never states when to use the skill, and "synchronize" leaves the core behavior vague, so every dimension lands at the midpoint. It is serviceable but risks both failing to trigger on natural phrasings ("open a PR for the docs") and conflicting with generic documentation-handling skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to regenerate or sync documentation or codemaps, or to open a pull request with documentation changes."

Concretize "synchronize" — state what actually happens, e.g. "regenerates docs and codemaps from the codebase and opens a pull request containing the changes."

Include natural synonyms users would say: "PR", "docs", "sync", "code map".

DimensionReasoningScore

Specificity

"Synchronize documentation, codemaps, and create pull request" names the domain (documentation, codemaps, PRs) and 1-2 actions ("synchronize", "create pull request"), matching the 1-2-concrete-actions anchor. It is not 4 because "synchronize" is generic, the mechanism is never specified, and there are not several distinct concrete actions; it is not 2 because "create pull request" is a concrete action beyond mere domain-naming.

3 / 5

Completeness

The "what" is stated ("Synchronize documentation, codemaps, and create pull request") though "synchronize" is vague, while the "when" is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the "what" includes the concrete "create pull request" rather than being wholly vague.

3 / 5

Trigger Term Quality

Relevant keywords exist ("pull request", "documentation") but common variations are missing: no "PR", "docs", or "sync", and "codemaps" is technical jargon rather than a phrase users naturally say. No trigger phrasing of any kind appears, so it fits "some relevant keywords but missing common variations or synonyms" (3) rather than "good keyword coverage" (4).

3 / 5

Distinctiveness Conflict Risk

The docs + codemaps + PR combination is somewhat niche, but "Synchronize documentation" broadly overlaps with documentation-generation and formatting skills, and with no trigger guidance, generic doc-update requests could route here incorrectly. This fits "somewhat specific but could still overlap with similar skills" (3); it lacks the distinct trigger phrases needed for 4.

3 / 5

Total

12

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

modu-ai/moai-adk

Path

.agents/skills/moai-sync/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.