Documentos

Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.

CSV-first weekly recovery review during an active SEO recovery. No SISTRIX API key required. Compares current and previous SISTRIX keyword exports and produces a structured Monday Check report with Recovery Signal Score, per-cluster recovery stage, winner/loser neutralization analysis, money-keyword protection list, URL-level recovery table, optional GSC cross-check, optional conversion-rate valid

Explica o funcionamento do atopile Language Server (pygls), incluindo a construção de grafos por documento para recursos como autocompletar, hover e definições, e os invariantes que garantem sua velocidade e robustez.

Map user journeys with touchpoints, emotional states, pain points, and opportunities across the full arc of a user's experience over time. Use when the user asks to map a user journey, create a customer journey map, design a service blueprint, document touchpoints and friction points, or visualize the end-to-end experience of a user across multiple interactions. NOT for static navigation structure

Use when you need to run a binary, trace execution, or observe runtime behavior. Runtime analysis via QEMU emulation, GDB debugging, and Frida hooking - syscall tracing (strace), breakpoints, memory inspection, function interception. Keywords - "run binary", "execute", "debug", "trace syscalls", "set breakpoint", "qemu", "gdb", "frida", "strace", "watch memory"

Writes a blameless incident postmortem document from an incident timeline or Slack thread.

[TODO: Write comprehensive description in third-person. Start with "This skill provides..." or "This skill should be used when..."] [TODO: Add "Use when" scenarios - specific situations where Claude should use this skill] [TODO: Add keywords - technologies, use cases, error messages that should trigger this skill]

Structure long-form technical articles around the hook → promise → setup → development → payoff contract. Pick from canonical templates (deep-dive, tutorial, opinion, case study, whitepaper, technical narrative). Engineer section transitions and signposting. Match length to ambition (when 800 vs 1500 vs 3000 vs 5000+ words is right). Use when the user asks to outline a technical article, structure

Use when reverse engineering tools are missing, not working, or need configuration. Installation guides for radare2 (r2), Ghidra, GDB, QEMU, Frida, binutils, and cross-compilation toolchains. Keywords - "install radare2", "setup ghidra", "r2 not found", "qemu missing", "tool not installed", "configure gdb", "cross-compiler"

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction.

Gera uma base de conhecimento de produto estruturada a partir da análise de código, criando uma pasta codewiki/ com documentação de arquitetura, fluxos de usuário, referência de API e mapas de serviço. Também gera CLAUDE.md e suporta diversas estruturas de repositório.

Use when ready to document findings, generate a report, or summarize binary analysis results. Compiles analysis findings into structured reports - correlates facts from triage/static/dynamic phases, validates hypotheses, generates documentation with evidence chains. Keywords - "summarize findings", "generate report", "document analysis", "what did we find", "write up results", "export findings"