[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AP8R86J5NVRBCWD5VX4W8H":3,"skill-same:01M7AP8R86J5NVRBCWD5VX4W8H":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},"01M7AP8R86J5NVRBCWD5VX4W8H","PocketBase API Rules",null,"API rules and filter expressions for PocketBase access control. Use when setting permissions, writing filter expressions, configuring who can access what, or debugging 403\u002F404 responses. Covers all 5 rule types, filter syntax, operators, request\u002Fcollection macros, and field modifiers.","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-api-rules\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"PocketBase API Rules\"\ndescription: \"API rules and filter expressions for PocketBase access control. Use when setting permissions, writing filter expressions, configuring who can access what, or debugging 403\u002F404 responses. Covers all 5 rule types, filter syntax, operators, request\u002Fcollection macros, and field modifiers.\"\n---\n\n# PocketBase API Rules & Filter Expressions\n\n## Rule Types\n\nEach collection has 5 rule types. Each rule is a **filter expression** that must evaluate to `true` for the request to proceed.\n\n| Rule | Controls | Locked = | Empty string = |\n|------|----------|----------|----------------|\n| **List** | `GET \u002Fapi\u002Fcollections\u002F{name}\u002Frecords` | superusers only | everyone can list |\n| **View** | `GET \u002Fapi\u002Fcollections\u002F{name}\u002Frecords\u002F{id}` | superusers only | everyone can view |\n| **Create** | `POST \u002Fapi\u002Fcollections\u002F{name}\u002Frecords` | superusers only | everyone can create |\n| **Update** | `PATCH \u002Fapi\u002Fcollections\u002F{name}\u002Frecords\u002F{id}` | superusers only | everyone can update |\n| **Delete** | `DELETE \u002Fapi\u002Fcollections\u002F{name}\u002Frecords\u002F{id}` | superusers only | everyone can delete |\n\n**Critical**: `null`\u002Flocked means only superusers can perform the action (regular users and guests are denied). Empty string `\"\"` means EVERYONE including guests. Superusers always bypass API rules entirely — see below.\n\n## Superuser Bypass\n\nSuperusers (formerly admins) **always bypass API rules**. Rules only apply to regular auth records and guests.\n\n## Filter Syntax\n\n### Operators\n\n| Operator | Meaning | Example |\n|----------|---------|---------|\n| `=` | Equal | `status = \"active\"` |\n| `!=` | Not equal | `status != \"draft\"` |\n| `>` | Greater than | `count > 5` |\n| `>=` | Greater or equal | `count >= 5` |\n| `\u003C` | Less than | `count \u003C 10` |\n| `\u003C=` | Less or equal | `count \u003C= 10` |\n| `~` | LIKE (contains) | `title ~ \"hello\"` |\n| `!~` | NOT LIKE | `title !~ \"spam\"` |\n| `?=` | Any\u002Fhas (array contains) | `tags ?= \"TAG_ID\"` |\n| `?!=` | None (array not contains) | `tags ?!= \"TAG_ID\"` |\n| `?>` | Any greater than | `scores ?> 90` |\n| `?>=` | Any greater or equal | `scores ?>= 90` |\n| `?\u003C` | Any less than | `scores ?\u003C 10` |\n| `?\u003C=` | Any less or equal | `scores ?\u003C= 10` |\n| `?~` | Any LIKE | `emails ?~ \"@gmail.com\"` |\n| `?!~` | Any NOT LIKE | `emails ?!~ \"@test.com\"` |\n\n**Critical**: use `?=` (not `=`) for multi-valued fields (multi-select, multi-relation, multi-file). `=` checks the raw JSON string, `?=` checks individual values.\n\n### Logical Operators\n\n```\nstatus = \"active\" && author = @request.auth.id\nstatus = \"active\" || status = \"featured\"\n```\n\nParentheses for grouping: `(a = 1 || b = 2) && c = 3`\n\n### Values\n\n- Strings: `\"value\"` or `'value'`\n- Numbers: `123`, `45.67`\n- Booleans: `true`, `false`\n- `null` — empty\u002Fmissing value\n- Identifiers: field names, macros\n\n## Request Macros (`@request.*`)\n\nAccess the current request context in rules:\n\n| Macro | Type | Description |\n|-------|------|-------------|\n| `@request.auth.id` | `string` | Current auth record ID (empty if guest) |\n| `@request.auth.email` | `string` | Current auth record email |\n| `@request.auth.verified` | `bool` | Whether email is verified |\n| `@request.auth.collectionId` | `string` | Auth collection ID |\n| `@request.auth.collectionName` | `string` | Auth collection name |\n| `@request.auth.*` | `any` | Any field from the auth record |\n| `@request.body.fieldName` | `any` | Field value from request body |\n| `@request.query.paramName` | `string` | URL query parameter |\n| `@request.headers.name` | `string` | Request header (lowercase key) |\n| `@request.method` | `string` | HTTP method (GET\u002FPOST\u002FPATCH\u002FDELETE) |\n\n### Auth record relations\n\nYou can traverse relations on the auth record:\n```\n@request.auth.team.owner = @request.auth.id\n```\n\n## Collection Macros (`@collection.*`)\n\nCross-collection lookups without explicit joins:\n\n```\n@collection.memberships.user ?= @request.auth.id &&\n@collection.memberships.team ?= team\n```\n\nThis checks if a record exists in the `memberships` collection where the user matches the current auth user and the team matches the current record's team field.\n\n**Note**: `@collection.*` performs an implicit EXISTS subquery. It's powerful but can be slow on large datasets — add indexes.\n\n## Field Modifiers\n\nUse in create\u002Fupdate rules to validate specific field behaviors:\n\n| Modifier | Works on | Description |\n|----------|----------|-------------|\n| `:isset` | `@request.body.*` | True if the field was sent in the request (even if empty) |\n| `:changed` | record field | True if the field value differs from current stored value (update only) |\n| `:length` | `string`\u002F`array` | Returns the length |\n| `:each` | `array` | Applies the condition to each element |\n| `:lower` | `string` | Lowercased value |\n\n### Examples\n\n```\n\u002F\u002F Only allow changing status if user is owner\nstatus:changed = false || author = @request.auth.id\n\n\u002F\u002F Prevent setting role on create\n@request.body.role:isset = false\n\n\u002F\u002F Require at least 2 tags\n@request.body.tags:length >= 2\n\n\u002F\u002F Check each tag is from allowed list\n@request.body.tags:each ?= @collection.allowed_tags.id\n```\n\n## Datetime Macros\n\n| Macro | Example output |\n|-------|----------------|\n| `@now` | `2024-01-15 10:30:00.000Z` |\n| `@second` | `2024-01-15 10:30:00.000Z` |\n| `@minute` | `2024-01-15 10:30:00.000Z` |\n| `@hour` | `2024-01-15 10:00:00.000Z` |\n| `@day` | `2024-01-15 00:00:00.000Z` |\n| `@month` | `2024-01-01 00:00:00.000Z` |\n| `@year` | `2024-01-01 00:00:00.000Z` |\n| `@todayStart` | `2024-01-15 00:00:00.000Z` |\n| `@todayEnd` | `2024-01-15 23:59:59.999Z` |\n| `@monthStart` | `2024-01-01 00:00:00.000Z` |\n| `@monthEnd` | `2024-01-31 23:59:59.999Z` |\n| `@yearStart` | `2024-01-01 00:00:00.000Z` |\n| `@yearEnd` | `2024-12-31 23:59:59.999Z` |\n\nArithmetic: `@now - 7d`, `@now + 1h`, `@now - 30m`\n\n## `geoDistance()`\n\nFor location-based filtering:\n\n```\ngeoDistance(lat, lon, 40.7128, -74.0060) \u003C= 10000\n```\n\nArguments: `geoDistance(latField, lonField, targetLat, targetLon)` — returns meters.\n\n## Common Patterns\n\n### Owner-only access\n```\n\u002F\u002F View\u002FUpdate\u002FDelete rule:\nauthor = @request.auth.id\n```\n\n### Authenticated users only\n```\n@request.auth.id != \"\"\n```\n\n### Verified users only\n```\n@request.auth.verified = true\n```\n\n### Role-based access\n```\n@request.auth.role = \"admin\" || author = @request.auth.id\n```\n\n### Team membership\n```\n@collection.team_members.user ?= @request.auth.id &&\n@collection.team_members.team ?= team\n```\n\n### Public read, owner write\n```\n\u002F\u002F List\u002FView: \"\"  (empty = everyone)\n\u002F\u002F Create: @request.auth.id != \"\"\n\u002F\u002F Update\u002FDelete: author = @request.auth.id\n```\n\n### Prevent field modification\n```\n\u002F\u002F Update rule: prevent changing `owner` after creation\nowner:changed = false\n```\n\n### Time-limited access\n```\nexpires > @now\n```\n","# PocketBase API Rules & Filter Expressions\n\n## Rule Types\n\nEach collection has 5 rule types. Each rule is a **filter expression** that must evaluate to `true` for the request to proceed.\n\n| Rule | Controls | Locked = | Empty string = |\n|------|----------|----------|----------------|\n| **List** | `GET \u002Fapi\u002Fcollections\u002F{name}\u002Frecords` | superusers only | everyone can list |\n| **View** | `GET \u002Fapi\u002Fcollections\u002F{name}\u002Frecords\u002F{id}` | superusers only | everyone can view |\n| **Create** | `POST \u002Fapi\u002Fcollections\u002F{name}\u002Frecords` | superusers only | everyone can create |\n| **Update** | `PATCH \u002Fapi\u002Fcollections\u002F{name}\u002Frecords\u002F{id}` | superusers only | everyone can update |\n| **Delete** | `DELETE \u002Fapi\u002Fcollections\u002F{name}\u002Frecords\u002F{id}` | superusers only | everyone can delete |\n\n**Critical**: `null`\u002Flocked means only superusers can perform the action (regular users and guests are denied). Empty string `\"\"` means EVERYONE including guests. Superusers always bypass API rules entirely — see below.\n\n## Superuser Bypass\n\nSuperusers (formerly admins) **always bypass API rules**. Rules only apply to regular auth records and guests.\n\n## Filter Syntax\n\n### Operators\n\n| Operator | Meaning | Example |\n|----------|---------|---------|\n| `=` | Equal | `status = \"active\"` |\n| `!=` | Not equal | `status != \"draft\"` |\n| `>` | Greater than | `count > 5` |\n| `>=` | Greater or equal | `count >= 5` |\n| `\u003C` | Less than | `count \u003C 10` |\n| `\u003C=` | Less or equal | `count \u003C= 10` |\n| `~` | LIKE (contains) | `title ~ \"hello\"` |\n| `!~` | NOT LIKE | `title !~ \"spam\"` |\n| `?=` | Any\u002Fhas (array contains) | `tags ?= \"TAG_ID\"` |\n| `?!=` | None (array not contains) | `tags ?!= \"TAG_ID\"` |\n| `?>` | Any greater than | `scores ?> 90` |\n| `?>=` | Any greater or equal | `scores ?>= 90` |\n| `?\u003C` | Any less than | `scores ?\u003C 10` |\n| `?\u003C=` | Any less or equal | `scores ?\u003C= 10` |\n| `?~` | Any LIKE | `emails ?~ \"@gmail.com\"` |\n| `?!~` | Any NOT LIKE | `emails ?!~ \"@test.com\"` |\n\n**Critical**: use `?=` (not `=`) for multi-valued fields (multi-select, multi-relation, multi-file). `=` checks the raw JSON string, `?=` checks individual values.\n\n### Logical Operators\n\n```\nstatus = \"active\" && author = @request.auth.id\nstatus = \"active\" || status = \"featured\"\n```\n\nParentheses for grouping: `(a = 1 || b = 2) && c = 3`\n\n### Values\n\n- Strings: `\"value\"` or `'value'`\n- Numbers: `123`, `45.67`\n- Booleans: `true`, `false`\n- `null` — empty\u002Fmissing value\n- Identifiers: field names, macros\n\n## Request Macros (`@request.*`)\n\nAccess the current request context in rules:\n\n| Macro | Type | Description |\n|-------|------|-------------|\n| `@request.auth.id` | `string` | Current auth record ID (empty if guest) |\n| `@request.auth.email` | `string` | Current auth record email |\n| `@request.auth.verified` | `bool` | Whether email is verified |\n| `@request.auth.collectionId` | `string` | Auth collection ID |\n| `@request.auth.collectionName` | `string` | Auth collection name |\n| `@request.auth.*` | `any` | Any field from the auth record |\n| `@request.body.fieldName` | `any` | Field value from request body |\n| `@request.query.paramName` | `string` | URL query parameter |\n| `@request.headers.name` | `string` | Request header (lowercase key) |\n| `@request.method` | `string` | HTTP method (GET\u002FPOST\u002FPATCH\u002FDELETE) |\n\n### Auth record relations\n\nYou can traverse relations on the auth record:\n```\n@request.auth.team.owner = @request.auth.id\n```\n\n## Collection Macros (`@collection.*`)\n\nCross-collection lookups without explicit joins:\n\n```\n@collection.memberships.user ?= @request.auth.id &&\n@collection.memberships.team ?= team\n```\n\nThis checks if a record exists in the `memberships` collection where the user matches the current auth user and the team matches the current record's team field.\n\n**Note**: `@collection.*` performs an implicit EXISTS subquery. It's powerful but can be slow on large datasets — add indexes.\n\n## Field Modifiers\n\nUse in create\u002Fupdate rules to validate specific field behaviors:\n\n| Modifier | Works on | Description |\n|----------|----------|-------------|\n| `:isset` | `@request.body.*` | True if the field was sent in the request (even if empty) |\n| `:changed` | record field | True if the field value differs from current stored value (update only) |\n| `:length` | `string`\u002F`array` | Returns the length |\n| `:each` | `array` | Applies the condition to each element |\n| `:lower` | `string` | Lowercased value |\n\n### Examples\n\n```\n\u002F\u002F Only allow changing status if user is owner\nstatus:changed = false || author = @request.auth.id\n\n\u002F\u002F Prevent setting role on create\n@request.body.role:isset = false\n\n\u002F\u002F Require at least 2 tags\n@request.body.tags:length >= 2\n\n\u002F\u002F Check each tag is from allowed list\n@request.body.tags:each ?= @collection.allowed_tags.id\n```\n\n## Datetime Macros\n\n| Macro | Example output |\n|-------|----------------|\n| `@now` | `2024-01-15 10:30:00.000Z` |\n| `@second` | `2024-01-15 10:30:00.000Z` |\n| `@minute` | `2024-01-15 10:30:00.000Z` |\n| `@hour` | `2024-01-15 10:00:00.000Z` |\n| `@day` | `2024-01-15 00:00:00.000Z` |\n| `@month` | `2024-01-01 00:00:00.000Z` |\n| `@year` | `2024-01-01 00:00:00.000Z` |\n| `@todayStart` | `2024-01-15 00:00:00.000Z` |\n| `@todayEnd` | `2024-01-15 23:59:59.999Z` |\n| `@monthStart` | `2024-01-01 00:00:00.000Z` |\n| `@monthEnd` | `2024-01-31 23:59:59.999Z` |\n| `@yearStart` | `2024-01-01 00:00:00.000Z` |\n| `@yearEnd` | `2024-12-31 23:59:59.999Z` |\n\nArithmetic: `@now - 7d`, `@now + 1h`, `@now - 30m`\n\n## `geoDistance()`\n\nFor location-based filtering:\n\n```\ngeoDistance(lat, lon, 40.7128, -74.0060) \u003C= 10000\n```\n\nArguments: `geoDistance(latField, lonField, targetLat, targetLon)` — returns meters.\n\n## Common Patterns\n\n### Owner-only access\n```\n\u002F\u002F View\u002FUpdate\u002FDelete rule:\nauthor = @request.auth.id\n```\n\n### Authenticated users only\n```\n@request.auth.id != \"\"\n```\n\n### Verified users only\n```\n@request.auth.verified = true\n```\n\n### Role-based access\n```\n@request.auth.role = \"admin\" || author = @request.auth.id\n```\n\n### Team membership\n```\n@collection.team_members.user ?= @request.auth.id &&\n@collection.team_members.team ?= team\n```\n\n### Public read, owner write\n```\n\u002F\u002F List\u002FView: \"\"  (empty = everyone)\n\u002F\u002F Create: @request.auth.id != \"\"\n\u002F\u002F Update\u002FDelete: author = @request.auth.id\n```\n\n### Prevent field modification\n```\n\u002F\u002F Update rule: prevent changing `owner` after creation\nowner:changed = false\n```\n\n### Time-limited access\n```\nexpires > @now\n```\n",{"name":5,"description":7},"main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fpocketbase\u002Fpb-api-rules","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 API Rules\"",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill \"PocketBase API Rules\"",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill \"PocketBase API Rules\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fpocketbase\u002Fpb-api-rules\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",[],[]]