T01 · Skill Instruction Hijacking
- Location
templates/prd.md:51- Finding
Mandatory branded external-link injection into generated artifacts
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a readable Markdown-based product-management assistant skill with some install and output-branding caveats, but no hidden code execution, data access, or persistence in the reviewed artifact.
Before installing, use ClawHub or a pinned trusted version if available, and review generated deliverables for the attribution footer before sharing them externally. The reviewed artifact does not require secrets, background services, or automatic script execution.
templates/prd.md:51Mandatory branded external-link injection into generated artifacts
README.md:48Unpinned third-party package execution in installation and update instructions
Activation phrases like take this from idea to PRD and full PM sprint on this feature are generic enough to overlap with ordinary product discussion. In shared agent tooling, vague routing triggers can cause the skill to seize control of a conversation unexpectedly, applying a multi-phase workflow when the user may have intended a narrower request.
The trigger phrase coach me is extremely broad and likely to appear in normal user conversation, which can unexpectedly switch the skill into a more forceful operating mode. In agent environments that compose prompts or route across skills automatically, ambiguous activation increases the chance of unintended behavior, misapplied instructions, or prompt-surface collisions with other contexts.
The README instructs users to run npx skills add Digidai/product-manager-skills without pinning a version or commit. That exposes installs to supply-chain risk: future package changes, compromised upstream dependencies, or typo/package takeover could alter what gets executed at install time. In this context the file is installation guidance, so readers are likely to copy-paste it directly, which increases practical risk.
The PM Sprint workflow is triggered by broad natural-language phrases such as '从想法到 PRD' or '帮我完整做一遍这个功能'. Because these overlap with ordinary user requests, the skill may activate a multi-stage workflow unintentionally, causing unexpected prompt routing, hidden state transitions, or overly broad task execution. In an agent skill, ambiguous triggers are security-relevant because they reduce user control over when higher-impact behavior starts.
The Coaching mode advertises broad trigger phrases like 'coach me', '教练模式', '挑战我的想法', and '严格审视这个' without strong boundary conditions. These expressions can appear in normal conversation and may switch the assistant into a stricter behavioral mode unexpectedly, altering outputs, tone, and decision rules without clear user consent. While not code execution, this is still a real control-plane weakness in a prompt-driven skill because mode confusion can lead to unintended actions or advice pathways.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The TODO describes a mechanism for acting "when AI detects PM-relevant patterns during code work," but it does not define concrete trigger conditions or clear boundaries for when the behavior should or should not activate. This is a broad natural-language activation concept that could overlap with many ordinary coding interactions and cause unintended invocations.
The trigger phrase "take this from idea to PRD" is broad, natural language that could plausibly appear in ordinary conversation and unintentionally activate a complex workflow. In an agent skill context, overly broad triggers can cause unintended routing, surprise behavior, or prompt-context takeover of the interaction flow, especially because this workflow chains multiple phases automatically.
This markdown file defines activation behavior with broad natural-language conditions such as 'career and leadership topics,' 'Career goal is vague,' and 'User asks for frameworks,' without clear boundaries or exclusion conditions. Those phrases overlap with common coaching or workplace conversations, making it unclear when this skill should activate versus when it should not.
The voice guidelines prohibit specific words and punctuation globally (for example, "No em dashes" and banned words) without indicating that users may opt out or choose a different style. This is a natural-language policy concern because it forces a communication style unconditionally rather than offering a user preference.
No suspicious patterns detected.