About platform-database
platform-database is a skill for database-related tasks. It helps agents identify when its guidance applies, follow the referenced rules, and validate actionable results, with schema and migration reviews as an example.
Key features
- 01Identify database-task triggers
- 02Apply guidance from the rules index
- 03Follow the workflow and validate results
Use cases
- 01Review a database schema and migration plan
- 02Troubleshoot missed triggers or conflicting guidance
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/platform-databasein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
rules/_sections.mdindex-concurrent-creation.mdindex-covering-queries.mdindex-foreign-keys.mdmigration-add-columns-safely.mdmigration-forward-only.mdmigration-one-change.mdmigration-review-generated-sql.mdmigration-separate-data-schema.mdquery-avoid-functions-on-indexed.mdquery-avoid-leading-wildcards.mdquery-filter-early.mdquery-n-plus-one.mdquery-prefer-exists-over-in.mdquery-select-columns.mdquery-use-explain.mdschema-timestamps.mdschema-use-appropriate-types.mdtransaction-keep-short.mdtransaction-wrap-related-mutations.mdDetails
From the project READMEPrinciples
- Prefer UNION ALL over UNION unless you specifically need deduplication
Rules
See rules index for detailed patterns.
Examples
Positive Trigger
User: "Review this schema and migration plan for zero-downtime rollout."
Expected behavior: Use platform-database guidance, follow its workflow, and return actionable output.
Non-Trigger
User: "Implement ARIA labels and focus rings on this modal."
Expected behavior: Do not prioritize platform-database; choose a more relevant skill or proceed without it.
Troubleshooting
Skill Does Not Trigger
- Error: The skill is not selected when expected.
- Cause: Request wording does not clearly match the description trigger conditions.
- Solution: Rephrase with explicit domain/task keywords from the description and retry.
Guidance Conflicts With Another Skill
- Error: Instructions from multiple skills conflict in one task.
- Cause: Overlapping scope across loaded skills.
- Solution: State which skill is authoritative for the current step and apply that workflow first.
Output Is Too Generic
- Error: Result lacks concrete, actionable detail.
- Cause: Task input omitted context, constraints, or target format.
- Solution: Add specific constraints (environment, scope, format, success criteria) and rerun.
Workflow
- Identify whether the request clearly matches
platform-databasescope and triggers. - Apply the skill rules and referenced guidance to produce a concrete result.
- Validate output quality against constraints; if gaps remain, refine once with explicit assumptions.