Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - moving detail out of `SKILL.md` into `references/`
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent Markdown-only guide for deciding, creating, or auditing OpenClaw skills, with no hidden code execution or credential handling.
Install this if you want help designing lean skills. Review any generated skill trigger descriptions so they do not fire too broadly, and approve any actual file edits or new scripts based on your normal workflow.
Referenced artifact was not completely inspected
- moving detail out of `SKILL.md` into `references/`
Referenced artifact was not completely inspected
- moving detail out of `SKILL.md` into `references/`
Referenced artifact was not completely inspected
- moving detail out of `SKILL.md` into `references/`
Referenced artifact was not completely inspected
- moving detail out of `SKILL.md` into `references/`
Referenced artifact was not completely inspected
- moving detail out of `SKILL.md` into `references/`
Referenced artifact was not completely inspected
- moving detail out of `SKILL.md` into `references/`
Referenced artifact was not completely inspected
- moving detail out of `SKILL.md` into `references/`
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
Today's LLMs have strong theory of mind. When you explain *why* a step matters,
the model generalizes better than when you just bark orders.
Good: "Check for existing files first — overwriting without warning breaks trust
with the user and creates undo work."
Weak: "ALWAYS check for existing files. NEVER overwrite without asking. This is
This markdown file falls under the vague-trigger category. The guidance to make descriptions 'pushy enough to catch casual/informal phrasings' and to include adjacent concepts can encourage overly broad activation conditions that overlap with normal user speech, without adding limiting constraints or negative examples.
Telling authors to make descriptions 'slightly aggressive about when to fire' encourages ambiguous activation conditions by design. In the context of a meta-skill that helps define other skills, this pattern can propagate across many skills, leading to systematic overreach, incorrect delegation, and reduced predictability of agent behavior.
This guidance explicitly recommends broadening trigger phrases to capture adjacent and informal requests, including cases where the user does not explicitly ask for the named capability. In a skill-selection system, that increases the chance of over-triggering, causing the agent to invoke this skill for common requests outside its intended scope and potentially bypass more appropriate tools or narrower skills.
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.
Good: "Check for existing files first — overwriting without warning breaks trust
with the user and creates undo work."
Weak: "ALWAYS check for existing files. NEVER overwrite without asking. This is
CRITICAL."
If you catch yourself writing ALWAYS, NEVER, or CRITICAL in all caps, pause and
No suspicious patterns detected.