@nacos-group/cli 1.0.4 → 1.0.5-beta.3

package/README.md

@@ -84,6 +84,31 @@ nacos> config-list
 nacos> help
 ```
 
+### HTTPS Support
+
+Connect to Nacos servers over HTTPS (e.g., behind a TLS-terminating gateway or K8s Ingress):
+
+```bash
+# Explicit --scheme flag
+nacos-cli skill-list --host nacos.example.com --port 443 --scheme https -u nacos -p nacos
+
+# Auto-detect from host prefix (scheme is inferred automatically)
+nacos-cli skill-list --host https://nacos.example.com:443 -u nacos -p nacos
+
+# Via profile configuration
+nacos-cli --profile prod skill-list
+
+# Via environment variable
+NACOS_SCHEME=https nacos-cli skill-list --host nacos.example.com --port 443 -u nacos -p nacos
+```
+
+Scheme resolution priority (highest to lowest):
+1. `--scheme` command-line flag
+2. Auto-detected from `--host` prefix (`https://...`)
+3. Profile config file `scheme` field
+4. `NACOS_SCHEME` environment variable
+5. Default: `http`
+
 ## Commands
 
 ### AgentSpec Management
@@ -291,6 +316,27 @@ nacos> skill-release skill-creator --version 0.0.2
 > `HTTP 400 parameter validate error` just after `skill-review`, wait and retry
 > when `skill-describe` shows the version as `reviewed`.
 
+#### Manage Skill Visibility and Tags
+
+Set skill visibility scope:
+
+```bash
+nacos-cli skill-scope skill-creator --scope PUBLIC
+nacos-cli skill-scope skill-creator --scope PRIVATE
+
+# Terminal mode
+nacos> skill-scope skill-creator --scope PUBLIC
+```
+
+Set skill metadata tags:
+
+```bash
+nacos-cli skill-tags skill-creator --tags retail,finance
+
+# Terminal mode
+nacos> skill-tags skill-creator --tags retail,finance
+```
+
 #### Publish Skill (deprecated)
 
 `skill-publish` is kept as a backward-compatible shortcut that runs
@@ -369,6 +415,7 @@ nacos> quit           # Exit terminal
 |------|-------|---------|-------------|
 | --host | | market.hiclaw.io when `--host` and `--port` are both omitted; otherwise 127.0.0.1 when only `--port` is provided | Nacos server host |
 | --port | | 80 when `--host` and `--port` are both omitted; otherwise 8848 when omitted after `--host` | Nacos server port |
+| --scheme | | http | Protocol scheme: `http` or `https` |
 | --server | -s | market.hiclaw.io:80 when no host/port is provided | Nacos server address (deprecated, use --host and --port) |
 | --username | -u | nacos | Nacos username |
 | --password | -p | nacos | Nacos password |
@@ -376,54 +423,89 @@ nacos> quit           # Exit terminal
 | --config | -c | | Path to configuration file |
 | --help | -h | | Show help information |
 
-## Configuration File
+## Profile Configuration
 
-You can use a configuration file to avoid typing credentials every time:
+Use `profile edit` to create or update a profile configuration:
 
 ```bash
-# Create a config file
-cat > local.conf << EOF
-host: 127.0.0.1
-port: 8848
-username: nacos
-password: nacos
-namespace: ""
-EOF
+# Create or update the current profile
+nacos-cli profile edit
+
+# Create or update a named profile
+nacos-cli profile edit dev
 
-# Use the config file
-nacos-cli --config ./local.conf skill-list
+# Use a profile once
+nacos-cli --profile dev skill-list
+
+# Switch the default profile used when --profile is omitted
+nacos-cli profile switch dev
 ```
 
-### Configuration File Format
+Profile files are stored under `~/.nacos-cli/<profile>.conf`. They are YAML
+files managed by the CLI, and sensitive fields are encrypted before they are
+saved.
 
-The configuration file uses YAML format:
+Example generated profile:
 
 ```yaml
-# Nacos server host
 host: 127.0.0.1
-
-# Nacos server port
 port: 8848
+scheme: http          # http or https (default: http)
+authType: nacos
+username: ENC[v1:aes-256-gcm:...]
+password: ENC[v1:aes-256-gcm:...]
+namespace: ""
+```
 
