ClawHub

azure-bgp

v0.1.0

Analyze and resolve BGP oscillation and BGP route leaks in Azure Virtual WAN–style hub-and-spoke topologies (and similar cloud-managed BGP environments). Det...

⭐ 0· 20·0 current·0 all-time
by@wu-uk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill's name/description match the SKILL.md: it describes detection of preference cycles, valley‑free violations, and recommending Azure-appropriate mitigations (routing intent, export policies, communities, UDRs, ingress filtering, RPKI). Nothing in the instructions requires unrelated resources or credentials.
✓
Instruction Scope
Runtime instructions operate on user-supplied JSON inputs (topology.json, relationships.json, preferences.json, etc.), include pseudocode for cycle detection, and lay out decision logic and mitigation tiers. The SKILL.md does not instruct reading system files, accessing environment variables, calling external endpoints, or making changes in Azure — it focuses on analysis and recommendations only.
✓
Install Mechanism
No install specification and no code files are present; this is instruction-only so nothing is downloaded or written to disk by the skill itself.
ℹ
Credentials
The skill requires no environment variables or credentials (proportionate for a reasoning/analysis skill). Note: if a user expects automated remediation in Azure, additional credentials (Azure service principal or similar) would be required — those are not requested by this skill and would be an additional security consideration outside its current scope.
✓
Persistence & Privilege
always is false and there are no install artifacts or persistent permissions requested. disable-model-invocation is false (normal); autonomous invocation is allowed by default but the skill itself does not grant extra system privileges or persistent presence.
Assessment
This skill is a reasoning/template tool: it analyzes JSON topology inputs and recommends policy fixes but does not apply changes to Azure. Before using: (1) verify input JSON accuracy (garbage in → incorrect recommendations), (2) do not paste secrets into the inputs or prompts, (3) if you want automated remediation, set up a least-privilege Azure service principal and treat those credentials carefully (this skill does not request or store them), and (4) validate any recommended policy changes in a staging environment before applying to production.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ac6ff7snw7g3y3xe8d8rfg584r46y

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments