Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md A valid skill directory must contain a `SKILL.md` file with proper frontmatter (name, description). Confirm the path:
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Nacos registry helper that can install, update, and publish skills, with some credential and backup handling users should review before use.
Before installing, make sure you intend this skill to let an agent use nacos-cli against your configured Nacos registry. Confirm the active profile, namespace, and auth mode before any upload, review, or release, and avoid leaving private skill backups in /tmp on shared machines.
Referenced artifact was not completely inspected
A valid skill directory must contain a `SKILL.md` file with proper frontmatter (name, description). Confirm the path:
The activation guidance includes generic phrases like "how do I do X" and broad requests such as "what skills are available," which are common in everyday conversation and could cause the skill to be invoked too often. The document does not provide exclusion conditions or negative examples to narrow when this skill should activate versus when general assistance should be used.
The skill encourages reading and relying on persistent local environment variables and profile files for authentication and connection state. This creates session persistence and ambient-authority behavior: an agent may act using preexisting credentials or configuration without fresh user confirmation, potentially against the wrong Nacos environment or namespace. In a registry-management skill, that can lead to unintended access, publishing, or data disclosure.
nacos-cli uses a profile mechanism. Profile configs are stored in ~/.nacos-cli/<profile>.conf. The default profile is default (i.e., ~/.nacos-cli/default.conf).
Before asking the user to create or edit a profile, check whether the environment already provides a complete
sts-hiclaw setup:
This workflow persists local copies and backups of skills under predictable filesystem locations such as ~/.skills and /tmp. While operationally useful, it increases retention of potentially sensitive skill contents and local modifications, and /tmp backups may be accessible to other local users or remain after the task ends. In the context of team or private skill registries, that can expose unpublished or internal skill logic.
Option A: Discard local changes, use remote version
This is the simpler path. Back up the local version first, then overwrite with the remote:
# 1. Back up the current local skill
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
B) Merge local and remote changes, then publish as a new version
**Never overwrite local changes without asking.** Always back up before any destructive operation.
## How to Help Users Publish Skills to Nacos