[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BXTQJFE4ZMGG87YW9EBV5J":3,"skill-same:01M7BXTQJFE4ZMGG87YW9EBV5J":45},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BXTQJFE4ZMGG87YW9EBV5J","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.","linyouxue\u002Fskill-repair-benchmark","linyouxue","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F216151464?v=4","01M7BJEVCXKD74KH6FG9CBVSQB","林宥学","01M7BJEVE02NP217V93BKZFC0J",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002FSkillAxe-Completion-Guard3-Tatumass\u002Ftasks\u002Fazure-bgp-oscillation-route-leak\u002Frepaired_skill\u002Fazure-bgp\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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, 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### Step 4 — Classify Each Candidate Solution (Explicit output contract)\n\nMany benchmark tasks require a JSON mapping of `solution_name -> {oscillation_resolved, route_leak_resolved}`.\n\nUse these *task-aligned* definitions when setting booleans:\n\n- **oscillation_resolved = True** only if the change **breaks the preference cycle** (`preferences.json`) *or* enforces deterministic forwarding such that the cycle no longer affects route choice.\n- **route_leak_resolved = True** only if the change **prevents hub-to-hub propagation of provider\u002Fpeer-learned routes** (i.e., stops the specific valley-free violation \u002F hub-to-hub transit behavior).\n\nWhen evaluating a solution string, do not require device restarts or topology removal to count as a fix; prefer policy mechanisms available in Azure.\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 (classification rule):**\n\n- If a candidate says it **enables Virtual WAN hub routing intent** to force hub-to-hub traffic through Virtual WAN (e.g., via the Virtual WAN core\u002FASN), then classify:\n  - `oscillation_resolved = True` because intent **overrides BGP path selection**, eliminating the operational effect of a preference cycle on forwarding.\n  - `route_leak_resolved = True` because it **prevents hubs from using each other as unintended transit**, constraining hub-to-hub routing to the Virtual WAN policy path.\n\n**Notes:**\n- Routing intent operates above BGP: BGP can still learn routes, but forwarding is policy-driven.\n- For benchmark-style tasks, treat intent as a valid “resolution” when the intent statement explicitly enforces the intended hub-to-hub path.\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\n#### RPKI origin validation (how to classify)\n\nRPKI is a **route validity gate**. In tasks where the leak is modeled as acceptance\u002Fpropagation of an invalid origin,\n**enabling RPKI origin validation** at a hub should be classified as:\n\n- `oscillation_resolved = False` (it does not change the preference graph\u002Fcycle)\n- `route_leak_resolved = True` **when** the solution explicitly states it will validate the prefix’s correct origin ASN,\n  because invalid leaked announcements will be dropped and therefore not propagated.\n\n(If a task instead defines leak purely as export-policy violation independent of origin validity, then RPKI may be insufficient. When in doubt, follow the task’s leak definition and the solution wording: RPKI resolves leaks only insofar as it blocks the bad route from being accepted\u002Fpropagated.)\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**Classification rule (important for benchmarks):**\n- If a solution proposes a **UDR\u002Froute-table override** that forces a specific next hop \u002F path,\n  set:\n  - `oscillation_resolved = True` because the preference cycle no longer affects forwarding choice.\n  - `route_leak_resolved = True` because traffic is prevented from using the leaked hub-to-hub transit path.\n\n**Trade-off:**\nUDR is a data-plane fix that may “mask” the control-plane issue. However, for tasks that define “resolved” in terms of breaking the cycle’s effect and stopping hub-to-hub transit via Virtual WAN, UDR counts as resolved when it enforces the correct next hop.\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\n5. When required by the task, produce `solution_results` where each candidate fix is mapped to booleans using the definitions in **Step 4** above.\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, 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### Step 4 — Classify Each Candidate Solution (Explicit output contract)\n\nMany benchmark tasks require a JSON mapping of `solution_name -> {oscillation_resolved, route_leak_resolved}`.\n\nUse these *task-aligned* definitions when setting booleans:\n\n- **oscillation_resolved = True** only if the change **breaks the preference cycle** (`preferences.json`) *or* enforces deterministic forwarding such that the cycle no longer affects route choice.\n- **route_leak_resolved = True** only if the change **prevents hub-to-hub propagation of provider\u002Fpeer-learned routes** (i.e., stops the specific valley-free violation \u002F hub-to-hub transit behavior).\n\nWhen evaluating a solution string, do not require device restarts or topology removal to count as a fix; prefer policy mechanisms available in Azure.\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 (classification rule):**\n\n- If a candidate says it **enables Virtual WAN hub routing intent** to force hub-to-hub traffic through Virtual WAN (e.g., via the Virtual WAN core\u002FASN), then classify:\n  - `oscillation_resolved = True` because intent **overrides BGP path selection**, eliminating the operational effect of a preference cycle on forwarding.\n  - `route_leak_resolved = True` because it **prevents hubs from using each other as unintended transit**, constraining hub-to-hub routing to the Virtual WAN policy path.\n\n**Notes:**\n- Routing intent operates above BGP: BGP can still learn routes, but forwarding is policy-driven.\n- For benchmark-style tasks, treat intent as a valid “resolution” when the intent statement explicitly enforces the intended hub-to-hub path.\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\n#### RPKI origin validation (how to classify)\n\nRPKI is a **route validity gate**. In tasks where the leak is modeled as acceptance\u002Fpropagation of an invalid origin,\n**enabling RPKI origin validation** at a hub should be classified as:\n\n- `oscillation_resolved = False` (it does not change the preference graph\u002Fcycle)\n- `route_leak_resolved = True` **when** the solution explicitly states it will validate the prefix’s correct origin ASN,\n  because invalid leaked announcements will be dropped and therefore not propagated.\n\n(If a task instead defines leak purely as export-policy violation independent of origin validity, then RPKI may be insufficient. When in doubt, follow the task’s leak definition and the solution wording: RPKI resolves leaks only insofar as it blocks the bad route from being accepted\u002Fpropagated.)\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**Classification rule (important for benchmarks):**\n- If a solution proposes a **UDR\u002Froute-table override** that forces a specific next hop \u002F path,\n  set:\n  - `oscillation_resolved = True` because the preference cycle no longer affects forwarding choice.\n  - `route_leak_resolved = True` because traffic is prevented from using the leaked hub-to-hub transit path.\n\n**Trade-off:**\nUDR is a data-plane fix that may “mask” the control-plane issue. However, for tasks that define “resolved” in terms of breaking the cycle’s effect and stopping hub-to-hub transit via Virtual WAN, UDR counts as resolved when it enforces the correct next hop.\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\n5. When required by the task, produce `solution_results` where each candidate fix is mapped to booleans using the definitions in **Step 4** above.\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","cdcb6d230f3b15c3c33f8a2bdd16439f43602cbe","evaluation\u002Fresults\u002FSkillAxe-Completion-Guard3-Tatumass\u002Ftasks\u002Fazure-bgp-oscillation-route-leak\u002Frepaired_skill\u002Fazure-bgp",1,"https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark","https:\u002F\u002Fgithub.com\u002Flinyouxue","2026-11-14 20:28:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add linyouxue\u002Fskill-repair-benchmark --skill azure-bgp",{"tool":37,"command":38},"bunx","bunx skills add linyouxue\u002Fskill-repair-benchmark --skill azure-bgp",{"tool":40,"command":41},"pnpm","pnpm dlx skills add linyouxue\u002Fskill-repair-benchmark --skill azure-bgp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fevaluation\u002Fresults\u002FSkillAxe-Completion-Guard3-Tatumass\u002Ftasks\u002Fazure-bgp-oscillation-route-leak\u002Frepaired_skill\u002Fazure-bgp\u002FSKILL.md",true,[],[46,53,60,67,72,77],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7E1HGVRY73NBJ022CJG13X6","video-frame-extraction","Extract frames from video files and save them as images using OpenCV","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fvideo-frame-extraction\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7E1HAG5R7CJ9C8NYJS771MB","openai-vision","Analyze images and multi-frame sequences using OpenAI GPT vision models","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fopenai-vision\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7E1H7DADKB6QBWKC2KQ63SZ","image-ocr","Extract text content from images using Tesseract OCR via Python, including structured field extraction from receipts and forms","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_03\u002Finputs\u002Fskills\u002Fimage-ocr\u002FSKILL.md",[],[],{"skillNo":68,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7E1H0WBNT43TENGQY7AVZHD","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fvideo-frame-extraction\u002FSKILL.md",[],[],{"skillNo":73,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7E1GTC7D4N4Q2EF03875J9E","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fopenai-vision\u002FSKILL.md",[],[],{"skillNo":78,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7E1GQ92CWFMGH53KSSE4WER","https:\u002F\u002Fgithub.com\u002Flinyouxue\u002Fskill-repair-benchmark\u002Fblob\u002Fmain\u002Fjpg-ocr-stat\u002Fresult\u002Fskilltta-claude4.7\u002Fgroup_03\u002Frun_02\u002Finputs\u002Fskills\u002Fimage-ocr\u002FSKILL.md",[],[]]