unifi-yourskill

Solid

Use when [the specific situations, symptoms, and phrases someone would actually type when they hit this problem]. Include the error strings and the wrong-conclusion phrasings, not just the correct terminology: people search for "my wifi is slow", not "co-channel contention". Describe ONLY when to use it, never summarize the workflow inside. Keep the whole frontmatter under 1024 characters. End by naming what this skill is NOT for, pointing at the sibling skill that covers it.

AI & Automation 29 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
49
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# UniFi Yourskill One or two sentences: what this covers, and that it assumes the auth lanes and endpoint map from `unifi-connect`. Cross-reference siblings by name (`unifi-firewall`, `unifi-wifi`, `unifi-clients`, `unifi-context-map`) instead of repeating their content. ## Guidelines for a good UniFi skill Delete this section in your real skill; it is authoring guidance. - **Name:** `unifi-<area>`, lowercase and hyphens. The directory name MUST equal the frontmatter `name`. - **Description:** starts with "Use when", lists concrete triggers and symptom phrasings, ends with a "not for X, use Y" pointer. No workflow summary: an agent will follow the description instead of reading the body. - **Parameterize everything site-specific.** `<UDM_HOST>` never a real address, `$UNIFI_API_KEY` from env never a literal, `<DEVICE_ID>` / `<ZONE_ID>` / `<MAC>` placeholders. Where an example address is unavoidable use the documentation ranges: `192.0.2.x` (RFC 5737) and `aa:bb:cc:dd:ee:ff`. - **Never include a real inventory.** No MAC lists, no camera names or placements, no WAN address, no SSID names, no household or company names. See `unifi-context-map` for why this matters more here than in most repos. - **Original prose only.** Do not paste from Ubiquiti docs or help-centre articles. Write the lesson the docs do not teach, and link the docs as the canonical manual. - **Say which version you verified against**, in `compatibility` and in the body for any version-...

Details

Author
t3chnaztea
Repository
t3chnaztea/unifi-skills
Created
2 days ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

batocera-yourskill

Use when [the specific situations, symptoms, and phrases that should trigger this skill]. Pack the words someone would actually type or think when they hit this problem. Describe ONLY when to use it, never summarize the workflow inside. Keep the whole frontmatter under 1024 characters. End by naming what this skill is NOT for, pointing at the sibling skill that covers it.

4 Updated yesterday
t3chnaztea
AI & Automation Listed

your-skill-name

One sentence on WHAT this skill does, then WHEN to use it (situations and trigger phrases). Both halves matter — the description is how the agent decides to invoke the skill. Keep it a single concrete line. No angle brackets and no YAML folded scalars in frontmatter (it enters the system prompt).

0 Updated 1 weeks ago
surendranb
API & Backend Listed

unifi

Use this skill whenever the user asks about their UniFi network — connected clients, who's on the WiFi, which devices are online, access points, switches, gateways, network health, site health, active alarms, network events, WiFi configurations (SSIDs), controller sysinfo, or their authenticated UniFi identity. This skill covers the unifi-rmcp MCP server, a Rust bridge to official and internal UniFi APIs via X-API-KEY. Legacy convenience actions are read-only; mutating actions require explicit admin authorization. Trigger phrases include: "UniFi clients", "connected clients", "who's on the network", "UniFi devices", "access points", "APs", "UniFi switches", "WiFi networks", "WLAN config", "SSIDs", "network health", "UniFi health", "site health", "UniFi alarms", "network alerts", "network events", "UniFi events", "sysinfo", "controller version", "UniFi me". Always use this skill rather than guessing at curl commands or API paths — the UniFi REST API has several gotchas around path prefixes and auth that this s

1 Updated yesterday
dinglebear-ai