[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D67SHH5EYYJFM1PVVJBVZP":3,"skill-same:01M7D67SHH5EYYJFM1PVVJBVZP":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},"01M7D67SHH5EYYJFM1PVVJBVZP","cloud-logging-cross-project-configuration",null,"Configure and troubleshoot Google Cloud cross-project centralized logging and read-time aggregation. Use when: - Setting up log routing from multiple projects\u002Ffolders\u002Forganizations to a central log bucket. - Creating cross-project log sinks and configuring central log buckets. - Troubleshooting cross-project routing. Don't use for single-project basic configurations.","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-logging-cross-project-configuration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-logging-cross-project-configuration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloud-logging-cross-project-configuration\ndescription: 'Configure and troubleshoot Google Cloud cross-project centralized logging\n  and read-time aggregation. Use when: - Setting up log routing from multiple projects\u002Ffolders\u002Forganizations\n  to a central log bucket. - Creating cross-project log sinks and configuring central\n  log buckets. - Troubleshooting cross-project routing. Don''t use for single-project\n  basic configurations.'\nmetadata:\n  version: 1.0.2\n  category: CloudObservabilityAndMonitoring\n---\n\n# Configuring Cross-Project Logging\n\nThis skill describes how to use `gcloud` commands to configure Cloud Logging so\nthat you store log data in a central location, regardless of the point of\norigin. The skill also describes how to query log data when that data is stored\nin multiple projects.\n\n> [!IMPORTANT] **Sandbox Network Limitation (CRITICAL for Agent Testing):**\n> During evaluation or in restricted sandboxed environments, network traffic to\n> GCP APIs is blocked. Do **NOT** run network discovery commands to find\n> resource names, project IDs, or organization IDs. Always use the exact project\n> IDs or placeholders provided in the user prompt or instructions, for example,\n> `{project_id}`, `{source_project_id}`, `{central_project_id}`. Assume these\n> resources exist and proceed directly with configuration commands. Running\n> these discovery commands will cause the execution to hang and timeout.\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-logging-cross-project-configuration)\"`\nand append `agent-skills\u002F1.0 (skill:cloud-logging-cross-project-configuration)` to `User-Agent` headers.\n\n## Safety and Confirmation Tiers (CRITICAL)\n\nBefore executing any commands on behalf of the user, you MUST adhere to the\nfollowing safety tiers based on the action requested:\n\n1.  **Tier R: Read-Only**\n    *   **Description:** Commands that only read state or query logs.\n    *   **Example commands:**\n        *   `gcloud logging read`\n        *   `gcloud logging buckets list`\n    *   **Rule:** No confirmation needed. You may execute these commands\n        immediately to gather information.\n2.  **Tier M: Mutation (Non-Billing)**\n    *   **Description:** Configuration modifications or free metadata creations\n        that do not incur direct storage or billing costs and do not affect\n        resource security\u002Faccess policies.\n    *   **Example commands:**\n        *   `gcloud logging views create`\n        *   `gcloud logging views update`\n        *   `gcloud logging scopes create`\n        *   `gcloud logging buckets create`\n    *   **Rule:** No confirmation needed. You may execute these commands\n        immediately to apply configurations.\n3.  **Tier B: Billing and Security-Sensitive Mutations (High-Risk)**\n    *   **Description:** Operations that create billing-inducing resources or\n        integrations, or modify security and IAM access control policies\n        (presenting a risk of privilege escalation).\n    *   **Example commands:**\n        *   `gcloud logging metrics create`\n        *   `gcloud logging links create`\n        *   `gcloud projects add-iam-policy-binding`\n    *   **Rule:** **Interactive confirmation required.** These commands create\n        resources that incur billing costs or alter security access. You MUST\n        present the exact, literal command and receive user confirmation before\n        executing. NEVER execute in the same turn as asking.\n4.  **Tier D: Causes irreversible data loss**\n    *   **Description:** Actions that permanently discard or delete logs, for\n        example sink exclusions.\n    *   **Example commands:**\n        *   `gcloud logging buckets delete`\n        *   `gcloud logging sinks update --add-exclusion`\n    *   **Rule:** **Explicit typed confirmation required.** These commands\n        discard or delete logs immediately and irreversibly, or they may result\n        in log data not being stored. You MUST ask for explicit typed\n        confirmation, for example, \"Yes, discard logs\", and halt execution until\n        the user replies.\n\n## Decision Matrix: Centralized Storage vs. Distributed Storage with Read-Time Aggregation\n\nUse this decision matrix to evaluate and choose between **Centralized Storage**\nand **Read-Time Aggregation**. With centralized storage, log data is routed to\none log bucket, regardless of where the data originates. You write queries\nagainst the centralized log bucket. With read-time aggregation, log data is\nstored by the resource where it originates. However, a single query aggregates\nthe data by querying all resources.\n\nAfter you have determined the optimal architecture for handling cross-project\nlogs, follow the corresponding configuration steps detailed below.\n\n| Criterion             | Centralized Storage      | Read-Time Aggregation    |\n| :-------------------- | :----------------------- | :----------------------- |\n| **GCP Project Scale** | Scales to thousands of   | Best for \u003C 375 projects. |\n:                       : projects.                :                          :\n| **Log Storage**       | Consolidated in a single | Resides in originating   |\n:                       : log bucket.              : resources.               :\n| **SQL Analytics**     | Easy; unified querying   | Hard; requires querying  |\n:                       : via Observability        : multiple log buckets.    :\n:                       : Analytics.               :                          :\n| **Access Control**    | Scoped access via log    | Requires IAM access to   |\n:                       : views on the centralized : all views on resources   :\n:                       : log bucket.              : that store log data.     :\n| **Configuration**     | Options vary based on    | Will not interfere with  |\n: **Complexity**        : Project, Folder,         : bucket-based log-based   :\n:                       : Organization structure.  : metrics.                 :\n| **Cost**              | Potential for duplicate  | Cost-effective; no data  |\n:                       : storage of log buckets   : replication.             :\n:                       : if exclusions aren't     :                          :\n:                       : set.                     :                          :\n\n## Architecture\n\n### Centralized Storage (Log Routing)\n\n```mermaid\ngraph LR\n    subgraph \"Source Project(s)\"\n        Log[Resource Logs] --> Sink[\"Sink: route-to-central-project\"]\n    end\n\n    subgraph \"Central Project\"\n        Sink --> Bucket[\"Bucket: central-logs-bucket (us-central1)\"]\n    end\n```\n\n### Read-Time Aggregation (Log Scopes)\n\n```mermaid\ngraph LR\n    subgraph \"Source Project 1\"\n        Log1[Resource Logs] --> Bucket1[\"Bucket: _Default\"]\n    end\n\n    subgraph \"Source Project 2\"\n        Log2[Resource Logs] --> Bucket2[\"Bucket: _Default\"]\n    end\n\n    subgraph \"Scoping Project (No Log Storage)\"\n        Scope[\"Log scope: central-query-scope\"]\n        Scope -.-> View1[\"_AllLogs View on Bucket1\"]\n        Scope -.-> View2[\"_AllLogs View on Bucket2\"]\n    end\n```\n\n## Setup Steps: Centralized Storage (Log Routing)\n\nUse these steps to route logs from one or more source projects to a central log\nbucket in a project. Create or select the Google Cloud project that you will use\nfor storing your log data. This is the central project.\n\n### 1. Create log bucket in central project (Tier M)\n\nCreate a custom log bucket with Log Analytics enabled.\n\n> [Tip] Use regional log buckets, for example, set the location to\n> `us-central1`. Don't use the `global` location. This approach ensures\n> compatibility with Observability Analytics and SQL querying.\n\n```bash\ngcloud logging buckets create {bucket_id} \\\n    --project={central_project_id} \\\n    --location={region} \\\n    --retention-days={retention_days} \\\n    --enable-analytics\n```\n\n### 2. Create log sink in central project (Tier M)\n\nCreate a project-level sink in the central project pointing to the central log\nbucket. This sink routes logs that land in the central project's Log Router into\nthe central log bucket.\n\nAssuming the newly created bucket is specifically for centralizing data from\nother projects (and the central project is not one of the source projects), the\ncentral sink should exclude the central project's own logs. Include the\n`_Required` audit log exclusions on this central sink to avoid redundancy\nbetween `{bucket_id}` and the `_Required` bucket.\n\n```bash\ngcloud logging sinks create {sink_name} \\\n    logging.googleapis.com\u002Fprojects\u002F{central_project_id}\u002Flocations\u002F{region}\u002Fbuckets\u002F{bucket_id} \\\n    --project={central_project_id} \\\n    --exclusion=filter='logName:\"projects\u002F{central_project_id}\u002F\"' \\\n    --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Factivity\")' \\\n    --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Factivity\")' \\\n    --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Fsystem_event\")' \\\n    --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Fsystem_event\")' \\\n    --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Faccess_transparency\")' \\\n    --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Faccess_transparency\")'\n```\n\n### 3. Create log sink in source resource (Tier M)\n\nTo route logs to the central project, you must create a log sink in each source\norganization, folder, or project. While you can configure a sink to route only a\nsubset of logs using the `--log-filter` argument, recommended practice is to\nroute all non-audit logs, and then restrict access or partition logs at the\ndestination using custom Log Views on the centralized log bucket.\n\n*   **For an organization-level log sink**\n\n    ```bash\n    gcloud logging sinks create {sink_name} \\\n        logging.googleapis.com\u002Fprojects\u002F{central_project_id} \\\n        --organization={source_organization_id} \\\n        --include-children \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Factivity\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Factivity\")' \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Fsystem_event\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Fsystem_event\")' \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Faccess_transparency\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Faccess_transparency\")'\n    ```\n\n*   **For project-level log sinks**\n\n    ```bash\n    gcloud logging sinks create {sink_name} \\\n        logging.googleapis.com\u002Fprojects\u002F{central_project_id} \\\n        --project={source_project_id} \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Factivity\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Factivity\")' \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Fsystem_event\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Fsystem_event\")' \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Faccess_transparency\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Faccess_transparency\")'\n    ```\n\n### 4. Grant IAM permissions to sink writers (Tier B)\n\n> [!IMPORTANT] **Security Action (Tier B):** Granting IAM permissions changes\n> access control policy and must be explicitly confirmed by the user before\n> execution.\n\nTo allow the source sinks to route logs to the central project's router, and to\nallow the central sink to write logs to the central bucket:\n\n1.  **Grant Logs Writer permission to the source sink:** Retrieve the\n    `writerIdentity` of the source log sink and grant it\n    `roles\u002Flogging.logWriter` on the central project.\n\n    ```bash\n    # Get the writer identity of the source sink\n    gcloud logging sinks describe {sink_name} \\\n        --project={source_project_id} \\\n        --format=\"value(writerIdentity)\"\n    ```\n\n    The output is the `{source_writer_identity}` value (for example\n    `serviceAccount:...`) for the following command:\n\n    ```bash\n    # Grant Logs Writer permissions on the central project\n    gcloud projects add-iam-policy-binding {central_project_id} \\\n        --member={source_writer_identity} \\\n        --role=roles\u002Flogging.logWriter\n    ```\n\n2.  **Grant Bucket Writer permission to the central sink:** Retrieve the\n    `writerIdentity` of the central log sink and grant it\n    `roles\u002Flogging.bucketWriter` on the central project.\n\n    ```bash\n    # Get the writer identity of the central sink\n    gcloud logging sinks describe {central_sink_name} \\\n        --project={central_project_id} \\\n        --format=\"value(writerIdentity)\"\n    ```\n\n    The output is the `{central_writer_identity}` value for the following\n    command:\n\n    ```bash\n    # Grant Bucket Writer permissions on the central project\n    gcloud projects add-iam-policy-binding {central_project_id} \\\n        --member={central_writer_identity} \\\n        --role=roles\u002Flogging.bucketWriter\n    ```\n\n### 5. Create custom Log Views on the central bucket (Tier M)\n\nTo partition logs or restrict access by log ID or project (since all logs were\nrouted to the same central bucket), create custom Log Views on the central\nbucket.\n\n*   **Filter by log ID:**\n\n    ```bash\n    gcloud logging views create {view_id} \\\n        --bucket={bucket_id} \\\n        --location={region} \\\n        --project={central_project_id} \\\n        --log-filter='LOG_ID(\"{log_id}\")'\n    ```\n\n*   **Filter by source project:**\n\n    ```bash\n    gcloud logging views create {view_id} \\\n        --bucket={bucket_id} \\\n        --location={region} \\\n        --project={central_project_id} \\\n        --log-filter='project_id=\"{source_project_id}\"'\n    ```\n\n### Verify Centralized Log Routing (Tier R)\n\nTo verify that logs are being routed from the source projects to the central\nregional log bucket:\n\n1.  **Write a test log in the source project:**\n\n    ```bash\n    gcloud logging write {test_log_id} \"Test log entry for verification\" \\\n        --severity=WARNING \\\n        --project={source_project_id}\n    ```\n\n2.  **Read the test log from the central log bucket:** For regional log buckets,\n    you **must** specify the `--view` flag. Because the default view `_Default`\n    only contains logs matching the default filter, you should query the\n    **`_AllLogs`** view or your custom log view on the central bucket:\n\n    ```bash\n    gcloud logging read 'logName:\"projects\u002F{source_project_id}\u002Flogs\u002F{test_log_id}\"' \\\n        --bucket={bucket_id} \\\n        --location={region} \\\n        --view=_AllLogs \\\n        --project={central_project_id}\n    ```\n\n--------------------------------------------------------------------------------\n\n## Setup Steps: Read-Time Aggregation (Log Scopes)\n\nCreate or select a Google Cloud project that you will use for querying your log\ndata. This is the scoping project. Use these steps to configure a log scope. Log\nscopes let you issue a query for log data that is stored in multiple projects.\n\n### 1. Create a custom Log View (Optional but recommended) (Tier M)\n\nCreate a Log View in the source project to restrict which logs are accessible.\n\n> [!IMPORTANT] **Gotcha:** Log View filters can only contain specific\n> restrictions. Refer to\n> https:\u002F\u002Fdocs.cloud.google.com\u002Flogging\u002Fdocs\u002Flogs-views.md.txt#view-filter\n\n```bash\ngcloud logging views create {view_id} \\\n    --bucket={bucket_id} \\\n    --location={region} \\\n    --project={source_project_id} \\\n    --log-filter='LOG_ID(\"{log_id}\")'\n```\n\n*   `{bucket_id}`: for example, `_Default`\n*   `{region}`: for example, `global`\n*   `{view_id}`: for example, `app-logs-view`\n*   If you want to allow access to all logs in the log bucket, omit the\n    `--log-filter` flag.\n\n### 2. Create a log scope in the scoping project (Tier M)\n\nCreate a log scope in the scoping project listing the source resources, which\nmay be projects or specific log views.\n\n```bash\ngcloud logging scopes create {log_scope_id} \\\n    --project={scoping_project_id} \\\n    --resource-names={resource_names}\n```\n\n*   `{log_scope_id}`: for example, `central-query-scope`\n*   `{resource_names}`: Comma-separated list of log views. For example,\n    `projects\u002Fsource-project-1\u002Flocations\u002Fglobal\u002Fbuckets\u002F_Default\u002Fviews\u002Fapp-logs-view,projects\u002Fsource-project-2\u002Flocations\u002Fglobal\u002Fbuckets\u002F_Default\u002Fviews\u002Fapp-logs-view`.\n    You can include up to 100 views in the scope.\n\n### 3. Update Default Observability Scope (Optional) (Tier M)\n\nLink the log scope to the project's default observability scope so it is used by\ndefault in Logs Explorer.\n\n```bash\ngcloud observability scopes update _Default \\\n    --project={scoping_project_id} \\\n    --location=global \\\n    --log-scope=\u002F\u002Flogging.googleapis.com\u002Fprojects\u002F{scoping_project_id}\u002Flocations\u002Fglobal\u002FlogScopes\u002F{log_scope_id}\n```\n\n### 4. Grant IAM permissions to users (Tier B)\n\nUnlike centralized routing, permissions are checked at query time on all source\nprojects. Users running queries must have:\n\n*   `roles\u002Flogging.viewAccessor` granted on the specific Log View (with IAM\n    conditions) or `roles\u002Flogging.viewer` on the source projects.\n*   Access to the scoping project.\n\n## Troubleshooting Cross-Project Log Routing and Sink Permission Failures\n\nIf logs are not appearing in a central project's bucket after configuring\ncentralized logging:\n\n### 1. Verify Log Router Sink Filters in Source Resource\n\n*   Ensure that the log sink's filter matches the logs you expect to route.\n\n    > [!IMPORTANT] **Gotcha:** Standard filter expressions like `logName:abc` or\n    > `logName=\"projects\u002F{project_id}\u002Flogs\u002Fabc\"` can fail to match in log sinks.\n    > **Always** use `LOG_ID(\"abc\")` for precise matching in log sink filters.\n\n*   Verify that you have not configured an exclusion filter that accidentally\n    discards these logs.\n\n### 2. Verify and Grant Writer Identity Permissions (Most Common Cause)\n\nThe log sink's writer identity service account in the source project must be\nexplicitly granted the necessary permissions on the central resource.\n\n*   **Step A: Get the Writer Identity**\n\n    ```bash\n    gcloud logging sinks describe {sink_name} \\\n        --project={source_project_id} \\\n        --format=\"value(writerIdentity)\"\n    ```\n\n*   **Step B: Grant the Permission in the Central Project (Tier B)**\n\n    > [!IMPORTANT] **Security Action (Tier B):** Granting IAM permissions\n    > changes access control policy and must be explicitly confirmed by the user\n    > before execution.\n\n    *   **For Cloud Logging Buckets (standard):** Grant\n        `roles\u002Flogging.bucketWriter`:\n\n        ```bash\n        gcloud projects add-iam-policy-binding {central_project_id} \\\n            --member={writer_identity} \\\n            --role=roles\u002Flogging.bucketWriter\n        ```\n\n    *   **For GCS Buckets:** Grant `roles\u002Fstorage.objectCreator` on the GCS\n        bucket.\n\n    *   **For Pub\u002FSub Topics:** Grant `roles\u002Fpubsub.publisher` on the Pub\u002FSub\n        topic.\n\n    *   **For BigQuery Datasets:** Grant `roles\u002Fbigquery.dataEditor` on the\n        BigQuery dataset.\n\n--------------------------------------------------------------------------------\n\n## References and Supporting Links\n\n*   [GCP Cloud Logging - Routing and Storage Overview](https:\u002F\u002Fdocs.cloud.google.com\u002Flogging\u002Fdocs\u002Frouting\u002Foverview.md.txt)\n*   [GCP Cloud Logging - Log Scopes](https:\u002F\u002Fdocs.cloud.google.com\u002Flogging\u002Fdocs\u002Flog-scope\u002Fcreate-and-manage.md.txt)\n*   [GCP Cloud Logging - Custom Log Views](https:\u002F\u002Fdocs.cloud.google.com\u002Flogging\u002Fdocs\u002Flogs-views.md.txt)\n","# Configuring Cross-Project Logging\n\nThis skill describes how to use `gcloud` commands to configure Cloud Logging so\nthat you store log data in a central location, regardless of the point of\norigin. The skill also describes how to query log data when that data is stored\nin multiple projects.\n\n> [!IMPORTANT] **Sandbox Network Limitation (CRITICAL for Agent Testing):**\n> During evaluation or in restricted sandboxed environments, network traffic to\n> GCP APIs is blocked. Do **NOT** run network discovery commands to find\n> resource names, project IDs, or organization IDs. Always use the exact project\n> IDs or placeholders provided in the user prompt or instructions, for example,\n> `{project_id}`, `{source_project_id}`, `{central_project_id}`. Assume these\n> resources exist and proceed directly with configuration commands. Running\n> these discovery commands will cause the execution to hang and timeout.\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-logging-cross-project-configuration)\"`\nand append `agent-skills\u002F1.0 (skill:cloud-logging-cross-project-configuration)` to `User-Agent` headers.\n\n## Safety and Confirmation Tiers (CRITICAL)\n\nBefore executing any commands on behalf of the user, you MUST adhere to the\nfollowing safety tiers based on the action requested:\n\n1.  **Tier R: Read-Only**\n    *   **Description:** Commands that only read state or query logs.\n    *   **Example commands:**\n        *   `gcloud logging read`\n        *   `gcloud logging buckets list`\n    *   **Rule:** No confirmation needed. You may execute these commands\n        immediately to gather information.\n2.  **Tier M: Mutation (Non-Billing)**\n    *   **Description:** Configuration modifications or free metadata creations\n        that do not incur direct storage or billing costs and do not affect\n        resource security\u002Faccess policies.\n    *   **Example commands:**\n        *   `gcloud logging views create`\n        *   `gcloud logging views update`\n        *   `gcloud logging scopes create`\n        *   `gcloud logging buckets create`\n    *   **Rule:** No confirmation needed. You may execute these commands\n        immediately to apply configurations.\n3.  **Tier B: Billing and Security-Sensitive Mutations (High-Risk)**\n    *   **Description:** Operations that create billing-inducing resources or\n        integrations, or modify security and IAM access control policies\n        (presenting a risk of privilege escalation).\n    *   **Example commands:**\n        *   `gcloud logging metrics create`\n        *   `gcloud logging links create`\n        *   `gcloud projects add-iam-policy-binding`\n    *   **Rule:** **Interactive confirmation required.** These commands create\n        resources that incur billing costs or alter security access. You MUST\n        present the exact, literal command and receive user confirmation before\n        executing. NEVER execute in the same turn as asking.\n4.  **Tier D: Causes irreversible data loss**\n    *   **Description:** Actions that permanently discard or delete logs, for\n        example sink exclusions.\n    *   **Example commands:**\n        *   `gcloud logging buckets delete`\n        *   `gcloud logging sinks update --add-exclusion`\n    *   **Rule:** **Explicit typed confirmation required.** These commands\n        discard or delete logs immediately and irreversibly, or they may result\n        in log data not being stored. You MUST ask for explicit typed\n        confirmation, for example, \"Yes, discard logs\", and halt execution until\n        the user replies.\n\n## Decision Matrix: Centralized Storage vs. Distributed Storage with Read-Time Aggregation\n\nUse this decision matrix to evaluate and choose between **Centralized Storage**\nand **Read-Time Aggregation**. With centralized storage, log data is routed to\none log bucket, regardless of where the data originates. You write queries\nagainst the centralized log bucket. With read-time aggregation, log data is\nstored by the resource where it originates. However, a single query aggregates\nthe data by querying all resources.\n\nAfter you have determined the optimal architecture for handling cross-project\nlogs, follow the corresponding configuration steps detailed below.\n\n| Criterion             | Centralized Storage      | Read-Time Aggregation    |\n| :-------------------- | :----------------------- | :----------------------- |\n| **GCP Project Scale** | Scales to thousands of   | Best for \u003C 375 projects. |\n:                       : projects.                :                          :\n| **Log Storage**       | Consolidated in a single | Resides in originating   |\n:                       : log bucket.              : resources.               :\n| **SQL Analytics**     | Easy; unified querying   | Hard; requires querying  |\n:                       : via Observability        : multiple log buckets.    :\n:                       : Analytics.               :                          :\n| **Access Control**    | Scoped access via log    | Requires IAM access to   |\n:                       : views on the centralized : all views on resources   :\n:                       : log bucket.              : that store log data.     :\n| **Configuration**     | Options vary based on    | Will not interfere with  |\n: **Complexity**        : Project, Folder,         : bucket-based log-based   :\n:                       : Organization structure.  : metrics.                 :\n| **Cost**              | Potential for duplicate  | Cost-effective; no data  |\n:                       : storage of log buckets   : replication.             :\n:                       : if exclusions aren't     :                          :\n:                       : set.                     :                          :\n\n## Architecture\n\n### Centralized Storage (Log Routing)\n\n```mermaid\ngraph LR\n    subgraph \"Source Project(s)\"\n        Log[Resource Logs] --> Sink[\"Sink: route-to-central-project\"]\n    end\n\n    subgraph \"Central Project\"\n        Sink --> Bucket[\"Bucket: central-logs-bucket (us-central1)\"]\n    end\n```\n\n### Read-Time Aggregation (Log Scopes)\n\n```mermaid\ngraph LR\n    subgraph \"Source Project 1\"\n        Log1[Resource Logs] --> Bucket1[\"Bucket: _Default\"]\n    end\n\n    subgraph \"Source Project 2\"\n        Log2[Resource Logs] --> Bucket2[\"Bucket: _Default\"]\n    end\n\n    subgraph \"Scoping Project (No Log Storage)\"\n        Scope[\"Log scope: central-query-scope\"]\n        Scope -.-> View1[\"_AllLogs View on Bucket1\"]\n        Scope -.-> View2[\"_AllLogs View on Bucket2\"]\n    end\n```\n\n## Setup Steps: Centralized Storage (Log Routing)\n\nUse these steps to route logs from one or more source projects to a central log\nbucket in a project. Create or select the Google Cloud project that you will use\nfor storing your log data. This is the central project.\n\n### 1. Create log bucket in central project (Tier M)\n\nCreate a custom log bucket with Log Analytics enabled.\n\n> [Tip] Use regional log buckets, for example, set the location to\n> `us-central1`. Don't use the `global` location. This approach ensures\n> compatibility with Observability Analytics and SQL querying.\n\n```bash\ngcloud logging buckets create {bucket_id} \\\n    --project={central_project_id} \\\n    --location={region} \\\n    --retention-days={retention_days} \\\n    --enable-analytics\n```\n\n### 2. Create log sink in central project (Tier M)\n\nCreate a project-level sink in the central project pointing to the central log\nbucket. This sink routes logs that land in the central project's Log Router into\nthe central log bucket.\n\nAssuming the newly created bucket is specifically for centralizing data from\nother projects (and the central project is not one of the source projects), the\ncentral sink should exclude the central project's own logs. Include the\n`_Required` audit log exclusions on this central sink to avoid redundancy\nbetween `{bucket_id}` and the `_Required` bucket.\n\n```bash\ngcloud logging sinks create {sink_name} \\\n    logging.googleapis.com\u002Fprojects\u002F{central_project_id}\u002Flocations\u002F{region}\u002Fbuckets\u002F{bucket_id} \\\n    --project={central_project_id} \\\n    --exclusion=filter='logName:\"projects\u002F{central_project_id}\u002F\"' \\\n    --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Factivity\")' \\\n    --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Factivity\")' \\\n    --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Fsystem_event\")' \\\n    --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Fsystem_event\")' \\\n    --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Faccess_transparency\")' \\\n    --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Faccess_transparency\")'\n```\n\n### 3. Create log sink in source resource (Tier M)\n\nTo route logs to the central project, you must create a log sink in each source\norganization, folder, or project. While you can configure a sink to route only a\nsubset of logs using the `--log-filter` argument, recommended practice is to\nroute all non-audit logs, and then restrict access or partition logs at the\ndestination using custom Log Views on the centralized log bucket.\n\n*   **For an organization-level log sink**\n\n    ```bash\n    gcloud logging sinks create {sink_name} \\\n        logging.googleapis.com\u002Fprojects\u002F{central_project_id} \\\n        --organization={source_organization_id} \\\n        --include-children \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Factivity\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Factivity\")' \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Fsystem_event\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Fsystem_event\")' \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Faccess_transparency\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Faccess_transparency\")'\n    ```\n\n*   **For project-level log sinks**\n\n    ```bash\n    gcloud logging sinks create {sink_name} \\\n        logging.googleapis.com\u002Fprojects\u002F{central_project_id} \\\n        --project={source_project_id} \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Factivity\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Factivity\")' \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Fsystem_event\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Fsystem_event\")' \\\n        --exclusion=filter='LOG_ID(\"cloudaudit.googleapis.com\u002Faccess_transparency\")' \\\n        --exclusion=filter='LOG_ID(\"externalaudit.googleapis.com\u002Faccess_transparency\")'\n    ```\n\n### 4. Grant IAM permissions to sink writers (Tier B)\n\n> [!IMPORTANT] **Security Action (Tier B):** Granting IAM permissions changes\n> access control policy and must be explicitly confirmed by the user before\n> execution.\n\nTo allow the source sinks to route logs to the central project's router, and to\nallow the central sink to write logs to the central bucket:\n\n1.  **Grant Logs Writer permission to the source sink:** Retrieve the\n    `writerIdentity` of the source log sink and grant it\n    `roles\u002Flogging.logWriter` on the central project.\n\n    ```bash\n    # Get the writer identity of the source sink\n    gcloud logging sinks describe {sink_name} \\\n        --project={source_project_id} \\\n        --format=\"value(writerIdentity)\"\n    ```\n\n    The output is the `{source_writer_identity}` value (for example\n    `serviceAccount:...`) for the following command:\n\n    ```bash\n    # Grant Logs Writer permissions on the central project\n    gcloud projects add-iam-policy-binding {central_project_id} \\\n        --member={source_writer_identity} \\\n        --role=roles\u002Flogging.logWriter\n    ```\n\n2.  **Grant Bucket Writer permission to the central sink:** Retrieve the\n    `writerIdentity` of the central log sink and grant it\n    `roles\u002Flogging.bucketWriter` on the central project.\n\n    ```bash\n    # Get the writer identity of the central sink\n    gcloud logging sinks describe {central_sink_name} \\\n        --project={central_project_id} \\\n        --format=\"value(writerIdentity)\"\n    ```\n\n    The output is the `{central_writer_identity}` value for the following\n    command:\n\n    ```bash\n    # Grant Bucket Writer permissions on the central project\n    gcloud projects add-iam-policy-binding {central_project_id} \\\n        --member={central_writer_identity} \\\n        --role=roles\u002Flogging.bucketWriter\n    ```\n\n### 5. Create custom Log Views on the central bucket (Tier M)\n\nTo partition logs or restrict access by log ID or project (since all logs were\nrouted to the same central bucket), create custom Log Views on the central\nbucket.\n\n*   **Filter by log ID:**\n\n    ```bash\n    gcloud logging views create {view_id} \\\n        --bucket={bucket_id} \\\n        --location={region} \\\n        --project={central_project_id} \\\n        --log-filter='LOG_ID(\"{log_id}\")'\n    ```\n\n*   **Filter by source project:**\n\n    ```bash\n    gcloud logging views create {view_id} \\\n        --bucket={bucket_id} \\\n        --location={region} \\\n        --project={central_project_id} \\\n        --log-filter='project_id=\"{source_project_id}\"'\n    ```\n\n### Verify Centralized Log Routing (Tier R)\n\nTo verify that logs are being routed from the source projects to the central\nregional log bucket:\n\n1.  **Write a test log in the source project:**\n\n    ```bash\n    gcloud logging write {test_log_id} \"Test log entry for verification\" \\\n        --severity=WARNING \\\n        --project={source_project_id}\n    ```\n\n2.  **Read the test log from the central log bucket:** For regional log buckets,\n    you **must** specify the `--view` flag. Because the default view `_Default`\n    only contains logs matching the default filter, you should query the\n    **`_AllLogs`** view or your custom log view on the central bucket:\n\n    ```bash\n    gcloud logging read 'logName:\"projects\u002F{source_project_id}\u002Flogs\u002F{test_log_id}\"' \\\n        --bucket={bucket_id} \\\n        --location={region} \\\n        --view=_AllLogs \\\n        --project={central_project_id}\n    ```\n\n--------------------------------------------------------------------------------\n\n## Setup Steps: Read-Time Aggregation (Log Scopes)\n\nCreate or select a Google Cloud project that you will use for querying your log\ndata. This is the scoping project. Use these steps to configure a log scope. Log\nscopes let you issue a query for log data that is stored in multiple projects.\n\n### 1. Create a custom Log View (Optional but recommended) (Tier M)\n\nCreate a Log View in the source project to restrict which logs are accessible.\n\n> [!IMPORTANT] **Gotcha:** Log View filters can only contain specific\n> restrictions. Refer to\n> https:\u002F\u002Fdocs.cloud.google.com\u002Flogging\u002Fdocs\u002Flogs-views.md.txt#view-filter\n\n```bash\ngcloud logging views create {view_id} \\\n    --bucket={bucket_id} \\\n    --location={region} \\\n    --project={source_project_id} \\\n    --log-filter='LOG_ID(\"{log_id}\")'\n```\n\n*   `{bucket_id}`: for example, `_Default`\n*   `{region}`: for example, `global`\n*   `{view_id}`: for example, `app-logs-view`\n*   If you want to allow access to all logs in the log bucket, omit the\n    `--log-filter` flag.\n\n### 2. Create a log scope in the scoping project (Tier M)\n\nCreate a log scope in the scoping project listing the source resources, which\nmay be projects or specific log views.\n\n```bash\ngcloud logging scopes create {log_scope_id} \\\n    --project={scoping_project_id} \\\n    --resource-names={resource_names}\n```\n\n*   `{log_scope_id}`: for example, `central-query-scope`\n*   `{resource_names}`: Comma-separated list of log views. For example,\n    `projects\u002Fsource-project-1\u002Flocations\u002Fglobal\u002Fbuckets\u002F_Default\u002Fviews\u002Fapp-logs-view,projects\u002Fsource-project-2\u002Flocations\u002Fglobal\u002Fbuckets\u002F_Default\u002Fviews\u002Fapp-logs-view`.\n    You can include up to 100 views in the scope.\n\n### 3. Update Default Observability Scope (Optional) (Tier M)\n\nLink the log scope to the project's default observability scope so it is used by\ndefault in Logs Explorer.\n\n```bash\ngcloud observability scopes update _Default \\\n    --project={scoping_project_id} \\\n    --location=global \\\n    --log-scope=\u002F\u002Flogging.googleapis.com\u002Fprojects\u002F{scoping_project_id}\u002Flocations\u002Fglobal\u002FlogScopes\u002F{log_scope_id}\n```\n\n### 4. Grant IAM permissions to users (Tier B)\n\nUnlike centralized routing, permissions are checked at query time on all source\nprojects. Users running queries must have:\n\n*   `roles\u002Flogging.viewAccessor` granted on the specific Log View (with IAM\n    conditions) or `roles\u002Flogging.viewer` on the source projects.\n*   Access to the scoping project.\n\n## Troubleshooting Cross-Project Log Routing and Sink Permission Failures\n\nIf logs are not appearing in a central project's bucket after configuring\ncentralized logging:\n\n### 1. Verify Log Router Sink Filters in Source Resource\n\n*   Ensure that the log sink's filter matches the logs you expect to route.\n\n    > [!IMPORTANT] **Gotcha:** Standard filter expressions like `logName:abc` or\n    > `logName=\"projects\u002F{project_id}\u002Flogs\u002Fabc\"` can fail to match in log sinks.\n    > **Always** use `LOG_ID(\"abc\")` for precise matching in log sink filters.\n\n*   Verify that you have not configured an exclusion filter that accidentally\n    discards these logs.\n\n### 2. Verify and Grant Writer Identity Permissions (Most Common Cause)\n\nThe log sink's writer identity service account in the source project must be\nexplicitly granted the necessary permissions on the central resource.\n\n*   **Step A: Get the Writer Identity**\n\n    ```bash\n    gcloud logging sinks describe {sink_name} \\\n        --project={source_project_id} \\\n        --format=\"value(writerIdentity)\"\n    ```\n\n*   **Step B: Grant the Permission in the Central Project (Tier B)**\n\n    > [!IMPORTANT] **Security Action (Tier B):** Granting IAM permissions\n    > changes access control policy and must be explicitly confirmed by the user\n    > before execution.\n\n    *   **For Cloud Logging Buckets (standard):** Grant\n        `roles\u002Flogging.bucketWriter`:\n\n        ```bash\n        gcloud projects add-iam-policy-binding {central_project_id} \\\n            --member={writer_identity} \\\n            --role=roles\u002Flogging.bucketWriter\n        ```\n\n    *   **For GCS Buckets:** Grant `roles\u002Fstorage.objectCreator` on the GCS\n        bucket.\n\n    *   **For Pub\u002FSub Topics:** Grant `roles\u002Fpubsub.publisher` on the Pub\u002FSub\n        topic.\n\n    *   **For BigQuery Datasets:** Grant `roles\u002Fbigquery.dataEditor` on the\n        BigQuery dataset.\n\n--------------------------------------------------------------------------------\n\n## References and Supporting Links\n\n*   [GCP Cloud Logging - Routing and Storage Overview](https:\u002F\u002Fdocs.cloud.google.com\u002Flogging\u002Fdocs\u002Frouting\u002Foverview.md.txt)\n*   [GCP Cloud Logging - Log Scopes](https:\u002F\u002Fdocs.cloud.google.com\u002Flogging\u002Fdocs\u002Flog-scope\u002Fcreate-and-manage.md.txt)\n*   [GCP Cloud Logging - Custom Log Views](https:\u002F\u002Fdocs.cloud.google.com\u002Flogging\u002Fdocs\u002Flogs-views.md.txt)\n",{"name":5,"metadata":25,"description":7},{"version":26,"category":27},"1.0.2","CloudObservabilityAndMonitoring","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-logging-cross-project-configuration",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill cloud-logging-cross-project-configuration",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill cloud-logging-cross-project-configuration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-logging-cross-project-configuration\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"INSTALL-SOURCE.json","REFERENCE","参考文档",583,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-logging-cross-project-configuration\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",1963,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcloud-logging-cross-project-configuration\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",[],[]]