[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMVD71KAXKYP7PS66FEG4V":3,"skill-same:01M6MMVD71KAXKYP7PS66FEG4V":95},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6MMVD71KAXKYP7PS66FEG4V","google-cloud-networking-observability",null,"Investigates Google Cloud networking issues by analyzing logs, metrics, and diagnostics. Use when investigating VPC Flow Logs, NAT, firewall, or threat logs, querying latency and throughput metrics, or running Connectivity Tests for path diagnostics.","arkhe-genesis\u002FArkhe-OS","arkhe-genesis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272629719?v=4","01M6KJDTSTJD2AD5RFPVZNGYCP","Rafael Oliveira","01M6KJDTXSTA997KDK184EA55A",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"google cloud","google cloud networking observability","networking","google","observability","cloud","for","tests","connectivity","latency","Analyzing Logs","threat","use","vpc","nat","firewall","flow","analyzing","logs","issues","2026-11-10 10:12:30",false,"---\nname: google-cloud-networking-observability\ndescription: >-\n  Investigates Google Cloud networking issues by analyzing logs, metrics, and diagnostics. Use when investigating VPC Flow Logs, NAT, firewall, or threat logs, querying latency and throughput metrics, or running Connectivity Tests for path diagnostics.\n---\n\n# Google Cloud Networking Observability Expert\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, and top talkers.\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-   **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:\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-   **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## 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## ? 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, and top talkers.\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-   **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:\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-   **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## 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,"description":7},"main","74cd3c4137064fdcde71ed9fe5c4bff58921d899",".agents\u002Fskills\u002Fgoogle-cloud-networking-observability",0,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS","https:\u002F\u002Fgithub.com\u002Farkhe-genesis","2026-11-08 09:08:55",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add arkhe-genesis\u002FArkhe-OS --skill google-cloud-networking-observability",{"tool":57,"command":58},"bunx","bunx skills add arkhe-genesis\u002FArkhe-OS --skill google-cloud-networking-observability",{"tool":60,"command":61},"pnpm","pnpm dlx skills add arkhe-genesis\u002FArkhe-OS --skill google-cloud-networking-observability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002FSKILL.md",true,[65,71,75,79,83,87,91],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fcloud-nat-analysis.md","REFERENCE","参考文档",2767,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fcloud-nat-analysis.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fconnectivity-tests.md",1411,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fconnectivity-tests.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Ffirewall-analysis.md",3080,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Ffirewall-analysis.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fmcp-usage.md",2617,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fmcp-usage.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fmetrics-analysis.md",3078,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fmetrics-analysis.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fthreat-analysis.md",5787,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fthreat-analysis.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fvpc-flow-analysis.md",4904,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgoogle-cloud-networking-observability\u002Freferences\u002Fvpc-flow-analysis.md",[96,119,137,159,182,201],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":39},"01M6MN97RPP1Q9BG489WHW70R8","career-ops","AI job search command center -- evaluate offers, generate CVs, scan portals, track applications","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.ai-integrations\u002Fvscode\u002F.claude\u002Fskills\u002Fcareer-ops\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"ops","career","career ops","track","applications","evaluate","mode","true","command center","cvs","scan","command","offers","Job Search","search","generate",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":39},"01M6MN93GFX8W9J1PCKDKZVD3N","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[126,127,31,128,129,130,131,132,110,133,134,135,136],"zoom out","zoom","how","context","code","it","perspective","re","you","with","understand",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":148,"publishedAt":39},"01M6MN8Y2ETBC91BGREF4D39JH","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[149,150,151,135,152,153,154,155,156,31,157,158],"write","write a skill","progressive disclosure","resources","new agent","structure","new skill","build","user","create",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":39},"01M6MN8RWE2V2PPFVPD0G8FHKF","triage","Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[165],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},[161,167,168,158,169,170,171,172,173,174,175,31,38,176,25,177,178,179,180,181],"bugs","state machine","requests","machine","feature","roles","issue workflow","manage","issue","state","feature requests","prepare","triage issues","workflow","review",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":193,"publishedAt":39},"01M6MN8KVDBD28672WMER7HPXM","to-prd","Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fto-prd\u002FSKILL.md",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":191,"taxonomyTypeDesc":192},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[194,195,31,157,129,196,158,175,197,131,198,199,200],"to prd","prd","publish","issue tracker","project","conversation","tracker",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":39},"01M6MN8E9CGYVWVDDR0NJEFDBB","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fto-issues\u002FSKILL.md",[],[38,208,209,198,210,211,197,212,213,200,175,214,31,157,215,216,217,195,158],"to issues","spec","down","break","break down","tickets","implementation","work","convert","plan"]