T09 · Insecure Skill Coding Practices
- Location
SKILL.md:7- Finding
Undeclared External Processing of Corporate Documents
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a legitimate corporate knowledge-base assistant, but it under-discloses networked document processing and keeps sensitive search analytics in ways users should review before installing.
Review this before installing in a real company environment. Treat it as requiring network access if you enable indexing from Notion, Google Docs, Confluence, YouTube, embeddings, vector databases, or Telegram reports. Do not use it with confidential HR, salary, contract, finance, or NDA material until access control, query-log retention, redaction, export approval, and external-provider destinations are explicitly configured. Prefer explicit commands and confirmations for archive, delete, export, and indexing workflows.
SKILL.md:7Undeclared External Processing of Corporate Documents
config.yaml:18Declarative Access Levels Are Not Bound to Authenticated Identities
config.yaml:26Search Query Logging and Telegram Reporting Lack Privacy Safeguards
The manifest declares makes_requests: false, but the body describes Notion, Confluence, Google Docs, YouTube, Whisper, embedding APIs, and vector database integrations that inherently require network access. This misrepresentation can bypass operator trust decisions, sandbox policy, or approval workflows, causing unintended external data transfer from internal knowledge sources.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
done chmod +x "$TARGET/install.sh" 2>/dev/null || true
if [[ -f "$TARGET/test/smoke-test.sh" ]]; then chmod +x "$TARGET/test/smoke-test.sh" 2>/dev/null || true
fi
echo "[✓] Файлы скопированы в $TARGET" # 3. Создать .env из шаблона если нет
if [[ ! -f "$TARGET/.env" ]]; then cp "$SRC_DIR/.env.example" "$TARGET/.env" echo "[✓] Создан $TARGET/.env (заполнять только если нужны интеграции)"
else echo "[i] $TARGET/.env уже существует — не перезаписываю"
fi # 4. Напомнить про OBLIGATORY-поля
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
done chmod +x "$TARGET/install.sh" 2>/dev/null || true
if [[ -f "$TARGET/test/smoke-test.sh" ]]; then chmod +x "$TARGET/test/smoke-test.sh" 2>/dev/null || true
fi
echo "[✓] Файлы скопированы в $TARGET" # 3. Создать .env из шаблона если нет
if [[ ! -f "$TARGET/.env" ]]; then cp "$SRC_DIR/.env.example" "$TARGET/.env" echo "[✓] Создан $TARGET/.env (заполнять только если нужны интеграции)"
else echo "[i] $TARGET/.env уже существует — не перезаписываю"
fi # 4. Напомнить про OBLIGATORY-поля
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
done chmod +x "$TARGET/install.sh" 2>/dev/null || true
if [[ -f "$TARGET/test/smoke-test.sh" ]]; then chmod +x "$TARGET/test/smoke-test.sh" 2>/dev/null || true
fi
echo "[✓] Файлы скопированы в $TARGET" # 3. Создать .env из шаблона если нет
if [[ ! -f "$TARGET/.env" ]]; then cp "$SRC_DIR/.env.example" "$TARGET/.env" echo "[✓] Создан $TARGET/.env (заполнять только если нужны интеграции)"
else echo "[i] $TARGET/.env уже существует — не перезаписываю"
fi # 4. Напомнить про OBLIGATORY-поля
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
if [[ -f "$TARGET/test/smoke-test.sh" ]]; then chmod +x "$TARGET/test/smoke-test.sh" 2>/dev/null || true
fi
echo "[✓] Файлы скопированы в $TARGET" # 3. Создать .env из шаблона если нет
if [[ ! -f "$TARGET/.env" ]]; then cp "$SRC_DIR/.env.example" "$TARGET/.env" echo "[✓] Создан $TARGET/.env (заполнять только если нужны интеграции)"
else echo "[i] $TARGET/.env уже существует — не перезаписываю"
fi # 4. Напомнить про OBLIGATORY-поля
echo ""
Suspicious Unicode normalization or mixed-script content
The changelog content is written in Russian and does not offer any language choice or indicate that the file is intentionally region-specific. This creates a natural-language policy concern because it imposes a specific locale on readers without documented opt-in or justification.
Suspicious Unicode normalization or mixed-script content
The trigger phrases listed near quick start include very broad natural-language activators such as 'база знаний', 'FAQ', and onboarding-related phrases that are likely to occur in ordinary workplace conversation. This can cause unintended skill invocation, leading to accidental processing of internal prompts, documents, or employee queries in contexts where the user did not intend to activate the skill.
The documented modes rely on ambiguous one-word commands like 'найди', 'FAQ', 'онбординг', 'обнови', 'архив', 'удали', 'экспорт', and 'индексируй' without scope restrictions or confirmation requirements. In a chat-based environment these terms can appear in normal discussion, increasing the risk of accidental execution of sensitive operations such as deletion, archival, export, or indexing of internal knowledge.
Suspicious Unicode normalization or mixed-script content
The description emphasizes "Russian language native" and presents the skill as the only KB skill with full RU localization, but it does not state that users can choose another language or that operation is region-restricted for a justified compliance reason. This creates a natural-language locale policy concern because the skill appears to force a specific language context without user opt-in.
Several triggers are common workplace phrases such as 'FAQ', 'новый сотрудник', 'как сделать', and 'wiki', which can cause the skill to activate during unrelated conversations. In a skill that can add, update, export, archive, and index documents, accidental invocation can lead to unauthorized content operations or unintentional disclosure of internal knowledge.
The manifest text explicitly claims 'Работает без внешнего SaaS' and says tools like Guru and Botpress are not needed. However, later documentation describes indexing from Google Docs, Notion, Confluence, YouTube, Whisper transcription, and vector databases such as Pinecone/Weaviate, which are external services and APIs. This is a direct contradiction in the skill's stated intent versus its described behavior.
The smart-search trigger includes broad natural-language phrases like 'как сделать', which are likely to appear in ordinary requests not intended for this skill. Because search results may surface internal documents, accidental activation increases the chance of over-broad retrieval or exposing sensitive internal content to the wrong user context.
The skill instructs logging every search and every unanswered query for analytics without a clear user-facing notice, consent model, or data handling limits. Search terms in a corporate knowledge base often contain employee names, customer issues, credentials-adjacent details, or confidential project references, so indiscriminate logging creates privacy and compliance risk.
Logging all user searches and unanswered queries creates a durable natural-language record of potentially sensitive requests without any minimization rules. In a corporate knowledge system, those queries can contain internal incidents, HR matters, customer names, or confidential terms, turning analytics storage into a secondary sensitive data repository.
The FAQ/export templates include raw queries and usage analytics in plain language outputs, which can leak sensitive user inputs when exported to bots, documents, or other systems. Once exported, this data may spread beyond the original access boundary and be harder to audit or delete.
The SOP trigger includes a very broad phrase equivalent to 'how to correctly [action]', which can match many ordinary requests. Since the SOP mode can produce authoritative procedural content, accidental matches may leak internal process instructions or steer users into unintended workflow execution.
The reporting section describes collection of user activity metrics and query-level analytics without stating retention, audience, minimization, or user notice. In an internal enterprise setting, this can become covert monitoring of employee behavior and can expose sensitive operational searches through routine reports.
Publishing exact top searches and failed searches in usage reports creates a clear data-leak channel because users often search with sensitive business context, personnel issues, or incident details. The skill further states that reports may be sent to leadership channels, increasing the blast radius of any leaked query content.
A persistent search-log.csv in the knowledge storage structure indicates retained raw queries as a first-class artifact. This expands the attack surface because anyone with filesystem or repository access may obtain historical searches containing confidential information unrelated to the knowledge base documents themselves.
Suspicious Unicode normalization or mixed-script content
This code invokes external archiving tools and PowerShell, then performs a recursive delete with rm -rf on the temporary build directory. Although the script has comments about build behavior, it does not visibly warn the user at the point of execution that shell commands and filesystem deletion will occur, nor does it request confirmation.
Suspicious Unicode normalization or mixed-script content