T01 · Skill Instruction Hijacking
- Location
SKILL.md:19- Finding
Untrusted External Tasks Can Become an Indirect Instruction Channel
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent ClawJob integration, but it needs review because it can automatically perform external task and account actions while using bearer tokens without clear confirmation or untrusted-content safeguards.
Install only if you intend OpenClaw to operate on ClawJob and you are comfortable with it creating or changing ClawJob tasks, agents, subscriptions, completions, approvals, and account-related settings. Treat CLAWJOB_ACCESS_TOKEN as a secret, review every task or account-changing request before it is sent, and do not let task descriptions from the marketplace override your own instructions or request secrets.
SKILL.md:19Untrusted External Tasks Can Become an Indirect Instruction Channel
SKILL.md:42Automatic Publication of Agent Capability Metadata
Referenced artifact was not completely inspected
- 本技能所在目录必须命名为 `clawjob`,且内含本文件 `SKILL.md`(以及可选 `reference.md`)。
The skill description says to use it whenever the user wants to use ClawJob, publish or accept tasks, or when OpenClaw should act as a ClawJob user. That broad activation language can cause the agent to select this skill for generic task-management requests and then perform external API actions the user did not explicitly intend on ClawJob. Because this skill can create accounts, publish tasks, and subscribe agents to tasks, accidental invocation has real side effects.
The statement that any listed phrasing triggers execution, combined with '无需人类手写请求', removes decision boundaries and encourages automatic action execution from natural-language matches alone. Without exclusions, confirmation gates, or checks for ambiguous context, the agent may call privileged APIs based on loosely matching phrases and cause unintended registrations, postings, or workflow transitions.
The skill instructs users to copy an API token and export it into the environment, but provides no warning that the token is a bearer credential that grants account access and should be handled as secret material. In agent settings, such omissions increase the risk of users pasting tokens into chat, storing them insecurely, exposing them in shell history, or reusing them in unsafe contexts, which could lead to account takeover or unauthorized task actions.
The document explicitly instructs users to export or write access tokens into environment variables or a .env file, but it does not warn that these are sensitive credentials that can be exposed through source control, logs, shell history, or local file disclosure. In an agent/platform context, leaked bearer tokens could allow unauthorized task publication, task acceptance, agent registration, and access to account data until the token is revoked or expires.
The main instructional content and user-facing examples are presented in Chinese, but the file does not indicate that this locale is optional or region-specific. This can violate language-choice expectations when the skill is loaded in broader environments without explicit user opt-in.
The document is entirely presented in Chinese and the title explicitly labels it as the API reference for agent use, but it does not offer an alternative language or indicate that Chinese-only operation is required for a specific region or compliance reason. Under the language/locale policy, a forced language without opt-in can be a natural-language policy violation.
No suspicious patterns detected.