Essential command-line tools and system utilities.
MUST be loaded when setting up, installing, migrating, reviewing, auditing, or checking CLAUDE.md files in projects. Covers installing the promode CLAUDE.md into new projects, migrating existing CLAUDE.md content to AGENT_ORIENTATION.md (progressive disclosure), and auditing projects for conformance. Invoke PROACTIVELY when user mentions CLAUDE.md, project setup, agent configuration, or code meta files.
Systematic code refactoring following Martin Fowler's catalog. Methodologies: characterization tests, Red-Green-Refactor, incremental transformation. Capabilities: SOLID compliance, DRY cleanup, code smell detection, complexity reduction, legacy modernization, design patterns, functional programming patterns. Actions: refactor, extract, inline, rename, move, simplify code. Keywords: refactor, SOLID, DRY, code smell, complexity, extract method, inline, rename, move, clean code, technical debt, legacy code, design pattern, characterization test, Red-Green-Refactor, functional programming, higher-order function, immutability, pure function, composition, currying, side effects. Use when: improving code quality, reducing technical debt, applying SOLID principles, fixing DRY violations, removing code smells, modernizing legacy code, applying design patterns.
Use when user says "update CLAUDE.md", "refresh the docs", "sync claude config", "optimize project instructions", "clean up CLAUDE.md", or when documentation is stale, verbose, or out of sync with codebase reality.
Prefer modern CLI tools for better performance: rg (ripgrep) instead of grep for text searching, fd instead of find for file discovery, bat instead of cat for viewing files, sd instead of sed for text replacement, eza instead of ls for directory listing, dust instead of du, procs instead of ps. Use when writing bash scripts, optimizing command chains, working with file searches, or replacing grep/find/cat in workflows. These tools are faster, respect .gitignore, and have better output formatting.
Reviews BubbleTea TUI code for proper Elm architecture, model/update/view patterns, and Lipgloss styling. Use when reviewing terminal UI code using charmbracelet/bubbletea.
Guidance for using Serena's LSP-powered symbol analysis. Use when exploring codebases, finding symbol definitions, tracing references, or when grep/text search would be imprecise.
Development environment and tool integration guide for the md container. Reference for Chrome DevTools MCP, Node.js, virtualization, and other system tools. See ~/AGENTS.md for complete tool list.
Systematic debugging methodology with root cause analysis. Phases: investigate, hypothesize, validate, verify. Capabilities: backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention. Actions: debug, investigate, trace, analyze, validate, verify bugs. Keywords: debugging, root cause, bug fix, stack trace, error investigation, test failure, exception handling, breakpoint, logging, reproduce, isolate, regression, call stack, symptom vs cause, hypothesis testing, validation, verification protocol. Use when: encountering bugs, analyzing test failures, tracing unexpected behavior, investigating performance issues, preventing regressions, validating fixes before completion claims.
Search local browser history. Use when user asks about visited pages, forgotten URLs, or time spent on sites.
Explain how code works in detail. Use when trying to understand unfamiliar code, complex logic, or system architecture.
Debug web pages directly in Chrome using DevTools capabilities via MCP
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
This skill should be used when the user asks to "run benchmarks", "profile performance", "measure allocations", "optimize render speed", "find hot paths", "generate flamegraph", or mentions stackprof, memory profiler, or performance optimization.
Comprehensive iOS mobile application penetration testing skill with Frida/Objection integration for jailbroken and non-jailbroken devices. This skill should be used when performing security assessments on iOS applications including static analysis, dynamic analysis, runtime manipulation, traffic interception, keychain analysis, and vulnerability identification. Triggers on requests to pentest iOS apps, test iPhone/iPad security, analyze IPAs, bypass security controls, or perform OWASP MASTG iOS assessments.
Get the current observation from the OSWorld environment. Returns screenshot (base64 PNG) and accessibility tree (JSON).
A library for working with enum cases as first-class values, enabling key path-like access to enum cases
Update Slack messages in threads. Use when the user wants to edit, modify, or update an existing Slack message by providing channel ID, message timestamp, and new text content.
Handles custom GitLab API requests. Use for any endpoint not covered by other skills. Triggers: advanced API calls, extensions.
Read and retrieve messages from Slack threads. Use when the user wants to view, analyze, or extract conversation history from a Slack thread by providing channel ID and thread timestamp, or a Slack message URL.
Use when user asks to "search Twitter", "read a tweet", "check my bookmarks", "find mentions", "get tweets from a list", "see who I follow", "extract tweets", or needs programmatic access to X/Twitter for research and information synthesis. Handles reading, searching, bookmarks, lists, and social graph queries.
Download files and directories from remote machines via SSH/SCP or HTTP/HTTPS. Use when user mentions downloading from remote server, scp, rsync, fetch files from remote host, or getting files from remote machine. Supports progress display, resume, and auto-extraction.
