T09 · Insecure Skill Coding Practices
- Location
SKILL.md:151- Finding
Transaction-capable workflows can be deployed and executed without a mandatory final approval gate
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent for K3 blockchain automation, but it gives agents authority to deploy and manually run workflows that can trade, transfer tokens, or write contracts without a mandatory user approval checkpoint.
Review this skill carefully before installing. It is not deceptive or locally executable, but it can guide an agent to create persistent K3 automations that send data to third parties and perform blockchain actions. Require an explicit final review before deployment, use testnet or limited-fund wallets for any trading or contract-writing workflow, verify recipients and webhook/API destinations, protect API keys and bot tokens, and make sure scheduled workflows can be paused or revoked.
SKILL.md:151Transaction-capable workflows can be deployed and executed without a mandatory final approval gate
The trigger text is extremely broad and explicitly says to invoke the skill for a wide range of generic blockchain, crypto, DeFi, monitoring, and automation phrases, including vague requests like 'monitor this wallet' or 'track this token.' That creates a real risk of over-invocation, causing the agent to enter a workflow-building/deployment path in conversations where the user did not clearly consent to using K3 or to performing potentially external actions.
The skill guides the agent to generate, deploy, execute, and verify workflows that can send notifications and even perform on-chain actions such as swaps or contract writes, but it does not require a prominent user-facing warning or explicit confirmation before side effects occur. In this context, silent progression from planning to deployment/execution can lead to unintended external messages, scheduled automations, or blockchain transactions with financial consequences.
This reference documents trading, token transfer, and smart-contract write capabilities without explicit warnings that these actions can move assets, incur irreversible on-chain transactions, and cause direct financial loss if configured incorrectly or triggered by untrusted inputs. In a workflow-building skill aimed at automation, normalizing these capabilities without strong guardrails increases the chance that users or downstream agents will compose unsafe automations that execute real asset-moving actions.
The web scraping workflow pattern encourages automated extraction from websites without any guidance on respecting site terms of service, robots directives, rate limits, privacy constraints, or downstream handling of scraped content. In a blockchain/DeFi monitoring skill, users may target governance forums, protocol sites, or other third-party services at scale, creating legal, privacy, and operational abuse risks that the pattern currently normalizes.
The file describes external API writes, storage, email/Telegram/Slack delivery, and MCP integrations that transmit data and use credentials, but it does not warn about data leakage, secret handling, or the trust boundary created by third-party services. Because this skill is specifically designed to orchestrate cross-service blockchain workflows, users may send wallet data, prompts, reports, or credentials to external systems without understanding the privacy and security implications.
This markdown file advises users to add API keys in headers and later to verify a Telegram bot token, but it does not include any warning about protecting secrets, avoiding accidental exposure, or using secure storage. Because markdown files should warn about behaviors that could affect privacy or system integrity, the omission is a minor safety disclosure gap.
The section explains how to restore outbound notifications through email, Telegram, and webhooks, which can transmit workflow data to third-party services. The document does not warn users to verify recipients, review payload contents, or consider privacy implications before sending notifications.
No suspicious patterns detected.