Official agent skill

Planetscale Best Practices Matrix

by planetscale in planetscale/skills

A concise feature matrix for deciding which PlanetScale safety, observability, and automation recommendations apply by engine.

OfficialMITAuto-check passedDevOps & Cloud

Install Planetscale Best Practices Matrix

skills CLI
$ npx skills add planetscale/skills --skill planetscale-best-practices-matrix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install planetscale/skills planetscale-best-practices-matrix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/planetscale/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/planetscale-best-practices-matrix .claude/skills/planetscale-best-practices-matrix && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
planetscale-best-practices-matrix
GitHub stars
133
Token cost
~1.4k tokens
SKILL.md length
659 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

A concise feature matrix for deciding which PlanetScale safety, observability, and automation recommendations apply by engine.

  • Tasks that involve Observability
  • SKILL.md covers Purpose, Cross-engine recommendations, Vitess-specific recommendations and Postgres-specific…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Database administration

What it does

Planetscale Best Practices Matrix is an agent skill from planetscale/skills, published by the product's own GitHub organization. A concise feature matrix for deciding which PlanetScale safety, observability, and automation recommendations apply by engine.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Observability and Database administration. It works with PlanetScale and Model Context Protocol. The repository describes itself as: Skills that help you configure and get the most out of PlanetScale. The licence is MIT.

When your agent uses it

  • Tasks that involve Observability
  • Tasks that involve Database administration

Example prompts

  • “/planetscale-best-practices-matrix”

What it can do on your machine

Read from SKILL.md and the folder at commit 999045c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Planetscale Best Practices Matrix loads about 1.4k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 659 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from planetscale/skills at commit 999045c, republished under its MIT licence (© planetscale). 659 words, ~1,404 tokens.

