Loading...
Loading...
Found 145 Skills
Run TypeScript type checking with tsc --noEmit and parse errors into actionable, file-grouped output. Use when validating TypeScript code before commits, after refactors, or when checking for type regressions. Use for "type check", "tsc", "TypeScript errors", "type validation", or pre-commit TypeScript verification. Do NOT use for linting, test execution, runtime errors, or JavaScript-only projects without tsconfig.json.
Perses-aware code review: check Go backend against Perses patterns, React components against Perses UI conventions, CUE schemas against plugin spec, and dashboard definitions against best practices. Dispatches appropriate sub-reviewers. Use for "review perses", "perses pr", "perses code review". Do NOT use for general Go/React review without Perses context.
Systematic 4-phase codebase exploration: Detect, Explore, Map, Summarize. Use when starting work on an unfamiliar codebase, onboarding to a new project, reviewing a repository for the first time, or building context before debugging or code review. Use for "explore codebase", "what does this project do", "understand architecture", or "onboard me". Do NOT use for modifying files, running applications, performance optimization, or deep domain analysis.
Run Go quality checks via make check with intelligent error categorization and actionable fix suggestions. Use when user requests "run quality checks", "check PR quality", "verify code quality", or "run make check". Use before creating commits or during PR review. Do NOT use for non-Go repositories, repositories without a Makefile, or manual linter invocation.
Perses project lifecycle management: create, list, switch, and configure projects. Manage RBAC with roles and role bindings per project. Uses MCP tools when available, percli CLI as fallback. Use for "perses project", "create project", "perses rbac", "perses roles", "perses permissions". Do NOT use for dashboard creation (use perses-dashboard-create).
Restore session state from handoff artifacts and route to the next action. Priority cascade: HANDOFF.json (highest) > .continue-here.md > incomplete task_plan.md > git log. Presents a status dashboard, then executes the next action. Use for "resume", "continue", "pick up where I left off", "what was I doing", "continue work". Do NOT use for starting new tasks (use /do), reviewing past sessions (use /retro), or reading task plans (read task_plan.md directly).
Systematic 6-phase analysis of external repositories for ideas worth adopting: clone, parallel deep-read, self-inventory, synthesize gaps, targeted audit of affected subsystems, reality-grounded report. Use when evaluating whether an external repo provides value, analyzing repos for useful patterns, or comparing approaches. Do NOT use for general codebase exploration (use explore-pipeline instead).
Validate a published or draft-preview WordPress post in a real browser using Playwright. Checks rendered title, heading structure, image loading, OG/meta tags, JavaScript errors, and responsive layout at mobile/tablet/desktop breakpoints. When Chrome DevTools MCP is available, can use it for live browser inspection as an alternative to Playwright. Use for "validate wordpress post", "check live post", "verify published post", "wordpress post looks right", "check og tags", or "responsive check wordpress". Do NOT use for source markdown validation (use pre-publish-checker), SEO keyword analysis (use seo-optimizer), or uploading content (use wordpress-uploader).
CLI-based image generation from text prompts using Google Gemini APIs via Python. Use when user needs "generate image", "create image with AI", "gemini image", "text to image", "create sprite", or "generate character art". Supports model selection, batch generation, watermark removal, and background transparency. Do NOT use for web app image features (use nano-banana-builder), video/audio generation, or non-Gemini models.
WordPress REST API integration for posts and media via deterministic Python scripts. Use when uploading articles, creating drafts, publishing posts, uploading images, editing existing posts, or managing WordPress content. Use for "upload to wordpress", "create wordpress draft", "publish to your-blog", "upload image", or "edit wordpress post". Do NOT use for writing articles (use blog-post-writer) or editing prose style (use anti-ai-editor).
Maintain /do routing tables and command references when skills or agents are added, modified, or removed. Use when skill/agent metadata changes, after skill-creator-engineer or agent-creator-engineer runs, or when routing tables need synchronization. Use for "update routes", "sync routing", "routing table", or "refresh /do". Do NOT use for creating new skills/agents, modifying skill logic, or manual /do table edits.
Quick status check for current branch and PR state showing local changes, CI results, reviews, and merge readiness. Use when user wants branch status, PR state, CI check results, review status, or merge readiness. Use for "pr status", "what's the status", "is my PR ready", "check CI". Do NOT use for creating PRs, pushing changes, or fixing review comments.