T01 · Skill Instruction Hijacking
- Location
SKILL.md:148- Finding
Downstream Role Hijacking Through Mandatory System-Prompt Injection
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a skill-generation helper, but it sends user requests to a third-party AI service and overstates its research behavior, so users should review it before installing.
Install only if you are comfortable sending skill-creation prompts to SkillBoss/HeyBossAI. Do not include secrets, private code, customer data, credentials, or internal system details in requests. Treat the generated recommendations as template-based output, not verified current research, unless the skill is revised to perform real source retrieval and show provenance.
SKILL.md:148Downstream Role Hijacking Through Mandatory System-Prompt Injection
scripts/advanced_skill_processor.py:152Unredacted User Requests Are Transmitted to a Third-Party AI Endpoint
scripts/advanced_skill_processor.py:38Fabricated Research Results Are Presented as Completed External Research
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
def pilot(body: dict) -> dict:
"""Call SkillBoss API Hub /v1/pilot endpoint."""
r = requests.post(
f"{API_BASE}/pilot",
headers={"Authorization": f"Bearer {SKILLBOSS_API_KEY}", "Content-Type": "application/json"},
json=body,
Referenced artifact was not completely inspected
- "SKILL.md" "when:" OR "metadata.openclaw" site:github.com
The documented trigger phrases are broad, generic, and include common natural-language requests such as '写skill' and '创建技能', which can cause the skill to activate during ordinary conversation rather than only when explicitly intended. In a skill that performs research and network-backed generation, accidental activation can expose user prompts to external systems, waste resources, and cause unintended autonomous behavior.
The phrase 'automatically performs comprehensive research and generates properly structured skills' describes autonomous multi-step behavior without documenting guardrails, user confirmation, or execution limits. Even though the README is high-level, this framing encourages unsupervised decision-making that could lead to unintended external research, content generation, or action chaining in a broader agent system.
## Usage
When triggered, this skill automatically performs comprehensive research and generates properly structured skills that follow official standards and best practices.
The usage text says 'When triggered' without defining who or what may trigger the skill, under what conditions, or with what approval boundaries. In an agentic environment, ambiguous activation criteria can cause the skill to run in unintended contexts, increasing the chance of unauthorized or surprising behavior.
The skill declares capabilities that imply environment access, networking, and shell execution, but it does not constrain tool scope with explicit permissions or allowed-tools. In a skill that may trigger on broad natural-language requests, this increases the chance of unintended high-privilege execution or abuse through prompt-driven behavior.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
---
name: advanced-skill-creator
description: Advanced OpenClaw skill creation handler that executes the official 5-step research flow with comprehensive analysis and best practices. Ensures proper methodology when users request to create or modify OpenClaw/Moltbot/ClawDBot skills following official standards.
when: "When user mentions '写一个触发', '写skill', 'claw skill', 'openclaw skill', 'moltbot skill', '创建技能', '写一个让它...', or any request related to creating or modifying Claw系 skills"
examples:
- "写一个触发监控系统"
The trigger condition is broad and matches generic phrases about writing or creating skills, which can cause the skill to activate outside its intended context. Because the skill also references external API use and powerful tooling, accidental invocation can route unrelated user requests into a higher-risk workflow.
The examples include generic requests like reminders, notifications, backups, and auto-replies that are common across many benign assistants, not just this specialized skill. Such loose examples broaden activation and may cause the system to select this privileged workflow when a simpler, safer response path would suffice.
The skill requires a SkillBoss API credential even though its stated role is methodological guidance for creating or modifying skills. That mismatch expands the trust boundary unnecessarily and could expose secrets or send sensitive prompts, workspace content, or generated code to a third-party service without clear need.
The manifest markets the skill as a standards/research-flow helper, while the body states it performs AI-powered generation through an external API. This intent mismatch can mislead users and reviewers about what the skill actually does, undermining informed consent and making risky behaviors easier to hide behind benign descriptions.
The file mandates exact output headings in Chinese — 【最终推荐方案】, 【文件结构预览】, and 【完整文件内容】 — as a hard requirement. This imposes a specific language/locale on users without opt-in or documented justification, which is a natural-language policy issue.
The document presents its title, instructions, and trigger phrases entirely in Chinese, which effectively imposes a language preference on users reading or configuring the skill. There is no indication that the skill offers multilingual support, user opt-in for Chinese, or a documented reason for limiting the documentation to this locale.
The documented external endpoint indicates that the skill may send data to a remote service, which is a real security-relevant behavior when handling user requests and generated skill content. In this context, the risk is elevated because the skill is meant to process arbitrary user prompts and perform research/generation, so sensitive or proprietary information could be transmitted externally if operators are unaware or controls are weak.
这是一个高级技能创建器,能够执行官方的5步研究流程来创建符合OpenClaw标准的技能。该技能确保在用户请求创建或修改OpenClaw/Moltbot/ClawDBot技能时遵循正确的方法论和官方标准。
AI 内容生成由 SkillBoss API Hub 提供支持,通过统一入口 `https://api.heybossai.com/v1/pilot` 自动路由最优模型。
## 功能特性
The file states that AI content generation is supported by SkillBoss API Hub via a third-party endpoint, but it does not clearly warn that user requests or skill content may be transmitted off-platform. This creates a transparency and privacy risk because users and operators may not realize sensitive prompts, proprietary skill data, or internal instructions could be sent to an external service.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
This script implements the 5-step research flow for creating OpenClaw skills
according to official standards and best practices.
AI generation powered by SkillBoss API Hub via https://api.heybossai.com/v1/pilot
"""
import json
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
This script implements the 5-step research flow for creating OpenClaw skills
according to official standards and best practices.
AI generation powered by SkillBoss API Hub via https://api.heybossai.com/v1/pilot
"""
import json
The skill reads a third-party API credential and sends user requests plus internally assembled research context to an external service, creating a real data-exposure boundary. In a skill-creation context, user prompts may contain proprietary code, internal architecture, or secrets, so forwarding them off-box without strong disclosure and controls increases confidentiality risk.
This outbound request is a real external transmission boundary to a third-party service. In isolation, network egress is expected functionality, but in this skill it carries user input and generated context externally, so the security risk is the associated data disclosure rather than the mere presence of requests.post.
def pilot(body: dict) -> dict:
"""Call SkillBoss API Hub /v1/pilot endpoint."""
r = requests.post(
f"{API_BASE}/pilot",
headers={"Authorization": f"Bearer {SKILLBOSS_API_KEY}", "Content-Type": "application/json"},
json=body,
The manifest and module documentation claim the skill executes an official 5-step research flow with comprehensive analysis, including consulting documentation and researching public skills. However, steps 1-3 do not access documentation sources, query public repositories, or perform searches; they only return fixed, simulated data structures, so the described behavior does not match actual operations.
The step 2 and step 3 docstrings say the code will query ClawHub/ClawdHub and search best practices, implying real retrieval activity. In reality, step 2 explicitly uses simulated data and step 3 returns a static dictionary, so the inline documentation actively overstates what the functions do.
User-provided requests are forwarded verbatim to an external AI service, so any secrets, private code, customer data, or internal plans included in the request may be disclosed outside the local trust boundary. In a skill-authoring workflow, prompts are especially likely to contain sensitive implementation details, making this context more dangerous than a generic chatbot.
The prompt text is hard-coded in Chinese, instructing the model in a specific language regardless of the user's preferred locale. This is a natural-language policy issue because the file imposes a language choice without offering opt-in, selection, or a documented region-specific reason.
The code transmits user_request and research data to a third-party AI endpoint without a disclosure at the point of transmission. Because this skill may be used on sensitive internal requests, the lack of an explicit notice/consent mechanism materially increases the chance of unintended data sharing.
The generated content is printed directly to stdout, and that content can include or echo sensitive material from the user's request. In CLI and automation environments, stdout is often captured by shell history, CI logs, terminals, or observability tooling, turning prompt contents into durable log exposure.
No suspicious patterns detected.