Download SKILL.mdSave it as .claude/skills/planetscale-best-practices-matrix/SKILL.md (or your agent's skills folder).
name
planetscale-best-practices-matrix
description
A concise feature matrix for deciding which PlanetScale safety, observability, and automation recommendations apply by engine.

Best-practices matrix

Purpose

Map database findings to recommended PlanetScale features. Use this to ensure the assessment does not miss major safety and operational surfaces.

Cross-engine recommendations

Query Insights

Recommend for every production database:

  • Review slow, expensive, high-frequency, and erroring query patterns.
  • For Postgres, sort Insights by CPU (sort=cpuTime on the Insights API) when diagnosing CPU pressure.
  • For sharded Vitess, review vindex usage per query pattern and the usage trend after index or routing changes.
  • Correlate regressions with deploys.
  • Use tags/comments to map queries back to code.
  • Use tag filtering/navigation in Query Insights: the tags API (insights/tags, insights/tags/summaries) on both engines, plus tag:key:value filtering and per-execution tag drill-down in the Vitess dashboard.
  • Use anomalies as alert and automation inputs.
Webhooks

Recommend for operational events:

  • Anomalies.
  • Storage pressure.
  • Branch readiness/sleeping.
  • Primary promotion.
  • Maintenance.
  • Schema recommendations where available.
  • Deploy request lifecycle for Vitess.
MCP and agents

Recommend:

  • Use insights-only MCP for most autonomous analysis.
  • Use full MCP only with narrow scopes and read-only default.
  • Put database targeting and safety rules in AGENTS.md.
  • Agents generate PRs/issues/change plans; humans approve database changes.
SQLCommenter / query tags

Recommend:

  • Add framework-native SQLCommenter-compatible instrumentation.
  • Use low-cardinality tags.
  • Include application, service, route/job, feature, source, and release SHA.
  • Avoid PII and unbounded IDs.
Schema recommendation workflow

Recommend:

  • Triage open recommendations.
  • Correlate with code and Insights.
  • Convert into migrations or branch changes.
  • Test before production.
  • Apply only through approved workflow.

Vitess-specific recommendations

Safe migrations

Recommend for production branches and staging branches that accept deploy requests.

Deploy requests

Recommend for schema changes into protected branches.

Force cutover discipline

Recommend documenting who may use "force cutover now" for deploy requests delayed by long-running transactions. It stops running transactions to finish schema cutover, so frequent use should trigger workload review before enabling aggressive cutover as the database default.

Admin approval

Recommend for production deploy requests in multi-admin organizations.

In a single-admin organization, approval alone is not a guard against agents: that admin can open and approve the same deploy request. Prefer a separate agent identity, or a service token that cannot approve deploy requests.

Gated deployments

Recommend when cutover timing and human control matter.

Schema revert runbook

Recommend documenting revert responsibilities and the application rollback relationship.

Branch strategy

Recommend production, staging, and short-lived development branches with safe migrations on protected targets.

Sharding/keyspace review

Recommend when query patterns or growth suggest shard-awareness problems. Do not reshard automatically.

Postgres-specific recommendations

Show full SKILL.md (266 more words)Show less
User-defined roles

Recommend for application servers instead of default role. If roles are managed by Terraform and passwords should stay outside Terraform state, prefer planetscale_postgres_redacted_branch_role plus a separate password reset and secret-manager storage path.

pg_strict

Recommend for application roles after evaluation, especially to block accidental full-table update/delete mistakes.

Traffic Control

Recommend for resource isolation of agents, exports, reports, workers, integrations, BI, and known expensive fingerprints.

Backups and PITR

Recommend verifying retention and restore drill coverage. If Terraform is the customer's source of truth, recommend managing backup policies there so backup posture changes are reviewed as infrastructure code.

PgBouncer and connection pooling

Recommend where connection churn or serverless/edge behavior creates pressure, subject to transaction-pooling limitations.

Private connectivity and IP restrictions

Recommend for customers requiring private network posture or reduced public exposure. Treat changes as production-risking.

Extensions

Recommend only when use case is clear and restart/activation impact is accepted. Include auto_explain when automatic plan logging for slow queries would materially improve diagnosis and the resulting log volume is acceptable. If Terraform manages Postgres branch parameters or supported extensions, keep that source of truth aligned with approved dashboard/API changes.

Live connections

Recommend inspecting pscale branch connections top during active connection pressure incidents to identify sessions, blockers, and idle-in-transaction roots without relying on normal database connection capacity.

Output

For each matrix item, mark:

  • Applies: yes/no/unknown.
  • Current state.
  • Gap.
  • Value: the specific measured finding this feature addresses (query fingerprint, anomaly count, incident, metric). State the mechanism and the measurement. Gaps are capability gaps with quantified impact, not risks safely avoided.
  • Recommendation ID.
  • Approval requirement.

End with:

“No changes have been applied.”

© planetscale, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in planetscale-best-practices-matrix of planetscale/skills.

Open the folder on GitHubat commit 999045c

Compare with similar skills

Planetscale Best Practices Matrix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Planetscale Best Practices Matrix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Planetscale Best Practices Matrix this skillplanetscale/skills133—~1.4kAutomated safety check: PassMIT
UModel Root Cause Analysisalibaba/UnifiedModel412—~1.9kAutomated safety check: PassCustom licence
Observability Triageevery-app/open-seo23k—~1.7kAutomated safety check: PassMIT
Agentmeasureroy-tong/AgentMeasure218—~753Automated safety check: PassMIT
Logging Observabilitygetsentry/toolkit917—~2.6kAutomated safety check: PassCustom licence
AWS Cost Operationszxkane/aws-skills3671 repos~2.4kAutomated safety check: PassMIT

Similar skills

  • UModel Root Cause Analysis

    alibaba/UnifiedModel

    Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.

    412 GitHub stars~1.9k tokensUpdated 14 days ago
    DevOps & CloudAuto-check passed
  • Observability Triage

    every-app/open-seo

    Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, and a known-noise filter list applied automatically.

    23k GitHub stars~1.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Agentmeasure

    roy-tong/AgentMeasure

    Check whether agent telemetry preserves measurement semantics.

    218 GitHub stars~753 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Logging Observability

    getsentry/toolkit

    Official

    Review code for correct logging and error handling patterns.

    917 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • AWS Cost Operations

    zxkane/aws-skills

    AWS cost optimization, monitoring, and operational excellence expert.

    367 GitHub starsUsed in 1 repo~2.4k tokens
    DevOps & CloudAuto-check passed
  • Deploy Observability

    aliyun/alibabacloud-observability-mcp-server

    Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).

    166 GitHub stars~2.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes

