Loading...
Loading...
Found 42 Skills
Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".
Perform systematic self-review of code changes before commits using structured checklist. Validates architecture boundaries, code quality, test coverage, documentation, and project-specific anti-patterns. Use before committing, creating PRs, or when user says "review my changes", "self-review", "check my code". Adapts to Python, JavaScript, TypeScript, Go, Rust projects.
Educational map of behavioral risk screening—volume, velocity, and transit-style heuristics at address and transaction level. Use when the user asks about suspicious pattern detection, structuring-like activity, rapid fund movement, or AML-style behavior rules—not for tuning systems to evade monitoring or for legal conclusions.
Identifies and removes signs of AI-generated text to make writing sound more natural and human. Use when the user asks to humanize text, make writing sound more natural, remove AI patterns, edit for human voice, or convert AI-generated content to natural prose. Also triggers on requests to check for AI writing patterns, review text for robotic language, or improve writing authenticity. Based on Wikipedia's "Signs of AI writing" guidelines.
Remove AI-generated jargon and restore human voice to text. Built from analyzing 1,000+ AI vs human content pieces.
Remove signs of AI-generated writing from text. Use when editing or reviewing any content to make it sound more natural and human-written. Catches patterns like inflated language, rule of three, em dash overuse, vague attributions, copula avoidance, negative parallelisms, synonym cycling, filler phrases, excessive hedging, and soulless structure. Use when someone says "humanize this", "this sounds like AI", "make this sound human", "remove the AI", "clean this up", "de-AI this", "this reads like ChatGPT", or when reviewing any AI-assisted draft before publishing. Also use as a final pass on content from other skills like boring-remix or social-content. World Code integrated — applies voice.md rules when available.
Detects anti-patterns and code smells in .NET test suites. Use when the user asks to review test quality, find test smells, identify flaky test indicators, or audit tests for common mistakes. Covers assertion quality, test isolation, naming, flakiness indicators, over-mocking, and structural problems. Works with MSTest, xUnit, NUnit, and TUnit.
Validate, lint, audit, or fix PromQL queries and alerting rules; detects anti-patterns.
Guides creation of high-quality Agent Skills with domain expertise, anti-pattern detection, and progressive disclosure best practices. Activate on keywords: create skill, review skill, skill quality, skill best practices, skill anti-patterns, improve skill, skill audit. NOT for general coding advice, slash commands, MCP development, or non-skill Claude Code features.
Analyze and optimize slow SQL queries. Use when the user says a query is slow, asks to optimize or speed up SQL, wants to find anti-patterns, needs index recommendations, or asks for a query rewrite. Also use when EXPLAIN output shows full table scans or poor join strategies.
PreToolUse security-anti-pattern hook for Claude Code. Catches 12 common security risks (command injection, XSS, SQL injection, unsafe deserialization, GitHub Actions workflow injection, eval/new Function code injection) BEFORE the Edit/Write/MultiEdit operation completes. Session-state caching prevents duplicate warnings on the same file+rule combo. Stdlib only — no dependencies. Use when you want a safety net during Claude Code sessions that touch security-sensitive code (auth, payments, user input handling, IaC). Disable with ENABLE_SECURITY_REMINDER=0 if you need to perform a verified-safe operation that would otherwise trip a pattern. Triggers — "add security hook", "block unsafe code", "detect command injection before write", "prevent SQL injection patterns", "security warning hook".
Learns from DAG execution history to improve future performance. Identifies successful patterns, detects anti-patterns, and provides recommendations. Activate on 'learn patterns', 'execution patterns', 'what worked', 'optimize based on history', 'pattern analysis'. NOT for failure analysis (use dag-failure-analyzer) or performance profiling (use dag-performance-profiler).