agentleFS
itentialitential/infra-agent-skills/skills/network-access-control-management/SKILL.md

network-access-control-management

Skill1 starsChanged 32 days agoApache-2.0View on GitHub

Register, quarantine, release, and remove network endpoints, assign them to groups or profiles, and read their session state on a supported network access control (NAC/AAA) platform. Port- and network-level admission, distinct from zero-trust-access-policy-management's application-access policy. Covers Aruba ClearPass Policy Manager. Assumes an authenticated client for the target platform's API is already available; this skill does not provision or authenticate it. See references/INDEX.md for each platform's scope.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 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.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Not for application-access or internet-access policy in a cloud security service — see zero-trust-access-policy-management.

    line 17
  2. Very specific:

    Not for network-layer firewall rules — see firewall-management.

    line 19
  3. Very specific:

    Not for address assignment — see dhcp-scope-management and ipam-allocation.

    line 20
  4. Very specific:

    Only one platform is documented today.

    line 27
  5. Very specific:

    Only platforms listed in references/INDEX.md are covered.

    line 45
  6. Distinctive:

    Does not cover firewall rules, address assignment, or cloud application-access policy.

    line 47

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

Network Access Control Management

Manages endpoint admission on whichever network access control platform the caller is targeting — registering, quarantining, releasing, and removing endpoints and their group or profile assignment — following that platform's own documented procedure exactly.

When to use this skill

  • Reading, registering, assigning to a group or profile, quarantining, releasing, or deleting an endpoint, or reading its session state, on a supported NAC/AAA platform.
  • Not for application-access or internet-access policy in a cloud security service — see zero-trust-access-policy-management.
  • Not for network-layer firewall rules — see firewall-management.
  • Not for address assignment — see dhcp-scope-management and ipam-allocation.

Universal concepts (shared NAC/AAA vocabulary, not a wire standard)

  • Endpoints are identified by hardware (MAC) address where a platform documents that.
  • Whether an endpoint is admitted is decided by the platform's own policy; a record change affects access only where that policy uses it, so confirm the platform's own semantics before relying on it.
  • Only one platform is documented today; these claims are deliberately minimal and do not extend automatically to a platform not listed in references/INDEX.md.

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

  • Only platforms listed in references/INDEX.md are covered; any other needs a new reference file before this skill can be used for it.
  • Does not cover firewall rules, address assignment, or cloud application-access policy.
  • Authorization-policy rule authoring (the conditions that decide admission) is out of scope until a platform procedure documents it as its own distinct, gated procedure.

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 quarantine of a live endpoint, endpoint deletion, and group changes that alter existing access
  • 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.