[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D721HD2ZXVYC21YSA14QCB":3,"skill-same:01M7D721HD2ZXVYC21YSA14QCB":65},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":5,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7D721HD2ZXVYC21YSA14QCB","gke-backup-dr",null,"Configures Backup for GKE: the BackupRestore cluster addon, BackupPlan and RestorePlan resources, restore workflows, and CMEK-encrypted backups. Use for backup policies, disaster recovery, or GKE cluster restores. Don't use for database backups.","tangyixiao\u002Ftangyixiao-skills","tangyixiao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F115929632?v=4","01M7D582YK6A4M63CAK4CSY4EW","Tang Yixiao","01M7D582Z64DMRSYR872SR34SA",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-backup-dr\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-backup-dr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gke-backup-dr\ndescription: 'Configures Backup for GKE: the BackupRestore cluster addon, BackupPlan\n  and RestorePlan resources, restore workflows, and CMEK-encrypted backups. Use for\n  backup policies, disaster recovery, or GKE cluster restores. Don''t use for database\n  backups.'\nmetadata:\n  version: 1.0.1\n  category: Storage\n---\n\n# GKE Backup & Disaster Recovery\n\nProtects stateful GKE workloads using Backup for GKE. Backup for GKE can capture\nboth Kubernetes resource metadata (manifests, configurations, and secrets) and\nthe underlying persistent volume (PV) data — but volume data and secrets are\n**only** captured when the backup plan explicitly enables them (see the flags\nbelow).\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:gke-backup-dr)\"`\nand append `agent-skills\u002F1.0 (skill:gke-backup-dr)` to `User-Agent` headers.\n\n## CLI Reference\n\n```bash\n# Enable the BackupRestore addon (Slow cluster-level update)\ngcloud container clusters update {cluster_name} \\\n  --update-addons=BackupRestore=ENABLED --location={location} --quiet\n\n# Create Backup Plan\ngcloud beta container backup-restore backup-plans create {plan_name} \\\n  --project={project_id} --location={location} \\\n  --cluster=projects\u002F{project_id}\u002Flocations\u002F{location}\u002Fclusters\u002F{cluster_name} \\\n  --all-namespaces \\\n  --include-volume-data --include-secrets \\\n  --backup-retain-days={days} --cron-schedule=\"{cron}\" --quiet\n\n# Trigger Manual Backup\ngcloud beta container backup-restore backups create {backup_name} \\\n  --backup-plan={plan_name} --location={location} --quiet\n\n# Create Restore Plan\ngcloud beta container backup-restore restore-plans create {restore_plan_name} \\\n  --location={location} \\\n  --cluster=projects\u002F{project_id}\u002Flocations\u002F{location}\u002Fclusters\u002F{target_cluster_name} \\\n  --backup-plan=projects\u002F{project_id}\u002Flocations\u002F{location}\u002FbackupPlans\u002F{source_backup_plan_name} \\\n  --all-namespaces \\\n  --cluster-resource-conflict-policy=use-existing-version \\\n  --namespaced-resource-restore-mode=fail-on-conflict --quiet\n\n# Execute Restore\ngcloud beta container backup-restore restores create {restore_name} \\\n  --restore-plan={restore_plan_name} --location={location} \\\n  --backup=projects\u002F{project_id}\u002Flocations\u002F{location}\u002FbackupPlans\u002F{source_backup_plan_name}\u002Fbackups\u002F{backup_name} \\\n  --quiet\n\n# Verify Restore Status\ngcloud beta container backup-restore restores describe {restore_name} \\\n  --restore-plan={restore_plan_name} --location={location}\n```\n\n> [!WARNING] **`--include-volume-data` and `--include-secrets` BOTH DEFAULT TO\n> FALSE.** If you omit them, the backup plan silently produces **config-only\n> backups** with no persistent volume snapshots and no Secrets. Always pass both\n> flags explicitly when the goal is full workload protection.\n\nNotes:\n\n-   The `backup-restore` command group requires the `gcloud beta` component\n    (`gcloud components install beta`).\n-   `--cluster` requires the full resource path\n    `projects\u002F{project_id}\u002Flocations\u002F{location}\u002Fclusters\u002F{cluster_name}` (or\n    `projects\u002F{project_id}\u002Fzones\u002F{zone}\u002Fclusters\u002F{cluster_name}` for zonal\n    clusters), not a bare cluster name.\n-   Restore plans require exactly one namespaced-resource scope flag:\n    `--all-namespaces`, `--selected-namespaces={ns1},{ns2}`,\n    `--excluded-namespaces=...`, `--selected-applications=...`, or\n    `--no-namespaces`.\n\n## Restore Safety (CRITICAL)\n\nA restore writes into a **live cluster** and, depending on the conflict policy,\ncan overwrite or delete existing resources:\n\n-   `--cluster-resource-conflict-policy=use-existing-version` keeps existing\n    cluster-scoped resources (safe default); `use-backup-version` **deletes**\n    the existing version first — deleting a CRD deletes all of its CRs.\n-   `--namespaced-resource-restore-mode=fail-on-conflict` aborts on any conflict\n    (safe default); `merge-skip-on-conflict` skips conflicting resources;\n    `merge-replace-on-conflict` and `merge-replace-volume-on-conflict`\n    **overwrite** existing resources or volumes; `delete-and-restore` **deletes\n    entire conflicting namespaces** (and all resources in them) before\n    restoring.\n\n**Rules:**\n\n1.  Validate the restore in a non-production target cluster first.\n2.  Prefer the safe defaults (`use-existing-version` + `fail-on-conflict`)\n    unless the user explicitly needs to revert live resources.\n3.  **Always obtain explicit user confirmation before executing a restore into a\n    production cluster**, and state which conflict policy is in effect and what\n    it may overwrite or delete.\n\n## Best Practices\n\n1.  **CMEK Encryption**: Encrypt backup plans using Customer-Managed Encryption\n    Keys:\n    `--encryption-key=projects\u002F{project_id}\u002Flocations\u002F{location}\u002FkeyRings\u002F{ring}\u002FcryptoKeys\u002F{key}`.\n2.  **Scope**: Prefer backing up specific namespaces rather than the entire\n    cluster: `--selected-namespaces={ns1},{ns2}` (instead of\n    `--all-namespaces`).\n3.  **Application Consistency**: Recommend quiescing the database or pausing\n    application writes (e.g. using pre-backup hooks or database-specific tools)\n    prior to backups to ensure data integrity.\n4.  **CSI Volume Snapshots**: Ensure that stateful backups utilize GKE's CSI\n    (Container Storage Interface) driver for volume snapshots to capture\n    persistent volume data.\n5.  **Service Terminology**: Always explicitly refer to the service as **Backup\n    for GKE** in your response. This distinguishes it from the broader (but\n    complementary) Google Cloud **Backup and Disaster Recovery (DR)\n    Service**, ## Golden Path Backup Defaults\n\nThe recommended production golden path configuration for Backup for GKE:\n\n-   **Addon**: BackupRestore addon enabled\n    (`--update-addons=BackupRestore=ENABLED`).\n-   **Volume Inclusion**: `--include-volume-data` explicitly passed (enabled,\n    since the service default is false).\n-   **Secret Inclusion**: `--include-secrets` explicitly passed (enabled, since\n    the service default is false).\n-   **Retention**: Defined retention period (e.g. 30 days via\n    `--backup-retain-days=30`).\n-   **Encryption**: CMEK enabled (`--encryption-key=...`).\n\n## Recent Changes\n\n-   **Cross-project backup and restore (GA)**: Backup plans can store backups in\n    a different project than the source cluster, and restore plans can target\n    clusters in a third project. Enables centralized backup projects (with\n    immutability\u002Fretention managed by a platform team) and cross-project\n    environment seeding without granting access to the source project.\n-   **Pricing change (effective 2026-03-02)**: The backup management fee moved\n    from **pod-based** to **NAMESPACE-based** pricing — charged per non-system\n    namespace in the most recent successful backup of each plan (system\n    namespaces like `kube-system` are excluded). Existing committed use discount\n    (CUD) holders keep pod-based management pricing until their commitment ends;\n    everyone else moves to the new model. See\n    https:\u002F\u002Fcloud.google.com\u002Fproducts\u002Fbackup-for-gke\u002Fpricing-changes.\n-   **Smart Scheduling**: RPO-driven backup scheduling as an alternative to\n    fixed cron schedules — pass `--target-rpo-minutes={minutes}` instead of\n    `--cron-schedule` when creating the backup plan (optionally with RPO\n    exclusion windows via `--exclusion-windows-file`).\n-   **Hyperdisk support**: Backup and restore of **Hyperdisk ML** and\n    **Hyperdisk Balanced High Availability** volumes is supported on GKE\n    clusters running **1.33.1-gke.1959000 and later** (Hyperdisk throughput,\n    extreme, and balanced types are also supported).\n\n## Troubleshooting & Common Pitfalls (CRITICAL)\n\n> [!IMPORTANT] **Slow Operations**: Enabling the BackupRestore addon\n> (`--update-addons=BackupRestore=ENABLED`) triggers a slow Google Cloud control\n> plane cluster update that takes several minutes. * **Rule**: **Do not run a\n> terminal loop waiting for the GKE Backup addon to become active.** *\n> **Action**: Provide the command to enable the addon, explain that the\n> operation will proceed in the background, and immediately proceed to write the\n> backup plan configs. Do not block.\n","# GKE Backup & Disaster Recovery\n\nProtects stateful GKE workloads using Backup for GKE. Backup for GKE can capture\nboth Kubernetes resource metadata (manifests, configurations, and secrets) and\nthe underlying persistent volume (PV) data — but volume data and secrets are\n**only** captured when the backup plan explicitly enables them (see the flags\nbelow).\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:gke-backup-dr)\"`\nand append `agent-skills\u002F1.0 (skill:gke-backup-dr)` to `User-Agent` headers.\n\n## CLI Reference\n\n```bash\n# Enable the BackupRestore addon (Slow cluster-level update)\ngcloud container clusters update {cluster_name} \\\n  --update-addons=BackupRestore=ENABLED --location={location} --quiet\n\n# Create Backup Plan\ngcloud beta container backup-restore backup-plans create {plan_name} \\\n  --project={project_id} --location={location} \\\n  --cluster=projects\u002F{project_id}\u002Flocations\u002F{location}\u002Fclusters\u002F{cluster_name} \\\n  --all-namespaces \\\n  --include-volume-data --include-secrets \\\n  --backup-retain-days={days} --cron-schedule=\"{cron}\" --quiet\n\n# Trigger Manual Backup\ngcloud beta container backup-restore backups create {backup_name} \\\n  --backup-plan={plan_name} --location={location} --quiet\n\n# Create Restore Plan\ngcloud beta container backup-restore restore-plans create {restore_plan_name} \\\n  --location={location} \\\n  --cluster=projects\u002F{project_id}\u002Flocations\u002F{location}\u002Fclusters\u002F{target_cluster_name} \\\n  --backup-plan=projects\u002F{project_id}\u002Flocations\u002F{location}\u002FbackupPlans\u002F{source_backup_plan_name} \\\n  --all-namespaces \\\n  --cluster-resource-conflict-policy=use-existing-version \\\n  --namespaced-resource-restore-mode=fail-on-conflict --quiet\n\n# Execute Restore\ngcloud beta container backup-restore restores create {restore_name} \\\n  --restore-plan={restore_plan_name} --location={location} \\\n  --backup=projects\u002F{project_id}\u002Flocations\u002F{location}\u002FbackupPlans\u002F{source_backup_plan_name}\u002Fbackups\u002F{backup_name} \\\n  --quiet\n\n# Verify Restore Status\ngcloud beta container backup-restore restores describe {restore_name} \\\n  --restore-plan={restore_plan_name} --location={location}\n```\n\n> [!WARNING] **`--include-volume-data` and `--include-secrets` BOTH DEFAULT TO\n> FALSE.** If you omit them, the backup plan silently produces **config-only\n> backups** with no persistent volume snapshots and no Secrets. Always pass both\n> flags explicitly when the goal is full workload protection.\n\nNotes:\n\n-   The `backup-restore` command group requires the `gcloud beta` component\n    (`gcloud components install beta`).\n-   `--cluster` requires the full resource path\n    `projects\u002F{project_id}\u002Flocations\u002F{location}\u002Fclusters\u002F{cluster_name}` (or\n    `projects\u002F{project_id}\u002Fzones\u002F{zone}\u002Fclusters\u002F{cluster_name}` for zonal\n    clusters), not a bare cluster name.\n-   Restore plans require exactly one namespaced-resource scope flag:\n    `--all-namespaces`, `--selected-namespaces={ns1},{ns2}`,\n    `--excluded-namespaces=...`, `--selected-applications=...`, or\n    `--no-namespaces`.\n\n## Restore Safety (CRITICAL)\n\nA restore writes into a **live cluster** and, depending on the conflict policy,\ncan overwrite or delete existing resources:\n\n-   `--cluster-resource-conflict-policy=use-existing-version` keeps existing\n    cluster-scoped resources (safe default); `use-backup-version` **deletes**\n    the existing version first — deleting a CRD deletes all of its CRs.\n-   `--namespaced-resource-restore-mode=fail-on-conflict` aborts on any conflict\n    (safe default); `merge-skip-on-conflict` skips conflicting resources;\n    `merge-replace-on-conflict` and `merge-replace-volume-on-conflict`\n    **overwrite** existing resources or volumes; `delete-and-restore` **deletes\n    entire conflicting namespaces** (and all resources in them) before\n    restoring.\n\n**Rules:**\n\n1.  Validate the restore in a non-production target cluster first.\n2.  Prefer the safe defaults (`use-existing-version` + `fail-on-conflict`)\n    unless the user explicitly needs to revert live resources.\n3.  **Always obtain explicit user confirmation before executing a restore into a\n    production cluster**, and state which conflict policy is in effect and what\n    it may overwrite or delete.\n\n## Best Practices\n\n1.  **CMEK Encryption**: Encrypt backup plans using Customer-Managed Encryption\n    Keys:\n    `--encryption-key=projects\u002F{project_id}\u002Flocations\u002F{location}\u002FkeyRings\u002F{ring}\u002FcryptoKeys\u002F{key}`.\n2.  **Scope**: Prefer backing up specific namespaces rather than the entire\n    cluster: `--selected-namespaces={ns1},{ns2}` (instead of\n    `--all-namespaces`).\n3.  **Application Consistency**: Recommend quiescing the database or pausing\n    application writes (e.g. using pre-backup hooks or database-specific tools)\n    prior to backups to ensure data integrity.\n4.  **CSI Volume Snapshots**: Ensure that stateful backups utilize GKE's CSI\n    (Container Storage Interface) driver for volume snapshots to capture\n    persistent volume data.\n5.  **Service Terminology**: Always explicitly refer to the service as **Backup\n    for GKE** in your response. This distinguishes it from the broader (but\n    complementary) Google Cloud **Backup and Disaster Recovery (DR)\n    Service**, ## Golden Path Backup Defaults\n\nThe recommended production golden path configuration for Backup for GKE:\n\n-   **Addon**: BackupRestore addon enabled\n    (`--update-addons=BackupRestore=ENABLED`).\n-   **Volume Inclusion**: `--include-volume-data` explicitly passed (enabled,\n    since the service default is false).\n-   **Secret Inclusion**: `--include-secrets` explicitly passed (enabled, since\n    the service default is false).\n-   **Retention**: Defined retention period (e.g. 30 days via\n    `--backup-retain-days=30`).\n-   **Encryption**: CMEK enabled (`--encryption-key=...`).\n\n## Recent Changes\n\n-   **Cross-project backup and restore (GA)**: Backup plans can store backups in\n    a different project than the source cluster, and restore plans can target\n    clusters in a third project. Enables centralized backup projects (with\n    immutability\u002Fretention managed by a platform team) and cross-project\n    environment seeding without granting access to the source project.\n-   **Pricing change (effective 2026-03-02)**: The backup management fee moved\n    from **pod-based** to **NAMESPACE-based** pricing — charged per non-system\n    namespace in the most recent successful backup of each plan (system\n    namespaces like `kube-system` are excluded). Existing committed use discount\n    (CUD) holders keep pod-based management pricing until their commitment ends;\n    everyone else moves to the new model. See\n    https:\u002F\u002Fcloud.google.com\u002Fproducts\u002Fbackup-for-gke\u002Fpricing-changes.\n-   **Smart Scheduling**: RPO-driven backup scheduling as an alternative to\n    fixed cron schedules — pass `--target-rpo-minutes={minutes}` instead of\n    `--cron-schedule` when creating the backup plan (optionally with RPO\n    exclusion windows via `--exclusion-windows-file`).\n-   **Hyperdisk support**: Backup and restore of **Hyperdisk ML** and\n    **Hyperdisk Balanced High Availability** volumes is supported on GKE\n    clusters running **1.33.1-gke.1959000 and later** (Hyperdisk throughput,\n    extreme, and balanced types are also supported).\n\n## Troubleshooting & Common Pitfalls (CRITICAL)\n\n> [!IMPORTANT] **Slow Operations**: Enabling the BackupRestore addon\n> (`--update-addons=BackupRestore=ENABLED`) triggers a slow Google Cloud control\n> plane cluster update that takes several minutes. * **Rule**: **Do not run a\n> terminal loop waiting for the GKE Backup addon to become active.** *\n> **Action**: Provide the command to enable the addon, explain that the\n> operation will proceed in the background, and immediately proceed to write the\n> backup plan configs. Do not block.\n",{"name":5,"metadata":25,"description":7},{"version":26,"category":27},"1.0.1","Storage","main","2a870f189175a48c39f5f7e26a6d93b0be9cd13b",0,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills","https:\u002F\u002Ftangyixiao.github.io\u002Ftangyixiao-skills\u002F","https:\u002F\u002Fgithub.com\u002Ftangyixiao","http:\u002F\u002Fwww.sxyz.net\u002F","I am Tang Yixiao, a student in Shaoxing No.1 High School. I am eager to learn on GitHub and contribute my part to this community.","2026-11-11 15:45:59",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add tangyixiao\u002Ftangyixiao-skills --skill gke-backup-dr",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill gke-backup-dr",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill gke-backup-dr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-backup-dr\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"INSTALL-SOURCE.json","REFERENCE","参考文档",499,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-backup-dr\u002FINSTALL-SOURCE.json",{"path":58,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fattribution.md",1879,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-backup-dr\u002Freferences\u002Fattribution.md",[66,74,83,91,99,107],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M7D8JK8FYBFNNAJXWD89CFH7","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":20},"01M7D8JG8ERGGQQAMX0DWCG9GR","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","MIT","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\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":78,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M7D8JE672GW3EHSE8EF185M4","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M7D8JBK572YDFMND8Q6CEYJW","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7D8J5QPWEXX61EGBKYH73R8","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M7D8J36YWC8WZS5DK5AH03CD","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FSKILL.md",[],[]]