[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7HA7QY2G3FBYWYY4CW847":3,"skill-same:01M7D7HA7QY2G3FBYWYY4CW847":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},"01M7D7HA7QY2G3FBYWYY4CW847","google-cloud-waf-reliability",null,"Evaluates, designs, and improves the reliability, resilience, availability, fault tolerance, and disaster recovery (DR) of Google Cloud workloads based on the design principles and recommendations in the Reliability pillar of the Google Cloud Well-Architected Framework. Use when the user asks about reliability-related topics like workload uptime, designing for high availability (HA) or DR, setting and meeting RTO\u002FRPO targets, SRE best practices, backup strategies, multi-region failover, or fault-tolerant architecture on Google Cloud. Don't use for other Well-Architected Framework pillars such as Cost Optimization, Operational Excellence, or Security, or for hands-on resource deployment and live incident troubleshooting.","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\u002Fgoogle-cloud-waf-reliability\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-waf-reliability\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: google-cloud-waf-reliability\nmetadata:\n  version: 1.0.2\n  category: WellArchitectedFramework\ndescription: Evaluates, designs, and improves the reliability, resilience, availability,\n  fault tolerance, and disaster recovery (DR) of Google Cloud workloads based on the\n  design principles and recommendations in the Reliability pillar of the Google Cloud\n  Well-Architected Framework. Use when the user asks about reliability-related topics\n  like workload uptime, designing for high availability (HA) or DR, setting and meeting\n  RTO\u002FRPO targets, SRE best practices, backup strategies, multi-region failover, or\n  fault-tolerant architecture on Google Cloud. Don't use for other Well-Architected\n  Framework pillars such as Cost Optimization, Operational Excellence, or Security,\n  or for hands-on resource deployment and live incident troubleshooting.\n---\n\n# Google Cloud Well-Architected Framework skill for the Reliability pillar\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read and follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## Overview\n\nThe Reliability pillar of the Google Cloud Well-Architected Framework provides\nprinciples and recommendations to help you design, deploy, and manage reliable,\nresilient, and highly available workloads in Google Cloud. A reliable system\nconsistently performs its intended functions under defined conditions, is\nresilient to failures, and recovers gracefully from disruptions, thereby\nminimizing downtime, enhancing user experience, and ensuring data integrity.\n\n## Core principles\n\nThe recommendations in the reliability pillar of the Well-Architected Framework\nare aligned with the following core principles:\n\n-  **Define reliability based on user-experience goals**: Measurement of\n   reliability should reflect the actual experience of the system's users rather\n   than merely relying on infrastructure metrics. Focus on outcomes that matter\n   most to users. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fdefine-reliability-based-on-user-experience-goals.md.txt\n\n-   **Set realistic targets for reliability**: Determine appropriate Service\n    Level Objectives (SLOs) that balance the cost and complexity of maximizing\n    availability against business requirements. Provide guidance on defining\n    Service Level Objectives (SLOs) based on monitoring signals, error budgets,\n    and user experience goals. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fset-targets.md.txt\n\n-  **Build highly available systems through resource redundancy**: Eliminate\n   single points of failure by duplicating critical components across zones and\n   regions to maintain operations during localized outages. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fbuild-highly-available-systems.md.txt\n\n-   **Take advantage of horizontal scalability**: Design system architectures to\n    scale horizontally (adding more instances) to seamlessly accommodate load\n    fluctuations and improve overall fault tolerance. Incorporate proactive\n    capacity planning to monitor and adjust project quotas and resource\n    availability anticipating sudden load spikes. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fhorizontal-scalability.md.txt\n\n-   **Detect potential failures by using observability**: Implement thorough\n    monitoring, logging, and alerting systems to proactively detect, diagnose,\n    and address anomalies before they cause user-facing issues. Monitor the\n    golden signals (latency, traffic, errors, and saturation) and set up alerts\n    for when the signals cross specified thresholds. Use Cloud Monitoring to\n    build comprehensive dashboards for the golden signals. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fobservability.md.txt\n\n-   **Design for graceful degradation**: Architect systems to maintain critical\n    functionality, even if at reduced performance or with limited features, when\n    dependencies fail or the system experiences extreme stress. To avoid\n    cascading failures, recommend setting up alerts to detect failures early,\n    using the circuit-breaker pattern, handling timeouts effectively to release\n    blocked resources, utilizing retries with exponential backoff and jitter to\n    avoid overwhelming recovering backend systems, and returning custom error\n    responses or static fallback pages. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fgraceful-degradation.md.txt\n\n-  **Perform testing for recovery from failures**: Build confidence in system\n   resilience by continuously simulating failures and verifying the\n   effectiveness of automated and manual recovery procedures. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fperform-testing-for-recovery-from-failures.md.txt\n\n-  **Perform testing for recovery from data loss**: Regularly test backup and\n   restore protocols to ensure rapid recovery from data corruption or loss,\n   remaining within the defined Recovery Time Objective (RTO) and Recovery Point\n   Objective (RPO). Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fperform-testing-for-recovery-from-data-loss.md.txt\n\n-  **Conduct thorough postmortems**: Foster a blameless culture by investigating\n   outages comprehensively to understand root causes, followed by implementing\n   measures that prevent recurrence. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fconduct-postmortems.md.txt\n\n## Relevant Google Cloud products\n\nThe following are _examples_ of Google Cloud products and features that are\nrelevant to reliability:\n\n- **Compute**: Compute Engine Managed Instance Groups (MIGs), Google Kubernetes\n  Engine (GKE), Cloud Run\n- **Networking**: Cloud Load Balancing, Cloud CDN, Cloud DNS\n- **Storage and databases**: Cloud Storage (multi-region), Cloud SQL High\n  Availability, Spanner, Filestore, Firestore\n- **Operations**: Cloud Monitoring, Cloud Logging, Google Cloud Managed Service\n  for Prometheus\n- **Disaster recovery**: Backup and DR Service, Filestore backups\n\n## Workload assessment questions\n\nAsk appropriate questions to understand the reliability-related requirements and\nconstraints of the workload and the user's organization. Choose questions from\nthe following list:\n\n- How does your organization define and measure the reliability of your systems\n  in relation to user experience?\n- How does your organization approach setting reliability targets for your\n  services?\n- What is your organization's strategy for ensuring high availability through\n  resource redundancy?\n- How does your organization leverage horizontal scalability to maintain\n  performance and reliability?\n- How does your organization utilize observability (metrics, logs, traces) to\n  gain insights and detect potential failures?\n- How does your organization manage alerting based on observability data to\n  ensure timely responses to significant issues without causing alert fatigue?\n- What measures does your organization take to ensure systems can gracefully\n  degrade during high load or partial failures?\n- How frequently and comprehensively does your organization test for recovery\n  from system failures (e.g., regional failovers, release rollbacks)?\n- What is your organization's approach to testing for recovery from data loss?\n- How does your organization conduct and utilize postmortems after incidents?\n\n## Validation checklist\n\nUse the following checklist to evaluate the architecture's alignment with\nreliability recommendations:\n\n- User-focused SLIs and SLOs are explicitly defined and actively monitored.\n- The architecture avoids single points of failure through cross-zone or\n  cross-region redundancy.\n- Autoscaling is enabled to handle variable demand without manual intervention.\n- Application and infrastructure health checks are configured to trigger\n  automated failovers.\n- Regular backup schedules are in place, and restoration processes are routinely\n  tested.\n- The system architecture incorporates patterns like circuit breakers, retries\n  with exponential backoff, and rate limiting to support graceful degradation.\n- Game days or chaos engineering practices are regularly held to validate\n  failure recovery.\n- A formalized, blameless postmortem process exists to ensure organizational\n  learning from operational incidents.\n","# Google Cloud Well-Architected Framework skill for the Reliability pillar\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read and follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## Overview\n\nThe Reliability pillar of the Google Cloud Well-Architected Framework provides\nprinciples and recommendations to help you design, deploy, and manage reliable,\nresilient, and highly available workloads in Google Cloud. A reliable system\nconsistently performs its intended functions under defined conditions, is\nresilient to failures, and recovers gracefully from disruptions, thereby\nminimizing downtime, enhancing user experience, and ensuring data integrity.\n\n## Core principles\n\nThe recommendations in the reliability pillar of the Well-Architected Framework\nare aligned with the following core principles:\n\n-  **Define reliability based on user-experience goals**: Measurement of\n   reliability should reflect the actual experience of the system's users rather\n   than merely relying on infrastructure metrics. Focus on outcomes that matter\n   most to users. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fdefine-reliability-based-on-user-experience-goals.md.txt\n\n-   **Set realistic targets for reliability**: Determine appropriate Service\n    Level Objectives (SLOs) that balance the cost and complexity of maximizing\n    availability against business requirements. Provide guidance on defining\n    Service Level Objectives (SLOs) based on monitoring signals, error budgets,\n    and user experience goals. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fset-targets.md.txt\n\n-  **Build highly available systems through resource redundancy**: Eliminate\n   single points of failure by duplicating critical components across zones and\n   regions to maintain operations during localized outages. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fbuild-highly-available-systems.md.txt\n\n-   **Take advantage of horizontal scalability**: Design system architectures to\n    scale horizontally (adding more instances) to seamlessly accommodate load\n    fluctuations and improve overall fault tolerance. Incorporate proactive\n    capacity planning to monitor and adjust project quotas and resource\n    availability anticipating sudden load spikes. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fhorizontal-scalability.md.txt\n\n-   **Detect potential failures by using observability**: Implement thorough\n    monitoring, logging, and alerting systems to proactively detect, diagnose,\n    and address anomalies before they cause user-facing issues. Monitor the\n    golden signals (latency, traffic, errors, and saturation) and set up alerts\n    for when the signals cross specified thresholds. Use Cloud Monitoring to\n    build comprehensive dashboards for the golden signals. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fobservability.md.txt\n\n-   **Design for graceful degradation**: Architect systems to maintain critical\n    functionality, even if at reduced performance or with limited features, when\n    dependencies fail or the system experiences extreme stress. To avoid\n    cascading failures, recommend setting up alerts to detect failures early,\n    using the circuit-breaker pattern, handling timeouts effectively to release\n    blocked resources, utilizing retries with exponential backoff and jitter to\n    avoid overwhelming recovering backend systems, and returning custom error\n    responses or static fallback pages. Grounding document:\n    https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fgraceful-degradation.md.txt\n\n-  **Perform testing for recovery from failures**: Build confidence in system\n   resilience by continuously simulating failures and verifying the\n   effectiveness of automated and manual recovery procedures. Grounding\n   document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fperform-testing-for-recovery-from-failures.md.txt\n\n-  **Perform testing for recovery from data loss**: Regularly test backup and\n   restore protocols to ensure rapid recovery from data corruption or loss,\n   remaining within the defined Recovery Time Objective (RTO) and Recovery Point\n   Objective (RPO). Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fperform-testing-for-recovery-from-data-loss.md.txt\n\n-  **Conduct thorough postmortems**: Foster a blameless culture by investigating\n   outages comprehensively to understand root causes, followed by implementing\n   measures that prevent recurrence. Grounding document:\n   https:\u002F\u002Fdocs.cloud.google.com\u002Farchitecture\u002Fframework\u002Freliability\u002Fconduct-postmortems.md.txt\n\n## Relevant Google Cloud products\n\nThe following are _examples_ of Google Cloud products and features that are\nrelevant to reliability:\n\n- **Compute**: Compute Engine Managed Instance Groups (MIGs), Google Kubernetes\n  Engine (GKE), Cloud Run\n- **Networking**: Cloud Load Balancing, Cloud CDN, Cloud DNS\n- **Storage and databases**: Cloud Storage (multi-region), Cloud SQL High\n  Availability, Spanner, Filestore, Firestore\n- **Operations**: Cloud Monitoring, Cloud Logging, Google Cloud Managed Service\n  for Prometheus\n- **Disaster recovery**: Backup and DR Service, Filestore backups\n\n## Workload assessment questions\n\nAsk appropriate questions to understand the reliability-related requirements and\nconstraints of the workload and the user's organization. Choose questions from\nthe following list:\n\n- How does your organization define and measure the reliability of your systems\n  in relation to user experience?\n- How does your organization approach setting reliability targets for your\n  services?\n- What is your organization's strategy for ensuring high availability through\n  resource redundancy?\n- How does your organization leverage horizontal scalability to maintain\n  performance and reliability?\n- How does your organization utilize observability (metrics, logs, traces) to\n  gain insights and detect potential failures?\n- How does your organization manage alerting based on observability data to\n  ensure timely responses to significant issues without causing alert fatigue?\n- What measures does your organization take to ensure systems can gracefully\n  degrade during high load or partial failures?\n- How frequently and comprehensively does your organization test for recovery\n  from system failures (e.g., regional failovers, release rollbacks)?\n- What is your organization's approach to testing for recovery from data loss?\n- How does your organization conduct and utilize postmortems after incidents?\n\n## Validation checklist\n\nUse the following checklist to evaluate the architecture's alignment with\nreliability recommendations:\n\n- User-focused SLIs and SLOs are explicitly defined and actively monitored.\n- The architecture avoids single points of failure through cross-zone or\n  cross-region redundancy.\n- Autoscaling is enabled to handle variable demand without manual intervention.\n- Application and infrastructure health checks are configured to trigger\n  automated failovers.\n- Regular backup schedules are in place, and restoration processes are routinely\n  tested.\n- The system architecture incorporates patterns like circuit breakers, retries\n  with exponential backoff, and rate limiting to support graceful degradation.\n- Game days or chaos engineering practices are regularly held to validate\n  failure recovery.\n- A formalized, blameless postmortem process exists to ensure organizational\n  learning from operational incidents.\n",{"name":5,"metadata":25,"description":7},{"version":26,"category":27},"1.0.2","WellArchitectedFramework","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 google-cloud-waf-reliability",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill google-cloud-waf-reliability",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill google-cloud-waf-reliability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-waf-reliability\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"INSTALL-SOURCE.json","REFERENCE","参考文档",544,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-waf-reliability\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",1932,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-waf-reliability\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",[],[]]