Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - `SKILL.md`: Canonical root-layer boundaries, credential rules, and workflow guidance.
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed ALab root-administration guide with high-impact capabilities, but its instructions are coherent, scoped, and include credential and destructive-action safeguards.
Install only if you intend to let an agent assist with ALab root-level administration. Keep root keys out of prompts and logs, prefer stdin or ignored local secret files, review audit/scope before revoking keys, and use dry-runs plus exact confirmations for destructive cleanup or removal commands.
Referenced artifact was not completely inspected
- `SKILL.md`: Canonical root-layer boundaries, credential rules, and workflow guidance.
This skill enables implicit invocation for a global admin capability that is explicitly intended for root authority, credential management, cache/backup pruning, and audit operations. Allowing automatic selection without tightly scoped trigger constraints increases the chance that routine or ambiguous user requests will invoke a highly privileged skill, causing unintended destructive actions or disclosure of sensitive administrative data.
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.
Notes: Root/admin may inspect project credentials; does not render raw admin keys.
- **`key revoke`**: Revoke a credential by id.
Parameters: Required `<key_id>`; optional `--project <project_id>`.
Notes: Root-only for revocation; do not revoke the wrong active key without checking audit and scope.
- **`context show`**: Inspect path context markers and registered ALab paths.
Parameters: Optional `--path <dir>`; default `.`.
Notes: Use before repair or when a command is running in an unexpected project/experiment/inspection context.
The skill content is written as Chinese operational guidance throughout, including headings, cautions, and command explanations, but it does not state that Chinese is optional or that this file is specifically intended for a Chinese-language audience. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
The file identifies itself as the synchronized Chinese version, and the operational guidance throughout is presented in Chinese with no note that users may choose another language. This can violate a language/locale policy when a skill forces a specific language presentation without explicit opt-in or alternative.
No suspicious patterns detected.