CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-platform-database-cloud

Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.

Quality

65%

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-platform-database-cloud/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 works well as a platform-selection decision guide with accurate, specific comparisons, but it under-delivers on execution: no runnable code examples, no sequenced workflows with validation for database operations, and a progressive-disclosure structure pointing at reference files that are missing from the bundle. It reads as the level-1 summary of a modular skill whose levels 2+ were never shipped.

Suggestions

Ship the four referenced files (references/neon.md, supabase.md, firestore.md, comparison.md) or delete the 'Platform-Specific Deep Dives' section — every pointer is currently a dead path.

Add one minimal executable snippet per platform for the connection pattern (e.g. a 3-line @neondatabase/serverless query and a createClient call), and sequence the migration section as numbered steps ending in a verification command.

Collapse the Quick Decision Guide / Database Type Selection / Use Case Alignment overlap into a single mapping, and move volatile free-tier pricing and version numbers into a reference file so they can be updated without touching the overview.

DimensionReasoningScore

Conciseness

The body is mostly tight bullet-style facts, but there is real redundancy: the 'Quick Decision Guide', 'Database Type Selection', and 'Use Case Alignment' sections repeat the same platform-to-need mapping three times. It also inlines time-sensitive details ('PostgreSQL 16', free-tier storage/MAU/limits pricing) that will go stale, and a footer of factory metadata ('Generated with: MoAI-ADK Skill Factory v2.0', 'Status: Production Ready') that earns no tokens. Not 2 because the prose never explains concepts Claude already knows; not 4 because the repeated decision lists and volatile pricing could clearly be trimmed or moved.

3 / 5

Actionability

There is genuinely concrete guidance — exact package names ('@neondatabase/serverless', 'drizzle-orm/neon-http'), env vars (DATABASE_URL_POOLED, SUPABASE_SERVICE_ROLE_KEY), and real commands ('supabase migration new', 'supabase db push', 'firebase deploy --only firestore:rules'). But large stretches ('Neon provides serverless PostgreSQL with auto-scaling...', the feature and pricing matrices) describe the platforms rather than instruct, and no complete, copy-paste example exists for even the connection-setup patterns. Not 4 because the core patterns stop at naming functions rather than showing how to call them.

3 / 5

Workflow Clarity

The selection flow (need → platform) is clear, but the operational content — migration strategy, rules deployment, branching/resets — is presented as parallel one-line command hints with no sequence and no validation checkpoints, and the rubric explicitly caps database-operation workflows without feedback loops at 3. Not 2 because the decision guide and per-platform command lists do give a usable rough sequence; not 4 because no step says how to verify a migration or deploy succeeded.

3 / 5

Progressive Disclosure

The body's structure is right — an overview with clearly signaled one-level-deep pointers ('Neon Serverless PostgreSQL at reference/neon.md', 'reference/supabase.md', 'reference/firestore.md', 'reference/comparison.md') — but the bundle contains no references/ directory at all, so every deep-dive pointer is dead and the promised detail is unreachable (the paths also say 'reference/' while the convention is 'references/'). Not 3 because 'references present but not clearly signaled' is a lesser failure; here the navigation claims content that does not exist, which is structurally worse than inlining would have been.

2 / 5

Total

11

/

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 'Use when' clause, third-person voice, and strong natural trigger terms anchored by three concrete product names. Its main weakness is that it states coverage rather than concrete actions, leaving the reader to infer what the skill actually does.

Suggestions

Replace 'specialist covering...' with concrete verbs, e.g. 'Compare, select, set up, and configure cloud databases: Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync).'

Expand the 'when' clause with explicit trigger moments: 'Use when choosing or setting up cloud databases, or when the user mentions Neon, Supabase, or Firestore.'

DimensionReasoningScore

Specificity

The description names the domain concretely — 'Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync)' — with platform-specific capabilities, but the actions are minimal: 'covering' and 'choosing or setting up' describe scope rather than concrete things the skill does. It fits anchor 3 (domain named, weak on concrete actions) better than anchor 4 (several specific actions listed) and is clearly above anchor 2, which expects only a generic domain name.

3 / 5

Completeness

Both parts are present: the 'what' ('Cloud database platform specialist covering Neon... Supabase... Firestore') and the 'when' ('Use when choosing or setting up cloud databases'). Not 5 because the 'when' clause is a single broad condition — it does not enumerate explicit trigger moments like 'when the user mentions Supabase, Neon, or Firestore'; not 3 because 'when' is explicit, not merely implied.

4 / 5

Trigger Term Quality

Natural trigger terms are strong: users would literally say 'Neon', 'Supabase', 'Firestore', 'PostgreSQL', 'serverless', 'NoSQL', 'real-time', 'offline sync', and 'cloud databases'. Not anchor 5 because common phrasings like 'which database should I use', 'set up Postgres', or product-name variants are not covered; clearly above anchor 3, which expects missing synonyms.

4 / 5

Distinctiveness Conflict Risk

The three named platforms give it a clear niche that most database-adjacent skills would not collide with. Not 5 because the broad trigger 'choosing or setting up cloud databases' could overlap with a general PostgreSQL, ORM, or backend-data skill; well above anchor 3, since the platform names sharply delimit the space.

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/v3.0/moai-platform-database-cloud/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.