-# Username for authentication
-username: nacos
+Sensitive fields (`username`, `password`, `accessKey`, `secretKey`, and
+`securityToken`) are encrypted with AES-256-GCM before being saved by the CLI.
+The local encryption key is stored at `~/.nacos-cli/key` with `0600`
+permissions. Existing plaintext config files remain readable for backward
+compatibility; the next profile load or `profile edit` rewrites sensitive fields
+in encrypted form.
 
-# Password for authentication
-password: nacos
+Profile management commands:
 
-# Namespace ID (optional, leave empty for public namespace)
-namespace: ""
+```bash
+# List profiles
+nacos-cli profile list
+nacos-cli profile list --output json
+
+# Show or read profile values
+nacos-cli profile show dev
+nacos-cli profile get dev server
+nacos-cli profile get auth-type
+
+# Non-interactively create or update profile values
+nacos-cli profile set dev host=127.0.0.1 port=8848 auth-type=none
+nacos-cli profile set dev auth-type=nacos username=nacos password=nacos
+nacos-cli profile set dev server=127.0.0.1:8848 namespace=public
+
+# Delete a profile
+nacos-cli profile delete dev
 ```
 
 ### Configuration Priority
 
 Configuration values are applied in the following priority order:
 1. **Command line arguments** (highest priority)
-2. **Configuration file**
-3. **Default values** (lowest priority)
+2. **Explicit `--profile` or `--config` file**
+3. **Current profile selected by `profile switch`**
+4. **Environment variables**
+5. **Default values** (lowest priority)
+
+Supported environment variables:
+
+```bash
+export NACOS_HOST=127.0.0.1
+export NACOS_PORT=8848
+export NACOS_NAMESPACE=xxx
+export NACOS_SCHEME=https    # http or https (default: http)
+```
 
 For example:
 - `nacos-cli --config ./local.conf --host 10.0.0.1` - Uses `10.0.0.1` from command line, other values from config file
+- `NACOS_HOST=127.0.0.1 NACOS_PORT=8848 NACOS_NAMESPACE=xxx nacos-cli skill-list` - Uses environment variables when command line and config file values are not provided
 - `nacos-cli` - Uses default `market.hiclaw.io:80` when neither `--host` nor `--port` is provided
 - `nacos-cli --host 127.0.0.1` - Uses `127.0.0.1:8848` because `--host` was provided without `--port`
 - `nacos-cli --port 8849` - Uses `127.0.0.1:8849` because only `--port` was provided
@@ -441,6 +523,8 @@ nacos-cli/
 │   ├── upload_skill.go        # skill-upload
 │   ├── review_skill.go        # skill-review
 │   ├── release_skill.go       # skill-release
+│   ├── update_skill_scope.go  # skill-scope
+│   ├── update_skill_tags.go   # skill-tags
 │   ├── publish_skill.go       # skill-publish (deprecated wrapper)
 │   ├── sync_skill.go          # skill-sync
 │   ├── list_agentspec.go      # agentspec-list
@@ -511,6 +595,19 @@ MIT License
 
 ## Changelog
 
+### Next Release
+
+- Fixed `skill-upload` and `agentspec-upload` creating ZIP archives with an
+  extra directory prefix, causing server-side extraction failures
+  ([#46](https://github.com/nacos-group/nacos-cli/issues/46))
+- Fixed ZIP archive paths using OS-native backslashes on Windows, violating
+  the ZIP specification's forward-slash requirement
+  ([#26](https://github.com/nacos-group/nacos-cli/issues/26))
+- Added HTTPS support via `--scheme` flag, profile `scheme` field, and `NACOS_SCHEME`
+  environment variable ([#57](https://github.com/nacos-group/nacos-cli/issues/57))
+- Auto-detect scheme from `--host` URL prefix (e.g. `--host https://nacos.example.com`)
+- All 22 hardcoded `http://` URL constructions replaced with configurable scheme
+
 ### v1.0.4 (2026-05-08)
 
 - Aligned `agentspec-*` commands with `skill-*` around the full server lifecycle

package/bin/cli.js

@@ -7,7 +7,7 @@ const os = require('os');
 
 // Fixed nacos-cli binary version
 // npm package version is independent from binary version
-const VERSION = '1.0.4';
+const VERSION = '1.0.5-beta.3';
 
 // Detect platform and architecture
 function getBinaryName() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nacos-group/cli",
-  "version": "1.0.4",
+  "version": "1.0.5-beta.3",
   "description": "A command-line tool for managing Nacos configurations and AI skills",
   "bin": {
     "nacos-cli": "./bin/cli.js"