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

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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 is well-organized as a comparison/decision overview with decent actionability via named packages and commands, but it lacks executable code, repeats material across sections, and critically points to reference files that are absent from the bundle.

Suggestions

Provide at least one minimal executable code block per platform (e.g. a Supabase createClient query or a Firestore initializeFirestore snippet) instead of only naming the packages in prose.

Either include the referenced reference/*.md files in the bundle or remove the deep-dive references and inline the essential details, since the pointers currently lead nowhere.

Consolidate the redundant feature/pricing mappings that appear in both Quick Reference and the Selection Matrix, and add an explicit validate-then-proceed step to the migration/branching workflows.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient comparison/decision content, but it restates platform descriptions Claude already knows (what Neon/Supabase/Firestore are) and repeats feature mappings across the Quick Reference, Selection Matrix, and Feature Comparison sections rather than consolidating, adding padding.	3 / 5
Actionability	It names packages, env vars, and CLI commands (e.g. @neondatabase/serverless, DATABASE_URL_POOLED, supabase migration new, firebase deploy --only firestore:rules) but presents them as prose descriptions rather than copy-paste executable code blocks, leaving the actual query/deploy steps incomplete.	3 / 5
Workflow Clarity	Decision guides and migration commands give a rough sequence, and there is a Verification checklist, but the database operations (schema push, branching, deploys) lack explicit validate-then-proceed feedback loops, so checkpoints are implicit rather than enforced.	3 / 5
Progressive Disclosure	The body repeatedly references reference/neon.md, reference/supabase.md, reference/firestore.md, and reference/comparison.md as the location of the real detail, but none of these bundle files exist in the skill, so the disclosure is signaled but unfulfilled and navigation is broken.	2 / 5
	Total	11 / 20 Passed

Description

62%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 cleanly identifies the three covered platforms and includes an explicit Use-when clause, giving it solid completeness and distinctiveness. Specificity and trigger-term quality are mid-range because the actions are generic and several natural trigger phrases are absent.

Suggestions

Replace generic verbs ('covering', 'choosing or setting up') with concrete actions such as provisioning databases, configuring branching, writing RLS policies, and setting up offline sync.

Add natural trigger phrases a user would actually say, e.g. 'Use when working with Neon, Supabase, or Firestore, or when choosing between SQL and NoSQL cloud databases'.

Mention key feature terms (pgvector, Row-Level Security, database branching, real-time subscriptions) so the description surfaces for those specific needs.

Dimension	Reasoning	Score
Specificity	Names the three concrete platforms and their distinguishing characteristics (serverless PostgreSQL, real-time, NoSQL with offline sync), but the only stated actions are 'covering' and 'choosing or setting up' — generic rather than enumerating specific operations like provisioning, branching, or RLS policy creation.	3 / 5
Completeness	Provides a clear 'what' (specialist covering the three named platforms with their capabilities) and an explicit 'when' clause ('Use when choosing or setting up cloud databases'); the 'when' is present but somewhat broad rather than tied to specific trigger phrases.	4 / 5
Trigger Term Quality	Includes natural product names (Neon, Supabase, Firestore) and several terms users say (cloud database, serverless postgresql, offline sync), but the description itself omits common variations such as 'postgres', 'vector database', 'RLS', or file/context cues a user would naturally voice.	3 / 5
Distinctiveness Conflict Risk	The three named platforms plus the cloud-database framing carve a clear niche that is distinguishable from sibling skills (auth, language, domain skills), though the generic 'choosing or setting up' could lightly overlap with a general backend skill.	4 / 5
	Total	14 / 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-platform-database-cloud/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.