Menu
Tier0 platform operations entry point: CLI setup, authentication, routing to UNS, Flow, service info, and API key diagnostics skills.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Tier0 UNS operations: browse, read, write, history, search, create, update, delete, and restore namespace nodes and topics.
Tier0 Flow management for Node-RED: list, create, update, delete, export, and deploy SourceFlow and EventFlow canvas JSON.
| name | tier0 |
| description | Tier0 platform operations entry point: CLI setup, authentication, routing to UNS, Flow, service info, and API key diagnostics skills. |
| metadata | {"requires":{"bins":["tier0"]},"cliHelp":"tier0 --help"} |
This is the shared entry point for Tier0 CLI work. Keep this file focused on setup, authentication, and routing. Task-specific behavior belongs in the matching sub skill or reference file.
Use this skill when the user asks about:
Recommended install:
npx @tier0/cli@latest
Alternative install:
curl -fsSL https://raw.githubusercontent.com/FREEZONEX/Tier0-cli/main/install.sh | bash
If using the alternative installer, install skills separately:
npx skills add FREEZONEX/Tier0-skill
SaaS uses https://tier0.dev by default.
Private deployments must be configured before login:
tier0 config --base-url <tier0-base-url>
If base-url changes, run login again or set an API key for that instance. Existing keys are tied to the previous instance and Workspace.
Preferred when an API key is already available:
tier0 config --api-key <api-key>
Browser device flow:
tier0 login --no-wait --json
Show the returned verification_url to the user. Then poll with:
tier0 login --setup-code <setup_code>
The polling command blocks until browser authorization completes or times out.
Read the target sub skill or reference before executing a task-specific command.
| User goal | Read |
|---|---|
| Browse, search, read, write, history, create, update, delete, or restore UNS nodes/topics | uns/SKILL.md |
| List, inspect, create, update, delete, export, or deploy Node-RED Flows | flow/SKILL.md |
| Check service connectivity and gateway info | info/info.md |
| Check API key identity and permissions | auth/whoami.md |
| Concept | Meaning |
|---|---|
| Workspace | Tenant boundary for all resources |
| UNS | Unified Namespace, a tree of paths and data topics |
| Path | Folder-like namespace segment |
| Topic | Full leaf path, such as Plant/Line1/Metric/Temperature |
| Flow | Node-RED instance managed by Tier0 |
Flow names and UNS paths are often manually kept similar, but current APIs do not expose a guaranteed relation field. When the user asks about a named device or data point, check both UNS and Flow unless they explicitly ask for only one side.
Quote wildcard topics in shells that expand *, +, or #:
tier0 uns read --topic 'Plant/+/Metric/Temperature'
For complex JSON, prefer files or stdin over fragile shell quoting.
The CLI checks for updates in the background at most once every 24 hours. Upgrade manually with:
tier0 upgrade
tier0 skills update