Maintain a persistent SQLite customer database within the sales-cs workspace. The system hook injects peer (DB primary key) and the Sender block provides user_id_external (raw awada user ID). Use peer for all DB operations.
54
60%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./crews/sales-cs/skills/customer-db/SKILL.mdSecurity
1 high severity finding. 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.
The skill repeatedly instructs the agent to emit shell commands that include session-derived identifiers (e.g., <[CustomerDB].peer>, <Sender.id>) verbatim, which forces the LLM to output sensitive identifier values directly.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
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.
运行时会把 Sender(untrusted metadata)中的 `id` 与客户会话中解析到的文本字段用于调用本地脚本写入 SQLite(如 `follow-up-create.sh` 的 `--reason`/`--context-summary`、`cs-update.sh` 的 `--purpose`/`--prompt-source`),这些字段可由外部用户自由文本间接影响。
fdc03d6
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.