jaggerxtrm
36 verified skills36 total stars
hook-development
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
tools1
delegating
Proactively delegates tasks to cost-optimized agents before working in main session. MUST suggest for: tests, typos, formatting, docs, refactors, code reviews, feature implementation, debugging, commit validation. Skips main session token usage by routing to GLM (simple/deterministic), Gemini (reasoning/analysis), Qwen (quality/patterns), or multi-agent orchestration (review, feature dev, bug hunt). Never suggest for: architecture decisions, security-critical code, unknown-cause bugs, performance optimization.
development1
gitnexus-exploring
Navigate unfamiliar code using GitNexus knowledge graph
development1
python-testing
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
development1
scoping-service-skills
Task intake and service routing for any task type. Reads service-registry.json directly, detects intent, maps to the right expert skill(s), and emits a structured XML scope plan before any files are touched. Invoke via /scope "task description" before starting any investigation, feature, refactor, config-change, or exploration task.
development1
using-serena-lsp
Explores and edits code using semantic tools and LSP plugins. Use when reading code, understanding structure, finding symbols, or performing surgical edits to functions and classes.
tools1
test-planning
Plans and creates test issues alongside implementation work using bd issue tracker. Activates at two points: (1) when creating an issue board from a spec/plan — classifies each issue by code layer and attaches the right testing strategy as a companion issue or AC gate, and (2) when closing an implementation issue — checks whether adequate test coverage was planned, improves existing test issues if needed. Use this skill PROACTIVELY whenever you see implementation issues being created without test coverage, when an epic is being broken into tasks, when closing/reviewing implementation work, or when the user asks about testing strategy for a set of issues. Also activate when you see bd create, bd children, bd close in a planning context.
development1
using-quality-gates
Quality Gates workflow for Claude Code. Use when editing code in projects with quality enforcement. Covers the full cycle: TDD guard (write failing test first) → implement → auto-lint/typecheck. Activates on code edits, quality issues, or when user asks about testing/linting workflow.
development1
using-service-skills
Service catalog discovery and expert persona activation. At session start, a catalog of registered expert personas is injected automatically. Use this skill to discover, understand, and activate the right expert for any task.
tools1
xt-merge
Merges queued PRs from xt worktree sessions in the correct order (FIFO), maintaining linear history by rebasing remaining PRs after each merge. Use this skill whenever the user has multiple open PRs from xt worktrees, asks to "merge my PRs", "process the PR queue", "drain the queue", "merge worktree branches", or says "what PRs do I have open". Also activate after any xt-end completion when other PRs are already open, or when the user asks "can I merge yet" or "is CI green". Handles the full sequence: list → sort → CI check → merge oldest → rebase cascade → repeat until queue is empty.
testing1
clean-code
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
development1
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
tools1
docker-expert
Docker containerization expert with deep knowledge of multi-stage builds, image optimization, container security, Docker Compose orchestration, and production deployment patterns. Use PROACTIVELY for Dockerfile optimization, container issues, image size problems, security hardening, networking, and orchestration challenges.
devops1
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
testing1
senior-data-scientist
World-class data science skill for statistical modeling, experimentation, causal inference, and advanced analytics. Expertise in Python (NumPy, Pandas, Scikit-learn), R, SQL, statistical methods, A/B testing, time series, and business intelligence. Includes experiment design, feature engineering, model evaluation, and stakeholder communication. Use when designing experiments, building predictive models, performing causal analysis, or driving data-driven decisions.
development1
planning
Structured planning skill for xtrm ecosystem projects. Creates a well-documented bd issue board from any task, feature, spec, or idea — with phases, dependencies, rich descriptions, and integrated test coverage via test-planning. MUST activate whenever the user wants to "plan", "design", "architect", "break down", "structure", "scope out", or "start" a feature or epic. Also activate when: the user describes a complex task without existing issues, pastes a spec or PRD to decompose, asks "how should I approach X" or "where do I start", mentions wanting to create implementation issues, or starts a new worktree session without a claimed issue. Activate even when the user says something like "I want to implement X" — if there's no existing issue board for X, planning comes first. Never skip planning when a task spans more than 2 files or 3 steps — that's when a structured board saves hours.
testing1
creating-service-skills
Generate operational service skill packages for any service in the project. Produces SKILL.md documentation, diagnostic scripts, and references through a mandatory two-phase workflow. Use when onboarding to a new service, adding a new skill, or when a skill is missing from the catalog.
documentation1
security-pipeline
Bootstrap a complete security pipeline (Dependabot + OSV + Semgrep + gitleaks + pre-commit hooks + Codex review) on any GitHub repo. Designed for free user-private repos where GitHub Advanced Security is unavailable. Reusable across Python/TypeScript/Go/Rust stacks.
development1
prompt-improving
Prompt Improver (Trigger: /prompt-improving "raw prompt"). Applies Claude XML best practices to user prompts before execution. Use when the user specifically invokes /prompt-improving.
testing1
orchestrating-agents
Orchestrates task handoff and "handshaking" between Gemini and Qwen CLI agents. Facilitates specialized reviews, second opinions, and cross-validation of complex logic. Use when a task requires multi-model collaboration, a second LLM perspective, or iterative feedback between terminal agents.
tools1
session-close-report
Generate or update the structured technical handoff report at session close. Prefer one same-day SSOT report: update the latest report for today when it exists, otherwise run `xt report generate`, then fill every `<!-- FILL -->` section from orchestrator context.
testing1
xt-debugging
Complete debugging workflow — error analysis, log interpretation, performance profiling, and GitNexus call-chain tracing. Use when investigating bugs, errors, crashes, or performance issues.
development1
xt-end
Autonomous session close flow for xt worktree sessions. Use this skill whenever the user says "done", "finished", "wrap up", "close session", "ship it", "I'm done", "ready to merge", or similar. Also activate when all beads issues in the session are closed, or when the user explicitly runs /xt-end. This skill is designed for headless/specialist use: it must make deterministic decisions, auto-remediate common anomalies, and avoid clarification questions unless execution is truly blocked.
testing1
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
data-ai1
clean-code
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
development1
documenting
Maintain SSOT documentation with drift detection. Runs drift_detector.py scan on invoke to identify stale memories. Creates/updates Serena memories with auto-generated INDEX blocks. MUST be suggested after any feature, refactor, or architecture change is verified complete.
development1
gitnexus-refactoring
Plan safe refactors using blast radius and dependency mapping
development1
gitnexus-impact-analysis
Analyze blast radius before making code changes
development1
senior-backend
Comprehensive backend development skill for building scalable backend systems using NodeJS, Express, Go, Python, Postgres, GraphQL, REST APIs. Includes API scaffolding, database optimization, security implementation, and performance tuning. Use when designing APIs, optimizing database queries, implementing business logic, handling authentication/authorization, or reviewing backend code.
development1
senior-devops
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.
tools1
senior-security
Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.
tools1
sync-docs
Doc audit and structural sync for xtrm projects. Use whenever the README feels too long, docs are out of sync after a sprint, the CHANGELOG is behind, or the user asks to "sync docs", "doc audit", "split readme", "check docs health", or "detect drift". Prefer the xtrm docs command suite (`xtrm docs list`, `xtrm docs show`, `xtrm docs cross-check`) for operator-facing inspection, then use docs-only drift detection on README.md, CHANGELOG.md, and docs/ plus the Python analyzers as validation/backstop tools.
tools1
using-TDD
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
development1
updating-service-skills
Detect implementation drift and sync expert persona documentation. Activates automatically via PostToolUse hook when files in a registered service territory are modified. Use when a skill's documentation has fallen behind the actual implementation.
tools1
using-xtrm
Behavioral operating manual for an xtrm-equipped Claude Code session. Covers when to use which tool, how to handle questions and triggers, workflow examples, and skill routing. Reference material (hook list, gate rules, full bd commands, git workflow) lives in CLAUDE.md. Injected automatically at session start via additionalSystemPrompt.
tools1
service-skills
Operational service-knowledge system for a project's services. One skill that creates, discovers, activates, updates, and scopes per-service expert skill packages (SKILL.md + diagnostic scripts + references), kept in sync with the code via a GitNexus-aware drift engine. Use when onboarding to a service, routing a task to the right expert, scaffolding a missing skill, or syncing a skill after the implementation drifted. Triggers: /service-skills, /creating-service-skills, /using-service-skills, /updating-service-skills, /scope, or any task that touches a registered service territory.
development1