nanocosmos-skills
Skills that teach your AI coding assistant the nanocosmos platform.
Install them once, and Claude Code (or Cursor, Copilot, and similar tools)
answers questions about nanoStream and
nanoStudio with verified, documentation-backed knowledge — and can run checks
against your own account instead of guessing.
Public home: https://github.com/nanocosmos/nanocosmos-skills
What this is, in plain words
A skill is a folder with a SKILL.md file (instructions written for an AI
assistant) plus, where useful, small scripts and reference documents. Your
assistant reads a skill only when a question matches it, so installing all of
them costs nothing until they are needed. The scripts are ordinary bash and
python3 files you can read before running; they call the public nanocosmos
APIs with your credentials and only ever reach your own organisation's
streams and metrics.
With the skills installed you can ask things like:
- "Is my stream
XXXXX-YYYYY really live, and why does it take five seconds to start?"
- "Give me a working nanoPlayer 5 config for secure playback of this stream."
- "What was our buffering ratio last night, per stream and per country?"
- "How do I set up nanoStudio Chroma for three branded outputs from one green-screen feed?"
- "Build me a dark, broadcast-style control panel for this player page."
What the skills are not: a support channel, and not a replacement for the
documentation. They are made for nanocosmos
customers and evaluating users, are updated frequently, and contain no
internal-only nanocosmos information. When a question needs account-side
checks or platform-side monitoring, the skills say so and point you to
support.
Generated repository. Everything here is generated from nanocosmos's
internal knowledge base and re-released on every sync. Don't edit files
here — corrections land in the source. Found a mistake? Open an issue.
Skills
| Skill | For | What it enables |
|---|
nanostream-analytics | anyone with a dashboard account | Query your own nanoStream Analytics metrics (buffering, latency, startup time, playback errors by geo/browser, usage volumes) with your dashboard credentials — including the query semantics that prevent wrong answers. Read-only |
nanostream-development | developers / integrators | Ingest with ffmpeg/OBS (RTMP/SRT), playback paths (JS player, iframe, emulated MP4/M3U8, RTMP pull), nanoPlayer 5 configuration with verified parameter values, JWT-secure playback, ABR groups, ready-to-fork player pages |
nanostudio | producers / operators | The real-time production tools product line. nanoStudio Chroma: server-side chroma-key and multi-brand compositing — one green-screen feed in, multiple branded streams out to nanoStream and global destinations. More production tools (audio/video improvement, denoising) are planned |
nanostream-diagnostics | anyone operating streams | Self-serve troubleshooting with your own organisation's API key: is the stream really live, GOP/keyframe measurement (the top cause of slow starts), stream architecture resolution, token validation, plus 30+ troubleshooting references (ingest, playback, quality, latency, errors, captions, recording) |
dark-neutral-studio | frontend developers | A complete portable dark-UI design system for AV/broadcast tooling — tokens, CSS, layout, status semantics; pairs with the nanostream-development player pages |
Install
Pick one route per machine — they all deliver the same five skills, and two
routes side by side would load every skill twice.
1. Claude Code plugin (recommended)
One install, all five skills, updated together:
claude plugin marketplace add nanocosmos/nanocosmos-skills
claude plugin install nanocosmos@nanocosmos
Working from a local clone instead? claude plugin marketplace add /path/to/nanocosmos-skills does the same. For everyone working in one
repository, add --scope project to both commands and commit the
.claude/settings.json they write.
2. Clone into your skills folder
Claude Code loads any folder under its skills directory that carries a
.claude-plugin/plugin.json as a plugin, so a plain clone is enough:
git clone https://github.com/nanocosmos/nanocosmos-skills.git ~/.claude/skills/nanocosmos-skills
The skills appear as nanocosmos:<skill> in the next session (or after
/reload-plugins). Update with git pull. Inside one project, use a git
submodule at .claude/skills/nanocosmos-skills instead; Claude Code asks you
to trust the workspace once before loading it.
3. Generic skills installers
Both installers read the Agent Skills format and place the skills where your
assistant expects them — Claude Code, Cursor, Codex, Copilot, Windsurf and
others. Default scope is the current project; the flags shown install for
every project.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
