
from scammer.skill62
Detect likely scam messages, identify the scam stage, and predict the scammer's next move to help users defend themselves.
This skill distills common scam playbooks into structured detection logic: it analyses user-provided messages or screenshots, identifies which stage of a scam flow the interaction is in, extracts key signals, and recommends next steps to stay safe. It is explicitly defensive — meant to help users recognise scams, not facilitate them.
Use this skill when a user pastes a suspicious message, uploads a screenshot of a conversation, or asks whether a contact or offer is legitimate. Triggers include commands like /detect-scam, /scammer [message], or natural-language prompts such as "帮我看看这条消息" / "这是诈骗吗". It also supports add/manage flows for maintaining a local scam pattern library.
This skill is written as a Claude/agent-style SKILL.md with instructions and tool calls (Read, Write, Edit, Bash). It will work best with agents that support file Read/Write and Bash tool integrations (Claude Code, agentic CLI-based agents).
Scammer.skill is a bilingual (Chinese/English) agent skill for detecting scam messages, identifying scam phases, and predicting next moves. It includes detailed prompt-driven workflows for detection and adding new scam patterns, with version management via Python scripts. No scripts were bundled in the fetched data (they live in the GitHub repo's tools/ directory), so no execution testing was possible. The SKILL.md references external Python tools (pattern_writer.py, version_manager.py) that aren't included in the fetched scripts.
Well-structured skill with clear trigger conditions, multiple workflows (detect, add, manage, correct), and version management. The skill is defensive/educational (helping users identify scams), not malicious. Architecture follows the skill spec reasonably well with frontmatter, prompts/, tools/, and scams/ directories. Main weakness is that the referenced Python tools aren't bundled in the scripts field — they're external dependencies that would need to be present in the skill directory. The skill is quite verbose in its SKILL.md, which could be leaner with more content in references/.