Configure notification integrations (Telegram, Discord, Slack) via natural language
56
47%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/configure-notifications/SKILL.mdSecurity
2 findings — 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Insecure credential handling detected (high risk: 1.00). This skill explicitly asks the agent to collect user tokens/webhook URLs and to embed them verbatim into config files, curl commands, test requests, and printed summaries, which requires the LLM to handle and output secrets directly.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Third-party content exposure detected (high risk: 0.80). The skill explicitly fetches and parses untrusted, user-generated third-party content as part of its runtime workflow (e.g., Telegram getUpdates in "Telegram Setup" Step 4 to extract chat IDs and the Custom Integration / Generic Webhook flows that POST to and read responses from arbitrary webhook URLs), and those extracted values are used to configure notification targets and subsequent actions—so remote content can materially influence where and how the agent sends notifications.
48ffaac
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.