T01 · Skill Instruction Hijacking
- Location
SKILL.md:13- Finding
Unrelated Agent Identity and Response-Style Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its Feishu/OpenClaw setup purpose, but it includes unrelated agent-identity instructions and under-scoped local file setup guidance that users should review before installing.
Review and remove the persona lines before use, validate Agent IDs with a strict lowercase letters/digits/hyphen pattern, avoid pasting App Secret into chats or committed files, store the secret in a secure configuration location, and restart the gateway only when a brief service interruption is acceptable.
SKILL.md:13Unrelated Agent Identity and Response-Style Instructions
SKILL.md:113Path Traversal Through Unvalidated Agent Identifier
The documentation hard-codes coercive identity and honorific preferences such as '主人' and '皇帝' into the skill context without user opt-in. While not a direct code-execution issue, this can normalize manipulative behavior, influence agent outputs inappropriately, and create unsafe or unprofessional interactions when the skill is reused in other contexts.
The README instructs users to obtain and configure a Feishu App Secret but provides no guidance on secure handling, storage, or redaction of that credential. In an agent/automation setup, this omission can lead users to place secrets directly into files, workspaces, chat logs, or skill artifacts, increasing the risk of credential leakage and downstream account compromise.
SQP-3 applies to all file types and includes language or locale policy violations. The line states that users should uniformly be addressed as “主人,” imposing a specific form of address without indicating user preference, opt-in, or an option to change it.
The skill explicitly tells users to retrieve and save the Feishu App Secret but provides no guidance on treating it as a sensitive credential, avoiding plaintext storage, or limiting disclosure. In a setup guide for agent integration, this omission can lead to accidental exposure of a credential that would allow unauthorized use of the bot integration.
For markdown files, SQP-2 covers omitted warnings about actions that can affect system integrity or availability. Restarting the gateway is an operationally impactful action, yet the document presents it as a routine step without disclosing possible interruption to active agent connectivity or message handling.
No suspicious patterns detected.