Detect and use llms.txt files for LLM-optimized documentation. Use when checking if a site has LLM-ready docs before scraping.
Extract text and layout from images and PDFs using LLMWhisperer API. Good for handwriting and complex forms.
Check LLM Wiki health. Finds orphan pages, broken wikilinks, contradictions, stale content, missing pages, cross-reference gaps, and suggests improvements.
Initialize the LLM Wiki. Creates directory structure, index, log, sets up qmd collection, and runs initial ingest of all existing content from raw/, docs/, and notes/.
Optimize the LLM Wiki. Compacts verbose pages, merges near-duplicates, reorganizes misplaced content, strengthens cross-references, improves consistency, and generates missing…
LLVM IR and pass pipeline skill. Use when working directly with LLVM Intermediate Representation (IR), running opt passes, generating IR with llc, inspecting or writing LLVM IR…
Synchronisiert automatisch die verfügbaren LM-Studio-Modelle mit der chatLanguageModels.json Konfiguration.
Build Flutter UI bằng package lme_ui (lme-ui-flutter). Auto-trigger khi project có dependency `lme_ui`, file Dart import `package:lme_ui/lme_ui.dart`, hoặc user nói "build…
LMNT integration. Manage Leads, Persons, Organizations, Deals, Projects, Pipelines and more. Use when the user wants to interact with LMNT data.
Automate Lmnt tasks via Rube MCP (Composio). Always search tools first for current schemas. — from general/automation
Configure learning management system settings, user roles, course templates, gradebooks, and third-party integrations
Reduces token usage from paid providers by offloading work to local LM Studio models. Use when: (1) Cutting costs—use local models for summarization, extraction, classification,…
Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.
Analyzes current or recent session for errors, inefficiencies, and improvement opportunities across skills, tools, hooks, and communication.
Installs agents, configures MCP servers, aligns marketplace plugins, creates and audits instructions. Use after setup or when agents/MCP/plugins need alignment.
Use when installing MCP packages and configuring Claude-side MCP registration, hooks, permissions, IDE extension mode, and migrations.
Use when installing or verifying this marketplace in Claude and Codex, aligning selected plugins, MCP settings, and Codex execution defaults.
Creates AGENTS.md canonical and CLAUDE.md @AGENTS.md stub; audits token budget, cache safety, import-pattern compliance. Use when instruction files need alignment.
Use when bootstrapping or managing VPS agent environments: fresh install, add project, hex-relay redeploy, diagnostics, or fleet plan/apply.
Use when installing, verifying, or updating the shared VPS host runtime for Claude Code, Codex, MCP, and marketplace plugins.
Use when deploying, redeploying, verifying, migrating, or syncing users for the hex-relay Telegram/API control plane on a VPS.
Use when inspecting health, drift, logs, auth, ports, systemd, tmux, or safe repair needs for one VPS project environment.
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.
Creates root documentation files (AGENTS.md, CLAUDE.md, docs/README.md, standards, principles). Use for initial project doc setup.
Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.
Extracts procedural content from project docs into slash commands. Use when docs contain deploy, test, or troubleshoot procedures.
Creates slash commands from procedural doc sections. Use when transforming documentation prose into executable commands.
Reviews skills (D1-D11 + M1-M6 criteria) or .claude/commands for quality. Use when validating skill correctness before release.
Decomposes scope into Epics, Stories, and RICE priorities. Use when user has project scope and wants full Agile breakdown.
Discovers growth opportunities using Traffic-First KILL funnel. Use when searching for next product direction with validated demand.
Creates or replans 3-7 Epics from scope using Decompose-First pattern. Use when initiative needs Epic-level breakdown or Epic scope changed.
Analyzes Story and builds optimal task plan (1-8 tasks), then routes to create or replan. Use when Story needs task breakdown or replanning.
Compares ideal plan vs existing tasks and applies KEEP/UPDATE/OBSOLETE/CREATE changes. Use when Story tasks need re-sync with updated requirements.
Use when an evaluation run needs review-driven documentation updates and a structured documentation summary.
Use when accepted findings require bounded repair changes and a structured repair summary.
Use when an evaluation run requires bounded iterative refinement with trace and cleanup evidence.
Executes implementation tasks through Todo, In Progress, To Review. Use when task needs coding with KISS/YAGNI. Not for test tasks.
Reviews task implementation for quality, code standards, and test coverage. Use when task is in To Review. Sets task Done or To Rework. — from general/general-misc
Reviews task implementation for quality, code standards, and test coverage. Use when task is in To Review. Sets task Done or To Rework. — from majiayu000/claude-skill-registry
Fixes tasks in To Rework by applying reviewer feedback, then returns to To Review. Use when task was rejected during review.
Runs parallel external agent reviews (Codex + Gemini) on code changes. Process-as-arrive, critical verification with debate. Returns filtered suggestions.
Runs existing test suite to catch regressions after implementation changes. Use when Story needs regression verification. No status changes.
Audit project documentation quality across 8 categories (Hierarchy, SSOT, Compactness, Requirements, Actuality, Legacy, Stack Adaptation, Semantic Content).
Checks hierarchy, links, SSOT, compression, requirements compliance, freshness, legacy cleanup. Use when auditing documentation structure.
Checks inline code documentation quality: WHY-not-WHAT, density, forbidden content, docstrings quality, actuality, legacy cleanup. Use when auditing comments and docstrings.
Verifies claims in .md files (paths, versions, counts, configs, endpoints) against codebase, cross-checks contradictions. Use when auditing docs accuracy.
Checks build, lint, type, test, and CI delivery gate failures. Use when auditing whether the project can reliably ship.
Checks DRY, KISS/YAGNI, error handling, DI patterns. Use when auditing code principles compliance.
Checks evidence-backed duplication, over-abstraction, and unused extensibility. Use when auditing DRY/KISS/YAGNI risk.
Checks local maintainability hotspots: complexity, long methods, god modules, signatures, algorithms, and constants. Also flags identifier drift across API/DTO/DB layers.
Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.
Checks dependency health and generic custom utility/integration replacement opportunities. Use when auditing dependency and reuse risk.
Checks unreachable code, unused imports/variables/functions, commented-out code, unsupported patterns. Use when auditing dead code.
Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.
Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.
Checks structured logging, health checks, metrics collection, request tracing, log levels. Use when auditing observability.
Checks async races, thread safety, TOCTOU, deadlocks, blocking I/O, resource contention. Use when auditing concurrency safety.
Checks races, deadlocks, async hazards, TOCTOU, blocking I/O, and shared resource contention. Use when auditing concurrency correctness.
Checks bootstrap initialization, graceful shutdown, resource cleanup, signal handling, liveness/readiness probes. Use when auditing app lifecycle.