跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 planetscale-vitess-safety-review

Planetscale Vitess Safety Review

审查一个行星表 用于安全迁移、部署请求、计划建议、洞察、网络搜索和操作安全的视频数据库.

1068 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

审查一个行星表 用于安全迁移、部署请求、计划建议、洞察、网络搜索和操作安全的视频数据库.

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Vitess safety review、Purpose、Primary safety features to evaluate、Safe migrations、Deploy requests、Schema revert。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Review a PlanetScale Vitess database for safe migrations, deploy requests, schema recommendations, Insights, webhooks, and operational safety.

Vitess safety reviewPurposePrimary safety features to evaluateSafe migrationsDeploy requestsSchema revertBranch strategyQuery InsightsAnomaliesSchema recommendationsBackups and restoreSharding and keyspace safety

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
planetscale-vitess-safety-review
description
Review a PlanetScale Vitess database for safe migrations, deploy requests, schema recommendations, Insights, webhooks, and operational safety.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「planetscale-vitess-safety-review」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-f86afc9b41653add-%E8%A1%8C%E6%98%9F%E7%BA%A7%E7%97%85%E6%AF%92%E5%AE%89%E5%85%A8%E5%AE%A1%E6%9F%A5.html
请存为 .cursor/skills/planetscale-vitess-safety-review/SKILL.md 或 .claude/skills/planetscale-vitess-safety-review/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/planetscale/skills' --list

npx skills add 'https://github.com/planetscale/skills' --skill 'planetscale-vitess-safety-review'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: planetscale-vitess-safety-review description: Review a PlanetScale Vitess database for safe migrations, deploy requests, schema recommendations, Insights, webhooks, and operational safety.

Vitess safety review

Purpose

Recommend best practices for a PlanetScale Vitess database. Focus on production safety, deployability, observability, and agent-safe automation. Do not apply any changes.

Primary safety features to evaluate

Safe migrations

Check whether safe migrations are enabled on production and staging branches.

Recommend enabling safe migrations when:

  • The branch receives production traffic.
  • The team runs DDL outside deploy requests.
  • There is no protected branch workflow.
  • The application is expected to evolve schema frequently.

Explain the tradeoff: safe migrations reject direct DDL on protected branches and force schema changes through deploy requests. That is a feature, but it can break teams relying on direct production DDL. Treat enablement as a behavior-changing change requiring approval.

Deploy requests

Check:

  • Whether deploy requests are used for schema changes.
  • Whether administrator approval is required.
  • Whether deploy requests are reviewed for data loss, conflicts, lint errors, foreign key problems, charset issues, and shard impact.
  • Whether teams use gated deployments for cutover control.
  • Whether “deploy instantly” is used and whether the team understands it removes the gated-deployment/revert shape.
  • Whether cutover is regularly delayed by long-running transactions.
  • Whether deploy request events are subscribed to via webhooks.

Recommend:

  • Require deploy requests for production schema changes.
  • Enable administrator approval for production deploy requests when there is more than one administrator.
  • In a single-admin organization, administrator approval does not stop an agent that acts as that admin: the admin who opens a deploy request can also approve it. If the goal is to keep agents from self-approving, give the agent a separate user, or a service token without deploy request approval permission.
  • Prefer normal safe deployments over instant deployments unless the migration is known to be instant-safe and the rollback story is acceptable.
  • Use gated deployment when cutover timing matters.
  • Treat “force cutover now” as an operator-controlled action for delayed cutovers: it aggressively stops running transactions to complete schema cutover. Recommend reviewing the blocking workload and incident context before use, and only recommend the database-level aggressive cutover default when frequent cutover blocking is understood and accepted.

Schema revert

Check whether the team knows the revert window and whether their incident runbook includes it.

Recommend documenting:

  • How to identify a bad schema migration.
  • How to revert within the supported window.
  • Who is authorized to revert.
  • Which application deploy should be rolled back together with the schema revert.

Branch strategy

Recommend a branch topology:

  • main or equivalent production branch with safe migrations enabled.
  • staging branch based from production with safe migrations enabled.
  • Short-lived development branches based from staging.
  • Deploy requests from development to staging, then staging to production when appropriate.

Do not create branches without approval.

Query Insights

Review Insights for:

  • Slow queries.
  • Queries reading too many rows.
  • Erroring queries.
  • Queries with poor index usage.
  • For sharded databases, whether query patterns use relevant vindexes and how vindex usage changes after index or routing changes.
  • Unusual query volume.
  • Missing SQL comment tags.
  • Tag breakdowns when built-in metadata or SQLCommenter tags are present: tag:key:value filtering in the dashboard, and the insights/tags and insights/tags/summaries API endpoints for programmatic breakdowns.
  • Deploy correlation data.

Recommend enabling or improving application query tagging so Insights can attribute queries to app, route, controller, action, job, deployment SHA, and feature.

Anomalies

Review active and recent anomalies.

Recommend:

  • Subscribe branch.anomaly webhooks to the team’s alerting or automation system.
  • Route anomaly payloads to a triage workflow that opens an issue or agent task.
  • Correlate anomalies with deploy requests, application deploys, and query tags.
  • Do not automatically apply schema or code changes from anomaly events; generate a proposal or PR only.

Schema recommendations

Review open schema recommendations.

For each recommendation, capture:

  • Type: add index, remove redundant index, primary key exhaustion, unused table, legacy charset/collation, or other.
  • Affected table and keyspace.
  • Supporting query telemetry.
  • DDL.
  • Expected benefit.
  • Risk.
  • Test plan.

Recommend implementation path:

  • Convert the recommendation into an application migration or PlanetScale branch schema change.
  • Open a deploy request.
  • Review generated DDL and shard impact.
  • Benchmark or validate on a branch.
  • Deploy with safe migrations.
  • Monitor Insights and anomaly state after deployment.

Do not apply recommendations directly.

Backups and restore

Check backup posture and restore runbooks.

Recommend:

  • Verify automated backups exist.
  • Run a non-production restore drill periodically.
  • Document restore target, RPO/RTO expectation, and application cutover plan.
  • For sharded databases, document shard-aware restore expectations.

Sharding and keyspace safety

If the database is sharded, review:

  • Keyspaces and shards.
  • Vschema.
  • Cross-shard query patterns.
  • Whether schema deploy requests show per-shard impact.
  • Whether queries use shard-friendly access paths.

Recommend an agent-safe sharding review only as a proposal. Never reshard, change vschema, or alter routing automatically.

Webhook recommendations for Vitess

Evaluate and recommend webhooks for:

  • branch.anomaly
  • branch.primary_promoted
  • branch.ready
  • branch.sleeping
  • cluster.storage
  • keyspace.storage
  • deploy_request.opened
  • deploy_request.queued
  • deploy_request.in_progress
  • deploy_request.pending_cutover
  • deploy_request.schema_applied
  • deploy_request.errored
  • deploy_request.reverted
  • deploy_request.closed
  • branch.schema_recommendation if available in the webhook API for the customer’s database

Recommended destinations:

  • Alerting for anomaly, primary promotion, storage, and deploy errors.
  • Slack or internal notifications for deploy request lifecycle.
  • Agent intake queue for schema recommendations and anomalies, with PR-only output by default.

Output

Return:

  • Current Vitess safety posture.
  • Missing safety features.
  • Recommended workflow.
  • Recommended webhook subscriptions.
  • Schema recommendation triage table.
  • Deploy safety gaps.
  • Proposed changes requiring approval.

End with:

“No Vitess changes have been applied.”

相关技能

运维与云

Docker Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…