load-balancing
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Create, read, update, and delete load-balancer virtual server (VIP) and pool/pool-member objects on a supported load-balancing platform — currently F5 BIG-IP LTM (iControl REST), Citrix ADC/NetScaler (NITRO REST), HAProxy (config file + Runtime API), and Cloudflare Load Balancing (REST; hostname-based, with pools and monitors). A VIP configuration often references a certificate by identifier for TLS termination — provisioning that certificate is certificate-management's job, not this skill's; this skill only consumes the reference. Assumes an authenticated client for the target platform's API/CLI is already available; this skill does not provision or authenticate it.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- proyecto26/system-design-skillstheir own version, first seen Nov 1, 2026
- ffsshhttiikk/opencode-agents-skillstheir own version, first seen Feb 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- proyecto26/system-design-skills★ 118same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alert-monitor-managementSkill
- automation-job-executionSkill
- casb-policy-managementSkill
- casb-posture-assessmentSkill
- certificate-managementSkill
- change-managementSkill
- cloud-security-group-auditSkill
- cmdb-asset-managementSkill
- compute-instance-provisioningSkill
- config-backup-managementSkill
- connector-tunnel-managementSkill
- container-workload-deploymentSkill
- crm-contact-managementSkill
- dcim-asset-managementSkill
- dhcp-scope-managementSkill
- dns-record-managementSkill
- dns-zone-managementSkill
- firewall-managementSkill
- incident-managementSkill
- infrastructure-plan-executionSkill
- interface-link-troubleshootingSkill
- ipam-allocationSkill
- log-querySkill
- metric-querySkill
- network-access-control-managementSkill
- network-health-verificationSkill
- network-state-collectionSkill
- notificationsSkill
- repository-pull-request-managementSkill
- routing-troubleshootingSkill
- sdwan-policy-managementSkill
- sdwan-site-onboardingSkill
- secret-retrievalSkill
- software-upgrade-lifecycleSkill
- vpn-tunnel-managementSkill
- vulnerability-lookupSkill
- waf-managementSkill
- wireless-network-managementSkill
- zero-trust-access-policy-managementSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Not for issuing or renewing the TLS certificate a VIP terminates — see certificate-management for that.
- Very specific: line 66
Does not cover certificate issuance/renewal, even where a VIP configuration references a certificate by identifier — see …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Load Balancing
Manages load-balancer virtual server (VIP) and pool/pool-member objects on whichever load-balancing platform the caller is targeting, following that platform's own documented procedure exactly.
When to use this skill
- Creating, reading, updating, or deleting a virtual server (VIP), or adding/removing/updating a pool member's state, on a supported platform.
- Not for issuing or renewing the TLS certificate a VIP terminates — see
certificate-managementfor that. A VIP may reference a certificate by identifier, but provisioning that certificate is out of scope here.
Universal concepts (shared load-balancing vocabulary, not a wire standard)
There is no wire-level standard grounding this capability (unlike, say, DNS) — the claims below are
verified against the four platforms currently listed in references/INDEX.md (F5 BIG-IP LTM, Citrix
ADC, HAProxy, Cloudflare Load Balancing), with the exceptions noted. Treat them as the current common
ground, not a guarantee that every future vendor added here will match:
- A VIP is its own object, separate from the pool/backend of members it directs traffic to. On the
three appliance-style platforms it is identified by an address+port pair (F5
ltm virtual'sdestination; Citrixlbvserver'sipv46+port; HAProxy'sfrontend/bind) and the member side is a distinct object (F5ltm pool; Citrixservice; HAProxybackend/server). Cloudflare is the exception to the address+port part: its load balancer is identified by a DNS hostname with no listener address, and its pools are separate objects it references. - The VIP references its pool/backend by name/identifier — it does not embed member definitions
directly. F5's
poolfield, HAProxy'sdefault_backend, Citrix's explicitlbvserver_service_binding, and Cloudflare's list of referenced pools are all references or bindings, never a single combined create. - A pool/backend member is defined by a target address (and usually a port). How a platform
identifies a member for update or removal differs (F5 member resource name, Citrix
service.ip, HAProxyserverline, Cloudflare an origin entry identified by its name within the pool) — see each platform's ownprocedure.md. - Every platform distinguishes disabling/draining a member from removing it, with more than one
documented flavor of "disabled" on most (F5's
sessionvs.state; Citrix's graceful vs. non-graceful disable; HAProxy's maintenance/drain/health-down; Cloudflare's per-origin enabled flag versus removing the origin). Do not normalize these into one generic "disabled" status — report the specific mechanism actually used.
See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements this shape concretely.
Procedure
- Identify the target platform — from the caller's request or the
platformargument. Checkreferences/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet. - Open
references/<platform>/procedure.mdand follow it exactly — it contains that platform's full operational procedure, error handling, patterns, known limitations, tools, and verification checklist. - Report the outcome using that platform procedure's own status vocabulary — don't normalize it away, and don't conflate a pool member being disabled/drained with it being removed, on a platform that distinguishes them.
Known limitations
- Currently covers F5 BIG-IP LTM, Citrix ADC/NetScaler, HAProxy, and Cloudflare Load Balancing — see
references/INDEX.mdfor exact scope per vendor and known gaps. A platform not listed there needs a new reference file before this skill can be used for it. - Does not cover certificate issuance/renewal, even where a VIP configuration references a
certificate by identifier — see
certificate-managementfor that.
Contributing to this skill
SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific procedure changes — a new error
code, a corrected field, a changed call mechanism detail — belong in that platform's own
references/<platform>/procedure.md, never here.
Tools
Each platform assumes its own authenticated client — see references/INDEX.md for which, and that
platform's procedure.md for the specific operations.
Verification checklist
- Target platform confirmed against
references/INDEX.mdbefore proceeding - That platform's own
procedure.mdwas followed, including its own confirmation gates on destructive changes (VIP deletion, pool member removal from a live pool) - Outcome reported using the platform procedure's own status vocabulary, distinguishing a disabled/drained pool member from a removed one where the platform makes that distinction
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

