Routing Architecture
majiayu000/litellm-rs
LiteLLM-RS Routing Architecture. An agent skill from majiayu000/litellm-rs.
This skill should be used when the user asks to "manage UniFi devices", "configure UniFi networks", "create a VLAN", "provision an SSID", "create firewall rules", "reorder firewall policies"…
$ npx skills add hyperb1iss/unifly --skill unifly -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hyperb1iss/unifly unifly --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hyperb1iss/unifly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/unifly .claude/skills/unifly && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "unifly" agent skill from https://github.com/hyperb1iss/unifly/tree/main/skills/unifly into .claude/skills/unifly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unifly", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hyperb1iss/unifly/tree/main/skills/uniflyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hyperb1iss/unifly --skill unifly -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hyperb1iss/unifly unifly --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyperb1iss/unifly.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/unifly .agents/skills/unifly && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "unifly" agent skill from https://github.com/hyperb1iss/unifly/tree/main/skills/unifly into .agents/skills/unifly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unifly", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hyperb1iss/unifly --skill unifly -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hyperb1iss/unifly unifly --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyperb1iss/unifly.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/unifly .cursor/skills/unifly && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "unifly" agent skill from https://github.com/hyperb1iss/unifly/tree/main/skills/unifly into .cursor/skills/unifly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unifly", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hyperb1iss/unifly.git --path skills/unifly--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hyperb1iss/unifly --skill unifly -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hyperb1iss/unifly unifly --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyperb1iss/unifly.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/unifly .gemini/skills/unifly && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "unifly" agent skill from https://github.com/hyperb1iss/unifly/tree/main/skills/unifly into .gemini/skills/unifly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unifly", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hyperb1iss/unifly uniflyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hyperb1iss/unifly --skill unifly -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hyperb1iss/unifly.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/unifly .github/skills/unifly && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "unifly" agent skill from https://github.com/hyperb1iss/unifly/tree/main/skills/unifly into .github/skills/unifly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unifly", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hyperb1iss/unifly --skill unifly -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hyperb1iss/unifly unifly --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyperb1iss/unifly.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/unifly .opencode/skills/unifly && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "unifly" agent skill from https://github.com/hyperb1iss/unifly/tree/main/skills/unifly into .opencode/skills/unifly/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unifly", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
uniflyThis skill should be used when the user asks to "manage UniFi devices", "configure UniFi networks", "create a VLAN", "provision an SSID", "create firewall rules", "reorder firewall policies"…
Unifly is an agent skill from hyperb1iss/unifly. This skill should be used when the user asks to "manage UniFi devices", "configure UniFi networks", "create a VLAN", "provision an SSID", "create firewall rules", "reorder firewall policies", "create a NAT rule", "set up port forwarding", "configure masquerade NAT", "add DNS records", "manage traffic matching lists", "create DHCP reservations", "list DHCP reservations", "block a client", "kick a client", "find a client by IP or name", "adopt a device", "restart a UniFi device", "cycle a PoE port", "upgrade device…
Its SKILL.md is about 7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including reference files (for example `examples/firewall-block-iot.json`, `examples/nat-masquerade.json` and `examples/nat-port-forward.json`).
It sits in DevOps & Cloud, covering Cloud networking. It works with Rust. The repository describes itself as: 🌐 Elegant UniFi network management CLI & TUI - for humans and agents. The licence is Apache-2.0.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit b565654. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
jqbrewcargoFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
UNIFI_API_KEYUNIFI_PASSWORDFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Unifly loads about 7k tokens when it runs, and up to ~24k if it reads all its reference files. Until then it costs about 256 tokens; SKILL.md has 1,601 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from hyperb1iss/unifly at commit b565654, republished under its Apache-2.0 licence (© hyperb1iss). 1,601 words, ~6,998 tokens.
.claude/skills/unifly/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.unifly is a Rust CLI for managing Ubiquiti UniFi network infrastructure. It unifies the modern Integration API (REST, API key), the Session API (cookie plus CSRF), and Site Manager cloud APIs behind a single coherent interface, plus real-time WebSocket event streaming. 28 top-level commands cover devices and switch port config-as-code, clients, networks, WiFi, firewall policies, zones, and groups, NAT policies, ACLs, DNS, traffic matching lists, hotspot vouchers, DPI, stats, backups, the full VPN surface, site settings, cloud fleet queries, and a raw API escape hatch.
Unique capabilities worth leading with when the user's task suits them:
unifly events watch over WebSocket.reorder --get / reorder --set for
deterministic, round-trippable ordering edits.unifly api raw passthrough for endpoints unifly does not wrap.-p home, -p office) for managing multiple controllers
from one command line.Verify availability before running any command:
command -v unifly >/dev/null 2>&1 && unifly --version || echo "unifly not installed"If unifly is not installed, prefer brew install hyperb1iss/tap/unifly on
macOS or cargo install --git https://github.com/hyperb1iss/unifly.git unifly
elsewhere. After install, run unifly config init for a local controller or
unifly config cloud-setup for Site Manager. See examples/config.toml for
manual configuration.
unifly supports four modes. API key mode is enough for most HTTP
automation on UniFi OS controllers. Choose Hybrid when the task needs
live WebSocket features (events watch) or you want maximum compatibility.
| Mode | Credentials | What It Unlocks |
|---|---|---|
integration | API key | Integration API plus session HTTP on UniFi OS: CRUD, device commands, stats, reservations, admin, event list |
session | Username + password | Session HTTP + WebSocket only: events watch, stats, device commands, DPI control, admin, backups, NAT policies, firewall groups, switch port config-as-code, site settings |
hybrid | API key + username/pass | Everything above, including session WebSocket plus enriched records with maximum controller compatibility |
cloud | Site Manager API key | Connector-routed Integration CRUD plus unifly cloud fleet commands against api.ui.com |
Session WebSocket still rejects API keys, so events watch needs session or
hybrid. Cloud mode does not expose Session API endpoints or WebSocket
streaming.
For the complete command-to-API gate matrix (which commands require which
auth mode), consult references/concepts.md.
All commands follow unifly [global-flags] <command> <action> [args].
| Command | Aliases | Actions |
|---|---|---|
devices | dev, d | list, get, adopt, remove, restart, locate, port-cycle, ports, ports-export, port-set, stats, pending, upgrade, provision, speedtest, tags |
clients | cl | list, find, get, roams, wifi, authorize, unauthorize, block, unblock, kick, forget, reservations (res), set-ip, remove-ip |
cloud | hosts [get], sites, switch, devices, isp [query], sdwan [get, status] | |
networks | net, n | list, get, create, update, delete, refs |
wifi | w | list, get, neighbors, channels, create, update, delete |
firewall | fw | policies {list, get, create, update, patch, delete, reorder}, zones {list, get, create, update, delete}, groups {list, get, create, update, delete} |
nat | policies {list, get, create, update, delete} | |
acl | list, get, create, update, delete, reorder | |
dns | list, get, create, update, delete | |
traffic-lists | list, get, create, update, delete | |
hotspot | list, get, create, delete, purge | |
events | list, watch | |
alarms | list, archive, archive-all | |
stats | site, device, client, gateway, dpi | |
dpi | apps, categories, status, enable, disable | |
topology | topo | (no subcommands) |
system | sys | info, health, sysinfo, backup {create, list, download, delete}, reboot, poweroff |
settings | list, get, set, export | |
sites | list, create, delete | |
admin | list, invite, revoke, update | |
wans | list | |
vpn | servers [get], tunnels [get], status, health, site-to-site {list, get, create, update, delete}, remote-access {list, get, create, update, suggest-port, download-config, delete}, clients {list, get, create, update, delete}, connections {list, get, restart}, peers {list, get, create, update, delete, subnets}, magic-site-to-site {list, get}, settings {list, get, set, patch} | |
radius | profiles | |
countries | (no subcommands) | |
api | Raw API passthrough (GET/POST/PUT/PATCH/DELETE any path) | |
config | init, cloud-setup, show, set, profiles, use, set-password, theme | |
tui | (no subcommands) | |
completions | bash, zsh, fish, powershell, elvish |
For flag details and gotchas, consult references/commands.md. Every entity
command accepts --help at runtime as the authoritative reference.
All list and get commands accept --output / -o:
| Format | Flag | Use Case |
|---|---|---|
table | -o table | Human display (default) |
json | -o json | Agent processing, pipe to jq |
json-compact | -o json-compact | Single-line JSON for scripting |
yaml | -o yaml | Config file output |
plain | -o plain | One ID per line for xargs pipelines |
Default for agent use: -o json. Emit structured output, pipe through
jq, and only fall back to table when the result is being shown to a human.
These patterns unlock unifly's most distinctive capabilities. For full
recipes with runnable shell scripts, consult references/workflows.md.
--from-file for complex create/updateMost entities accept --from-file <path.json> (or -F) instead of flag
salad: networks, wifi, firewall policies, firewall zones, firewall groups, nat policies, acl, dns, traffic-lists, vpn site-to-site, vpn remote-access, vpn clients, vpn peers, vpn settings patch, and devices port-set (JSONC for switch port config-as-code).
Construct the JSON payload, validate it, then apply. See examples/ for
payload templates.
unifly networks create -F examples/network-iot-vlan.json
unifly firewall policies create -F examples/firewall-block-iot.json# All events
unifly events watch
# Filter by EventCategory (case-insensitive): Device, Client, Network,
# System, Admin, Firewall, Vpn, Unknown
unifly events watch --types "Firewall,Admin"
# JSON stream for piping into alerting (severity serializes PascalCase)
unifly events watch --types Client -o json | jq -c 'select(.severity == "Warning")'# Read current order for a zone pair
unifly firewall policies reorder --source-zone <zid> --dest-zone <zid> --get
# Write back an explicit order
unifly firewall policies reorder --source-zone <zid> --dest-zone <zid> \
--set "<id1>,<id2>,<id3>"For endpoints unifly does not wrap (including UniFi v2 routes and Integration
paths), use unifly api. It routes through the Session client, so CSRF token
management and session caching are automatic.
unifly api "v2/api/site/default/traffic-flow-latest-statistics"
unifly api "cmd/stamgr" -m post -d '{"cmd":"kick-sta","mac":"aa:bb:cc:dd:ee:ff"}'
unifly api "api/s/default/set/setting/teleport" -m put -d '{"enabled":true}'unifly vpn site-to-site wraps Session API rest/networkconf records whose
purpose is site-vpn. This is the current CRUD path for manual IPsec and
OpenVPN site-to-site records exposed by the controller.
unifly vpn site-to-site list -o json
unifly vpn site-to-site get <id> -o json
unifly vpn site-to-site create -F site-to-site.json
unifly vpn site-to-site update <id> -F site-to-site.json
unifly vpn site-to-site delete <id>unifly vpn remote-access wraps Session API rest/networkconf records whose
purpose is remote-user-vpn. This is the current CRUD path for L2TP,
OpenVPN, and WireGuard remote-access servers exposed by the controller.
unifly vpn remote-access list -o json
unifly vpn remote-access get <id> -o json
unifly vpn remote-access create -F remote-access.json
unifly vpn remote-access update <id> -F remote-access.json
unifly vpn remote-access suggest-port -o json
unifly vpn remote-access download-config <id> --path .
unifly vpn remote-access delete <id>unifly vpn clients wraps Session API rest/networkconf records whose
purpose is vpn-client. This is the current CRUD path for configured
OpenVPN and WireGuard client profiles exposed by the controller.
unifly vpn clients list -o json
unifly vpn clients get <id> -o json
unifly vpn clients create -F vpn-client.json
unifly vpn clients update <id> -F vpn-client.json
unifly vpn clients delete <id>unifly vpn peers wraps the Session v2 API WireGuard peer endpoints for
remote-access VPN servers. list can enumerate all peers or scope to a
single server ID; create, update, and delete require the parent
remote-access server ID.
unifly vpn peers list -o json
unifly vpn peers list <server-id> -o json
unifly vpn peers get <server-id> <peer-id> -o json
unifly vpn peers create <server-id> -F peer.json
unifly vpn peers update <server-id> <peer-id> -F peer.json
unifly vpn peers delete <server-id> <peer-id>
unifly vpn peers subnets -o jsonunifly vpn connections wraps the Session v2 API VPN client connection
inventory exposed at v2/api/site/<site>/vpn/connections. restart
issues the same controller action the web UI uses for a single connection.
unifly vpn connections list -o json
unifly vpn connections get <id> -o json
unifly vpn connections restart <id>unifly vpn magic-site-to-site wraps the Session v2 API
magicsitetositevpn/configs inventory endpoint. It is currently
read-only.
unifly vpn magic-site-to-site list -o json
unifly vpn magic-site-to-site get <id> -o jsonunifly vpn settings wraps the Session API rest/setting records for the VPN
feature toggles the controller exposes today: teleport,
magic-site-to-site-vpn, openvpn, and peer-to-peer.
unifly vpn settings list -o json
unifly vpn settings get peer-to-peer -o json
unifly vpn settings set teleport --enabled true
unifly vpn settings patch peer-to-peer -F peer-to-peer.jsonsite-to-site get, remote-access get, clients get, connections get,
peers get, and magic-site-to-site get return redacted records with
summary fields and the sanitized controller payload under fields.
settings get returns a redacted wrapper with key, enabled, and fields.
patch accepts either the raw session setting body or that wrapper shape and
will send the inner fields object back to the controller.
hotspot purge --filter accepts the Integration filter DSL for bulk deletion
without ID iteration:
unifly hotspot purge --filter "status.eq('UNUSED')"
unifly hotspot purge --filter "name.contains('Conference')"Propose a change, let a human visually confirm in the TUI before committing:
# Agent inspects, proposes. Human runs unifly tui and verifies on
# screen 4 (Networks) or 5 (Firewall) before the agent applies the change.
unifly tuiunifly -p home devices list
unifly -p office firewall policies list
UNIFI_PROFILE=warehouse unifly system healthclients roams uses 50). The CLI prints a
truncation hint when results hit the default. For enumeration, always
pass --all or --limit 200 (or higher).UNIFI_ prefix, not UNIFLY_. Relevant
vars: UNIFI_URL, UNIFI_API_KEY, UNIFI_USERNAME, UNIFI_PASSWORD,
UNIFI_SITE, UNIFI_PROFILE, UNIFI_OUTPUT, UNIFI_INSECURE,
UNIFI_TIMEOUT, UNIFI_TOTP, UNIFI_HOST_ID, UNIFI_DEMO. The only
UNIFLY_* var is UNIFLY_THEME, which themes both CLI output and the
TUI.--yes / -y skips confirmation prompts for mutations. Required for
non-interactive use.events watch,
TUI live refresh). Client and device enrichment fields work in API key mode.unifly cloud ... talks to
Site Manager and auth_mode = "cloud" routes Integration-backed commands
through the connector, but Session-only features still need direct
controller access.0 on success, non-zero on error. Capture
stderr for diagnostics.--output format, with the confirmation on stderr. Capture IDs
directly: ID=$(unifly networks create ... -o json | jq -r .id);
-o plain emits the bare ID. Exceptions that print nothing because
the controller returns no record: sites create and
system backup create.command -v unifly.unifly config show before running commands that
require Session or Integration specifically.unifly system health -o json as the first touch to confirm
connectivity.list / get the entity first, capture IDs.--from-file.get to confirm state.--yes.references/commands.md: Per-command flag reference with gotchas
(non-obvious flags, dual-API boundaries, correct argument forms)references/concepts.md: UniFi networking concepts, dual-API gate
matrix, auth decision tree, environment variables, platform config paths,
MFA/TOTP, error taxonomyreferences/workflows.md: Runnable automation recipes (event
streaming, safe firewall reorder, bulk DHCP reservations, ad-blocking via
DNS policies, cafe voucher flow, incident response)examples/config.toml: Multi-profile config templateexamples/network-iot-vlan.json: VLAN creation payload for --from-fileexamples/firewall-block-iot.json: Firewall policy payloadexamples/nat-masquerade.json: NAT masquerade policy payloadexamples/nat-port-forward.json: Destination NAT (port forward) payloadexamples/wifi-iot.json: WiFi SSID payloadexamples/vpn-remote-access-wireguard.json: WireGuard remote-access VPN payloadexamples/vpn-site-to-site-ipsec.json: IPsec site-to-site tunnel payloadexamples/vpn-client-openvpn.json: OpenVPN client payloadexamples/vpn-wireguard-peer.json: WireGuard peer configuration payloadexamples/switch-ports.jsonc: Switch port config-as-code payload for
devices port-set -F© hyperb1iss, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 14 other files (references) in skills/unifly of hyperb1iss/unifly.
Open the folder on GitHubat commit b565654
Unifly next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Unifly this skillhyperb1iss/unifly | 264 | — | ~7k | Automated safety check: Pass | Apache-2.0 | |
| Routing Architecturemajiayu000/litellm-rs | 117 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Rustpgdogdev/pgdog | 5.6k | — | ~1.9k | Automated safety check: Notes | AGPL-3.0 | |
| NGINX Ingress Policy CRD Guidenginx/kubernetes-ingress | 5.1k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| ArvanCloud API Operatorerfnzdeh/arvancloud-agent-skill | 135 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Aliyun Swas Managecinience/alicloud-skills | 397 | 1 repos | ~1.9k | Automated safety check: Pass | MIT |
majiayu000/litellm-rs
LiteLLM-RS Routing Architecture. An agent skill from majiayu000/litellm-rs.
pgdogdev/pgdog
Rust coding best practices for idiomatic, efficient, and maintainable code.
nginx/kubernetes-ingress
Step-by-step checklist for adding a new Policy CRD type to the NGINX Ingress Controller, from the Go types and validation to config generation and templates.
erfnzdeh/arvancloud-agent-skill
Drives ArvanCloud's REST APIs for CDN, DNS, cloud servers, object storage and more, with helper scripts for calls, account inventory and certificates.
cinience/alicloud-skills
A skill your agent uses when managing Alibaba Cloud Simple Application Server (SWAS OpenAPI 2020-06-01) resources end-to-end, including querying instances, starting/stopping/rebooting, executing…
drawthingsai/draw-things-community
Set up and verify a new Draw Things CPU proxy and Envoy server using the scripts in Scripts/ServerManagement/CPUScript.
Works with
Categories
This skill should be used when the user asks to "manage UniFi devices", "configure UniFi networks", "create a VLAN", "provision an SSID", "create firewall rules", "reorder firewall policies"…. Unifly is an agent skill from hyperb1iss/unifly.
Unifly fits situations like: asks to manage UniFi devices; configure UniFi networks; provision an SSID; create firewall rules.
Run `npx skills add hyperb1iss/unifly --skill unifly -a claude-code`. Or copy the skill folder (skills/unifly in hyperb1iss/unifly) into .claude/skills/unifly in your project. Claude Code loads it when a task matches its description.
Run `npx skills add hyperb1iss/unifly --skill unifly -a codex`. Or copy the skill folder (skills/unifly in hyperb1iss/unifly) into .agents/skills/unifly in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hyperb1iss/unifly --skill unifly -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/unifly, .gemini/skills/unifly, .github/skills/unifly and .opencode/skills/unifly in your project.
Going by SKILL.md and its folder, Unifly needs the command-line tools its instructions call (jq, brew and cargo) and credentials named UNIFI_API_KEY and UNIFI_PASSWORD.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Unifly is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 7k tokens (SKILL.md is roughly 28k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Unifly: Routing Architecture (majiayu000/litellm-rs, 117 stars), Rust (pgdogdev/pgdog, 5.6k stars), NGINX Ingress Policy CRD Guide (nginx/kubernetes-ingress, 5.1k stars) and ArvanCloud API Operator (erfnzdeh/arvancloud-agent-skill, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
hyperb1iss (a GitHub user) maintains it in hyperb1iss/unifly, which has 264 GitHub stars. The repository was last updated on August 7, 2026.
Source: hyperb1iss/unifly on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.