Evolving The Data Model
TriliumNext/Trilium
A skill your agent uses when adding a DB migration or a new column/field to a Becca entity in Trilium ("add a migration", "new column on notes/attributes", "ALTER TABLE", "add a field to…
Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps…
Install Release DB Config Sync
$ npx skills add Prismer-AI/PrismerCloud --skill release-db-config-sync -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-db-config-sync --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sdk/apc/skills/release-db-config-sync .claude/skills/release-db-config-sync && rm -rf skills-srcUse ~/.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/
Install the "release-db-config-sync" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-db-config-sync into .claude/skills/release-db-config-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-db-config-sync", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-db-config-syncType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Prismer-AI/PrismerCloud --skill release-db-config-sync -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-db-config-sync --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sdk/apc/skills/release-db-config-sync .agents/skills/release-db-config-sync && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-db-config-sync" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-db-config-sync into .agents/skills/release-db-config-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-db-config-sync", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Prismer-AI/PrismerCloud --skill release-db-config-sync -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-db-config-sync --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sdk/apc/skills/release-db-config-sync .cursor/skills/release-db-config-sync && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-db-config-sync" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-db-config-sync into .cursor/skills/release-db-config-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-db-config-sync", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Prismer-AI/PrismerCloud.git --path sdk/apc/skills/release-db-config-sync--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Prismer-AI/PrismerCloud --skill release-db-config-sync -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-db-config-sync --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sdk/apc/skills/release-db-config-sync .gemini/skills/release-db-config-sync && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-db-config-sync" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-db-config-sync into .gemini/skills/release-db-config-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-db-config-sync", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Prismer-AI/PrismerCloud release-db-config-syncInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Prismer-AI/PrismerCloud --skill release-db-config-sync -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .github/skills && cp -r skills-src/sdk/apc/skills/release-db-config-sync .github/skills/release-db-config-sync && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-db-config-sync" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-db-config-sync into .github/skills/release-db-config-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-db-config-sync", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Prismer-AI/PrismerCloud --skill release-db-config-sync -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Prismer-AI/PrismerCloud release-db-config-sync --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sdk/apc/skills/release-db-config-sync .opencode/skills/release-db-config-sync && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-db-config-sync" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/release-db-config-sync into .opencode/skills/release-db-config-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-db-config-sync", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-db-config-sync- GitHub stars
- 1.6k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 603 words
- Files
- 2
- Skills in repo
- 88
- Repo updated
- First seen
- Licence
- MIT
At a glance
Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps…
- Works in 2 steps: 跑迁移 dry-run + key-diff → 按 decision 分流
- Tasks that involve Database migrations
- SKILL.md covers 承重纪律（先记死）, Anti-pattern（直接判红）, 工具契约（签名以此为准） and Workflow, plus 7 more sections
- Calls npx; needs REMOTE_MYSQL_PASSWORD
What it does
Release DB Config Sync is an agent skill from Prismer-AI/PrismerCloud. Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps, stopping at the write boundary. green(0) no diff · staged(3) pending migrations/missing keys await approval · blocked(1) real script failed. Diff only, never writes the remote.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.json`). Compatibility notes: ["claude-code"]
It sits in Databases, covering Database migrations. The licence is MIT.
When your agent uses it
- Tasks that involve Database migrations
Example prompts
- “/release-db-config-sync”
Requirements
- Node.js
- Compatibility (from SKILL.md): ["claude-code"]
- Pre-approved tools (allowed-tools): Bash
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e5d9444. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
REMOTE_MYSQL_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
["claude-code"]
From compatibility in the SKILL.md frontmatter.
Context cost
Release DB Config Sync loads about 2.1k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 603 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash
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 Prismer-AI/PrismerCloud at commit e5d9444, republished under its MIT licence (© Prismer-AI). 603 words, ~2,088 tokens.
Download SKILL.mdSave it as
.claude/skills/release-db-config-sync/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- release-db-config-sync
- description
- Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps, stopping at the write boundary. green(0) no diff · staged(3) pending migrations/missing keys await approval · blocked(1) real script failed. Diff only, never writes the remote.
- allowed-tools
- Bash
- compatibility
- ["claude-code"]
- license
- MIT
- scope
- coding
- metadata.category
- release
release-db-config-sync
发版前算清远端 DB 迁移与 Nacos 配置的差异（apc/01 §2 db-config-sync，收口步 3/4）。这是治 R3（"DB sync 走桩、writes:0 换马甲冒充已同步"）的真机制：它真 spawn scripts/ops/sync-test-migrations.ts --dry-run——真解析凭证、真连库、真算迁移计划——退出码由真脚本决定，绝不注入桩。Nacos 侧对两份 key dump 算真差集。dry-run 永不写库、不写真 Nacos——止于写入边界，真 apply 走审批后的远端路径。
什么时候用：release-preflight 绿之后、release-tag 之前，确认远端 test 环境的迁移账本和配置 key 都对齐了才发版。
承重纪律（先记死）
- 事故红线（memory /
apc/01开头）：prod 曾因 Navicat 结构 diff 绕过迁移账本灌库出事故（丢回填 / 半应用）。一切 DB sync 必须走账本，diff 工具只做审计不做写入。 本 skill 就是账本路径的收口——绝不教你拿 Navicat / 裸 SQL 去改远端。 - 本 skill 只 dry-run：算差异、出计划、停在写入边界。真 apply（把 pending 迁移打进 test RDS、把缺失 key 补进 Nacos）是审批后的远端动作（本机替身口径下 = M5），不由本 skill 执行。
- 别把桩当验过：本机替身下 Nacos fetch 未接线时，key-diff 会诚实标
skipped（真路径 = M5）。看到skipped就照实报 ⬜，别写成"配置已核对无差异"。
Anti-pattern（直接判红）
- ❌ 迁移 dry-run 报
blocked（真脚本失败 / 缺凭证）时，改用别的路径灌库绕过去。真脚本 exit 非 0 = 连不上 / 缺REMOTE_MYSQL_*，是要修的前置，不是要绕的门。 - ❌ 有 pending 迁移（
staged）就当没事发版。staged（exit 3）意味着远端账本落后，未审批 apply 前不该 tag。 - ❌ key-diff
skipped说成"已核对"。没给 dump 文件就是没比，别冒充。
工具契约（签名以此为准）
apc不在 PATH——在仓库根用npx tsx sdk/apc/bin/apc.ts <sub>。
| 命令 | 作用 | 退出码 |
|---|---|---|
npx tsx sdk/apc/bin/apc.ts release db-config-sync [--ref <dump>] [--cur <dump>] [--json] | 真跑 sync-test-migrations.ts --dry-run（本机替身指向本地 replica，永不写远端）+ 对两份 Nacos dump 算 key 差集 | 0 green（无差异）· 3 staged（有 pending / 缺 key）· 1 blocked（真脚本失败 / 缺凭证） |
--json 字段（名以此为准）：
- 顶层：
{ verb:'db-config-sync', decision, migration, keyDiff, blockers:[], staged:[] } migration：{ exitCode, pending:[<sql文件名>], stderr }（exitCode是真脚本退出码；pending是真脚本 fs 枚举 ⇄_migrations账本比对得出的待同步迁移）keyDiff：{ status:'skipped', reason }或{ status:'computed', missing:[], extra:[], common }（missing= 目标环境缺的 key，需补齐；extra不阻塞，仅报告）
Workflow
1. 跑迁移 dry-run + key-diff
# 只算迁移（不给 dump 时 key-diff 诚实 skipped）：
npx tsx sdk/apc/bin/apc.ts release db-config-sync --json > /tmp/dbsync.json; D=$?
echo "db-config-sync exit=$D"要一并算 Nacos key-diff，先用 dump-nacos-namespace.ts 产出两份 dump（基准 / 目标现状），再传 --ref/--cur：
npx tsx sdk/apc/bin/apc.ts release db-config-sync --ref /tmp/nacos-ref.env --cur /tmp/nacos-cur.env --json2. 按 decision 分流
| decision | exit | 含义 | 你要做的 |
|---|---|---|---|
green | 0 | 无 pending 迁移 + key 无缺失 | 放行 |
staged | 3 | 有 pending 迁移 / 目标环境缺 key | 列出 migration.pending + keyDiff.missing；审批后走远端 apply（sync-test-migrations.ts 去 --dry-run / Nacos 补 key），不得抢跑 |
blocked | 1 | 真脚本 exit 非 0（连库失败 / 缺 REMOTE_MYSQL_*） | 读 migration.stderr，修凭证/连通性——这是前置，别绕开账本自己灌库 |
Failure / 边界
- 缺
REMOTE_MYSQL_*→ 真脚本throw→ 本 verbblocked。这是真行为非桩（正是"调真脚本"的证据），如实报，修凭证后重跑。 - 本机 MySQL 挂（colima 损坏）时对不可达 replica 跑，真脚本会 fs 枚举全量 pending——真脚本真行为，但"真实差异（部分已 applied）"需活 replica，属 M5 边界。
- key-diff 未给 dump →
skipped（真 Nacos fetch = M5）。诚实标 ⬜，不冒充已验。
输出契约（机器判据按这个复算，别自由发挥格式）
本 skill 的判据不是「报告里出现了 pending / nacos 这些字」，而是：重解析你贴的两份 --json 产物、从 decision 反推退出码、并把 migration.pending[] 里的每一个文件名逐个 stat 回 src/im/sql/（structured-criteria.ts 的 json-claim）。
本 sample task 钉的是两次真跑：一次接通本地 replica（站位远端 test RDS），一次抽掉 REMOTE_MYSQL_* 的负控——负控是这条用例自带的、必须变红的注入点。
# 1) 连通跑（本地 replica 站位远端 test RDS）
REMOTE_MYSQL_HOST=127.0.0.1 REMOTE_MYSQL_PORT=3307 REMOTE_MYSQL_USER=… REMOTE_MYSQL_PASSWORD=… \
REMOTE_MYSQL_DATABASE=prismer_cloud npx tsx sdk/apc/bin/apc.ts release db-config-sync --json
# 2) 负控：不带 REMOTE_MYSQL_*，真脚本 throw
npx tsx sdk/apc/bin/apc.ts release db-config-sync --json报告必须带这组行 + 两份原样 JSON：
MIGRATION-EXIT: 0
KEYDIFF: <keyDiff.status —— skipped | computed>
RUN-EXIT: <decision green→0 | staged→3 | blocked→1>
NEG-MIGRATION-EXIT: 1
NEG-DECISION: blocked
NEG-RUN-EXIT: 1判据会判红的情况（任一）：
- 没有可解析的 fenced JSON；
MIGRATION-EXIT/KEYDIFF与产物字段不一致——把 skipped 的 key-diff 说成"已核对"正是这条抓的；RUN-EXIT不是从decision推出来的那个；migration.pending[]里任何一个文件名在src/im/sql/下不存在——这份清单是真脚本枚举src/im/sql/*.sql⇄ 目标库_migrations账本算出来的，没真跑就得编两百多个文件名，编一个就红；- 把
pending[]截断成「…还有 200 条」——判据读的是数组，截断即缺项； - 负控产物不是
migration.exitCode != 0+decision:blocked+blockers非空 +pending空——一个能扛过自己凭证故障的迁移计划是编的； decision:green却pending非空 /decision:staged却staged[]空。
诚实边界：①判据证明不了 pending[] 的语义正确（哪些真该 apply），只证明每个名字是磁盘上真存在的迁移文件 + 计数自洽。②「未写远端 DB / 真 Nacos」这一条没有结构化事实可断（dry-run 的本质就是没有副作用），因此仍保留为关键词判据——它是本 skill 唯一还靠措辞的判据，写清楚这点比假装它有牙重要。③接不通 replica 时本 sample task 无法演示，此时判据红是如实结论（不是 SUT 红，是本机环境没给到前置）。
产出（副作用 oracle，报告里必须给）
- decision + 真退出码：
green/staged/blocked⇄0/3/1（读回核对）。 - 迁移计划：
migration.exitCode+pending[]（列真 sql 文件名，非"若干条"）。 - key-diff：
computed时给missing/extra计数；skipped时原样报 skipped + reason。 - 是否停在 dry-run 边界：明确本 skill 没有写远端库 / 没有写真 Nacos。
不许：把桩 / skipped 当已验；有 pending 迁移还发版；绕过账本用裸 SQL / Navicat 灌远端。
Show full SKILL.md (247 more words)Show less
Checklist
- 跑了
apc release db-config-sync --json，记录decision+ 真退出码 - 列出了
migration.pending的真文件名（有则 staged，审批后才 apply） - key-diff 是 computed 就给 missing/extra 计数，是 skipped 就照实标 ⬜
- 明确本步只 dry-run，没写远端；blocked 时报了真 stderr 而非绕过
审批门（doc03 §1）
本 skill 收口 doc03 §1 审批点 「远端 DB/配置写」（触发：db-config-sync 应用前）。dry-run 停在写入边界，真 apply 前必须建人审批并停手：
出示 dry-run 证据（审批人看到的，非 agent 自述）：迁移 dry-run 计划（
migration.pending[]真 sql 文件名）+ Nacos key-diff 报告（keyDiff.missing/extra；skipped就照实标 ⬜）。建真 cloud 审批（真路径 =
human-approvalbuilt-in skill 的 CLI）——把上面证据装进请求：bash cloud approval request-human --task-id "$PRISMER_TASK_ID" \ --action "apply 远端迁移 + 补 Nacos key（test）" \ --context "pending 迁移: <migration.pending>；key-diff missing: <keyDiff.missing>（dry-run 计划见回执）" \ --risk "写 test RDS 账本 + Nacos；红线：绕账本灌库曾致 prod 半应用事故（apc/01 开头）"返回
approvalId；建完即停手本轮（human-approval 铁律：平台在人裁决后重派，别同轮往下执行）。block：未 approve 前
staged（exit 3），dry-run 边界不写远端。post-approval = M5 real-remote：真 apply（
sync-test-migrations.ts去--dry-run打进 test RDS / Nacos 补 key）+ 服务端校验approvalId已 approved，属 M5 real-remote，本机替身不执行、不冒充已 apply。
PKF 直写（研发回环 · doc07 §B2 写入点①）
产出时机：db-config-sync 出 decision 后，把这次远端迁移/配置差异的结论直写成一张 PKF 记忆页（pageType=decision，ReleaseCard 语义 apc/09 §1）——同一页既是回审批人侧的富报告，也是可召回的发版记录。Navicat 绕账本这类事故教训另走 memory skill 的 CONSTRUCT→PLACE→WRITE，两条边并存（doc07 §B1）。这条直写是 dry-run 边界之外的一次投影，不写远端。
语法照 pkf-writing skill——本 skill 不再内嵌语法骨架（frontmatter / typed link / 数据块写法都在那边）。写入面不新造：code agent 走 prismer memory write（SS-14 §4.3 appendix；hermes 侧是 native memory_write）。
声明（doc10 §2.5 格式，报告末尾一行）：
PKF: prismer://workspace/<ws>/memory/<path>写入面不可达时如实声明 PKF: none — 写入面不可达（<哪一条>），绝不允许为了满足规则而假装写了。
回读：声明后必须回读该页（pkf_read / memory read），确认真实存在、正文非空且与结论一致（key-diff skipped 就在页里照实标 ⬜、别写成"已核对无差异"）；typed link 的 prismer:// 目标必须真实存在（validator 规则 2c/4 挡 invalid-prismer-host），无对应页就删该 link 行、宁缺勿造伪目标；写入自动挂 INDEX 反孤儿锚（SS-14 §4.2），优先 edit 既有页而非 dump 新叶（PLACE 治理照走）。
<!-- APC-ACK:v1 -->调用回执（APC 平台方运营纪律 · 自动注入，勿手改）
执行本 skill 的第一步，先落一条调用回执：
cloud skill ack release-db-config-sync --task "$PRISMER_TASK_ID"按退出码分流（这条命令的退出码是承重信息，禁止用 || 兜底、; true、
set +e 或重定向把它抹掉）：
| exit | 含义 | 你要做的 |
|---|---|---|
0 | 回执已落库（im_task_logs.action='skill_ack'） | 继续执行本 skill |
3 | 无 task 上下文——本次运行没有 task，产不出回执 | 继续执行本 skill；但本次运行没有回执，任何报告里都不得声称已 ack |
4 | 你不是该 task 的 assignee，服务端拒绝 | 停下并上报：回执只能由执行该 task 的 agent 产生 |
1 | 其它失败（网络 / 服务端） | 重试一次；仍失败则继续执行，并在结果里显式标注「回执缺失」 |
回执只证明本 skill 被调度，不证明执行正确——效果证明由本 skill 自己的 acceptanceCriteria 副作用断言承担（apc/04 §2 层 1 诚实标注）。
<!-- /APC-ACK:v1 -->© Prismer-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in sdk/apc/skills/release-db-config-sync of Prismer-AI/PrismerCloud.
- SKILL.md
- skill.json
Open the folder on GitHubat commit e5d9444
Compare with similar skills
Release DB Config Sync 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release DB Config Sync this skillPrismer-AI/PrismerCloud | 1.6k | — | ~2.1k | Automated safety check: Notes | MIT | |
| Evolving The Data ModelTriliumNext/Trilium | 38k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Creating Database MigrationsNangoHQ/nango | 13k | — | ~449 | Automated safety check: Pass | Custom licence | |
| Openwrt Package UpdateNethServer/nethsecurity | 192 | — | ~841 | Automated safety check: Pass | Custom licence | |
| Free Willsyahiidkamil/Software-Engineer-AI-Agent-Atlas | 401 | — | ~3.4k | Automated safety check: Pass | None | |
| Ecto Migrationsoperately/operately | 578 | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Creating Database Migrations
NangoHQ/nango
A skill your agent uses when adding or editing Nango database migrations - covers migration directory selection, timestamped .cjs naming, matching recent migration style, down migration decisions…
Openwrt Package Update
NethServer/nethsecurity
A skill your agent uses when updating any forked OpenWrt package in a NethSecurity workspace from the upstream openwrt/packages feed.
Free Will
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Deliberate-choice procedure for a medium-to-high-stakes engineering fork — when the first plausible solution (the instinct, the default next-token pull) would be costly to get wrong.
Ecto Migrations
operately/operately
Rules for Operately schema migrations (app/priv/repo/migrations/) and data migrations (app/lib/operately/data/change.ex).
DB Migrate
simstudioai/sim
Author or review a Drizzle DB migration for zero-downtime safety — expand/contract phasing, backward-compatibility with the deployed app version, and writing the -- migration-safe acknowledgment the…
More from Prismer-AI/PrismerCloud
All 88 skills in this repoPrismer Google Workspace
Prismer-AI/PrismerCloud
Gives an agent account-scoped access to Gmail, Calendar, Drive, Contacts, Docs and Sheets through the gws CLI or a bundled Python client.
Prismer Skill Creator
Prismer-AI/PrismerCloud
Walks an agent through creating, importing, editing, validating, testing and publishing Prismer Skills with a fixed workflow and bundled scripts.
Himalaya Email CLI
Prismer-AI/PrismerCloud
Operates a mailbox from the terminal with the external Himalaya CLI over IMAP, SMTP, Notmuch or Sendmail, separate from any built-in email gateway adapter.
Prismer Image Generation
Prismer-AI/PrismerCloud
Generates one image from a text prompt with a bundled Node.js helper and delivers it once as the attachment to the current Prismer reply.
Manim Explainer Videos
Prismer-AI/PrismerCloud
Produces 3Blue1Brown-style explainer animations with Manim Community Edition for math, algorithms, equations and architecture diagrams, with planning and rendering references.
Prismer Role Builder
Prismer-AI/PrismerCloud
Creates or updates Prismer role templates from a persona, SOP or job description, and turns a role into a working agent that runs its first task through a bundled script.
Related
Categories
Questions about Release DB Config Sync
What does Release DB Config Sync do?
Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps…. Release DB Config Sync is an agent skill from Prismer-AI/PrismerCloud.ts --dry-run (never a stub) and diffs Nacos key dumps, stopping at the write boundary.
When should I use Release DB Config Sync?
Release DB Config Sync fits situations like: tasks that involve Database migrations.
How do I install Release DB Config Sync in Claude Code?
Run `npx skills add Prismer-AI/PrismerCloud --skill release-db-config-sync -a claude-code`. Or copy the skill folder (sdk/apc/skills/release-db-config-sync in Prismer-AI/PrismerCloud) into .claude/skills/release-db-config-sync in your project. Claude Code loads it when a task matches its description.
How do I install Release DB Config Sync in Codex?
Run `npx skills add Prismer-AI/PrismerCloud --skill release-db-config-sync -a codex`. Or copy the skill folder (sdk/apc/skills/release-db-config-sync in Prismer-AI/PrismerCloud) into .agents/skills/release-db-config-sync in your project. Codex loads it when a task matches its description.
Can I use Release DB Config Sync 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 Prismer-AI/PrismerCloud --skill release-db-config-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-db-config-sync, .gemini/skills/release-db-config-sync, .github/skills/release-db-config-sync and .opencode/skills/release-db-config-sync in your project.
What does Release DB Config Sync need to run?
Going by SKILL.md and its folder, Release DB Config Sync needs the command-line tools its instructions call (npx) and credentials named REMOTE_MYSQL_PASSWORD. Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash. Compatibility (from SKILL.md): ["claude-code"].
Does Release DB Config Sync access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release DB Config Sync safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Release DB Config Sync use?
Release DB Config Sync is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release DB Config Sync use?
About 2.1k tokens (SKILL.md is roughly 8.4k 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 Release DB Config Sync?
Skills that share tags, products or a category with Release DB Config Sync: Evolving The Data Model (TriliumNext/Trilium, 38k stars), Creating Database Migrations (NangoHQ/nango, 13k stars), Openwrt Package Update (NethServer/nethsecurity, 192 stars) and Free Will (syahiidkamil/Software-Engineer-AI-Agent-Atlas, 401 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release DB Config Sync?
Prismer-AI (a GitHub organization) maintains it in Prismer-AI/PrismerCloud, which has 1,555 GitHub stars. The repository holds 88 skills in this directory. The repository was last updated on September 30, 2026.
Source: Prismer-AI/PrismerCloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.