[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DJFPDPRFD8PQ5VH4FNFKHM":3,"skill-same:01M7DJFPDPRFD8PQ5VH4FNFKHM":198},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":34,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7DJFPDPRFD8PQ5VH4FNFKHM","octelium-management",null,"Manage the resources of a running Octelium Cluster with octeliumctl: Services (HTTP, SSH, PostgreSQL, MySQL, Kubernetes, TCP\u002FUDP, DNS, SOCKS5, RDP, MCP, LLM; public\u002Fanonymous, secretless upstream credentials, managed containers, dynamic config), Users, Groups, Namespaces, Policies and access control (CEL\u002FOPA conditions, priorities, inline and global Policies), IdentityProviders (GitHub, OIDC, SAML, workload OIDC assertions), Credentials, Sessions, Secrets and ClusterConfig. Use when creating, changing, auditing or deleting Cluster resources, granting or revoking access, writing Policy YAML, or running `octeliumctl apply\u002Fget\u002Fcreate\u002F update\u002Fdelete`. Not for connecting as a client (octelium-connect), installing a Cluster (octelium-quick-install, octelium-kubernetes-install), or upgrades, TLS certificates and Kubernetes-level operations (octelium-cluster-ops).","octelium\u002Foctelium-skills","octelium","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F114482526?v=4","01M7DJECEJJSBE1H8PMS3M8W1E","Octelium","01M7DJECF9SVXYNBZRPRS3PE3R",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: octelium-management\ndescription: >-\n  Manage the resources of a running Octelium Cluster with octeliumctl: Services (HTTP, SSH,\n  PostgreSQL, MySQL, Kubernetes, TCP\u002FUDP, DNS, SOCKS5, RDP, MCP, LLM; public\u002Fanonymous, secretless\n  upstream credentials, managed containers, dynamic config), Users, Groups, Namespaces, Policies\n  and access control (CEL\u002FOPA conditions, priorities, inline and global Policies),\n  IdentityProviders (GitHub, OIDC, SAML, workload OIDC assertions), Credentials, Sessions,\n  Secrets and ClusterConfig. Use when creating, changing, auditing or deleting Cluster resources,\n  granting or revoking access, writing Policy YAML, or running `octeliumctl apply\u002Fget\u002Fcreate\u002F\n  update\u002Fdelete`. Not for connecting as a client (octelium-connect), installing a Cluster\n  (octelium-quick-install, octelium-kubernetes-install), or upgrades, TLS certificates and\n  Kubernetes-level operations (octelium-cluster-ops).\nlicense: Apache-2.0\ncompatibility: Requires octeliumctl logged in to the Cluster with API access. Helper scripts need Python 3.9+ with PyYAML and jsonschema (or uv).\nmetadata:\n  author: Octelium Labs, LLC\n  version: \"0.1.0\"\n  verified-against: octelium v0.43.0\n  source-checked: octelium fe628332 (2026-10-05)\n---\n\n# Octelium: manage Cluster resources\n\nOctelium resources (Core API `core\u002Fv1`) live in the Cluster's own API, not in Kubernetes.\nThey are managed declaratively with `octeliumctl apply` (like `kubectl apply`) plus a few\nimperative commands. Every access decision is made by _Policies_: there is no built-in\nsuperuser, and nothing is reachable unless a Policy allows it.\n\n## Scope\n\n- **Use for:** authoring and applying resource YAML, access control, identity\n  (Users\u002FGroups\u002FIdPs\u002FCredentials\u002FSessions\u002FDevices), Secrets, ClusterConfig, auditing current\n  state, diagnosing \"why is X denied\".\n- **Hand off:** client connection and access problems → **octelium-connect**. Upgrades, TLS\n  certificates, Cluster health, `kubectl`-level work → **octelium-cluster-ops**. No Cluster yet\n  → an install skill.\n\n## Ground rules\n\nCheck the installed CLI's capabilities; the bundled CLI reference is v0.43.0. Follow these\nrules while preserving the user's authorized target and outcome. Prepare the concrete change\nand preview first; ask only for missing inputs or unresolved destructive scope.\n\n1. **Look before you change.** `octeliumctl get \u003Ckind> \u003Cname> -o yaml` for every resource you\n   touch, and the Policies involved. Never assume a resource's current content.\n2. **`apply` replaces whole resources.** Each document is the complete desired spec; any field\n   you omit is reset. To edit an existing resource, export it, change only what was asked,\n   and apply the full document. ClusterConfig is the same: its entire spec is replaced.\n3. **Validate and preview before apply.** Check `octeliumctl validate --help` and\n   `octeliumctl apply --help`. When supported, use `validate \u003Cpaths>` and\n   `apply --dry-run \u003Cpaths> [same flags as apply]`. Validation is local; dry-run reads current\n   state, skips mutations and does not guarantee server acceptance or reserve state. On older\n   CLIs, use `scripts\u002Fvalidate_resources.py` and `scripts\u002Fplan_apply.py` with `uv run` or\n   `python3`. Resolve helper paths against the loaded skill directory, keeping the user's project\n   as the working directory so resource paths still refer to it. The helpers add risk warnings\n   and field-level previews. Apply still drops unknown fields with a warning and can skip rejected resources\n   while applying the rest. Read its output for partial success.\n4. **`--prune` is destructive across kinds.** It deletes every non-system resource of *each\n   included kind* that isn't in the given paths, including kinds with no documents there. A\n   bare `octeliumctl apply --prune .\u002Fservices\u002F` would delete all Users, Groups, Policies,\n   IdentityProviders, Namespaces, Credentials and Configs, including the built-in `root` User,\n   the `root-init` Credential and the `allow-all` Policy. Use `--prune` only when the user asks\n   and the paths are the complete source of truth for the kinds you restrict it to with\n   `--include`; preview with native dry-run when supported and run `plan_apply.py --prune`\n   with the same flags for danger detection. Show the deletions first.\n5. **Never widen access to fix a denial.** Don't attach `allow-all`, add `matchAny` ALLOW rules,\n   disable Policies, remove DENY rules, or set `isPublic`\u002F`isAnonymous` to make something work,\n   unless the user explicitly asks for that exact change. Diagnose (references\u002Fpolicies.md),\n   then propose the narrowest rule and say who gains what.\n6. **Keep secrets out of ordinary files, arguments and output.** Don't put secret values in\n   committed or unprotected YAML, `--value` arguments or chat. Have the user run `octeliumctl create secret \u003Cname>`\n   (interactive prompt) in their terminal, or use `--file \u003Cpath>`, `--from-env VAR` or stdin\n   (`-f -`). Reference Secrets by name (`fromSecret: \u003Cname>`). New Credential tokens are shown\n   once: have the user create them in their terminal, or capture output to an authorized private\n   file without reading its contents into the transcript (references\u002Fidentity-and-access.md).\n7. **Don't lock the admins out.** Before deleting or changing `root`, `root-init`, `allow-all`,\n   admin Users\u002FGroups, IdentityProviders, or Policies on the `octelium-api` Namespace, confirm\n   another admin identity exists and works (e.g. `octeliumctl get user \u003Cadmin>` and a test\n   login by that admin).\n8. **Deletes and updates have no confirmation prompt.** `octeliumctl delete ...`, `update\n   session --reject`, `update credential --disable` act immediately. State exactly what will\n   happen and proceed if the user already authorized that target and outcome; ask only when\n   the scope or destructive effect remains unresolved.\n9. **Don't invent fields, enum values, names or references.** Take field names from the JSON\n   Schema of the kind (references\u002Fresource-model.md lists the URLs); take names from `get`.\n\nIn helper command examples, `octelium_skill_dir` is the absolute directory containing this\nloaded `SKILL.md`. Resolve it from the agent's skill location; don't change the project's working\ndirectory. For example: `uv run \"$octelium_skill_dir\u002Fscripts\u002Fvalidate_resources.py\" desired.yaml`.\n\n## Workflow\n\n1. **Context.** Domain (`OCTELIUM_DOMAIN` or `--domain`), CLI version (`octeliumctl version`),\n   authentication (octeliumctl shares the `octelium` Session; if none exists, the user must log\n   in: see the octelium-connect skill). Reuse authorized access; a diagnostic request doesn't\n   authorize reading tokens or starting browser login. Bound the first harmless API call with\n   the agent's command timeout. Use `timeout 30 octeliumctl get ns` only if GNU `timeout` is\n   available; on other hosts use the agent's equivalent and stop only the process you started.\n2. **Find the source of truth.** Ask whether the Cluster is managed from a Git directory of YAML.\n   If so, edit those files instead of creating drift, and apply from there.\n3. **Inspect** current resources (`get ... -o yaml`), including every Policy that affects the\n   request path (Service, Namespace, User, Groups, ClusterConfig global Policies).\n4. **Author** the smallest change. Start from exported YAML for existing resources; use\n   `assets\u002Ftemplates\u002F` and the references for new ones; check fields against the schema.\n5. **Validate** with native `octeliumctl validate` when supported, or\n   `scripts\u002Fvalidate_resources.py` on older CLIs. Use the helper for additional risk warnings.\n   Fix every error; review every warning.\n6. **Preview** with native `octeliumctl apply --dry-run` when supported, or\n   `scripts\u002Fplan_apply.py` on older CLIs, using the same paths and flags you will apply. Show\n   the user the plan when it updates or deletes anything, touches Policies or identity, or\n   exposes a Service publicly.\n7. **Apply** exactly what was previewed: `octeliumctl apply \u003Cpaths> [flags]`. Read the output for\n   `Unknown field`, `Could not create`, `Could not update` and `Skipping` lines.\n8. **Verify** with `get`, and for access changes, a real request by the intended User (or ask\n   the user to test).\n9. **Report** what changed, what access it grants or removes, and how to revert.\n\n## Command map\n\n| Task | Command |\n| --- | --- |\n| Apply desired state | `octeliumctl apply \u003Cfile-or-dir>... [--include K] [--exclude K] [--include-secret] [--prune]`; `-` reads stdin |\n| Validate \u002F preview (when supported) | `octeliumctl validate \u003Cpaths>`; `octeliumctl apply --dry-run \u003Cpaths> [apply flags]` |\n| Read | `octeliumctl get \u003Ckind> [name] [-o yaml\\|json]`; list flags `--page`, `--items-per-page`, `--order-by-name`, `--order-reverse`; filters `get svc --namespace`, `get cred\\|sess\\|dev\\|authn --user` |\n| Kinds for `get` | `service svc`, `namespace ns`, `user usr`, `group grp`, `policy pol`, `identityprovider idp`, `credential cred`, `session sess`, `device dev`, `authenticator authn`, `secret sec`, `config cfg`, `clusterconfig cc`, `gateway gw`, `region rgn` |\n| Create imperatively | `create secret`, `create config`, `create credential`, `create namespace` (everything else via `apply`) |\n| Update imperatively | `update session --approve\\|--reject\\|--expire-in`, `update credential --enable\\|--disable\\|--expire-in\\|--max-authn\\|--policy`, `update device\\|authenticator --approve\\|--reject`, `update secret\\|config` |\n| Delete | `octeliumctl delete \u003Ckind> \u003Cname>` (aliases `del`, `rm`); Services as `name` or `name.namespace` |\n\n`apply` manages Config, Policy, IdentityProvider, Namespace, Group, User, Service, Credential\n(Secret only with `--include-secret`) and ClusterConfig. Sessions, Devices, Authenticators,\nGateways and Regions are not applied.\n\n## References\n\nRead only what the task needs:\n\n| Need | File |\n| --- | --- |\n| Apply semantics, repo layout, export-edit-apply, prune safety, the helper scripts | [references\u002Fapply-workflow.md](references\u002Fapply-workflow.md) |\n| Kinds, naming (`svc.ns`), built-in resources, JSON Schema URLs | [references\u002Fresource-model.md](references\u002Fresource-model.md) |\n| Policy evaluation, conditions, `ctx` fields, priorities, recipes, diagnosing denials | [references\u002Fpolicies.md](references\u002Fpolicies.md) |\n| Service modes, upstreams, secretless auth, public\u002Fanonymous, TLS, containers, dynamic config | [references\u002Fservices.md](references\u002Fservices.md) |\n| Users, Groups, IdentityProviders, Credentials, Sessions, Devices, first-admin bootstrap | [references\u002Fidentity-and-access.md](references\u002Fidentity-and-access.md) |\n| Secrets, Configs and ClusterConfig | [references\u002Fsecrets-and-cluster-config.md](references\u002Fsecrets-and-cluster-config.md) |\n| Access logs, observability, common errors | [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md) |\n| Exact `octeliumctl` flags (snapshot) | [references\u002Fcli-octeliumctl.md](references\u002Fcli-octeliumctl.md) |\n| Starting-point YAML (validated) | `assets\u002Ftemplates\u002F*.yaml` |\n\n## Sources of truth\n\n1. **Resource structure:** the JSON Schema for the kind,\n   `https:\u002F\u002Foctelium.com\u002Fschemas\u002Foctelium\u002Flatest\u002Fcore.v1.\u003CKind>.schema.json` (bundled snapshot in\n   `assets\u002Fschemas\u002F`). Schema beats prose examples for field names, types and enums.\n2. **CLI syntax:** `octeliumctl \u003Ccommand> --help` on the installed version beats the bundled\n   snapshot.\n3. **Semantics and newer features:** https:\u002F\u002Foctelium.com\u002Fdocs\u002Foctelium\u002Flatest\u002Fllms.txt and the\n   page's Markdown twin (`\u003Cpage-url>.md`). Check them when a feature isn't covered here or may\n   have changed.\n","# Octelium: manage Cluster resources\n\nOctelium resources (Core API `core\u002Fv1`) live in the Cluster's own API, not in Kubernetes.\nThey are managed declaratively with `octeliumctl apply` (like `kubectl apply`) plus a few\nimperative commands. Every access decision is made by _Policies_: there is no built-in\nsuperuser, and nothing is reachable unless a Policy allows it.\n\n## Scope\n\n- **Use for:** authoring and applying resource YAML, access control, identity\n  (Users\u002FGroups\u002FIdPs\u002FCredentials\u002FSessions\u002FDevices), Secrets, ClusterConfig, auditing current\n  state, diagnosing \"why is X denied\".\n- **Hand off:** client connection and access problems → **octelium-connect**. Upgrades, TLS\n  certificates, Cluster health, `kubectl`-level work → **octelium-cluster-ops**. No Cluster yet\n  → an install skill.\n\n## Ground rules\n\nCheck the installed CLI's capabilities; the bundled CLI reference is v0.43.0. Follow these\nrules while preserving the user's authorized target and outcome. Prepare the concrete change\nand preview first; ask only for missing inputs or unresolved destructive scope.\n\n1. **Look before you change.** `octeliumctl get \u003Ckind> \u003Cname> -o yaml` for every resource you\n   touch, and the Policies involved. Never assume a resource's current content.\n2. **`apply` replaces whole resources.** Each document is the complete desired spec; any field\n   you omit is reset. To edit an existing resource, export it, change only what was asked,\n   and apply the full document. ClusterConfig is the same: its entire spec is replaced.\n3. **Validate and preview before apply.** Check `octeliumctl validate --help` and\n   `octeliumctl apply --help`. When supported, use `validate \u003Cpaths>` and\n   `apply --dry-run \u003Cpaths> [same flags as apply]`. Validation is local; dry-run reads current\n   state, skips mutations and does not guarantee server acceptance or reserve state. On older\n   CLIs, use `scripts\u002Fvalidate_resources.py` and `scripts\u002Fplan_apply.py` with `uv run` or\n   `python3`. Resolve helper paths against the loaded skill directory, keeping the user's project\n   as the working directory so resource paths still refer to it. The helpers add risk warnings\n   and field-level previews. Apply still drops unknown fields with a warning and can skip rejected resources\n   while applying the rest. Read its output for partial success.\n4. **`--prune` is destructive across kinds.** It deletes every non-system resource of *each\n   included kind* that isn't in the given paths, including kinds with no documents there. A\n   bare `octeliumctl apply --prune .\u002Fservices\u002F` would delete all Users, Groups, Policies,\n   IdentityProviders, Namespaces, Credentials and Configs, including the built-in `root` User,\n   the `root-init` Credential and the `allow-all` Policy. Use `--prune` only when the user asks\n   and the paths are the complete source of truth for the kinds you restrict it to with\n   `--include`; preview with native dry-run when supported and run `plan_apply.py --prune`\n   with the same flags for danger detection. Show the deletions first.\n5. **Never widen access to fix a denial.** Don't attach `allow-all`, add `matchAny` ALLOW rules,\n   disable Policies, remove DENY rules, or set `isPublic`\u002F`isAnonymous` to make something work,\n   unless the user explicitly asks for that exact change. Diagnose (references\u002Fpolicies.md),\n   then propose the narrowest rule and say who gains what.\n6. **Keep secrets out of ordinary files, arguments and output.** Don't put secret values in\n   committed or unprotected YAML, `--value` arguments or chat. Have the user run `octeliumctl create secret \u003Cname>`\n   (interactive prompt) in their terminal, or use `--file \u003Cpath>`, `--from-env VAR` or stdin\n   (`-f -`). Reference Secrets by name (`fromSecret: \u003Cname>`). New Credential tokens are shown\n   once: have the user create them in their terminal, or capture output to an authorized private\n   file without reading its contents into the transcript (references\u002Fidentity-and-access.md).\n7. **Don't lock the admins out.** Before deleting or changing `root`, `root-init`, `allow-all`,\n   admin Users\u002FGroups, IdentityProviders, or Policies on the `octelium-api` Namespace, confirm\n   another admin identity exists and works (e.g. `octeliumctl get user \u003Cadmin>` and a test\n   login by that admin).\n8. **Deletes and updates have no confirmation prompt.** `octeliumctl delete ...`, `update\n   session --reject`, `update credential --disable` act immediately. State exactly what will\n   happen and proceed if the user already authorized that target and outcome; ask only when\n   the scope or destructive effect remains unresolved.\n9. **Don't invent fields, enum values, names or references.** Take field names from the JSON\n   Schema of the kind (references\u002Fresource-model.md lists the URLs); take names from `get`.\n\nIn helper command examples, `octelium_skill_dir` is the absolute directory containing this\nloaded `SKILL.md`. Resolve it from the agent's skill location; don't change the project's working\ndirectory. For example: `uv run \"$octelium_skill_dir\u002Fscripts\u002Fvalidate_resources.py\" desired.yaml`.\n\n## Workflow\n\n1. **Context.** Domain (`OCTELIUM_DOMAIN` or `--domain`), CLI version (`octeliumctl version`),\n   authentication (octeliumctl shares the `octelium` Session; if none exists, the user must log\n   in: see the octelium-connect skill). Reuse authorized access; a diagnostic request doesn't\n   authorize reading tokens or starting browser login. Bound the first harmless API call with\n   the agent's command timeout. Use `timeout 30 octeliumctl get ns` only if GNU `timeout` is\n   available; on other hosts use the agent's equivalent and stop only the process you started.\n2. **Find the source of truth.** Ask whether the Cluster is managed from a Git directory of YAML.\n   If so, edit those files instead of creating drift, and apply from there.\n3. **Inspect** current resources (`get ... -o yaml`), including every Policy that affects the\n   request path (Service, Namespace, User, Groups, ClusterConfig global Policies).\n4. **Author** the smallest change. Start from exported YAML for existing resources; use\n   `assets\u002Ftemplates\u002F` and the references for new ones; check fields against the schema.\n5. **Validate** with native `octeliumctl validate` when supported, or\n   `scripts\u002Fvalidate_resources.py` on older CLIs. Use the helper for additional risk warnings.\n   Fix every error; review every warning.\n6. **Preview** with native `octeliumctl apply --dry-run` when supported, or\n   `scripts\u002Fplan_apply.py` on older CLIs, using the same paths and flags you will apply. Show\n   the user the plan when it updates or deletes anything, touches Policies or identity, or\n   exposes a Service publicly.\n7. **Apply** exactly what was previewed: `octeliumctl apply \u003Cpaths> [flags]`. Read the output for\n   `Unknown field`, `Could not create`, `Could not update` and `Skipping` lines.\n8. **Verify** with `get`, and for access changes, a real request by the intended User (or ask\n   the user to test).\n9. **Report** what changed, what access it grants or removes, and how to revert.\n\n## Command map\n\n| Task | Command |\n| --- | --- |\n| Apply desired state | `octeliumctl apply \u003Cfile-or-dir>... [--include K] [--exclude K] [--include-secret] [--prune]`; `-` reads stdin |\n| Validate \u002F preview (when supported) | `octeliumctl validate \u003Cpaths>`; `octeliumctl apply --dry-run \u003Cpaths> [apply flags]` |\n| Read | `octeliumctl get \u003Ckind> [name] [-o yaml\\|json]`; list flags `--page`, `--items-per-page`, `--order-by-name`, `--order-reverse`; filters `get svc --namespace`, `get cred\\|sess\\|dev\\|authn --user` |\n| Kinds for `get` | `service svc`, `namespace ns`, `user usr`, `group grp`, `policy pol`, `identityprovider idp`, `credential cred`, `session sess`, `device dev`, `authenticator authn`, `secret sec`, `config cfg`, `clusterconfig cc`, `gateway gw`, `region rgn` |\n| Create imperatively | `create secret`, `create config`, `create credential`, `create namespace` (everything else via `apply`) |\n| Update imperatively | `update session --approve\\|--reject\\|--expire-in`, `update credential --enable\\|--disable\\|--expire-in\\|--max-authn\\|--policy`, `update device\\|authenticator --approve\\|--reject`, `update secret\\|config` |\n| Delete | `octeliumctl delete \u003Ckind> \u003Cname>` (aliases `del`, `rm`); Services as `name` or `name.namespace` |\n\n`apply` manages Config, Policy, IdentityProvider, Namespace, Group, User, Service, Credential\n(Secret only with `--include-secret`) and ClusterConfig. Sessions, Devices, Authenticators,\nGateways and Regions are not applied.\n\n## References\n\nRead only what the task needs:\n\n| Need | File |\n| --- | --- |\n| Apply semantics, repo layout, export-edit-apply, prune safety, the helper scripts | [references\u002Fapply-workflow.md](references\u002Fapply-workflow.md) |\n| Kinds, naming (`svc.ns`), built-in resources, JSON Schema URLs | [references\u002Fresource-model.md](references\u002Fresource-model.md) |\n| Policy evaluation, conditions, `ctx` fields, priorities, recipes, diagnosing denials | [references\u002Fpolicies.md](references\u002Fpolicies.md) |\n| Service modes, upstreams, secretless auth, public\u002Fanonymous, TLS, containers, dynamic config | [references\u002Fservices.md](references\u002Fservices.md) |\n| Users, Groups, IdentityProviders, Credentials, Sessions, Devices, first-admin bootstrap | [references\u002Fidentity-and-access.md](references\u002Fidentity-and-access.md) |\n| Secrets, Configs and ClusterConfig | [references\u002Fsecrets-and-cluster-config.md](references\u002Fsecrets-and-cluster-config.md) |\n| Access logs, observability, common errors | [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md) |\n| Exact `octeliumctl` flags (snapshot) | [references\u002Fcli-octeliumctl.md](references\u002Fcli-octeliumctl.md) |\n| Starting-point YAML (validated) | `assets\u002Ftemplates\u002F*.yaml` |\n\n## Sources of truth\n\n1. **Resource structure:** the JSON Schema for the kind,\n   `https:\u002F\u002Foctelium.com\u002Fschemas\u002Foctelium\u002Flatest\u002Fcore.v1.\u003CKind>.schema.json` (bundled snapshot in\n   `assets\u002Fschemas\u002F`). Schema beats prose examples for field names, types and enums.\n2. **CLI syntax:** `octeliumctl \u003Ccommand> --help` on the installed version beats the bundled\n   snapshot.\n3. **Semantics and newer features:** https:\u002F\u002Foctelium.com\u002Fdocs\u002Foctelium\u002Flatest\u002Fllms.txt and the\n   page's Markdown twin (`\u003Cpage-url>.md`). Check them when a feature isn't covered here or may\n   have changed.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":29},{"author":25,"version":26,"source-checked":27,"verified-against":28},"Octelium Labs, LLC","0.1.0","octelium fe628332 (2026-10-05)","octelium v0.43.0","Requires octeliumctl logged in to the Cluster with API access. Helper scripts need Python 3.9+ with PyYAML and jsonschema (or uv).","main","a3e3f906091d5e63044a695dc0d8946740a15269","skills\u002Foctelium-management","https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills","https:\u002F\u002Foctelium.com","https:\u002F\u002Fgithub.com\u002Foctelium","A next-gen FOSS unified zero trust secure access platform that's relevant for the age of AI and dynamic workloads","2026-10-10 07:17:27",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add octelium\u002Foctelium-skills --skill octelium-management",{"tool":44,"command":45},"bunx","bunx skills add octelium\u002Foctelium-skills --skill octelium-management",{"tool":47,"command":48},"pnpm","pnpm dlx skills add octelium\u002Foctelium-skills --skill octelium-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002FSKILL.md",true,[52,58,62,66,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142,146,152,156,160,164,168,172,176,180,186,190,194],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Fschemas\u002Fcore.v1.AccessLog.schema.json","ASSET","资产文件",57238,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.AccessLog.schema.json",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"assets\u002Fschemas\u002Fcore.v1.Authenticator.schema.json",17350,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Authenticator.schema.json",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"assets\u002Fschemas\u002Fcore.v1.ClusterConfig.schema.json",51337,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.ClusterConfig.schema.json",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"assets\u002Fschemas\u002Fcore.v1.ComponentLog.schema.json",4481,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.ComponentLog.schema.json",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Fschemas\u002Fcore.v1.Config.schema.json",7091,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Config.schema.json",{"path":75,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Fschemas\u002Fcore.v1.Credential.schema.json",16175,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Credential.schema.json",{"path":79,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Fschemas\u002Fcore.v1.Device.schema.json",26136,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Device.schema.json",{"path":83,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":84,"sourceHtmlUrl":85},"assets\u002Fschemas\u002Fcore.v1.Gateway.schema.json",8359,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Gateway.schema.json",{"path":87,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":88,"sourceHtmlUrl":89},"assets\u002Fschemas\u002Fcore.v1.Group.schema.json",13838,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Group.schema.json",{"path":91,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":92,"sourceHtmlUrl":93},"assets\u002Fschemas\u002Fcore.v1.IdentityProvider.schema.json",17991,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.IdentityProvider.schema.json",{"path":95,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":96,"sourceHtmlUrl":97},"assets\u002Fschemas\u002Fcore.v1.Namespace.schema.json",13782,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Namespace.schema.json",{"path":99,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":100,"sourceHtmlUrl":101},"assets\u002Fschemas\u002Fcore.v1.Policy.schema.json",12027,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Policy.schema.json",{"path":103,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":104,"sourceHtmlUrl":105},"assets\u002Fschemas\u002Fcore.v1.PolicyTrigger.schema.json",17351,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.PolicyTrigger.schema.json",{"path":107,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":108,"sourceHtmlUrl":109},"assets\u002Fschemas\u002Fcore.v1.Region.schema.json",7370,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Region.schema.json",{"path":111,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":112,"sourceHtmlUrl":113},"assets\u002Fschemas\u002Fcore.v1.Secret.schema.json",7359,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Secret.schema.json",{"path":115,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":116,"sourceHtmlUrl":117},"assets\u002Fschemas\u002Fcore.v1.Service.schema.json",199814,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Service.schema.json",{"path":119,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":120,"sourceHtmlUrl":121},"assets\u002Fschemas\u002Fcore.v1.Session.schema.json",43551,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.Session.schema.json",{"path":123,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":124,"sourceHtmlUrl":125},"assets\u002Fschemas\u002Fcore.v1.User.schema.json",19912,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Fschemas\u002Fcore.v1.User.schema.json",{"path":127,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":128,"sourceHtmlUrl":129},"assets\u002Ftemplates\u002Ffirst-admin.yaml",830,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Ftemplates\u002Ffirst-admin.yaml",{"path":131,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":132,"sourceHtmlUrl":133},"assets\u002Ftemplates\u002Fgroup-service-access.yaml",411,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Ftemplates\u002Fgroup-service-access.yaml",{"path":135,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":136,"sourceHtmlUrl":137},"assets\u002Ftemplates\u002Fpostgres-secretless.yaml",626,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Ftemplates\u002Fpostgres-secretless.yaml",{"path":139,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":140,"sourceHtmlUrl":141},"assets\u002Ftemplates\u002Fserved-by-connector.yaml",664,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Ftemplates\u002Fserved-by-connector.yaml",{"path":143,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":144,"sourceHtmlUrl":145},"assets\u002Ftemplates\u002Fworkload-github-actions.yaml",514,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fassets\u002Ftemplates\u002Fworkload-github-actions.yaml",{"path":147,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":150,"sourceHtmlUrl":151},"references\u002Fapply-workflow.md","REFERENCE","参考文档",10796,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Freferences\u002Fapply-workflow.md",{"path":153,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":154,"sourceHtmlUrl":155},"references\u002Fcli-octeliumctl.md",27739,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Freferences\u002Fcli-octeliumctl.md",{"path":157,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":158,"sourceHtmlUrl":159},"references\u002Fidentity-and-access.md",7558,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Freferences\u002Fidentity-and-access.md",{"path":161,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":162,"sourceHtmlUrl":163},"references\u002Fpolicies.md",11235,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Freferences\u002Fpolicies.md",{"path":165,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":166,"sourceHtmlUrl":167},"references\u002Fresource-model.md",5792,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Freferences\u002Fresource-model.md",{"path":169,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":170,"sourceHtmlUrl":171},"references\u002Fsecrets-and-cluster-config.md",4593,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Freferences\u002Fsecrets-and-cluster-config.md",{"path":173,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":174,"sourceHtmlUrl":175},"references\u002Fservices.md",8137,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Freferences\u002Fservices.md",{"path":177,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":178,"sourceHtmlUrl":179},"references\u002Ftroubleshooting.md",3653,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Freferences\u002Ftroubleshooting.md",{"path":181,"resourceType":182,"resourceTypeDesc":183,"sizeBytes":184,"sourceHtmlUrl":185},"scripts\u002F_common.py","SCRIPT","脚本",9404,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fscripts\u002F_common.py",{"path":187,"resourceType":182,"resourceTypeDesc":183,"sizeBytes":188,"sourceHtmlUrl":189},"scripts\u002Fexport_resources.py",4372,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fscripts\u002Fexport_resources.py",{"path":191,"resourceType":182,"resourceTypeDesc":183,"sizeBytes":192,"sourceHtmlUrl":193},"scripts\u002Fplan_apply.py",11691,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fscripts\u002Fplan_apply.py",{"path":195,"resourceType":182,"resourceTypeDesc":183,"sizeBytes":196,"sourceHtmlUrl":197},"scripts\u002Fvalidate_resources.py",10594,"https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-management\u002Fscripts\u002Fvalidate_resources.py",[199,206,213,220,227],{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":19},"01M7DJG02MG7V25VDHYGFNH08A","octelium-quick-install","Install, resume, repair or remove a single-node Octelium Cluster on one Linux VM\u002FVPS with the official quick installer (https:\u002F\u002Foctelium.com\u002Finstall-cluster.sh), which provisions K3s, Multus, PostgreSQL and Valkey and bootstraps Octelium. Covers host and domain prerequisites, NAT\u002Fcloud firewalls (`--nat`, `--public-ip`, ports), installer options, resuming a failed run, post-install public DNS and TLS certificate (certbot + `octops cert`), the first login with the initial token, and the safe use of `--uninstall`, `--purge-data`, `--reset-db` and `--force`. Use for \"install Octelium on a server\u002FVPS\u002Fhomelab\u002Fsingle node\" or installer errors. Not for existing or multi-node Kubernetes (octelium-kubernetes-install), upgrades and certificate rotation of a running Cluster (octelium-cluster-ops), or managing resources (octelium-management).","https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-quick-install\u002FSKILL.md",[],[],{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"publishedAt":19},"01M7DJFC2H14W1B3S6K7NTCPYB","octelium-kubernetes-install","Plan and perform a production Octelium Cluster installation on an existing Kubernetes cluster (EKS, GKE, AKS, DigitalOcean, Linode, on-prem, k3s\u002FRKE2\u002FTalos, multi-node) with `octops init` and a Bootstrap file. Covers Octelium data-plane\u002Fcontrol-plane node labels, primary CNI plus Multus (Cilium non-exclusive), CNI conf dir, Gateway public IPs and the `octelium.com\u002Foverride-gw-ip` annotation, the LoadBalancer Ingress, front proxy mode, SPIFFE, external PostgreSQL and Redis\u002FValkey with passwordFromSecret, network ranges, QUIC, and post-install DNS, TLS (cert-manager or `octops cert`) and first login. Use for \"install Octelium on Kubernetes\u002Fproduction\u002Fmulti-node\" or `octops init` problems. Not for a single fresh VM (octelium-quick-install), upgrades or Day-2 operations (octelium-cluster-ops), or managing resources (octelium-management).","https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-kubernetes-install\u002FSKILL.md",[],[],{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":19},"01M7DJF1PWZ14WCPW7AK5MN9XC","octelium-connect","Use the octelium client to reach an existing Octelium Cluster as a User. Covers installing the CLIs, logging in (browser\u002FIdP, authentication token, OIDC assertion, access token), `octelium connect` (detached, rootless, `-p` publishing Services to localhost, `--serve` to host Services, embedded SSH\u002FSOCKS5, QUIC), reaching Services by name or FQDN (HTTP, SSH, PostgreSQL, MySQL, Kubernetes via `octelium config`), `octelium ssh`\u002F`cp`, running the client in Docker, Kubernetes or CI, and fixing login, tunnel and DNS failures. Use when someone wants to access, connect to or serve through Octelium. Not for creating Services, Users or Policies (octelium-management) or for installing\u002Foperating a Cluster (octelium-quick-install, octelium-kubernetes-install, octelium-cluster-ops).","https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-connect\u002FSKILL.md",[],[],{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":19},"01M7DJEPQV48JJEH7N518JYC1F","octelium-cluster-ops","Operate an installed Octelium Cluster at the Kubernetes\u002Finfrastructure level with octops and kubectl: check for and perform upgrades (`octops upgrade`), set or rotate the Cluster and Namespace TLS certificates (`octops cert`, cert-manager, the `cert-cluster` Secret), install or upgrade packages (Cordium, Enterprise), check Cluster health and component logs, add or change data-plane nodes and Gateway public IPs, recover the initial admin token, and uninstall (`octops uninstall`). Use for Day-2 operations and outages where the Cluster itself (not a Policy) is suspect. Not for first-time installation (octelium-quick-install, octelium-kubernetes-install), managing Users\u002FServices\u002FPolicies (octelium-management), or client-side connection problems (octelium-connect).","https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Foctelium-cluster-ops\u002FSKILL.md",[],[],{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":233,"publishedAt":19},"01M7DJEDQS37W1R2725V86ZFVB","cordium","Install, configure and use Cordium, the identity-based sandbox platform built on Octelium and Kubernetes. Use for Cordium Workspaces, the cordium CLI, Go\u002FPython\u002FRust\u002FTypeScript SDKs, the web portal and Cordium Agent, Workspace\u002FTemplate YAML, Spaces and Memberships, pre-builds, Secrets and GitProviders, UserConfig and UserSecrets, Volumes and WorkspaceSnapshots, secretless access, egress rules and the Cordium ClusterConfig. Routes to configuration references and worked examples for development, AI agents and CI\u002FCD. Not for Octelium Services and Policies in general (octelium-management), client tunnels (octelium-connect), or installing and operating the Octelium Cluster (octelium-quick-install, octelium-kubernetes-install, octelium-cluster-ops).","https:\u002F\u002Fgithub.com\u002Foctelium\u002Foctelium-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcordium\u002FSKILL.md",[],[]]