[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P224S0T70CC3GXJQE86BBC":3,"skill-same:01M6P224S0T70CC3GXJQE86BBC":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":13,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6P224S0T70CC3GXJQE86BBC","drizzle-migration-conflict",null,"Diagnose, repair, and prevent Drizzle Kit migration conflicts involving generated SQL, snapshots, journals, merge queues, and team workflows.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdrizzle-migration-conflict\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"drizzle migration conflict","drizzle","migration","conflict","community","rg","kit","merge-conflicts","drizzle kit","critical","repair","python","snapshots","databases","agent-skills","generated","ci","license","database","diagnose","2026-11-10 10:12:30",false,"---\nname: drizzle-migration-conflict\ndescription: \"Diagnose, repair, and prevent Drizzle Kit migration conflicts involving generated SQL, snapshots, journals, merge queues, and team workflows.\"\ncategory: databases\nrisk: critical\nsource: community\nsource_repo: chaunsin\u002Fagent-skills\nsource_type: community\ndate_added: \"2026-06-29\"\nauthor: chaunsin\ntags: [drizzle, migrations, database, ci, merge-conflicts]\ntools: [git, python, rg]\nlicense: \"Apache-2.0\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fchaunsin\u002Fagent-skills\u002Fblob\u002Fmaster\u002FLICENSE\"\n---\n\n# Drizzle Migration Conflict\n\nUse this skill to help a user diagnose, repair, and prevent Drizzle Kit migration conflicts in a\nmulti-developer repository. Drizzle migrations encode both SQL and migration snapshots, so the safe\nanswer depends on the current migration directory shape, the Drizzle Kit version, and the git state.\n\n## When to Use This Skill\n\n- Use when Drizzle migration files, `_journal.json`, or `snapshot.json` conflict after a pull, merge, rebase, or PR update.\n- Use when `drizzle-kit check` reports non-commutative migrations or migration folder conflicts.\n- Use when a team wants a safe repair flow for generated Drizzle migrations after schema changes converge.\n- Use when designing CI or merge-queue policy to prevent repeated Drizzle migration conflicts.\n\n## Safety rules\n\n- Start in read-only diagnosis mode unless the user explicitly asks to fix files.\n- Do not run `drizzle-kit migrate`, `drizzle-kit push`, database seed scripts, or any command that\n  connects to a live database unless the user explicitly requests it and the target is clear.\n- Treat `drizzle-kit check`, project typechecks, and tests as command execution that may load project\n  config, environment variables, or scripts. Inspect scripts\u002Fconfig first, and require an explicit\n  non-production or disposable target before any DB-backed validation.\n- Do not delete migration files, rewrite `_journal.json`, or run `git checkout --ours`,\n  `git checkout --theirs`, `git restore`, or `rm` unless the user has confirmed the exact side and\n  files to change.\n- Do not recommend `drizzle-kit push` as the production solution for migration conflicts; it skips\n  the auditable migration history that teams need.\n- Treat `--ignore-conflicts` as an exception for a known false positive, not as the normal fix.\n- Preserve schema source code changes unless the user explicitly asks to discard them. Conflict\n  repair normally discards generated migrations and regenerates them from the merged schema.\n- If `ours` and `theirs` could mean different branches depending on merge direction, ask the user to\n  identify the parent branch before suggesting checkout commands.\n\n## Required references\n\n- Read `references\u002Fsources.md` when the answer depends on current Drizzle behavior, official\n  guidance, or one of the preserved external links.\n- Read `references\u002Fconflict-resolution.md` before recommending a repair flow.\n- Read `references\u002Fci-policy.md` before proposing CI, merge queue, or team workflow changes.\n- Read `references\u002Freport-template.md` before writing a diagnostic report.\n\n## Source references\n\nThe full list of official docs, Drizzle GitHub discussions, community scripts, and merge-queue\nreferences lives in `references\u002Fsources.md` with trust levels and caveats. Read that file whenever\nthe answer depends on current Drizzle behavior. Re-verify the official docs and the most relevant\ndiscussion when the project's `drizzle-kit` major version changes, since migration internals\n(snapshot format, journal shape, `drizzle-kit check` semantics) have shifted between releases.\n\n## Mode selection\n\nClassify the task first:\n\n1. **Diagnose** - The user has a conflict or failed `drizzle-kit check` and wants to understand it.\n2. **Repair** - The user explicitly asks to fix or regenerate migration files.\n3. **CI hardening** - The user wants to prevent future conflicts in PRs or merge queues.\n4. **Explain** - The user wants a conceptual answer or a team playbook.\n\nWhen the mode is not explicit, choose Diagnose.\n\nEach mode unlocks a specific set of actions. Do not cross these boundaries without an explicit upgrade:\n\n- **Diagnose** - read-only only. Run `git status`, `git ls-files -u`, the helper script, and file\n  inspection. Do not run `drizzle-kit check`, typechecks, tests, or any write command. Report\n  findings and the proposed repair path, but do not execute it.\n- **Repair** - adds file writes and `drizzle-kit generate`\u002F`check` execution, each gated by the\n  Safety rules and explicit confirmation of the exact files and side (`ours`\u002F`theirs`) to change.\n- **CI hardening** - adds proposing or editing CI\u002Fworkflow files. Do not run migration commands\n  against the user's database to validate the workflow; validate the workflow syntax and logic only.\n- **Explain** - conceptual only. No commands against the repo beyond optional read-only inspection.\n\n## Repository discovery\n\nCollect repo facts before giving commands:\n\n```bash\ngit status --short\ngit rev-parse --show-toplevel\ngit rev-parse --abbrev-ref HEAD\ngit ls-files -u\nrg --files -g 'drizzle.config.*' -g 'package.json' -g 'pnpm-lock.yaml' -g 'yarn.lock' -g 'package-lock.json'\n```\n\nThen inspect the relevant files:\n\n- `drizzle.config.*` for `out`, `schema`, dialect, and config shape.\n- `package.json` scripts for the project-approved `generate`, `check`, and `migrate` commands.\n- `package.json` dependencies or lockfile snippets for `drizzle-kit` and `drizzle-orm` versions.\n- The migration output directory, either from config or common names like `drizzle\u002F`, `migrations\u002F`,\n  or `src\u002Fdb\u002Fmigrations\u002F`.\n\nIf this skill's helper script is available, run it in read-only mode:\n\n```bash\npython3 \u003Cskill-dir>\u002Fscripts\u002Fcheck_drizzle_migrations.py --root .\n```\n\nResolve `\u003Cskill-dir>` to the installed skill directory before running. Check these locations in order\nand use the first that contains `scripts\u002Fcheck_drizzle_migrations.py`:\n\n1. The target repository's vendored copy: `\u003Crepo-root>\u002Fskills\u002Fdrizzle-migration-conflict`.\n2. The Claude Code skills directory: `~\u002F.claude\u002Fskills\u002Fdrizzle-migration-conflict`.\n3. Any other install location reported by the user's environment.\n\nIf none of these resolve, fall back to the manual `git`\u002F`rg` inspection commands above and tell the\nuser the helper script was not found. Use `--config \u003Cfile>` and `--migrations-dir \u003Cdir>` when the\nproject has multiple Drizzle configs or outputs. The script never connects to a database and never\nwrites files; it only reads migration directories and reports structural issues.\n\n## Migration structure decision\n\nIdentify the structure before proposing a fix:\n\n- **Legacy structure**: `\u003Cout>\u002Fmeta\u002F_journal.json`, `\u003Cout>\u002Fmeta\u002F*_snapshot.json`, and root-level\n  migration SQL files such as `\u003Cout>\u002F0003_name.sql`.\n- **Folder-based structure**: each migration is a directory containing `migration.sql` and\n  `snapshot.json`.\n- **Unknown or mixed structure**: stop and report ambiguity. Do not guess a destructive repair.\n\n## Recommended repair principles\n\n- Resolve schema source conflicts first. The regenerated migration must reflect the merged schema,\n  not one side's stale snapshot.\n- Treat the parent or target branch migration history as the source of truth when repairing a feature\n  branch after updating from that branch.\n- Prefer discarding and regenerating generated migration artifacts over hand-editing journal or\n  snapshot files.\n- After regeneration, validate in tiers: database-free structural checks first; then `drizzle-kit\n  check` only after confirming its config\u002Fenv cannot point at production; then project tests only\n  after inspecting the scripts and any database targets.\n- If the user asks to apply changes, state exactly which files will be changed before performing the\n  write.\n\n## Output rules\n\n- Use the user's language when practical, but keep command snippets and file paths literal.\n- State the detected migration structure and selected mode.\n- Separate confirmed conflicts from assumptions and missing evidence.\n- Give a safe default path first, then optional automation or CI hardening.\n- For destructive steps, label them as \"requires confirmation\" and explain what will be lost.\n- Never echo secrets. When inspecting `drizzle.config.*`, `.env`, or environment variables, do not\n  include database URLs, passwords, tokens, or connection strings in the report. Reference them as\n  `\u003Credacted>` or describe only whether they point at a production-like target.\n- Use the conclusion values from `references\u002Freport-template.md` for diagnostic reports:\n  `NO_CONFLICT_FOUND`, `SAFE_TO_REGENERATE`, `NEEDS_USER_CONFIRMATION`, or `BLOCKED_BY_AMBIGUITY`.\n\n## Limitations\n\n- This skill cannot guarantee that a regenerated migration is production-safe without review against the target database state and deployment process.\n- It does not run DB-backed migration commands unless the user explicitly confirms the target and the command.\n- It is focused on Drizzle Kit migration conflicts, not general schema design or application-query optimization.\n\n## Test prompts\n\nUse these prompts to validate the skill behavior:\n\n- \"My Drizzle `_journal.json` and `0003_snapshot.json` conflict during merge. Tell me what to do.\"\n- \"We upgraded to the migration folder layout and `drizzle-kit check` reports a non-commutative conflict.\"\n- \"Design CI so our team stops merging broken Drizzle migrations.\"\n- \"Can I solve this production Drizzle migration conflict with `drizzle-kit push`?\"\n- \"Use the links in the skill to re-check the current official Drizzle migration conflict guidance.\"\n- \"We're halfway through moving from the legacy flat layout to folder-based migrations. How do we handle a conflict during the transition?\"\n- \"Our `drizzle.config.ts` sets `out` from `process.env.MIGRATIONS_DIR`, and the helper says no out directory was found. What now?\"\n- \"`drizzle-kit check` keeps failing on a migration we know commutes. Can we just always pass `--ignore-conflicts`?\"\n","# Drizzle Migration Conflict\n\nUse this skill to help a user diagnose, repair, and prevent Drizzle Kit migration conflicts in a\nmulti-developer repository. Drizzle migrations encode both SQL and migration snapshots, so the safe\nanswer depends on the current migration directory shape, the Drizzle Kit version, and the git state.\n\n## When to Use This Skill\n\n- Use when Drizzle migration files, `_journal.json`, or `snapshot.json` conflict after a pull, merge, rebase, or PR update.\n- Use when `drizzle-kit check` reports non-commutative migrations or migration folder conflicts.\n- Use when a team wants a safe repair flow for generated Drizzle migrations after schema changes converge.\n- Use when designing CI or merge-queue policy to prevent repeated Drizzle migration conflicts.\n\n## Safety rules\n\n- Start in read-only diagnosis mode unless the user explicitly asks to fix files.\n- Do not run `drizzle-kit migrate`, `drizzle-kit push`, database seed scripts, or any command that\n  connects to a live database unless the user explicitly requests it and the target is clear.\n- Treat `drizzle-kit check`, project typechecks, and tests as command execution that may load project\n  config, environment variables, or scripts. Inspect scripts\u002Fconfig first, and require an explicit\n  non-production or disposable target before any DB-backed validation.\n- Do not delete migration files, rewrite `_journal.json`, or run `git checkout --ours`,\n  `git checkout --theirs`, `git restore`, or `rm` unless the user has confirmed the exact side and\n  files to change.\n- Do not recommend `drizzle-kit push` as the production solution for migration conflicts; it skips\n  the auditable migration history that teams need.\n- Treat `--ignore-conflicts` as an exception for a known false positive, not as the normal fix.\n- Preserve schema source code changes unless the user explicitly asks to discard them. Conflict\n  repair normally discards generated migrations and regenerates them from the merged schema.\n- If `ours` and `theirs` could mean different branches depending on merge direction, ask the user to\n  identify the parent branch before suggesting checkout commands.\n\n## Required references\n\n- Read `references\u002Fsources.md` when the answer depends on current Drizzle behavior, official\n  guidance, or one of the preserved external links.\n- Read `references\u002Fconflict-resolution.md` before recommending a repair flow.\n- Read `references\u002Fci-policy.md` before proposing CI, merge queue, or team workflow changes.\n- Read `references\u002Freport-template.md` before writing a diagnostic report.\n\n## Source references\n\nThe full list of official docs, Drizzle GitHub discussions, community scripts, and merge-queue\nreferences lives in `references\u002Fsources.md` with trust levels and caveats. Read that file whenever\nthe answer depends on current Drizzle behavior. Re-verify the official docs and the most relevant\ndiscussion when the project's `drizzle-kit` major version changes, since migration internals\n(snapshot format, journal shape, `drizzle-kit check` semantics) have shifted between releases.\n\n## Mode selection\n\nClassify the task first:\n\n1. **Diagnose** - The user has a conflict or failed `drizzle-kit check` and wants to understand it.\n2. **Repair** - The user explicitly asks to fix or regenerate migration files.\n3. **CI hardening** - The user wants to prevent future conflicts in PRs or merge queues.\n4. **Explain** - The user wants a conceptual answer or a team playbook.\n\nWhen the mode is not explicit, choose Diagnose.\n\nEach mode unlocks a specific set of actions. Do not cross these boundaries without an explicit upgrade:\n\n- **Diagnose** - read-only only. Run `git status`, `git ls-files -u`, the helper script, and file\n  inspection. Do not run `drizzle-kit check`, typechecks, tests, or any write command. Report\n  findings and the proposed repair path, but do not execute it.\n- **Repair** - adds file writes and `drizzle-kit generate`\u002F`check` execution, each gated by the\n  Safety rules and explicit confirmation of the exact files and side (`ours`\u002F`theirs`) to change.\n- **CI hardening** - adds proposing or editing CI\u002Fworkflow files. Do not run migration commands\n  against the user's database to validate the workflow; validate the workflow syntax and logic only.\n- **Explain** - conceptual only. No commands against the repo beyond optional read-only inspection.\n\n## Repository discovery\n\nCollect repo facts before giving commands:\n\n```bash\ngit status --short\ngit rev-parse --show-toplevel\ngit rev-parse --abbrev-ref HEAD\ngit ls-files -u\nrg --files -g 'drizzle.config.*' -g 'package.json' -g 'pnpm-lock.yaml' -g 'yarn.lock' -g 'package-lock.json'\n```\n\nThen inspect the relevant files:\n\n- `drizzle.config.*` for `out`, `schema`, dialect, and config shape.\n- `package.json` scripts for the project-approved `generate`, `check`, and `migrate` commands.\n- `package.json` dependencies or lockfile snippets for `drizzle-kit` and `drizzle-orm` versions.\n- The migration output directory, either from config or common names like `drizzle\u002F`, `migrations\u002F`,\n  or `src\u002Fdb\u002Fmigrations\u002F`.\n\nIf this skill's helper script is available, run it in read-only mode:\n\n```bash\npython3 \u003Cskill-dir>\u002Fscripts\u002Fcheck_drizzle_migrations.py --root .\n```\n\nResolve `\u003Cskill-dir>` to the installed skill directory before running. Check these locations in order\nand use the first that contains `scripts\u002Fcheck_drizzle_migrations.py`:\n\n1. The target repository's vendored copy: `\u003Crepo-root>\u002Fskills\u002Fdrizzle-migration-conflict`.\n2. The Claude Code skills directory: `~\u002F.claude\u002Fskills\u002Fdrizzle-migration-conflict`.\n3. Any other install location reported by the user's environment.\n\nIf none of these resolve, fall back to the manual `git`\u002F`rg` inspection commands above and tell the\nuser the helper script was not found. Use `--config \u003Cfile>` and `--migrations-dir \u003Cdir>` when the\nproject has multiple Drizzle configs or outputs. The script never connects to a database and never\nwrites files; it only reads migration directories and reports structural issues.\n\n## Migration structure decision\n\nIdentify the structure before proposing a fix:\n\n- **Legacy structure**: `\u003Cout>\u002Fmeta\u002F_journal.json`, `\u003Cout>\u002Fmeta\u002F*_snapshot.json`, and root-level\n  migration SQL files such as `\u003Cout>\u002F0003_name.sql`.\n- **Folder-based structure**: each migration is a directory containing `migration.sql` and\n  `snapshot.json`.\n- **Unknown or mixed structure**: stop and report ambiguity. Do not guess a destructive repair.\n\n## Recommended repair principles\n\n- Resolve schema source conflicts first. The regenerated migration must reflect the merged schema,\n  not one side's stale snapshot.\n- Treat the parent or target branch migration history as the source of truth when repairing a feature\n  branch after updating from that branch.\n- Prefer discarding and regenerating generated migration artifacts over hand-editing journal or\n  snapshot files.\n- After regeneration, validate in tiers: database-free structural checks first; then `drizzle-kit\n  check` only after confirming its config\u002Fenv cannot point at production; then project tests only\n  after inspecting the scripts and any database targets.\n- If the user asks to apply changes, state exactly which files will be changed before performing the\n  write.\n\n## Output rules\n\n- Use the user's language when practical, but keep command snippets and file paths literal.\n- State the detected migration structure and selected mode.\n- Separate confirmed conflicts from assumptions and missing evidence.\n- Give a safe default path first, then optional automation or CI hardening.\n- For destructive steps, label them as \"requires confirmation\" and explain what will be lost.\n- Never echo secrets. When inspecting `drizzle.config.*`, `.env`, or environment variables, do not\n  include database URLs, passwords, tokens, or connection strings in the report. Reference them as\n  `\u003Credacted>` or describe only whether they point at a production-like target.\n- Use the conclusion values from `references\u002Freport-template.md` for diagnostic reports:\n  `NO_CONFLICT_FOUND`, `SAFE_TO_REGENERATE`, `NEEDS_USER_CONFIRMATION`, or `BLOCKED_BY_AMBIGUITY`.\n\n## Limitations\n\n- This skill cannot guarantee that a regenerated migration is production-safe without review against the target database state and deployment process.\n- It does not run DB-backed migration commands unless the user explicitly confirms the target and the command.\n- It is focused on Drizzle Kit migration conflicts, not general schema design or application-query optimization.\n\n## Test prompts\n\nUse these prompts to validate the skill behavior:\n\n- \"My Drizzle `_journal.json` and `0003_snapshot.json` conflict during merge. Tell me what to do.\"\n- \"We upgraded to the migration folder layout and `drizzle-kit check` reports a non-commutative conflict.\"\n- \"Design CI so our team stops merging broken Drizzle migrations.\"\n- \"Can I solve this production Drizzle migration conflict with `drizzle-kit push`?\"\n- \"Use the links in the skill to re-check the current official Drizzle migration conflict guidance.\"\n- \"We're halfway through moving from the legacy flat layout to folder-based migrations. How do we handle a conflict during the transition?\"\n- \"Our `drizzle.config.ts` sets `out` from `process.env.MIGRATIONS_DIR`, and the helper says no out directory was found. What now?\"\n- \"`drizzle-kit check` keeps failing on a migration we know commutes. Can we just always pass `--ignore-conflicts`?\"\n",{"name":5,"risk":32,"tags":48,"tools":50,"author":52,"source":27,"license":14,"category":36,"date_added":53,"description":7,"source_repo":54,"source_type":27,"license_source":55},[24,49,41,39,30],"migrations",[51,34,28],"git","chaunsin","2026-06-29","chaunsin\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fchaunsin\u002Fagent-skills\u002Fblob\u002Fmaster\u002FLICENSE","main","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fdrizzle-migration-conflict","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill drizzle-migration-conflict",{"tool":68,"command":69},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill drizzle-migration-conflict",{"tool":71,"command":72},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill drizzle-migration-conflict","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdrizzle-migration-conflict\u002FSKILL.md",true,[76,82,86,90,94],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fci-policy.md","REFERENCE","参考文档",4101,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdrizzle-migration-conflict\u002Freferences\u002Fci-policy.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fconflict-resolution.md",7527,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdrizzle-migration-conflict\u002Freferences\u002Fconflict-resolution.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Freport-template.md",2653,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdrizzle-migration-conflict\u002Freferences\u002Freport-template.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fsources.md",4373,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdrizzle-migration-conflict\u002Freferences\u002Fsources.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fcheck_drizzle_migrations.py","SCRIPT","脚本",25543,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdrizzle-migration-conflict\u002Fscripts\u002Fcheck_drizzle_migrations.py",[101,128,152,176,202,226],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":111,"publishedAt":43},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[112,113,114,115,116,117,103,118,119,120,121,122,27,56,123,32,124,125,126,127],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":43},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[135,136,137,138,139,140,141,142,143,144,145,146,147,122,148,27,149,150,32,151],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":43},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[159,160,161,162,163,164,165,40,166,167,168,169,170,27,56,171,172,173,174,175],"transcript","youtube transcript","youtube","safe","github","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":191,"publishedAt":43},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[182,183,186],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":184,"categoryName":185,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":187,"categoryName":188,"taxonomyType":189,"taxonomyTypeDesc":190},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[159,160,161,192,162,193,163,164,40,194,195,196,197,168,198,27,56,199,200,201],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":212,"publishedAt":43},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":184,"categoryName":185,"taxonomyType":20,"taxonomyTypeDesc":21},[161,213,214,139,162,215,216,217,218,40,196,219,220,221,222,56,223,171,224,225],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":233,"publishedAt":43},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[232],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[234,161,235,236,162,193,194,237,238,195,196,197,168,239,198,27,56,199,240,174],"youtube full","full","google","server","dlp","credits","automatic"]