agentleFS
itentialitential/infra-agent-skills/skills/waf-management/SKILL.md

waf-management

Skill1 starsChanged 32 days agoApache-2.0View on GitHub

Create, read, update, and delete web application firewall (WAF) rules, rate-limit rules, and managed-ruleset bindings on a supported platform (Cloudflare WAF). Application-layer/HTTP rule management, distinct from firewall-management's network-layer rules and NAT — even where the same vendor offers both. Assumes an authenticated client for the target platform's API is already available; this skill does not provision or authenticate it.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Not for network-layer firewall rules or NAT — see firewall-management for that.

    line 16
  2. Distinctive:

    Only one platform is listed, so each claim below holds only where that platform documents it.

    line 22
  3. Very specific:

    Does not cover network-layer firewall rules or NAT, even where the same vendor/product offers both — see firewall-management for that.

    line 48

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

WAF Management

Manages web application firewall rules, rate-limit rules, and managed-ruleset bindings on whichever platform the caller is targeting, following that platform's own documented procedure exactly.

When to use this skill

  • Creating, reading, updating, or deleting a WAF rule, rate-limit rule, or a managed-ruleset binding (e.g. enabling a vendor-curated OWASP ruleset) on a supported platform.
  • Not for network-layer firewall rules or NAT — see firewall-management for that. A platform may offer both under one product line (Cloudflare, F5, Palo Alto all do); this skill covers only the HTTP/application-layer rule object, never the network ACL.

Universal concepts (shared WAF vocabulary, not a wire standard)

Only one platform is listed, so each claim below holds only where that platform documents it.

  • A rule pairs a match expression with an action and is evaluated in order. Where documented, some actions end evaluation for that request, so position decides whether a rule ever applies.
  • A rate-limit rule counts requests per chosen identity over a time window. Where documented, its action applies once the count passes the limit.
  • A managed ruleset is a vendor-maintained rule group, bound to the application with optional overrides. Where documented, a deployment can be tuned per rule.

See references/INDEX.md for which platforms have a procedure, and each platform file for how it implements this shape concretely.

Procedure

  1. Identify the target platform — from the caller's request or the platform argument. Check references/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet.
  2. Open references/<platform>/procedure.md and follow it exactly — it contains that platform's full operational procedure, error handling, patterns, known limitations, tools, and verification checklist.
  3. Report the outcome using that platform procedure's own status vocabulary — don't normalize it away.

Known limitations

  • Platform coverage is exactly the platforms in references/INDEX.md; a platform not listed there needs a new reference file before this skill can be used for it.
  • Does not cover network-layer firewall rules or NAT, even where the same vendor/product offers both — see firewall-management for 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 API path — 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.md before proceeding
  • That platform's own procedure.md was followed, including its own confirmation gates on destructive changes (rule deletion, ruleset unbinding that removes active protection)
  • Outcome reported using the platform procedure's own status vocabulary

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.