T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/cjg-proposal-cli.py:66- Finding
Cross-Skill credential access and transmission
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not just a methodology extractor; it adds default-on logging, silent cloud-related hooks, cross-skill scanning, creator-token handling, and a remote proposal path that can lead to persistent local changes.
Install only if you are comfortable with default local logging, external cloud endpoints, persistent anonymous identifiers, and creator-token/proposal workflows. Keep cloud sync off unless needed, avoid using proposal approval with sensitive credentials, review any proposed local file changes manually, and do not process confidential documents without isolating temporary files.
scripts/cjg-proposal-cli.py:66Cross-Skill credential access and transmission
scripts/download_signals.py:106Cloud synchronization request occurs while cloud synchronization is disabled
SKILL.md:160Mandatory lifecycle execution and final-response injection
scripts/upload_signals.py:446Session start processes telemetry for unrelated installed Skills
references/ingestion.md:33Unpinned runtime dependency installation
references/ingestion.md:27Predictable shared temporary files expose processed documents
SKILL.md:138Remotely supplied proposals can be converted into persistent Skill modifications
scripts/forge-register.py:90Creator bearer token is stored in a plaintext file without restrictive permissions
The skill advertises transforming knowledge materials, but also describes uploading local telemetry to an external cloud service after scanning local state and log files. Even if the content claims only tags are uploaded, the undocumented expansion into networked telemetry creates exfiltration risk and violates least surprise for a skill handling sensitive research and client materials.
The skill advertises transforming knowledge materials, but also describes uploading local telemetry to an external cloud service after scanning local state and log files. Even if the content claims only tags are uploaded, the undocumented expansion into networked telemetry creates exfiltration risk and violates least surprise for a skill handling sensitive research and client materials.
The skill advertises transforming knowledge materials, but also describes uploading local telemetry to an external cloud service after scanning local state and log files. Even if the content claims only tags are uploaded, the undocumented expansion into networked telemetry creates exfiltration risk and violates least surprise for a skill handling sensitive research and client materials.
The skill advertises transforming knowledge materials, but also describes uploading local telemetry to an external cloud service after scanning local state and log files. Even if the content claims only tags are uploaded, the undocumented expansion into networked telemetry creates exfiltration risk and violates least surprise for a skill handling sensitive research and client materials.
The skill advertises transforming knowledge materials, but also describes uploading local telemetry to an external cloud service after scanning local state and log files. Even if the content claims only tags are uploaded, the undocumented expansion into networked telemetry creates exfiltration risk and violates least surprise for a skill handling sensitive research and client materials.
The skill advertises transforming knowledge materials, but also describes uploading local telemetry to an external cloud service after scanning local state and log files. Even if the content claims only tags are uploaded, the undocumented expansion into networked telemetry creates exfiltration risk and violates least surprise for a skill handling sensitive research and client materials.
The skill advertises transforming knowledge materials, but also describes uploading local telemetry to an external cloud service after scanning local state and log files. Even if the content claims only tags are uploaded, the undocumented expansion into networked telemetry creates exfiltration risk and violates least surprise for a skill handling sensitive research and client materials.
The skill advertises transforming knowledge materials, but also describes uploading local telemetry to an external cloud service after scanning local state and log files. Even if the content claims only tags are uploaded, the undocumented expansion into networked telemetry creates exfiltration risk and violates least surprise for a skill handling sensitive research and client materials.
The skill states it only produces methodology cards, yet it also performs proposal approval and local file modification workflows. This inconsistency is dangerous because users and reviewers may underestimate its authority to change local artifacts and accept remote change sets under a non-administrative label.
The file introduces telemetry, cloud sync, and persistent signal collection features that materially exceed the skill’s declared purpose of extracting methodology from provided materials. This scope expansion creates an unnecessary data collection and exfiltration surface, especially because the mechanisms are built into normal session flow rather than being isolated optional admin tooling.
The documentation states that local logging is enabled by default at install time and runs at session boundaries, despite that behavior not being part of the user-facing skill purpose. Default-on behavioral logging is dangerous because it creates silent persistence of user interaction metadata without affirmative consent, increasing privacy and compliance risk.
Automatic skill-edit capture and baseline tracking are unrelated to methodology extraction and monitor user or operator modifications over time. Even if content is hashed or reduced to path-level events, this still creates persistent surveillance of editing behavior and expands the skill into change-monitoring without justified need.
The 'mandatory final-step' rule forces log writes at the end of every response and explicitly specifies silent failure, creating a hidden, durable collection mechanism embedded in core operation. This is especially dangerous because it systematizes covert telemetry in routine interactions and reduces the chance that users or reviewers will notice collection failures or attempted collection.
This script implements local surveillance of edits to skill files, including hashing tracked content and appending edit events to a signals log, which is unrelated to the stated purpose of the bagua-furnace skill: extracting reusable methodology from knowledge materials. In an agent-skill ecosystem, unrelated monitoring logic expands the skill's authority and creates covert observability over other skill assets, increasing the risk of unauthorized telemetry or future data exfiltration even if this version claims local-only behavior.
The skill uses 'env' capability that is not listed in its permissions. This may indicate deceptive intent or missing permission declarations.
The script implements cloud slug registration, email verification, and creator token acquisition, which is materially unrelated to the advertised skill purpose of extracting methodologies from content. This kind of capability expansion is dangerous because it introduces outbound network interaction and identity/token handling into a skill users would not expect to perform account-registration workflows, increasing the risk of covert credential collection or unauthorized service enrollment.
Although the skill says it does not produce executable Agent Skills, it includes self-iteration and cloud-fed evolution mechanics that can alter behavior over time. That weakens reviewability because the effective behavior can drift after installation through proposal and signal-driven update loops.
Default-on local telemetry and optional cloud sync are not necessary for the claimed task of methodology extraction and create avoidable privacy exposure. The danger is heightened because this skill is meant to process dense knowledge materials that may include confidential business notes, transcripts, and client-shared links.
The user-facing control phrases for cloud sync and signal management are specified only in Chinese, and later operational commands are likewise defined only with Chinese utterances. This creates a language/locale constraint in the skill's natural-language interface without documenting an alternative or obtaining user opt-in.
Creator registration and token provisioning workflows are outside the natural scope of end-user content extraction and introduce credential-handling risk. Even if intended for maintainers, including them in the same skill increases the chance of accidental token storage, misuse, or privilege confusion.
Mandatory session hooks, usage accounting, and signal upload add telemetry and operational side effects unrelated to the extraction role. Because the hooks are described as required at session start and end, they create a persistent tracking mechanism around every use of the skill.
This markdown file contains user-facing natural language exclusively in Chinese, and there is no indication that the skill is region-specific or that users may choose another language. Under the policy rule for language/locale constraints, forcing a specific language without opt-in is a natural-language policy violation.
This markdown file contains user-facing natural-language content only in Chinese, and nowhere indicates that the skill supports other languages or that Chinese is a required regional/compliance constraint. Under the language/locale policy rule, forcing a specific language without user opt-in is a policy concern.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
# 清晰化 · 保真报告(S7 闸门)
- 生成时间:2026-08-26
- 源技能:~/.workbuddy/skills/bagua-furnace/SKILL.md
- 技能类型:workflow(多步 SOP + 写文件)+ 轻人设
## 保真核对(对照已签批 S5 终版设计)
The trigger list is very broad and includes generic phrases like '笔记提炼' and '链接提炼' that can match ordinary user requests unrelated to this skill’s intended scope. In an agent-routing context, this can cause unintended invocation on arbitrary user content, increasing the chance of unnecessary network access, content ingestion, or privacy-impacting processing.