[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AP99SH0ZD6MWCGY18D616X":3,"skill-same:01M7AP99SH0ZD6MWCGY18D616X":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AP99SH0ZD6MWCGY18D616X","PocketBase Migrations",null,"Schema migrations and versioning for PocketBase. Use when creating migrations, managing schema versions, syncing collections between environments, using automigrate, or creating collections programmatically. Covers migrate commands, migration file format, snapshot imports, and the _migrations tracking table.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fpocketbase\u002Fpb-migrations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"PocketBase Migrations\"\ndescription: \"Schema migrations and versioning for PocketBase. Use when creating migrations, managing schema versions, syncing collections between environments, using automigrate, or creating collections programmatically. Covers migrate commands, migration file format, snapshot imports, and the _migrations tracking table.\"\n---\n\n# PocketBase Migrations & Schema Versioning\n\n## Overview\n\nPocketBase supports two approaches to schema management:\n\n1. **Auto-migrate** (default in dev) — Dashboard changes auto-generate migration files in `pb_migrations\u002F`\n2. **Manual migrations** — write migration files by hand for full control\n\n## CLI Commands\n\n```bash\n# Create a new empty migration file\n.\u002Fpocketbase migrate create \"add_posts_collection\"\n# Creates: pb_migrations\u002F1234567890_add_posts_collection.js\n\n# Apply all pending migrations\n.\u002Fpocketbase migrate up\n\n# Revert the last applied migration\n.\u002Fpocketbase migrate down\n\n# Generate a full snapshot of all current collections\n.\u002Fpocketbase migrate collections\n# Creates a migration file that recreates all collections from scratch\n\n# Sync migration history with actual DB state (mark all as applied)\n.\u002Fpocketbase migrate history-sync\n```\n\n## Auto-migrate Mode\n\nEnabled by default. When you change collections in the Dashboard, PocketBase auto-generates migration files in `pb_migrations\u002F`.\n\n```bash\n# Start with auto-migrate (default)\n.\u002Fpocketbase serve\n\n# Disable auto-migrate (production)\n.\u002Fpocketbase serve --automigrate=0\n```\n\n**Workflow**:\n1. Develop with auto-migrate ON — use Dashboard to design schema\n2. Migration files are auto-generated in `pb_migrations\u002F`\n3. Commit these files to git\n4. Deploy: migrations run automatically on `serve` start\n5. In production: use `--automigrate=0` to prevent Dashboard changes from generating new migrations\n\n## Migration File Format\n\n```js\n\u002F\u002F pb_migrations\u002F1234567890_add_posts_collection.js\n\nmigrate(\n    \u002F\u002F UP — apply migration\n    function(app) {\n        var collection = new Collection({\n            name: \"posts\",\n            type: \"base\",\n            fields: [\n                { name: \"title\", type: \"text\", required: true },\n                { name: \"body\", type: \"editor\" },\n                { name: \"author\", type: \"relation\", collectionId: \"USERS_COLLECTION_ID\", cascadeDelete: false, maxSelect: 1, required: true },\n                { name: \"status\", type: \"select\", values: [\"draft\", \"published\", \"archived\"] },\n                { name: \"published_at\", type: \"date\" },\n                { name: \"tags\", type: \"relation\", collectionId: \"TAGS_COLLECTION_ID\", maxSelect: 0 }\n            ],\n            indexes: [\n                \"CREATE INDEX idx_posts_author ON posts (author)\",\n                \"CREATE INDEX idx_posts_status ON posts (status)\",\n                \"CREATE UNIQUE INDEX idx_posts_title ON posts (title)\"\n            ],\n            listRule: \"\",   \u002F\u002F WARNING: \"\" means public access — use a filter or null to restrict\n            viewRule: \"\",   \u002F\u002F WARNING: \"\" means public access — use a filter or null to restrict\n            createRule: \"@request.auth.id != ''\",\n            updateRule: \"author = @request.auth.id\",\n            deleteRule: \"author = @request.auth.id\"\n        })\n        app.save(collection)\n    },\n    \u002F\u002F DOWN — revert migration\n    function(app) {\n        var collection = app.findCollectionByNameOrId(\"posts\")\n        app.delete(collection)\n    }\n)\n```\n\n**Important**: the `app` inside migrations is a transactional instance. If any error occurs, the entire migration is rolled back.\n\n## Creating Collections Programmatically\n\n### Base collection\n\n```js\nvar collection = new Collection({\n    name: \"posts\",\n    type: \"base\",\n    fields: [\n        { name: \"title\", type: \"text\", required: true, min: 3, max: 200 },\n        { name: \"slug\", type: \"text\", required: true, autogenerate: { pattern: \"slugify(title)\" } },\n        { name: \"body\", type: \"editor\" },\n        { name: \"cover\", type: \"file\", maxSelect: 1, maxSize: 5242880, mimeTypes: [\"image\u002Fjpeg\", \"image\u002Fpng\", \"image\u002Fwebp\"] },\n        { name: \"views\", type: \"number\", min: 0 },\n        { name: \"metadata\", type: \"json\", maxSize: 2000000 },\n        { name: \"featured\", type: \"bool\" },\n        { name: \"published_at\", type: \"date\" }\n    ]\n})\napp.save(collection)\n```\n\n### Auth collection\n\n```js\nvar collection = new Collection({\n    name: \"users\",\n    type: \"auth\",\n    fields: [\n        { name: \"name\", type: \"text\", required: true },\n        { name: \"avatar\", type: \"file\", maxSelect: 1, maxSize: 5242880 },\n        { name: \"role\", type: \"select\", values: [\"user\", \"editor\", \"admin\"], required: true }\n    ],\n    passwordAuth: { enabled: true, identityFields: [\"email\", \"username\"] },\n    oauth2: { enabled: true },\n    otp: { enabled: false },\n    mfa: { enabled: false },\n    authToken: { duration: 604800 }  \u002F\u002F 7 days\n})\napp.save(collection)\n```\n\n### View collection\n\n```js\nvar collection = new Collection({\n    name: \"posts_stats\",\n    type: \"view\",\n    viewQuery: \"SELECT p.id, p.title, COUNT(c.id) as comments_count, p.views FROM posts p LEFT JOIN comments c ON c.post = p.id GROUP BY p.id\",\n    listRule: \"\",\n    viewRule: \"\"\n})\napp.save(collection)\n```\n\n## Modifying Existing Collections\n\n```js\nmigrate(function(app) {\n    var collection = app.findCollectionByNameOrId(\"posts\")\n\n    \u002F\u002F Add a new field\n    collection.fields.add({\n        name: \"subtitle\",\n        type: \"text\",\n        max: 500\n    })\n\n    \u002F\u002F Remove a field\n    collection.fields.removeByName(\"old_field\")\n\n    \u002F\u002F Update API rules\n    collection.listRule = \"@request.auth.id != ''\"\n    collection.viewRule = \"\"\n\n    \u002F\u002F Add index\n    collection.indexes.push(\"CREATE INDEX idx_posts_subtitle ON posts (subtitle)\")\n\n    app.save(collection)\n}, function(app) {\n    var collection = app.findCollectionByNameOrId(\"posts\")\n    collection.fields.removeByName(\"subtitle\")\n    app.save(collection)\n})\n```\n\n## Raw SQL in Migrations\n\n```js\nmigrate(function(app) {\n    app.db().newQuery(\"ALTER TABLE posts ADD COLUMN legacy_id TEXT DEFAULT ''\").execute()\n    app.db().newQuery(\"UPDATE posts SET legacy_id = id WHERE legacy_id = ''\").execute()\n}, function(app) {\n    app.db().newQuery(\"ALTER TABLE posts DROP COLUMN legacy_id\").execute()\n})\n```\n\n**Warning**: raw SQL bypasses PocketBase's schema cache. Run `migrate collections` afterward to re-sync if needed.\n\n## Settings & Superuser in Migrations\n\n### Initialize app settings\n\n```js\nonBootstrap(function(e) {\n    var settings = e.app.settings()\n    settings.meta.appName = \"My App\"\n    settings.meta.appURL = \"https:\u002F\u002Fmyapp.com\"\n    settings.meta.senderName = \"My App\"\n    settings.meta.senderAddress = \"noreply@myapp.com\"\n    settings.smtp.enabled = true\n    settings.smtp.host = \"smtp.example.com\"\n    settings.smtp.port = 587\n    settings.smtp.username = $os.getenv(\"SMTP_USER\")\n    settings.smtp.password = $os.getenv(\"SMTP_PASS\")\n    e.app.save(settings)\n    return e.next()\n})\n```\n\n### Create superuser in migration\n\n```js\nmigrate(function(app) {\n    var superusers = app.findCollectionByNameOrId(\"_superusers\")\n    var record = new Record(superusers)\n    \u002F\u002F IMPORTANT: always set PB_ADMIN_EMAIL and PB_ADMIN_PASSWORD env vars\n    var email = $os.getenv(\"PB_ADMIN_EMAIL\")\n    var password = $os.getenv(\"PB_ADMIN_PASSWORD\")\n    if (!email || !password) {\n        throw new Error(\"PB_ADMIN_EMAIL and PB_ADMIN_PASSWORD env vars are required\")\n    }\n    record.set(\"email\", email)\n    record.set(\"password\", password)\n    app.save(record)\n})\n```\n\n## Snapshot Migrations\n\n`.\u002Fpocketbase migrate collections` generates a complete snapshot — useful for:\n- Bootstrapping a new environment\n- Resetting migration history\n- Reviewing full schema in one file\n\nThe generated file uses `app.importCollections(collections)` which supports two modes:\n- **Default (merge\u002Fextend)**: adds new collections and fields, updates existing ones, doesn't delete anything\n- **Delete missing**: `app.importCollections(collections, true)` — deletes collections\u002Ffields not in the snapshot\n\n## `_migrations` Table\n\nPocketBase tracks applied migrations in the internal `_migrations` table:\n- `id` — auto-generated\n- `file` — migration filename\n- `applied` — timestamp\n\n`migrate history-sync` marks all existing migration files as applied without running them — useful when importing an existing database.\n\n## Best Practices\n\n1. **Dev**: use auto-migrate + Dashboard for schema design, commit generated files\n2. **Staging\u002FProd**: deploy with `--automigrate=0`, migrations run on startup\n3. **Always write DOWN migrations** — reversibility saves you when things go wrong\n4. **One concern per migration** — don't mix unrelated schema changes\n5. **Test migrations**: apply on a copy of production data before deploying\n6. **Use `migrate collections`** periodically to snapshot current state for documentation\n7. **Never edit applied migrations** — create a new migration to fix issues\n8. **Seed data**: prefer a dedicated migration for one-time initial data; if using `onBootstrap`, make the seed logic idempotent (existence checks\u002Fupserts) because bootstrap runs on every app start\n","# PocketBase Migrations & Schema Versioning\n\n## Overview\n\nPocketBase supports two approaches to schema management:\n\n1. **Auto-migrate** (default in dev) — Dashboard changes auto-generate migration files in `pb_migrations\u002F`\n2. **Manual migrations** — write migration files by hand for full control\n\n## CLI Commands\n\n```bash\n# Create a new empty migration file\n.\u002Fpocketbase migrate create \"add_posts_collection\"\n# Creates: pb_migrations\u002F1234567890_add_posts_collection.js\n\n# Apply all pending migrations\n.\u002Fpocketbase migrate up\n\n# Revert the last applied migration\n.\u002Fpocketbase migrate down\n\n# Generate a full snapshot of all current collections\n.\u002Fpocketbase migrate collections\n# Creates a migration file that recreates all collections from scratch\n\n# Sync migration history with actual DB state (mark all as applied)\n.\u002Fpocketbase migrate history-sync\n```\n\n## Auto-migrate Mode\n\nEnabled by default. When you change collections in the Dashboard, PocketBase auto-generates migration files in `pb_migrations\u002F`.\n\n```bash\n# Start with auto-migrate (default)\n.\u002Fpocketbase serve\n\n# Disable auto-migrate (production)\n.\u002Fpocketbase serve --automigrate=0\n```\n\n**Workflow**:\n1. Develop with auto-migrate ON — use Dashboard to design schema\n2. Migration files are auto-generated in `pb_migrations\u002F`\n3. Commit these files to git\n4. Deploy: migrations run automatically on `serve` start\n5. In production: use `--automigrate=0` to prevent Dashboard changes from generating new migrations\n\n## Migration File Format\n\n```js\n\u002F\u002F pb_migrations\u002F1234567890_add_posts_collection.js\n\nmigrate(\n    \u002F\u002F UP — apply migration\n    function(app) {\n        var collection = new Collection({\n            name: \"posts\",\n            type: \"base\",\n            fields: [\n                { name: \"title\", type: \"text\", required: true },\n                { name: \"body\", type: \"editor\" },\n                { name: \"author\", type: \"relation\", collectionId: \"USERS_COLLECTION_ID\", cascadeDelete: false, maxSelect: 1, required: true },\n                { name: \"status\", type: \"select\", values: [\"draft\", \"published\", \"archived\"] },\n                { name: \"published_at\", type: \"date\" },\n                { name: \"tags\", type: \"relation\", collectionId: \"TAGS_COLLECTION_ID\", maxSelect: 0 }\n            ],\n            indexes: [\n                \"CREATE INDEX idx_posts_author ON posts (author)\",\n                \"CREATE INDEX idx_posts_status ON posts (status)\",\n                \"CREATE UNIQUE INDEX idx_posts_title ON posts (title)\"\n            ],\n            listRule: \"\",   \u002F\u002F WARNING: \"\" means public access — use a filter or null to restrict\n            viewRule: \"\",   \u002F\u002F WARNING: \"\" means public access — use a filter or null to restrict\n            createRule: \"@request.auth.id != ''\",\n            updateRule: \"author = @request.auth.id\",\n            deleteRule: \"author = @request.auth.id\"\n        })\n        app.save(collection)\n    },\n    \u002F\u002F DOWN — revert migration\n    function(app) {\n        var collection = app.findCollectionByNameOrId(\"posts\")\n        app.delete(collection)\n    }\n)\n```\n\n**Important**: the `app` inside migrations is a transactional instance. If any error occurs, the entire migration is rolled back.\n\n## Creating Collections Programmatically\n\n### Base collection\n\n```js\nvar collection = new Collection({\n    name: \"posts\",\n    type: \"base\",\n    fields: [\n        { name: \"title\", type: \"text\", required: true, min: 3, max: 200 },\n        { name: \"slug\", type: \"text\", required: true, autogenerate: { pattern: \"slugify(title)\" } },\n        { name: \"body\", type: \"editor\" },\n        { name: \"cover\", type: \"file\", maxSelect: 1, maxSize: 5242880, mimeTypes: [\"image\u002Fjpeg\", \"image\u002Fpng\", \"image\u002Fwebp\"] },\n        { name: \"views\", type: \"number\", min: 0 },\n        { name: \"metadata\", type: \"json\", maxSize: 2000000 },\n        { name: \"featured\", type: \"bool\" },\n        { name: \"published_at\", type: \"date\" }\n    ]\n})\napp.save(collection)\n```\n\n### Auth collection\n\n```js\nvar collection = new Collection({\n    name: \"users\",\n    type: \"auth\",\n    fields: [\n        { name: \"name\", type: \"text\", required: true },\n        { name: \"avatar\", type: \"file\", maxSelect: 1, maxSize: 5242880 },\n        { name: \"role\", type: \"select\", values: [\"user\", \"editor\", \"admin\"], required: true }\n    ],\n    passwordAuth: { enabled: true, identityFields: [\"email\", \"username\"] },\n    oauth2: { enabled: true },\n    otp: { enabled: false },\n    mfa: { enabled: false },\n    authToken: { duration: 604800 }  \u002F\u002F 7 days\n})\napp.save(collection)\n```\n\n### View collection\n\n```js\nvar collection = new Collection({\n    name: \"posts_stats\",\n    type: \"view\",\n    viewQuery: \"SELECT p.id, p.title, COUNT(c.id) as comments_count, p.views FROM posts p LEFT JOIN comments c ON c.post = p.id GROUP BY p.id\",\n    listRule: \"\",\n    viewRule: \"\"\n})\napp.save(collection)\n```\n\n## Modifying Existing Collections\n\n```js\nmigrate(function(app) {\n    var collection = app.findCollectionByNameOrId(\"posts\")\n\n    \u002F\u002F Add a new field\n    collection.fields.add({\n        name: \"subtitle\",\n        type: \"text\",\n        max: 500\n    })\n\n    \u002F\u002F Remove a field\n    collection.fields.removeByName(\"old_field\")\n\n    \u002F\u002F Update API rules\n    collection.listRule = \"@request.auth.id != ''\"\n    collection.viewRule = \"\"\n\n    \u002F\u002F Add index\n    collection.indexes.push(\"CREATE INDEX idx_posts_subtitle ON posts (subtitle)\")\n\n    app.save(collection)\n}, function(app) {\n    var collection = app.findCollectionByNameOrId(\"posts\")\n    collection.fields.removeByName(\"subtitle\")\n    app.save(collection)\n})\n```\n\n## Raw SQL in Migrations\n\n```js\nmigrate(function(app) {\n    app.db().newQuery(\"ALTER TABLE posts ADD COLUMN legacy_id TEXT DEFAULT ''\").execute()\n    app.db().newQuery(\"UPDATE posts SET legacy_id = id WHERE legacy_id = ''\").execute()\n}, function(app) {\n    app.db().newQuery(\"ALTER TABLE posts DROP COLUMN legacy_id\").execute()\n})\n```\n\n**Warning**: raw SQL bypasses PocketBase's schema cache. Run `migrate collections` afterward to re-sync if needed.\n\n## Settings & Superuser in Migrations\n\n### Initialize app settings\n\n```js\nonBootstrap(function(e) {\n    var settings = e.app.settings()\n    settings.meta.appName = \"My App\"\n    settings.meta.appURL = \"https:\u002F\u002Fmyapp.com\"\n    settings.meta.senderName = \"My App\"\n    settings.meta.senderAddress = \"noreply@myapp.com\"\n    settings.smtp.enabled = true\n    settings.smtp.host = \"smtp.example.com\"\n    settings.smtp.port = 587\n    settings.smtp.username = $os.getenv(\"SMTP_USER\")\n    settings.smtp.password = $os.getenv(\"SMTP_PASS\")\n    e.app.save(settings)\n    return e.next()\n})\n```\n\n### Create superuser in migration\n\n```js\nmigrate(function(app) {\n    var superusers = app.findCollectionByNameOrId(\"_superusers\")\n    var record = new Record(superusers)\n    \u002F\u002F IMPORTANT: always set PB_ADMIN_EMAIL and PB_ADMIN_PASSWORD env vars\n    var email = $os.getenv(\"PB_ADMIN_EMAIL\")\n    var password = $os.getenv(\"PB_ADMIN_PASSWORD\")\n    if (!email || !password) {\n        throw new Error(\"PB_ADMIN_EMAIL and PB_ADMIN_PASSWORD env vars are required\")\n    }\n    record.set(\"email\", email)\n    record.set(\"password\", password)\n    app.save(record)\n})\n```\n\n## Snapshot Migrations\n\n`.\u002Fpocketbase migrate collections` generates a complete snapshot — useful for:\n- Bootstrapping a new environment\n- Resetting migration history\n- Reviewing full schema in one file\n\nThe generated file uses `app.importCollections(collections)` which supports two modes:\n- **Default (merge\u002Fextend)**: adds new collections and fields, updates existing ones, doesn't delete anything\n- **Delete missing**: `app.importCollections(collections, true)` — deletes collections\u002Ffields not in the snapshot\n\n## `_migrations` Table\n\nPocketBase tracks applied migrations in the internal `_migrations` table:\n- `id` — auto-generated\n- `file` — migration filename\n- `applied` — timestamp\n\n`migrate history-sync` marks all existing migration files as applied without running them — useful when importing an existing database.\n\n## Best Practices\n\n1. **Dev**: use auto-migrate + Dashboard for schema design, commit generated files\n2. **Staging\u002FProd**: deploy with `--automigrate=0`, migrations run on startup\n3. **Always write DOWN migrations** — reversibility saves you when things go wrong\n4. **One concern per migration** — don't mix unrelated schema changes\n5. **Test migrations**: apply on a copy of production data before deploying\n6. **Use `migrate collections`** periodically to snapshot current state for documentation\n7. **Never edit applied migrations** — create a new migration to fix issues\n8. **Seed data**: prefer a dedicated migration for one-time initial data; if using `onBootstrap`, make the seed logic idempotent (existence checks\u002Fupserts) because bootstrap runs on every app start\n",{"name":5,"description":7},"main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fpocketbase\u002Fpb-migrations","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill \"PocketBase Migrations\"",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill \"PocketBase Migrations\"",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill \"PocketBase Migrations\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fpocketbase\u002Fpb-migrations\u002FSKILL.md",true,[],[46,53,62,69,76,83],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]