Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - Đặt tên chính xác `SKILL.md`
Security audit
Security checks for vulnerabilities and agentic risk
This is a Vietnamese guide for creating skills with a small local validator, and the risky-looking scanner hits are examples or scope-quality notes rather than hidden unsafe behavior.
Install this if you want Vietnamese guidance for creating skills. When copying its templates into real skills, narrow trigger phrases, add explicit confirmation before external service changes, and run the validator only on folders you intend to inspect.
Referenced artifact was not completely inspected
- Đặt tên chính xác `SKILL.md`
Referenced artifact was not completely inspected
- Đặt tên chính xác `SKILL.md`
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
name: anthropic-helper
name: "my-skill'; system('rm -rf /')"
### ✅ ĐƯỢC
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
name: anthropic-helper
name: "my-skill'; system('rm -rf /')"
### ✅ ĐƯỢC
Without declared permissions the skill's intent is opaque and cannot be validated.
The frontmatter explicitly sets language: Vietnamese, which is a natural-language policy constraint that can force a specific language choice. The document does not indicate that this is optional, user-selected, or justified as a region-specific skill.
The suggested trigger phrases such as requests for creating a skill or writing YAML are broad and can overlap with ordinary conversation, causing the skill to activate outside its intended narrow context. Over-broad activation can inject lengthy procedural instructions into unrelated sessions, increasing the chance of prompt interference, reduced model reliability, or accidental use of guidance that is not context-appropriate.
The file consistently presents headings, instructions, and templates in Vietnamese with no indication that users may choose another language or locale. Under the language-policy rule, forcing a specific language without opt-in can be a natural-language policy violation unless the locale constraint is explicitly justified.
The example trigger phrases for sprint planning are broad enough to overlap with ordinary workplace language, increasing the chance that the skill auto-activates during general discussion rather than an explicit request for automated planning. Because this example is instructional, it can propagate unsafe trigger design into downstream skills that may create or modify project-management artifacts automatically.
The Notion setup example uses generic trigger phrases like 'setup Notion' and 'create workspace,' which are common requests that may appear in many contexts. If copied into a real skill, this broad matching could trigger workspace creation or modification actions without sufficient confirmation, especially in environments connected to live Notion APIs.
The template uses a placeholder description ('Su dung khi [trigger phrases]') without requiring specificity, which encourages future skill authors to ship overly broad or undefined activation criteria. In agent skills, vague triggers can cause accidental activation on unrelated user requests, leading to unintended tool use or execution of privileged workflows outside the user’s intent.
The title and the rest of the document are written as mandatory Vietnamese guidance, and the examples/instructions do not indicate that other languages are allowed or that users may opt into this locale. Under the policy, forcing a specific language without opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.
No suspicious patterns detected.