unifi-yourskill
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.
Profile →npx skills add t3chnaztea/unifi-skills --skill template --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 mo
- Guidelines for a good UniFi skill
- Overview
- When to use
- [Your sections]
What does the unifi-yourskill skill do?
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.
How do I install it?
Run `npx skills add t3chnaztea/unifi-skills --skill template --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From t3chnaztea/unifi-skills, a repository with 24 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.