[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7B3H43F21QC59N3PCMFES":3,"skill-same:01M7D7B3H43F21QC59N3PCMFES":97},{"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},"01M7D7B3H43F21QC59N3PCMFES","google-cloud-networking-observability",null,"Investigates Google Cloud networking issues by analyzing GCP logs, metrics, and diagnostics. Use when investigating dropped network traffic, packet drops, drop reasons, VPC Flow Logs (including Private Service Connect \u002F PSC, serverless \u002F App Engine Direct VPC, and cost estimation), NAT, firewall, or threat logs, querying latency and throughput metrics, or running Connectivity Tests for path diagnostics. Don't use for generic VM management or non-observability tasks.","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-networking-observability\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: google-cloud-networking-observability\nmetadata:\n  version: 1.0.6\n  category: Compute\ndescription: Investigates Google Cloud networking issues by analyzing GCP logs, metrics,\n  and diagnostics. Use when investigating dropped network traffic, packet drops, drop\n  reasons, VPC Flow Logs (including Private Service Connect \u002F PSC, serverless \u002F App\n  Engine Direct VPC, and cost estimation), NAT, firewall, or threat logs, querying\n  latency and throughput metrics, or running Connectivity Tests for path diagnostics.\n  Don't use for generic VM management or non-observability tasks.\n---\n\n# Google Cloud Networking Observability Expert\n\n## Attribution\n\nFor all `gcloud` CLI, REST API, and MCP attribution requirements when executing\ncommands with this skill, follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## 🛑 Core Directive: Results First\n\n1.  **Identify the Primary Source**: Quickly determine if the user needs\n    firewall logs, threat logs, Cloud NAT, VPC Flow logs, or metrics.\n2.  **Execute & Present**: Perform the minimum required query to get a direct\n    answer.\n3.  **Definitive Termination**: Once you identify the requested data, regardless\n    of the value (including 0, null, or \"No traffic\"), present the finding and\n    call the finish tool in the same turn. Do NOT attempt to find \"active\" or\n    \"busier\" resources to provide a \"better\" answer unless specifically\n    instructed to troubleshoot a resource that is expected to be busy.\n\n## Log & Telemetry Overview\n\n-   **Threat Logs**: Specialized logs from Cloud Firewall Plus and Cloud IDS\n    that identify malicious traffic patterns (for example, SQL injection or\n    malware) using deep packet inspection.\n-   **VPC Flow Logs**: Capture sample IP traffic to and from network interfaces.\n    Use for traffic analysis, volume trends, top talkers, dropped traffic, and\n    packet loss.\n-   **Firewall Logs**: Record connection attempts matched by firewall rules. Use\n    to identify \"DENY\" events or verify \"ALLOW\" rules.\n-   **Cloud NAT Logs**: Audit NAT translations. Use to audit traffic going\n    through NAT gateways or troubleshoot port exhaustion.\n-   **Networking Metrics**: Aggregated time-series data for throughput, RTT\n    (latency), and packet loss. Use for historical trends and performance\n    monitoring.\n-   **Connectivity Tests**: Static analysis tool for path diagnostics. Use to\n    identify firewall or routing misconfigurations between endpoints.\n\n## Procedures\n\n### 0. Log Source Preference\n\n-   **ALWAYS** check for BigQuery linked datasets (for example,\n    `big_query_linked_dataset`, `_AllLogs`) before using Cloud Logging for\n    high-volume analysis or aggregations. This is the preferred method for\n    finding trends or top-blocking rules.\n-   **Schema & Sample Discovery**: Before writing complex aggregations or filter\n    queries in BigQuery or Cloud Logging, first inspect a single sample log\n    record (`LIMIT 1` with `--format=json` in `bq query`, or `--limit=1` in\n    `gcloud logging read`) to verify the exact payload schema and field paths.\n-   **Metadata Awareness (BigQuery)**: Subnetworks may be configured with\n    `EXCLUDE_ALL_METADATA`, causing VM names to be NULL in VPC Flow Logs. If a\n    query by VM name returns nothing, retry using the internal IP address\n    (`jsonPayload.connection.src_ip`).\n\n### 1. Tool Selection & Discovery\n\n-   **MCP Servers First**: Use\n    [Cloud Monitoring MCP](references\u002Fmcp-usage.md#cloud-monitoring-mcp),\n    [BigQuery MCP](references\u002Fmcp-usage.md#bigquery-mcp), or\n    [Cloud Logging MCP](references\u002Fmcp-usage.md#cloud-logging-mcp).\n-   **Resource Discovery**: If a user-specified resource (for example, NAT\n    gateway, VPN tunnel) is not found in metrics\u002Flogs:\n    1.  Use `run_shell_command` with `gcloud` to list resources in the project.\n    2.  Search [Cloud Logging MCP](references\u002Fmcp-usage.md#cloud-logging-mcp)\n        for the resource name to find correct labels.\n-   **CLI Fallback**: Use `gcloud` or `bq` only if MCP servers are unavailable.\n    DO NOT use gcloud monitoring; it is restricted. Immediately use the curl\n    templates in [metrics-analysis.md](references\u002Fmetrics-analysis.md).\n\n### 2. Schema Verification & Error Recovery\n\nIf a BigQuery query fails with an 'Unrecognized name' error or schema mismatch:\n\n1. **Validate Schema**: Run `bq show --schema --format=json\n{project_id}:{dataset_id}.{table_id}` to verify field names and casing (for\nexample, `jsonPayload` versus `json_payload`). 2. **Dry Run**: Before executing\na corrected query, use `bq query --use_legacy_sql=false --dry_run\n\"{query_text}\"` to verify field references without incurring cost or execution\ntime. 3. **Retry**: Apply identified fixes to the original query and execute.\n\n### 3. Analysis Guides (Read Only When Needed)\n\nFor detailed SQL patterns, field definitions, and advanced troubleshooting, read\nthe corresponding reference file:\n\n-   **Threat Log Analysis**:\n    [references\u002Fthreat-analysis.md](references\u002Fthreat-analysis.md)\n-   **VPC Flow Analysis**:\n    [references\u002Fvpc-flow-analysis.md](references\u002Fvpc-flow-analysis.md)\n-   **VPC Flow Logs Cost Estimation**:\n    [references\u002Fvpc-flow-logs-cost-estimation.md](references\u002Fvpc-flow-logs-cost-estimation.md)\n-   **Cloud NAT Analysis**:\n    [references\u002Fcloud-nat-analysis.md](references\u002Fcloud-nat-analysis.md)\n-   **Firewall Rule Analysis**:\n    [references\u002Ffirewall-analysis.md](references\u002Ffirewall-analysis.md)\n-   **Networking Metrics**:\n    [references\u002Fmetrics-analysis.md](references\u002Fmetrics-analysis.md)\n-   **Connectivity Test Analysis**:\n    [references\u002Fconnectivity-tests.md](references\u002Fconnectivity-tests.md)\n\n> **CRITICAL**: If the user asks for **Cost Estimation**, you MUST strictly use\n> `references\u002Fvpc-flow-logs-cost-estimation.md`. Do NOT read or use\n> `references\u002Fvpc-flow-analysis.md` for cost estimation tasks.\n\n## Boundaries (CRITICAL)\n\n-   **ALWAYS** present the direct answer as soon as it is identified.\n-   **NEVER** run more than 2 exploratory queries before showing results.\n-   **NEVER** perform secondary verification (for example, don't check VPC flows\n    after finding a firewall block) without explicit user permission.\n-   **ALWAYS** print the generated SQL for review before execution.\n-   **ALWAYS** include a link to the Flow Analyzer in the\n    [Google Cloud Console](https:\u002F\u002Fconsole.cloud.google.com\u002Fnet-intelligence\u002Fflow-analyzer).\n-   **NEVER** query a second data source (such as, BigQuery logs) if the primary\n    source (for example, Cloud Monitoring metrics) has already provided a\n    conclusive answer. **DO NOT** compare metrics and logs to \"verify\" accuracy\n    unless the user specifically asks why they differ.\n-   **NO DISCREPANCY LOOPS**: If Tool A provides a result (such as, 80,000\n    counts) and Tool B provides a different result (for example, 1,000 counts),\n    **DO NOT** initiate a deep dive to explain the difference. Present the\n    result from the primary tool and STOP.\n-   **ALWAYS** perform time-range calculations (such as, \"12 hours ago\") during\n    the first turn to save steps.\n-   **Conclusive Acceptance of Inactivity**: Treat a result of \"0\", \"0 traffic\",\n    \"No data found\", or \"No records found\" as a conclusive finding for the\n    requested timeframe and resource. You MUST report this as the definitive\n    state and terminate immediately.\n-   **Standardized Discovery Path**: For all \"Top-N\" or volume-based discovery\n    tasks (for example, \"highest traffic,\" \"most hits,\" \"top talkers\"), you MUST\n    use BigQuery aggregation on _AllLogs datasets. Manual aggregation of\n    individual time-series points using the Monitoring API is forbidden due to\n    step inefficiency.\n-   **Ban on Auxiliary Scripting**: Execute all data retrieval and parsing logic\n    as direct tool calls (bq, curl, gcloud). Do NOT write or execute local shell\n    scripts (.sh) or python files, as these introduce avoidable environment and\n    permission errors that lead to investigation timeouts.\n-   **Discovery Efficiency**: For volume analysis (for example, \"how many\n    connections\" or \"top IPs by bytes\"), BigQuery aggregation on VPC Flow logs\n    (_AllLogs) is the **Primary Source of Truth**. If BigQuery data is\n    available, it is conclusive. Do NOT query Monitoring API to \"double check\"\n    BigQuery counts.\n","# Google Cloud Networking Observability Expert\n\n## Attribution\n\nFor all `gcloud` CLI, REST API, and MCP attribution requirements when executing\ncommands with this skill, follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## 🛑 Core Directive: Results First\n\n1.  **Identify the Primary Source**: Quickly determine if the user needs\n    firewall logs, threat logs, Cloud NAT, VPC Flow logs, or metrics.\n2.  **Execute & Present**: Perform the minimum required query to get a direct\n    answer.\n3.  **Definitive Termination**: Once you identify the requested data, regardless\n    of the value (including 0, null, or \"No traffic\"), present the finding and\n    call the finish tool in the same turn. Do NOT attempt to find \"active\" or\n    \"busier\" resources to provide a \"better\" answer unless specifically\n    instructed to troubleshoot a resource that is expected to be busy.\n\n## Log & Telemetry Overview\n\n-   **Threat Logs**: Specialized logs from Cloud Firewall Plus and Cloud IDS\n    that identify malicious traffic patterns (for example, SQL injection or\n    malware) using deep packet inspection.\n-   **VPC Flow Logs**: Capture sample IP traffic to and from network interfaces.\n    Use for traffic analysis, volume trends, top talkers, dropped traffic, and\n    packet loss.\n-   **Firewall Logs**: Record connection attempts matched by firewall rules. Use\n    to identify \"DENY\" events or verify \"ALLOW\" rules.\n-   **Cloud NAT Logs**: Audit NAT translations. Use to audit traffic going\n    through NAT gateways or troubleshoot port exhaustion.\n-   **Networking Metrics**: Aggregated time-series data for throughput, RTT\n    (latency), and packet loss. Use for historical trends and performance\n    monitoring.\n-   **Connectivity Tests**: Static analysis tool for path diagnostics. Use to\n    identify firewall or routing misconfigurations between endpoints.\n\n## Procedures\n\n### 0. Log Source Preference\n\n-   **ALWAYS** check for BigQuery linked datasets (for example,\n    `big_query_linked_dataset`, `_AllLogs`) before using Cloud Logging for\n    high-volume analysis or aggregations. This is the preferred method for\n    finding trends or top-blocking rules.\n-   **Schema & Sample Discovery**: Before writing complex aggregations or filter\n    queries in BigQuery or Cloud Logging, first inspect a single sample log\n    record (`LIMIT 1` with `--format=json` in `bq query`, or `--limit=1` in\n    `gcloud logging read`) to verify the exact payload schema and field paths.\n-   **Metadata Awareness (BigQuery)**: Subnetworks may be configured with\n    `EXCLUDE_ALL_METADATA`, causing VM names to be NULL in VPC Flow Logs. If a\n    query by VM name returns nothing, retry using the internal IP address\n    (`jsonPayload.connection.src_ip`).\n\n### 1. Tool Selection & Discovery\n\n-   **MCP Servers First**: Use\n    [Cloud Monitoring MCP](references\u002Fmcp-usage.md#cloud-monitoring-mcp),\n    [BigQuery MCP](references\u002Fmcp-usage.md#bigquery-mcp), or\n    [Cloud Logging MCP](references\u002Fmcp-usage.md#cloud-logging-mcp).\n-   **Resource Discovery**: If a user-specified resource (for example, NAT\n    gateway, VPN tunnel) is not found in metrics\u002Flogs:\n    1.  Use `run_shell_command` with `gcloud` to list resources in the project.\n    2.  Search [Cloud Logging MCP](references\u002Fmcp-usage.md#cloud-logging-mcp)\n        for the resource name to find correct labels.\n-   **CLI Fallback**: Use `gcloud` or `bq` only if MCP servers are unavailable.\n    DO NOT use gcloud monitoring; it is restricted. Immediately use the curl\n    templates in [metrics-analysis.md](references\u002Fmetrics-analysis.md).\n\n### 2. Schema Verification & Error Recovery\n\nIf a BigQuery query fails with an 'Unrecognized name' error or schema mismatch:\n\n1. **Validate Schema**: Run `bq show --schema --format=json\n{project_id}:{dataset_id}.{table_id}` to verify field names and casing (for\nexample, `jsonPayload` versus `json_payload`). 2. **Dry Run**: Before executing\na corrected query, use `bq query --use_legacy_sql=false --dry_run\n\"{query_text}\"` to verify field references without incurring cost or execution\ntime. 3. **Retry**: Apply identified fixes to the original query and execute.\n\n### 3. Analysis Guides (Read Only When Needed)\n\nFor detailed SQL patterns, field definitions, and advanced troubleshooting, read\nthe corresponding reference file:\n\n-   **Threat Log Analysis**:\n    [references\u002Fthreat-analysis.md](references\u002Fthreat-analysis.md)\n-   **VPC Flow Analysis**:\n    [references\u002Fvpc-flow-analysis.md](references\u002Fvpc-flow-analysis.md)\n-   **VPC Flow Logs Cost Estimation**:\n    [references\u002Fvpc-flow-logs-cost-estimation.md](references\u002Fvpc-flow-logs-cost-estimation.md)\n-   **Cloud NAT Analysis**:\n    [references\u002Fcloud-nat-analysis.md](references\u002Fcloud-nat-analysis.md)\n-   **Firewall Rule Analysis**:\n    [references\u002Ffirewall-analysis.md](references\u002Ffirewall-analysis.md)\n-   **Networking Metrics**:\n    [references\u002Fmetrics-analysis.md](references\u002Fmetrics-analysis.md)\n-   **Connectivity Test Analysis**:\n    [references\u002Fconnectivity-tests.md](references\u002Fconnectivity-tests.md)\n\n> **CRITICAL**: If the user asks for **Cost Estimation**, you MUST strictly use\n> `references\u002Fvpc-flow-logs-cost-estimation.md`. Do NOT read or use\n> `references\u002Fvpc-flow-analysis.md` for cost estimation tasks.\n\n## Boundaries (CRITICAL)\n\n-   **ALWAYS** present the direct answer as soon as it is identified.\n-   **NEVER** run more than 2 exploratory queries before showing results.\n-   **NEVER** perform secondary verification (for example, don't check VPC flows\n    after finding a firewall block) without explicit user permission.\n-   **ALWAYS** print the generated SQL for review before execution.\n-   **ALWAYS** include a link to the Flow Analyzer in the\n    [Google Cloud Console](https:\u002F\u002Fconsole.cloud.google.com\u002Fnet-intelligence\u002Fflow-analyzer).\n-   **NEVER** query a second data source (such as, BigQuery logs) if the primary\n    source (for example, Cloud Monitoring metrics) has already provided a\n    conclusive answer. **DO NOT** compare metrics and logs to \"verify\" accuracy\n    unless the user specifically asks why they differ.\n-   **NO DISCREPANCY LOOPS**: If Tool A provides a result (such as, 80,000\n    counts) and Tool B provides a different result (for example, 1,000 counts),\n    **DO NOT** initiate a deep dive to explain the difference. Present the\n    result from the primary tool and STOP.\n-   **ALWAYS** perform time-range calculations (such as, \"12 hours ago\") during\n    the first turn to save steps.\n-   **Conclusive Acceptance of Inactivity**: Treat a result of \"0\", \"0 traffic\",\n    \"No data found\", or \"No records found\" as a conclusive finding for the\n    requested timeframe and resource. You MUST report this as the definitive\n    state and terminate immediately.\n-   **Standardized Discovery Path**: For all \"Top-N\" or volume-based discovery\n    tasks (for example, \"highest traffic,\" \"most hits,\" \"top talkers\"), you MUST\n    use BigQuery aggregation on _AllLogs datasets. Manual aggregation of\n    individual time-series points using the Monitoring API is forbidden due to\n    step inefficiency.\n-   **Ban on Auxiliary Scripting**: Execute all data retrieval and parsing logic\n    as direct tool calls (bq, curl, gcloud). Do NOT write or execute local shell\n    scripts (.sh) or python files, as these introduce avoidable environment and\n    permission errors that lead to investigation timeouts.\n-   **Discovery Efficiency**: For volume analysis (for example, \"how many\n    connections\" or \"top IPs by bytes\"), BigQuery aggregation on VPC Flow logs\n    (_AllLogs) is the **Primary Source of Truth**. If BigQuery data is\n    available, it is conclusive. Do NOT query Monitoring API to \"double check\"\n    BigQuery counts.\n",{"name":5,"metadata":25,"description":7},{"version":26,"category":27},"1.0.6","Compute","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-networking-observability",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill google-cloud-networking-observability",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill google-cloud-networking-observability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002FSKILL.md",true,[51,57,61,65,69,73,77,81,85,89,93],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"INSTALL-SOURCE.json","REFERENCE","参考文档",571,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\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",1846,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fattribution.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fcloud-nat-analysis.md",2731,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fcloud-nat-analysis.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fconnectivity-tests.md",1411,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fconnectivity-tests.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Ffirewall-analysis.md",3094,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Ffirewall-analysis.md",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fmcp-usage.md",2617,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fmcp-usage.md",{"path":82,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fmetrics-analysis.md",3078,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fmetrics-analysis.md",{"path":86,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fthreat-analysis.md",5815,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fthreat-analysis.md",{"path":90,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fvpc-flow-analysis.md",6498,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fvpc-flow-analysis.md",{"path":94,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fvpc-flow-logs-cost-estimation.md",12124,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fvpc-flow-logs-cost-estimation.md",[98,106,115,123,131,139],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"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":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"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",[],[]]