[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D66J3VZXMJMNF978J33MD3":3,"skill-same:01M7D66J3VZXMJMNF978J33MD3":77},{"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},"01M7D66J3VZXMJMNF978J33MD3","cloud-build-basics",null,"Teaches the fundamentals of Cloud Build on Google Cloud. Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.","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\u002Fcloud-build-basics\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-build-basics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloud-build-basics\nmetadata:\n  version: 1.0.2\n  category: DevOps\ndescription: Teaches the fundamentals of Cloud Build on Google Cloud. Covers core\n  concepts, API enablement, console navigation to the Build History page, and the\n  end-to-end workflow for creating and manually running a basic build trigger. Do\n  not use for managing private pools or complex pipeline architectures.\n---\n\n# Cloud Build Basics\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:cloud-build-basics)\"`\nand append `agent-skills\u002F1.0 (skill:cloud-build-basics)` to `User-Agent` headers.\n\n## Prerequisites\n\nBefore starting, ensure the following prerequisites are met:\n\n1.  **Google Cloud SDK**: Ensure the [Google Cloud SDK](https:\u002F\u002Fcloud.google.com\u002Fsdk\u002Fdocs\u002Finstall) is installed and configured.\n2.  **Authentication**: Authenticate the gcloud CLI:\n    ```bash\n    gcloud auth login\n    gcloud auth application-default login\n    ```\n3.  **Project ID**: Know the target Google Cloud Project ID. Set the context:\n    ```bash\n    gcloud config set project \u003CPROJECT_ID>\n    ```\n4.  **Enable Cloud Build API**: The Cloud Build API must be enabled for the project.\n    ```bash\n    gcloud services enable cloudbuild.googleapis.com\n    ```\n5.  **Permissions**: Ensure the user or service account has the necessary permissions, such as `roles\u002Fcloudbuild.builds.editor` and `roles\u002Fserviceusage.serviceUsageAdmin` (to enable the API).\n\n## Core Concepts\n\nCloud Build (GCB) is a serverless platform that executes your builds on Google Cloud. It translates your source code into deployable artifacts, such as Docker containers or Java archives.\n\n| Concept | Description |\n| :--- | :--- |\n| **`cloudbuild.yaml`** | The required configuration file that defines the build steps. It is written in YAML or JSON. |\n| **Build Steps** | A sequence of actions (steps) GCB performs. Each step runs a command inside a specific Docker container (the builder). Common builders include `gcr.io\u002Fcloud-builders\u002Fgcloud`, `gcr.io\u002Fcloud-builders\u002Fdocker`, and custom containers. |\n| **Artifacts** | The output of the build, typically a container image pushed to Google Container Registry (GCR) or Artifact Registry (AR), or other deployable files. |\n| **Triggers** | Automation rules that invoke a build in response to an event, such as a push to a Git repository, a Pub\u002FSub message, or a manual request. |\n\n## Navigation: Viewing Build History\n\nThe Cloud Build Build History page is the central place to monitor the status of past and ongoing builds.\n\n1.  **Open the Cloud Console**: Navigate to the Google Cloud Console.\n2.  **Go to Cloud Build**: Use the search bar or the navigation menu to find **Cloud Build**.\n3.  **Select Build History**: In the left navigation pane, select **History** (or use the direct URL: `https:\u002F\u002Fconsole.cloud.google.com\u002Fcloud-build\u002Fbuilds`).\n4.  **Review Builds**:\n    *   **Status**: Check the status column (`SUCCESS`, `FAILURE`, `WORKING`, `QUEUED`).\n    *   **Region**: Use the region filter at the top to view builds that ran in a specific region (important for regional worker pools).\n    *   **Logs**: Click on a specific Build ID to view the detailed logs, execution steps, and build summary. This is crucial for debugging failed builds.\n\n> [!NOTE]\n> If this is your first time visiting the page, you might see the \"zero-state\" experience, which offers options to run a sample build or create your first trigger (as noted in the [`cb-list-build-zero-state`](references\u002Fcb-list-build-zero-state.md) skill). Note that region settings for triggers and builds are immutable after creation and must be chosen deliberately.\n\n## Creating a Basic Automated Trigger\n\nThis process defines an automation rule to run a build whenever code is pushed to a specified Git branch.\n\n### Step 1: Start Trigger Creation\n\n1.  Navigate to the **Cloud Build Triggers** page (`https:\u002F\u002Fconsole.cloud.google.com\u002Fcloud-build\u002Ftriggers`).\n2.  Click **Create trigger**.\n\n### Step 2: Configure Trigger Settings\n\n1.  **Name**: Provide a unique, descriptive name (e.g., `github-main-branch-build`).\n2.  **Region**: Select the region where the trigger configuration will be stored (e.g., `global` or a specific regional endpoint). **Note: Trigger and build region settings are immutable after creation and must be chosen deliberately.**\n3.  **Event**: Select the event type. For automated CI\u002FCD, select **Push to a branch**.\n4.  **Source**: Select the repository source:\n    *   **Repository**: Connect your source repository (GitHub, Bitbucket, Cloud Source Repositories, etc.). If needed, authorize the connection.\n    *   **Repository Name**: Select the specific repository you want to link.\n5.  **Branch**: Enter the branch pattern (e.g., `^main$` or `^develop`).\n\n### Step 3: Configure Build Settings\n\n1.  **Configuration**: Select **Cloud Build configuration file (yaml or json)**.\n2.  **Location**: Keep the default **Repository** and specify the path to your build configuration file (e.g., `cloudbuild.yaml`).\n    *   *Alternative*: For very simple builds, you can choose **Inline** to paste the YAML configuration directly into the trigger.\n3.  **(Optional) Service Account**: For production environments, select a dedicated service account with limited permissions to enforce the principle of least privilege.\n\n### Step 4: Save and Test\n\n1.  Click **Create**. The trigger is now active and will run automatically on the next matching Git push.\n\n> [!TIP]\n> The `cb-create-trigger` skill provides detailed `gcloud` commands for creating triggers across all types (GitHub, Pub\u002FSub, Webhook) and configurations (inline, Dockerfile, YAML). Use that skill for CLI automation.\n\n## Running an Existing Trigger Manually\n\nSometimes you need to run a trigger on demand, outside of its normal automation flow (e.g., to rebuild an old commit or test a new substitution).\n\n> [!IMPORTANT]\n> **Substitution Immutability**: You can only override values for substitution variables that are **already defined in the trigger configuration**. You cannot introduce new substitution variable keys at runtime.\n\n### Option A: Via the Cloud Console\n\n1.  Navigate to the **Cloud Build Triggers** page (`https:\u002F\u002Fconsole.cloud.google.com\u002Fcloud-build\u002Ftriggers`).\n2.  Locate the trigger you wish to run.\n3.  Click the vertical ellipsis (⋮) next to the trigger and select **Run**.\n4.  A dialog will appear, allowing you to specify:\n    *   **Source branch\u002Ftag**: Choose the specific Git reference to build from.\n    *   **Substitution Variables**: Override any existing substitution variables (e.g., set `_VERSION` to a new value).\n5.  Click **Run trigger**. The build will start immediately, and you can monitor its status on the **History** page.\n\n### Option B: Via the gcloud CLI\n\nUse the `gcloud builds triggers run` command to invoke the trigger and optionally override parameters.\n\n```bash\n# Run the trigger against the 'main' branch\ngcloud builds triggers run \u003CTRIGGER_NAME> \\\n    --region=\u003CREGION> \\\n    --branch=main\n\n# Run the trigger and override a substitution variable\ngcloud builds triggers run \u003CTRIGGER_NAME> \\\n    --region=\u003CREGION> \\\n    --branch=main \\\n    --substitutions=_IMAGE_TAG=\"20231027-manual\"\n\n# Monitor the initiated build\n# Note: The run command outputs the build ID. Use it to check status:\n# gcloud builds log \u003CBUILD_ID> --region=\u003CREGION>\n```\n\n> [!NOTE]\n> The `cb-run-trigger` skill provides more complex invocation examples, including running against a specific commit SHA or using tags.\n\n## Related Skills\n\n*   [`cb-create-trigger`](references\u002Fcb-create-trigger.md): Detailed CLI-focused instructions for creating all trigger types.\n*   [`cb-list-build-zero-state`](references\u002Fcb-list-build-zero-state.md): Advanced management of the Cloud Build dashboard and onboarding zero state.\n*   [`cb-run-trigger`](references\u002Fcb-run-trigger.md): Comprehensive guide to manually running triggers using various `gcloud` options.\n\n## External Resources & Documentation\n\n*   [Cloud Build Documentation](https:\u002F\u002Fcloud.google.com\u002Fbuild\u002Fdocs)\n*   [Cloud Build Configuration File Schema](https:\u002F\u002Fcloud.google.com\u002Fbuild\u002Fdocs\u002Fbuild-config-file-schema)\n*   [Automating Builds with Triggers](https:\u002F\u002Fcloud.google.com\u002Fbuild\u002Fdocs\u002Fautomating-builds\u002Fcreate-manage-triggers)\n*   [gcloud CLI builds Reference](https:\u002F\u002Fcloud.google.com\u002Fsdk\u002Fgcloud\u002Freference\u002Fbuilds)\n","# Cloud Build Basics\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:cloud-build-basics)\"`\nand append `agent-skills\u002F1.0 (skill:cloud-build-basics)` to `User-Agent` headers.\n\n## Prerequisites\n\nBefore starting, ensure the following prerequisites are met:\n\n1.  **Google Cloud SDK**: Ensure the [Google Cloud SDK](https:\u002F\u002Fcloud.google.com\u002Fsdk\u002Fdocs\u002Finstall) is installed and configured.\n2.  **Authentication**: Authenticate the gcloud CLI:\n    ```bash\n    gcloud auth login\n    gcloud auth application-default login\n    ```\n3.  **Project ID**: Know the target Google Cloud Project ID. Set the context:\n    ```bash\n    gcloud config set project \u003CPROJECT_ID>\n    ```\n4.  **Enable Cloud Build API**: The Cloud Build API must be enabled for the project.\n    ```bash\n    gcloud services enable cloudbuild.googleapis.com\n    ```\n5.  **Permissions**: Ensure the user or service account has the necessary permissions, such as `roles\u002Fcloudbuild.builds.editor` and `roles\u002Fserviceusage.serviceUsageAdmin` (to enable the API).\n\n## Core Concepts\n\nCloud Build (GCB) is a serverless platform that executes your builds on Google Cloud. It translates your source code into deployable artifacts, such as Docker containers or Java archives.\n\n| Concept | Description |\n| :--- | :--- |\n| **`cloudbuild.yaml`** | The required configuration file that defines the build steps. It is written in YAML or JSON. |\n| **Build Steps** | A sequence of actions (steps) GCB performs. Each step runs a command inside a specific Docker container (the builder). Common builders include `gcr.io\u002Fcloud-builders\u002Fgcloud`, `gcr.io\u002Fcloud-builders\u002Fdocker`, and custom containers. |\n| **Artifacts** | The output of the build, typically a container image pushed to Google Container Registry (GCR) or Artifact Registry (AR), or other deployable files. |\n| **Triggers** | Automation rules that invoke a build in response to an event, such as a push to a Git repository, a Pub\u002FSub message, or a manual request. |\n\n## Navigation: Viewing Build History\n\nThe Cloud Build Build History page is the central place to monitor the status of past and ongoing builds.\n\n1.  **Open the Cloud Console**: Navigate to the Google Cloud Console.\n2.  **Go to Cloud Build**: Use the search bar or the navigation menu to find **Cloud Build**.\n3.  **Select Build History**: In the left navigation pane, select **History** (or use the direct URL: `https:\u002F\u002Fconsole.cloud.google.com\u002Fcloud-build\u002Fbuilds`).\n4.  **Review Builds**:\n    *   **Status**: Check the status column (`SUCCESS`, `FAILURE`, `WORKING`, `QUEUED`).\n    *   **Region**: Use the region filter at the top to view builds that ran in a specific region (important for regional worker pools).\n    *   **Logs**: Click on a specific Build ID to view the detailed logs, execution steps, and build summary. This is crucial for debugging failed builds.\n\n> [!NOTE]\n> If this is your first time visiting the page, you might see the \"zero-state\" experience, which offers options to run a sample build or create your first trigger (as noted in the [`cb-list-build-zero-state`](references\u002Fcb-list-build-zero-state.md) skill). Note that region settings for triggers and builds are immutable after creation and must be chosen deliberately.\n\n## Creating a Basic Automated Trigger\n\nThis process defines an automation rule to run a build whenever code is pushed to a specified Git branch.\n\n### Step 1: Start Trigger Creation\n\n1.  Navigate to the **Cloud Build Triggers** page (`https:\u002F\u002Fconsole.cloud.google.com\u002Fcloud-build\u002Ftriggers`).\n2.  Click **Create trigger**.\n\n### Step 2: Configure Trigger Settings\n\n1.  **Name**: Provide a unique, descriptive name (e.g., `github-main-branch-build`).\n2.  **Region**: Select the region where the trigger configuration will be stored (e.g., `global` or a specific regional endpoint). **Note: Trigger and build region settings are immutable after creation and must be chosen deliberately.**\n3.  **Event**: Select the event type. For automated CI\u002FCD, select **Push to a branch**.\n4.  **Source**: Select the repository source:\n    *   **Repository**: Connect your source repository (GitHub, Bitbucket, Cloud Source Repositories, etc.). If needed, authorize the connection.\n    *   **Repository Name**: Select the specific repository you want to link.\n5.  **Branch**: Enter the branch pattern (e.g., `^main$` or `^develop`).\n\n### Step 3: Configure Build Settings\n\n1.  **Configuration**: Select **Cloud Build configuration file (yaml or json)**.\n2.  **Location**: Keep the default **Repository** and specify the path to your build configuration file (e.g., `cloudbuild.yaml`).\n    *   *Alternative*: For very simple builds, you can choose **Inline** to paste the YAML configuration directly into the trigger.\n3.  **(Optional) Service Account**: For production environments, select a dedicated service account with limited permissions to enforce the principle of least privilege.\n\n### Step 4: Save and Test\n\n1.  Click **Create**. The trigger is now active and will run automatically on the next matching Git push.\n\n> [!TIP]\n> The `cb-create-trigger` skill provides detailed `gcloud` commands for creating triggers across all types (GitHub, Pub\u002FSub, Webhook) and configurations (inline, Dockerfile, YAML). Use that skill for CLI automation.\n\n## Running an Existing Trigger Manually\n\nSometimes you need to run a trigger on demand, outside of its normal automation flow (e.g., to rebuild an old commit or test a new substitution).\n\n> [!IMPORTANT]\n> **Substitution Immutability**: You can only override values for substitution variables that are **already defined in the trigger configuration**. You cannot introduce new substitution variable keys at runtime.\n\n### Option A: Via the Cloud Console\n\n1.  Navigate to the **Cloud Build Triggers** page (`https:\u002F\u002Fconsole.cloud.google.com\u002Fcloud-build\u002Ftriggers`).\n2.  Locate the trigger you wish to run.\n3.  Click the vertical ellipsis (⋮) next to the trigger and select **Run**.\n4.  A dialog will appear, allowing you to specify:\n    *   **Source branch\u002Ftag**: Choose the specific Git reference to build from.\n    *   **Substitution Variables**: Override any existing substitution variables (e.g., set `_VERSION` to a new value).\n5.  Click **Run trigger**. The build will start immediately, and you can monitor its status on the **History** page.\n\n### Option B: Via the gcloud CLI\n\nUse the `gcloud builds triggers run` command to invoke the trigger and optionally override parameters.\n\n```bash\n# Run the trigger against the 'main' branch\ngcloud builds triggers run \u003CTRIGGER_NAME> \\\n    --region=\u003CREGION> \\\n    --branch=main\n\n# Run the trigger and override a substitution variable\ngcloud builds triggers run \u003CTRIGGER_NAME> \\\n    --region=\u003CREGION> \\\n    --branch=main \\\n    --substitutions=_IMAGE_TAG=\"20231027-manual\"\n\n# Monitor the initiated build\n# Note: The run command outputs the build ID. Use it to check status:\n# gcloud builds log \u003CBUILD_ID> --region=\u003CREGION>\n```\n\n> [!NOTE]\n> The `cb-run-trigger` skill provides more complex invocation examples, including running against a specific commit SHA or using tags.\n\n## Related Skills\n\n*   [`cb-create-trigger`](references\u002Fcb-create-trigger.md): Detailed CLI-focused instructions for creating all trigger types.\n*   [`cb-list-build-zero-state`](references\u002Fcb-list-build-zero-state.md): Advanced management of the Cloud Build dashboard and onboarding zero state.\n*   [`cb-run-trigger`](references\u002Fcb-run-trigger.md): Comprehensive guide to manually running triggers using various `gcloud` options.\n\n## External Resources & Documentation\n\n*   [Cloud Build Documentation](https:\u002F\u002Fcloud.google.com\u002Fbuild\u002Fdocs)\n*   [Cloud Build Configuration File Schema](https:\u002F\u002Fcloud.google.com\u002Fbuild\u002Fdocs\u002Fbuild-config-file-schema)\n*   [Automating Builds with Triggers](https:\u002F\u002Fcloud.google.com\u002Fbuild\u002Fdocs\u002Fautomating-builds\u002Fcreate-manage-triggers)\n*   [gcloud CLI builds Reference](https:\u002F\u002Fcloud.google.com\u002Fsdk\u002Fgcloud\u002Freference\u002Fbuilds)\n",{"name":5,"metadata":25,"description":7},{"version":26,"category":27},"1.0.2","DevOps","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 cloud-build-basics",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill cloud-build-basics",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill cloud-build-basics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-build-basics\u002FSKILL.md",true,[51,57,61,65,69,73],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"INSTALL-SOURCE.json","REFERENCE","参考文档",514,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-build-basics\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",1894,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-build-basics\u002Freferences\u002Fattribution.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fcb-create-trigger.md",11854,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-build-basics\u002Freferences\u002Fcb-create-trigger.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fcb-list-build-zero-state.md",7404,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-build-basics\u002Freferences\u002Fcb-list-build-zero-state.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fcb-run-trigger.md",6061,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-build-basics\u002Freferences\u002Fcb-run-trigger.md",[78,86,95,103,111,119],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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",[],[]]