[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XCWFBSYT3Q3C4A2C6Z7Z6W":3,"skill-same:01M6XCWFBSYT3Q3C4A2C6Z7Z6W":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6XCWFBSYT3Q3C4A2C6Z7Z6W","azure-bgp",null,"Analyze and resolve BGP oscillation and BGP route leaks in Azure Virtual WAN–style hub-and-spoke topologies (and similar cloud-managed BGP environments). Detect preference cycles, identify valley-free violations, and propose allowed policy-level mitigations while rejecting prohibited fixes.","Waaaalnut\u002Fskillsbench","Waaaalnut","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F103995656?v=4","01M6XCS9K1V51EY3JMB7DGMX24","01M6XCS9Q4WPW88W62C55G1H44",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks-no-skills\u002Fazure-bgp-oscillation-route-leak\u002Fenvironment\u002Fskills\u002Fazure-bgp\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"azure","azure bgp","bgp","cloud","analyze","virtual","hub","route","free","style","detect","azure virtual wan","environments","hub-and-spoke","fixes","managed","policy","2026-11-10 10:12:30",false,"---\nname: azure-bgp\ndescription: \"Analyze and resolve BGP oscillation and BGP route leaks in Azure Virtual WAN–style hub-and-spoke topologies (and similar cloud-managed BGP environments). Detect preference cycles, identify valley-free violations, and propose allowed policy-level mitigations while rejecting prohibited fixes.\"\n---\n\n# Azure BGP Oscillation & Route Leak Analysis\n\nAnalyze and resolve BGP oscillation and BGP route leaks in Azure Virtual WAN–style hub-and-spoke topologies (and similar cloud-managed BGP environments).\n\nThis skill trains an agent to:\n\n- Detect preference cycles that cause BGP oscillation\n- Identify valley-free violations that constitute route leaks\n- Propose allowed, policy-level mitigations (routing intent, export policy, communities, UDR, ingress filtering)\n- Reject prohibited fixes (disabling BGP, shutting down peering, removing connectivity)\n\nThe focus is cloud-correct reasoning, not on-prem router manipulation.\n\n## When to Use This Skill\n\nUse this skill when a task involves:\n\n- Azure Virtual WAN, hub-and-spoke BGP, ExpressRoute, or VPN gateways\n- Repeated route flapping or unstable path selection\n- Unexpected transit, leaked prefixes, or valley-free violations\n- Choosing between routing intent, UDRs, or BGP policy fixes\n- Evaluating whether a proposed \"fix\" is valid in Azure\n\n## Core Invariants (Must Never Be Violated)\n\nAn agent must internalize these constraints before reasoning:\n\n- ❌ BGP sessions between hubs **cannot** be administratively disabled by customers as it's owned by azure\n- ❌ Peering connections **cannot** be shut down as a fix as it break all other traffic running on the connections\n- ❌ Removing connectivity is **not** a valid solution as it break all other traffic running\n- ✅ Problems **must** be fixed using routing policy, not topology destruction\n\n**Any solution violating these rules is invalid.**\n\n## Expected Inputs\n\nTasks using this skill typically provide small JSON files:\n\n| File | Meaning |\n|------|---------|\n| `topology.json` | Directed BGP adjacency graph |\n| `relationships.json` | Economic relationship per edge (provider, customer, peer) |\n| `preferences.json` | Per-ASN preferred next hop (may cause oscillation) |\n| `route.json` | Prefix and origin ASN |\n| `route_leaks.json` | Evidence of invalid propagation |\n| `possible_solutions.json` | Candidate fixes to classify |\n\n## Reasoning Workflow (Executable Checklist)\n\n### Step 1 — Sanity-Check Inputs\n\n- Every ASN referenced must exist in `topology.json`\n- Relationship symmetry must hold:\n  - `provider(A→B)` ⇔ `customer(B→A)`\n  - `peer` must be symmetric\n- If this fails, the input is invalid.\n\n### Step 2 — Detect BGP Oscillation (Preference Cycle)\n\n**Definition**\n\nBGP oscillation exists if ASes form a preference cycle, often between peers.\n\n**Detection Rule**\n\n1. Build a directed graph: `ASN → preferred next-hop ASN`\n2. If the graph contains a cycle, oscillation is possible\n3. A 2-node cycle is sufficient to conclude oscillation.\n\n**Example pseudocode:**\n\n```python\npref = {asn: prefer_via_asn, ...}\n\ndef find_cycle(start):\n    path = []\n    seen = {}\n    cur = start\n    while cur in pref:\n        if cur in seen:\n            return path[seen[cur]:]  # cycle found\n        seen[cur] = len(path)\n        path.append(cur)\n        cur = pref[cur]\n    return None\n```\n\n### Step 3 — Detect BGP Route Leak (Valley-Free Violation)\n\n**Valley-Free Rule**\n\n| Learned from | May export to |\n|--------------|---------------|\n| Customer | Anyone |\n| Peer | Customers only |\n| Provider | Customers only |\n\n**Leak Conditions**\n\nA route leak exists if either is true:\n\n1. Route learned from a **provider** is exported to a **peer or provider**\n2. Route learned from a **peer** is exported to a **peer or provider**\n\n## Fix Selection Logic (Ranked)\n\n### Tier 1 — Virtual WAN Routing Intent (Preferred)\n\n**Applies to:**\n- ✔ Oscillation\n- ✔ Route leaks\n\n**Why it works:**\n\n- **Routing intent operates above BGP** — BGP still learns routes, but does not decide forwarding\n- **Forwarding becomes deterministic and policy-driven** — Intent policy overrides BGP path selection\n- **Decouples forwarding correctness from BGP stability** — Even if BGP oscillates, forwarding is stable\n\n**For oscillation:**\n- Breaks preference cycles by enforcing a single forwarding hierarchy\n- Even if both hubs prefer each other's routes, intent policy ensures traffic follows one path\n\n**For route leaks:**\n- Prevents leaked peer routes from being used as transit\n- When intent mandates hub-to-hub traffic goes through Virtual WAN (ASN 65001), leaked routes cannot be used\n- Enforces valley-free routing by keeping provider routes in proper hierarchy\n\n**Agent reasoning:**\nIf routing intent is available, recommend it first.\n\n### Tier 2 — Export \u002F Route Policy (Protocol-Correct)\n\n**For oscillation:**\n\n- **Filter routes learned from a peer before re-advertising** — Removes one edge of the preference cycle\n- **Why this works**: In a cycle where Hub A prefers routes via Hub B and vice versa, filtering breaks one \"leg\":\n  - If Hub A filters routes learned from Hub B before re-announcing, Hub B stops receiving routes via Hub A\n  - Hub B can no longer prefer the path through Hub A because it no longer exists\n  - The cycle collapses, routing stabilizes\n\n**Example:**\nIf vhubvnet1 (ASN 65002) filters routes learned from vhubvnet2 (ASN 65003) before re-advertising, vhubvnet2 stops receiving routes via vhubvnet1, breaking the oscillation cycle.\n\n**For route leaks:**\n\n- **Enforce valley-free export rules** — Prevent announcing provider\u002Fpeer-learned routes to peers\u002Fproviders\n- **Use communities** (e.g., `no-export`) where applicable\n- **Ingress filtering** — Reject routes with invalid AS_PATH from peers\n- **RPKI origin validation** — Cryptographically rejects BGP announcements from ASes that are not authorized to originate a given prefix, preventing many accidental and sub-prefix leaks from propagating\n\n**Limitation:**\nDoes not control forwarding if multiple valid paths remain.\n\n### Tier 3 — User Defined Routes (UDR)\n\n**Applies to:**\n- ✔ Oscillation\n- ✔ Route leaks\n\n**Purpose:**\nAuthoritative, static routing mechanism in Azure that explicitly defines the next hop for network traffic based on destination IP prefixes, overriding Azure system routes and BGP-learned routes.\n\n**Routing Behavior:**\nEnforces deterministic forwarding independent of BGP decision processes. UDRs operate at the data plane layer and take precedence over dynamic BGP routes.\n\n**For oscillation:**\n- **Oscillation Neutralization** — Breaks the impact of BGP preference cycles by imposing a fixed forwarding path\n- Even if vhubvnet1 and vhubvnet2 continue to flip-flop their route preferences, the UDR ensures traffic always goes to the same deterministic next hop\n\n**For route leaks:**\n- **Route Leak Mitigation** — Overrides leaked BGP routes by changing the effective next hop\n- When a UDR specifies a next hop (e.g., prefer specific Virtual WAN hub), traffic cannot follow leaked peer routes even if BGP has learned them\n- **Leaked Prefix Neutralization** — UDR's explicit next hop supersedes the leaked route's next hop, preventing unauthorized transit\n\n**Use when:**\n- Routing intent is unavailable\n- Immediate containment is required\n\n**Trade-off:**\nUDR is a data-plane fix that \"masks\" the control-plane issue. BGP may continue to have problems, but forwarding is stabilized. Prefer policy fixes (routing intent, export controls) when available for cleaner architecture.\n\n## Prohibited Fixes (Must Be Rejected)\n\nThese solutions are **always invalid**:\n\n| Proposed Fix | Reason |\n|--------------|--------|\n| Disable BGP | Not customer-controllable |\n| Disable peering | prohibited operation and cannot solve the issue |\n| Shutdown gateways | Breaks SLA \u002F shared control plane |\n| Restart devices | Resets symptoms only |\n\n**Required explanation:**\n\nCloud providers separate policy control from connectivity existence to protect shared infrastructure and SLAs.\n\n**Why these are not allowed in Azure:**\n\nBGP sessions and peering connections in Azure (Virtual WAN, ExpressRoute, VPN Gateway) **cannot be administratively shut down or disabled** by customers. This is a fundamental architectural constraint:\n\n1. **Shared control plane**: BGP and peering are part of Azure's provider-managed, SLA-backed control plane that operates at cloud scale.\n2. **Availability guarantees**: Azure's connectivity SLAs depend on these sessions remaining active.\n3. **Security boundaries**: Customers control routing **policy** (what routes are advertised\u002Faccepted) but not the existence of BGP sessions themselves.\n4. **Operational scale**: Managing BGP session state for thousands of customers requires automation that manual shutdown would undermine.\n\n**Correct approach**: Fix BGP issues through **policy changes** (route filters, preferences, export controls, communities) rather than disabling connectivity.\n\n## Common Pitfalls\n\n- ❌ **Timer tuning or dampening fixes oscillation** — False. These reduce symptoms but don't break preference cycles.\n- ❌ **Accepting fewer prefixes prevents route leaks** — False. Ingress filtering alone doesn't stop export of other leaked routes.\n- ❌ **Removing peers is a valid mitigation** — False. This is prohibited in Azure.\n- ❌ **Restarting gateways fixes root cause** — False. Only resets transient state.\n\nAll are false.\n\n## Output Expectations\n\nA correct solution should:\n\n1. Identify oscillation and\u002For route leak correctly\n2. Explain why it occurs (preference cycle or valley-free violation)\n3. Recommend allowed policy-level fixes\n4. Explicitly reject prohibited fixes with reasoning\n\n## References\n\n- RFC 4271 — Border Gateway Protocol 4 (BGP-4)\n- Gao–Rexford model — Valley-free routing economics\n","# Azure BGP Oscillation & Route Leak Analysis\n\nAnalyze and resolve BGP oscillation and BGP route leaks in Azure Virtual WAN–style hub-and-spoke topologies (and similar cloud-managed BGP environments).\n\nThis skill trains an agent to:\n\n- Detect preference cycles that cause BGP oscillation\n- Identify valley-free violations that constitute route leaks\n- Propose allowed, policy-level mitigations (routing intent, export policy, communities, UDR, ingress filtering)\n- Reject prohibited fixes (disabling BGP, shutting down peering, removing connectivity)\n\nThe focus is cloud-correct reasoning, not on-prem router manipulation.\n\n## When to Use This Skill\n\nUse this skill when a task involves:\n\n- Azure Virtual WAN, hub-and-spoke BGP, ExpressRoute, or VPN gateways\n- Repeated route flapping or unstable path selection\n- Unexpected transit, leaked prefixes, or valley-free violations\n- Choosing between routing intent, UDRs, or BGP policy fixes\n- Evaluating whether a proposed \"fix\" is valid in Azure\n\n## Core Invariants (Must Never Be Violated)\n\nAn agent must internalize these constraints before reasoning:\n\n- ❌ BGP sessions between hubs **cannot** be administratively disabled by customers as it's owned by azure\n- ❌ Peering connections **cannot** be shut down as a fix as it break all other traffic running on the connections\n- ❌ Removing connectivity is **not** a valid solution as it break all other traffic running\n- ✅ Problems **must** be fixed using routing policy, not topology destruction\n\n**Any solution violating these rules is invalid.**\n\n## Expected Inputs\n\nTasks using this skill typically provide small JSON files:\n\n| File | Meaning |\n|------|---------|\n| `topology.json` | Directed BGP adjacency graph |\n| `relationships.json` | Economic relationship per edge (provider, customer, peer) |\n| `preferences.json` | Per-ASN preferred next hop (may cause oscillation) |\n| `route.json` | Prefix and origin ASN |\n| `route_leaks.json` | Evidence of invalid propagation |\n| `possible_solutions.json` | Candidate fixes to classify |\n\n## Reasoning Workflow (Executable Checklist)\n\n### Step 1 — Sanity-Check Inputs\n\n- Every ASN referenced must exist in `topology.json`\n- Relationship symmetry must hold:\n  - `provider(A→B)` ⇔ `customer(B→A)`\n  - `peer` must be symmetric\n- If this fails, the input is invalid.\n\n### Step 2 — Detect BGP Oscillation (Preference Cycle)\n\n**Definition**\n\nBGP oscillation exists if ASes form a preference cycle, often between peers.\n\n**Detection Rule**\n\n1. Build a directed graph: `ASN → preferred next-hop ASN`\n2. If the graph contains a cycle, oscillation is possible\n3. A 2-node cycle is sufficient to conclude oscillation.\n\n**Example pseudocode:**\n\n```python\npref = {asn: prefer_via_asn, ...}\n\ndef find_cycle(start):\n    path = []\n    seen = {}\n    cur = start\n    while cur in pref:\n        if cur in seen:\n            return path[seen[cur]:]  # cycle found\n        seen[cur] = len(path)\n        path.append(cur)\n        cur = pref[cur]\n    return None\n```\n\n### Step 3 — Detect BGP Route Leak (Valley-Free Violation)\n\n**Valley-Free Rule**\n\n| Learned from | May export to |\n|--------------|---------------|\n| Customer | Anyone |\n| Peer | Customers only |\n| Provider | Customers only |\n\n**Leak Conditions**\n\nA route leak exists if either is true:\n\n1. Route learned from a **provider** is exported to a **peer or provider**\n2. Route learned from a **peer** is exported to a **peer or provider**\n\n## Fix Selection Logic (Ranked)\n\n### Tier 1 — Virtual WAN Routing Intent (Preferred)\n\n**Applies to:**\n- ✔ Oscillation\n- ✔ Route leaks\n\n**Why it works:**\n\n- **Routing intent operates above BGP** — BGP still learns routes, but does not decide forwarding\n- **Forwarding becomes deterministic and policy-driven** — Intent policy overrides BGP path selection\n- **Decouples forwarding correctness from BGP stability** — Even if BGP oscillates, forwarding is stable\n\n**For oscillation:**\n- Breaks preference cycles by enforcing a single forwarding hierarchy\n- Even if both hubs prefer each other's routes, intent policy ensures traffic follows one path\n\n**For route leaks:**\n- Prevents leaked peer routes from being used as transit\n- When intent mandates hub-to-hub traffic goes through Virtual WAN (ASN 65001), leaked routes cannot be used\n- Enforces valley-free routing by keeping provider routes in proper hierarchy\n\n**Agent reasoning:**\nIf routing intent is available, recommend it first.\n\n### Tier 2 — Export \u002F Route Policy (Protocol-Correct)\n\n**For oscillation:**\n\n- **Filter routes learned from a peer before re-advertising** — Removes one edge of the preference cycle\n- **Why this works**: In a cycle where Hub A prefers routes via Hub B and vice versa, filtering breaks one \"leg\":\n  - If Hub A filters routes learned from Hub B before re-announcing, Hub B stops receiving routes via Hub A\n  - Hub B can no longer prefer the path through Hub A because it no longer exists\n  - The cycle collapses, routing stabilizes\n\n**Example:**\nIf vhubvnet1 (ASN 65002) filters routes learned from vhubvnet2 (ASN 65003) before re-advertising, vhubvnet2 stops receiving routes via vhubvnet1, breaking the oscillation cycle.\n\n**For route leaks:**\n\n- **Enforce valley-free export rules** — Prevent announcing provider\u002Fpeer-learned routes to peers\u002Fproviders\n- **Use communities** (e.g., `no-export`) where applicable\n- **Ingress filtering** — Reject routes with invalid AS_PATH from peers\n- **RPKI origin validation** — Cryptographically rejects BGP announcements from ASes that are not authorized to originate a given prefix, preventing many accidental and sub-prefix leaks from propagating\n\n**Limitation:**\nDoes not control forwarding if multiple valid paths remain.\n\n### Tier 3 — User Defined Routes (UDR)\n\n**Applies to:**\n- ✔ Oscillation\n- ✔ Route leaks\n\n**Purpose:**\nAuthoritative, static routing mechanism in Azure that explicitly defines the next hop for network traffic based on destination IP prefixes, overriding Azure system routes and BGP-learned routes.\n\n**Routing Behavior:**\nEnforces deterministic forwarding independent of BGP decision processes. UDRs operate at the data plane layer and take precedence over dynamic BGP routes.\n\n**For oscillation:**\n- **Oscillation Neutralization** — Breaks the impact of BGP preference cycles by imposing a fixed forwarding path\n- Even if vhubvnet1 and vhubvnet2 continue to flip-flop their route preferences, the UDR ensures traffic always goes to the same deterministic next hop\n\n**For route leaks:**\n- **Route Leak Mitigation** — Overrides leaked BGP routes by changing the effective next hop\n- When a UDR specifies a next hop (e.g., prefer specific Virtual WAN hub), traffic cannot follow leaked peer routes even if BGP has learned them\n- **Leaked Prefix Neutralization** — UDR's explicit next hop supersedes the leaked route's next hop, preventing unauthorized transit\n\n**Use when:**\n- Routing intent is unavailable\n- Immediate containment is required\n\n**Trade-off:**\nUDR is a data-plane fix that \"masks\" the control-plane issue. BGP may continue to have problems, but forwarding is stabilized. Prefer policy fixes (routing intent, export controls) when available for cleaner architecture.\n\n## Prohibited Fixes (Must Be Rejected)\n\nThese solutions are **always invalid**:\n\n| Proposed Fix | Reason |\n|--------------|--------|\n| Disable BGP | Not customer-controllable |\n| Disable peering | prohibited operation and cannot solve the issue |\n| Shutdown gateways | Breaks SLA \u002F shared control plane |\n| Restart devices | Resets symptoms only |\n\n**Required explanation:**\n\nCloud providers separate policy control from connectivity existence to protect shared infrastructure and SLAs.\n\n**Why these are not allowed in Azure:**\n\nBGP sessions and peering connections in Azure (Virtual WAN, ExpressRoute, VPN Gateway) **cannot be administratively shut down or disabled** by customers. This is a fundamental architectural constraint:\n\n1. **Shared control plane**: BGP and peering are part of Azure's provider-managed, SLA-backed control plane that operates at cloud scale.\n2. **Availability guarantees**: Azure's connectivity SLAs depend on these sessions remaining active.\n3. **Security boundaries**: Customers control routing **policy** (what routes are advertised\u002Faccepted) but not the existence of BGP sessions themselves.\n4. **Operational scale**: Managing BGP session state for thousands of customers requires automation that manual shutdown would undermine.\n\n**Correct approach**: Fix BGP issues through **policy changes** (route filters, preferences, export controls, communities) rather than disabling connectivity.\n\n## Common Pitfalls\n\n- ❌ **Timer tuning or dampening fixes oscillation** — False. These reduce symptoms but don't break preference cycles.\n- ❌ **Accepting fewer prefixes prevents route leaks** — False. Ingress filtering alone doesn't stop export of other leaked routes.\n- ❌ **Removing peers is a valid mitigation** — False. This is prohibited in Azure.\n- ❌ **Restarting gateways fixes root cause** — False. Only resets transient state.\n\nAll are false.\n\n## Output Expectations\n\nA correct solution should:\n\n1. Identify oscillation and\u002For route leak correctly\n2. Explain why it occurs (preference cycle or valley-free violation)\n3. Recommend allowed policy-level fixes\n4. Explicitly reject prohibited fixes with reasoning\n\n## References\n\n- RFC 4271 — Border Gateway Protocol 4 (BGP-4)\n- Gao–Rexford model — Valley-free routing economics\n",{"name":5,"description":7},"main","7eeb258ada72b7f58119b0e7a2c00ea89d9beedd","tasks-no-skills\u002Fazure-bgp-oscillation-route-leak\u002Fenvironment\u002Fskills\u002Fazure-bgp","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench","https:\u002F\u002Fgithub.com\u002FWaaaalnut","student of Zhejiang University","2026-04-21 23:16:23",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add Waaaalnut\u002Fskillsbench --skill azure-bgp",{"tool":53,"command":54},"bunx","bunx skills add Waaaalnut\u002Fskillsbench --skill azure-bgp",{"tool":56,"command":57},"pnpm","pnpm dlx skills add Waaaalnut\u002Fskillsbench --skill azure-bgp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks-no-skills\u002Fazure-bgp-oscillation-route-leak\u002Fenvironment\u002Fskills\u002Fazure-bgp\u002FSKILL.md",true,[],[62,76,91,119,140,159],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":72,"publishedAt":35},"01M6XEWMJ6VY3ZC53MPDCPG3GH","data-reconciliation","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fxlsx-recover-data\u002Fenvironment\u002Fskills\u002Fdata-reconciliation\u002FSKILL.md",[67],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[73,74,75],"data reconciliation","reconciliation","data",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":35},"01M6XEW8MNPMF1KRXV6ATGFRQF","speech-to-text","Transcribe video to timestamped text using Whisper tiny model (pre-installed).","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-tutorial-indexer\u002Fenvironment\u002Fskills\u002Fspeech-to-text\u002FSKILL.md",[],[83,84,85,86,87,88,89,90],"speech","text","speech to text","transcribe video","whisper","model","Video","transcribe",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":35},"01M6XEW3FQZP0T1RKQQJFXVY9T","video-processor","Process videos by removing segments and concatenating remaining parts. Use when you need to remove detected pauses\u002Fopenings from videos, create highlight reels, or batch process segment removals using ffmpeg filter_complex.","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-silence-remover\u002Fenvironment\u002Fskills\u002Fvideo-processor\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[89,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"processor","video processor","batch","create","reels","when","parts","segments","process","videos","you","segment","filter","ffmpeg","use","remove",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":35},"01M6XEVXJ5KZ0NTY3XZKRY4AS1","silence-detector","Detect initial silence segments in audio\u002Fvideo using energy-based analysis. Use when you need to find low-energy periods at the start of recordings (title slides, setup time, pre-roll silence).","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-silence-remover\u002Fenvironment\u002Fskills\u002Fsilence-detector\u002FSKILL.md",[125],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[127,128,129,130,108,113,131,132,133,134,28,110,135,136,89,137,138,139,117],"detector","silence detector","title","slides","time","energy","at","recordings","find","Audio","analysis","start","setup",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":35},"01M6XEVT3NGRN1FT7JPMAPXS6M","segment-combiner","Combine multiple segment detection results into a unified list. Use when you need to merge segments from different detectors, prepare removal lists for video processing, or consolidate detection outputs.","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-silence-remover\u002Fenvironment\u002Fskills\u002Fsegment-combiner\u002FSKILL.md",[],[114,147,89,148,149,150,151,152,108,153,154,110,113,155,156,117,157,158],"segment combiner","detection","prepare","merge","video processing","for","outputs","combine","processing","consolidate","results","list",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":35},"01M6XEVMPVASGS2KX86QK4FMT7","report-generator","Generate compression reports for video processing. Use when you need to create structured JSON reports with duration statistics, compression ratios, and segment details after video processing.","https:\u002F\u002Fgithub.com\u002FWaaaalnut\u002Fskillsbench\u002Fblob\u002Fmain\u002Ftasks\u002Fvideo-silence-remover\u002Fenvironment\u002Fskills\u002Freport-generator\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000034","行政与办公人员",[169,170,171,114,108,152,113,172,155,173,174,175,117,151,176,89,177,178,106],"generator","report generator","report","with","statistics","structured","reports","json","compression","generate"]