agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-unifi-network-consoles/SKILL.md

gadget-unifi-network-consoles

Skill2.6k starsChanged 25 days agoApache-2.0View on GitHub

Inspect read-only network inventory and status through an existing local UniFi Network controller using Muse Home Link. Use an authorized compatible HTTPS API for the intended site; not network configuration or client blocking.

1 other project uses a version of this, 1 of them edited.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 13 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the facebookincubator/muse-gadget-sdk repository that our weekly crawl found: only 14 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about facebookincubator/muse-gadget-sdk

The biggest 5 of 14 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 14

Talked about on GitHub, Bluesky and Hacker News (14 times).

On GitHub · 11

6 more on GitHub

On Hacker News · 1

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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. Distinctive:

    Use this skill when the home has an existing local UniFi Network controller/console with a compatible authenticated HTTPS API.

    line 11
  2. Very specific:

    Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.

    line 20
  3. Very specific:

    Use a version-compatible local API client and authentication flow.

    line 28
  4. Distinctive:

    Check API-level success/error metadata, authorization scope and returned site identity.

    line 35
  5. Distinctive:

    Read-only skill: no restart, adoption, blocking/unblocking, port, Wi-Fi, firewall or network configuration changes.

    line 40
  6. Distinctive:

    No assumed cloud SSO, new controller deployment, guessed private endpoints or official-support claim.

    line 41
  7. Distinctive:

    Do not expose raw client inventories beyond the user's request.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

UniFi Network Consoles — Read-Only Inventory

Use this skill when the home has an existing local UniFi Network controller/console with a compatible authenticated HTTPS API.

Identify the Device

  • Confirm console/controller product, UniFi OS and Network application versions using the authorized local endpoint.
  • Identify the requested site before enumerating its devices or clients. A UniFi access point alone is not necessarily the controller.

Prerequisites

Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.

  • An existing authorized local controller account/session with read-only access where available.
  • The correct controller API family and trusted TLS identity. Cloud SSO/account access is not assumed.
  • Permission to inspect network inventory; client names, identifiers and activity are private household data.

Workflow

  1. Use a version-compatible local API client and authentication flow. Legacy controllers commonly use /api; UniFi OS commonly proxies Network requests under /proxy/network/api. Confirm the deployed version rather than probing arbitrary variants.
  2. Authenticate over the local HTTPS service, preserving cookies/tokens and any required CSRF handling without logging them.
  3. Enumerate authorized sites, then request documented device/client/status reads for the selected site. Community methods include site listing and stat/device or stat/sta reads under that API's site route.
  4. Handle pagination and offline/stale records. Report the controller's observation time and distinguish connected clients from historical inventory.

Verify the Result

  • Check API-level success/error metadata, authorization scope and returned site identity.
  • A controller record is not proof that a client is currently reachable or that its smart-home control interface works.

Limits

  • Read-only skill: no restart, adoption, blocking/unblocking, port, Wi-Fi, firewall or network configuration changes.
  • No assumed cloud SSO, new controller deployment, guessed private endpoints or official-support claim.
  • Do not expose raw client inventories beyond the user's request.

Sources

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.

Check your setup, free