CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-platform-deployment

Deployment and hosting platform specialist covering Vercel, Railway, and Convex. Use when deploying applications, configuring edge functions, setting up continuous deployment, or managing serverless infrastructure.

Quality

69%

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/v2.16/moai-platform-deployment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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-organized, largely executable reference with strong code examples and a useful verification checklist. Its weaknesses are generic uncommanded workflow steps without inline validation, inlined platform deep-dives, broken reference/ pointers, and internal bookkeeping (refactor notes, duplicated metadata) that wastes context. Fixing the reference files and adding per-step commands would lift it substantially.

Suggestions

Create the referenced reference/vercel.md, reference/railway.md, reference/convex.md, and reference/comparison.md files (or remove the links) so the clearly signaled pointers actually resolve.

Add concrete commands or config snippets to the numbered pattern steps (e.g. 'Configure environment variables' should show the vercel env add command) and embed validation checkpoints such as healthcheck verification after each deploy step.

Delete the internal-bookkeeping sections (Refactor Notes with SPEC/audit references and the duplicated status/version footer) to reclaim context tokens.

DimensionReasoningScore

Conciseness

The body is dense and code-heavy with little conceptual padding, but it carries unnecessary tokens: the 'Refactor Notes' section (SPEC-V3R2-WF-001 references, R4 audit verdict), a duplicated status/version footer, and date-stamped metadata none of which help execution. This fits anchor 3 (mostly efficient but could be tightened) rather than 4, where only minor trimmable instances remain.

3 / 5

Actionability

Concrete, executable artifacts abound: vercel.json, an edge function, railway.toml, a multi-stage Dockerfile, a Convex schema, React integration, and three GitHub Actions workflows. It stops short of anchor 5 because some sections are prose-only directions, e.g. Blue-Green Deployment ('switch production alias using Vercel SDK') with no code or command, and the multi-region TOML snippet is partial.

4 / 5

Workflow Clarity

The five deployment patterns list numbered steps, but the steps are generic directives ('Configure environment variables', 'Set up private networking') with no commands, and validation only appears in a decoupled end-of-file checklist rather than as inline checkpoints. This matches anchor 3 (steps listed, validation gaps, checkpoints missing or implicit) rather than 4, whose example embeds a command in each step.

3 / 5

Progressive Disclosure

Sections are well organized and the four 'reference/*.md' pointers are clearly signaled with descriptions, but those files do not exist in the bundle, so navigation dead-ends. Meanwhile platform deep-dives that the skill's own refactor notes say should live in Level-3 modules remain inline. This lands on anchor 3 (some structure, content that should be separate is inline) rather than 4, since the references are non-functional.

3 / 5

Total

13

/

20

Passed

Description

70%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 solid description with an explicit, concrete 'Use when' clause and distinct platform-specific triggers. Its main weakness is the what-side: 'specialist covering' names the domain but never states the skill's concrete capabilities. Voice is correctly third person and length is appropriately concise.

Suggestions

Replace 'Deployment and hosting platform specialist covering...' with concrete third-person action verbs, e.g. 'Deploys applications to Vercel, Railway, and Convex; configures edge functions, CI/CD pipelines, and serverless infrastructure.'

Add a few high-frequency natural trigger terms such as 'docker', 'containers', or 'CI/CD' to broaden keyword coverage.

DimensionReasoningScore

Specificity

The what-clause 'Deployment and hosting platform specialist covering Vercel, Railway, and Convex' names the domain but contains no action verbs; the only concrete actions ('deploying applications, configuring edge functions, setting up continuous deployment, managing serverless infrastructure') appear in the when-clause. This matches anchor 3 (domain plus limited concrete actions) rather than 4, whose examples list several specific capability verbs on the what side.

3 / 5

Completeness

Both parts are present and the 'Use when...' clause is explicit with concrete triggers. It is not anchor 5 because the 'what' is a domain label ('specialist covering...') rather than an explicit list of what the skill actually does, unlike the anchor-5 example's 'Extract text and tables..., fill forms, merge documents'.

4 / 5

Trigger Term Quality

Natural phrases like 'deploying applications', 'hosting', 'edge functions', 'continuous deployment', and 'serverless infrastructure' plus the three platform names give good keyword coverage. It falls short of anchor 5 because common variations such as 'docker', 'containers', 'CI/CD', and 'pipeline' are absent.

4 / 5

Distinctiveness Conflict Risk

Naming Vercel, Railway, and Convex carves out a mostly distinct niche with clear trigger terms. It stays at 4 rather than 5 because 'deployment and hosting' is a broad category that could overlap with closely related platform skills (e.g., database or auth platform specialists).

4 / 5

Total

15

/

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/v2.16/moai-platform-deployment/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.