More from planetscale/skills

All 15 skills in this repo
  • Official

    Use the PlanetScale CLI (pscale) from automated agents with --format json, auth check, pscale sql, and per-command --force.

    133 GitHub stars~880 tokensUpdated yesterday
    Auto-check passed
  • Official

    Master skill that runs the full PlanetScale safe best-practices assessment — inventory, engine review, Insights, Traffic Control, webhooks, schema recommendations, codebase instrumentation, and…

    133 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Official

    Execute approved PlanetScale changes end-to-end without per-step approval when the operator has explicitly acknowledged the risk.

    133 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed
  • Enforce explicit approval gates for any PlanetScale, database, repository, credential, network, or automation mutation.

    133 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Inspect an application repository connected to PlanetScale and recommend SQLCommenter-compatible query tagging packages and conventions.

    133 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Official

    Produce the final PlanetScale best-practices report after running the inventory and relevant review skills.

    133 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Planetscale Best Practices Matrix

What does Planetscale Best Practices Matrix do?

A concise feature matrix for deciding which PlanetScale safety, observability, and automation recommendations apply by engine. Planetscale Best Practices Matrix is an agent skill from planetscale/skills, published by the product's own GitHub organization. A concise feature matrix for deciding which PlanetScale safety, observability, and automation recommendations apply by engine.

When should I use Planetscale Best Practices Matrix?

Planetscale Best Practices Matrix fits situations like: tasks that involve Observability; tasks that involve Database administration.

How do I install Planetscale Best Practices Matrix in Claude Code?

Run `npx skills add planetscale/skills --skill planetscale-best-practices-matrix -a claude-code`. Or copy the skill folder (planetscale-best-practices-matrix in planetscale/skills) into .claude/skills/planetscale-best-practices-matrix in your project. Claude Code loads it when a task matches its description.

How do I install Planetscale Best Practices Matrix in Codex?

Run `npx skills add planetscale/skills --skill planetscale-best-practices-matrix -a codex`. Or copy the skill folder (planetscale-best-practices-matrix in planetscale/skills) into .agents/skills/planetscale-best-practices-matrix in your project. Codex loads it when a task matches its description.

Can I use Planetscale Best Practices Matrix in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add planetscale/skills --skill planetscale-best-practices-matrix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planetscale-best-practices-matrix, .gemini/skills/planetscale-best-practices-matrix, .github/skills/planetscale-best-practices-matrix and .opencode/skills/planetscale-best-practices-matrix in your project.

What does Planetscale Best Practices Matrix need to run?

SKILL.md names no scripts, command-line tools or credentials: Planetscale Best Practices Matrix is instructions for the agent only.

Does Planetscale Best Practices Matrix access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Planetscale Best Practices Matrix safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Planetscale Best Practices Matrix use?

Planetscale Best Practices Matrix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Planetscale Best Practices Matrix use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Planetscale Best Practices Matrix?

Skills that share tags, products or a category with Planetscale Best Practices Matrix: UModel Root Cause Analysis (alibaba/UnifiedModel, 412 stars), Observability Triage (every-app/open-seo, 23k stars), Agentmeasure (roy-tong/AgentMeasure, 218 stars) and Logging Observability (getsentry/toolkit, 917 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Planetscale Best Practices Matrix?

planetscale (a GitHub organization, an official publisher) maintains it in planetscale/skills, which has 133 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: planetscale/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.