Sponsored by

Find leads on Reddit on auto pilot

Topic: ai-tools

1,082 skills in this topic.

spec-quality Specification quality framework for planning. Defines the minimum bar for what a plan must address — alternatives, non-goals, blast radius, risk flags, and test strategy. Referenced by schema guidance fields during queue-phase note filling. Read this skill whenever filling requirements or design notes for any MCP work item.
jpicklyk/task-orchestrator 177
pre-plan-workflow Internal workflow for plan mode — checks MCP for existing work, note schemas, and gate requirements to set the definition floor before planning begins. Triggered automatically when entering plan mode for any non-trivial implementation task.
jpicklyk/task-orchestrator 177
create-item Create an MCP work item from conversation context. Scans existing containers to anchor the item in the right place (Bugs, Features, Tech Debt, Observations, etc.), infers type and priority, creates single items or work trees, and pre-fills required notes. Use this whenever the conversation surfaces a bug, feature idea, tech debt item, or observation worth tracking persistently. Also use when user says "track this", "log this bug", "create a task for", or "add this to the backlog".
jpicklyk/task-orchestrator 177
prepare-release End-to-end release automation — reads commits since last tag, infers semver bump, drafts changelog, creates release PR, merges it, waits for CI green, tags, and monitors the Docker build to completion.
jpicklyk/task-orchestrator 177
session-retrospective Analyze the current implementation run — evaluate schema effectiveness, delegation alignment, note quality, plan-to-execution fit. Captures cross-session trends and proposes improvements when patterns repeat. Use after implementation runs, or when user says 'retrospective', 'session review', 'what did we learn', 'analyze this run', 'how did that go', 'evaluate our process', 'wrap up', 'end of session review'. Also use when the output style's retrospective nudge fires after complete_tree.
jpicklyk/task-orchestrator 177
implement End-to-end workflow for taking MCP work items from backlog to merged PR. Handles git branching, schema-driven planning, implementation, independent review, and PR creation. Composes spec-quality, review-quality, and schema-workflow skills into a single pipeline. Use when a user says "implement this", "work on this item", "fix these bugs", "pick up the next task", "create a PR for this", "go through the backlog", or references specific MCP item IDs for implementation.
jpicklyk/task-orchestrator 177
work-summary
jpicklyk/task-orchestrator 177
post-plan-workflow Internal workflow for post-plan materialization — creates MCP items from the approved plan and dispatches implementation. Triggered automatically after plan approval when MCP tracking is active.
jpicklyk/task-orchestrator 177
review-quality Review quality framework for the work-to-review transition gate. Guides verification of plan alignment, test quality, and code simplification before marking implementation complete. Referenced by schema guidance fields during review-phase note filling. Read this skill when filling review-checklist notes or when asked to review completed implementation work.
jpicklyk/task-orchestrator 177
feature-implementation Guide the full lifecycle of a feature-implementation tagged MCP item (the feature container) — from queue through review
jpicklyk/task-orchestrator 177
status-progression Navigate role transitions for MCP work items using advance_item. Shows current role, gate status, required notes, and the correct trigger to use. Use when a user says "advance this item", "move to work", "start this task", "complete this item", "what's the next status", "why can't I advance", "unblock this", "cancel this item", or "check gate status".
jpicklyk/task-orchestrator 177
batch-complete Complete or cancel multiple items at once — close out features, clean up old work, archive completed workstreams. Use when a user says "close out this feature", "complete everything under X", "cancel this workstream", "clean up old items", "bulk complete", "finish this feature", or "archive completed work".
jpicklyk/task-orchestrator 177
schema-workflow Guide an MCP work item through its schema-defined lifecycle — filling required notes using guidancePointer and advancing through gate-enforced phases. Internal skill triggered by hooks and output styles during orchestration workflows. Use when an item has schema tags and needs to progress through queue, work, review, or terminal phases with note gates.
jpicklyk/task-orchestrator 177
manage-schemas Create, view, edit, delete, and validate note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Use when user says "create schema", "show schemas", "edit schema", "delete schema", "validate config", "what schemas exist", "add a note to schema", "remove note from schema", or "configure gates".
jpicklyk/task-orchestrator 177
high-token-mode Forces heavy internal computation (thinking tokens) before each response. Used for stress testing / A/B testing LLM backend KPIs.
Lomnus-ai/TokenBurner 146
tokf-discover Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.
mpecan/tokf 147
tokf-filter This skill should be used when the user asks to "create a filter", "write a tokf filter", "add a filter for <tool>", "how do I filter output", or needs guidance on tokf filter step types, templates, pipes, or placement conventions.
mpecan/tokf 147
tokf-discover Find missed token savings in Claude Code sessions and create filters for unfiltered commands
mpecan/tokf 147
tokf-run Compress verbose CLI output with tokf before returning results. Activates for git, cargo, npm, docker, go, gradle, kubectl, and other supported commands.
mpecan/tokf 147
e2e Run e2e and unit tests for Claude Inspector. Use after code changes to verify regressions.
kangraemin/claude-inspector 114
deploy Claude Inspector macOS 배포 스킬. 빌드(코드사이닝+공증) → GitHub Release → Homebrew cask 업데이트 전체 플로우. '배포', 'deploy', '릴리즈', 'release', '배포해', '출시' 등 배포 관련 요청 시 반드시 이 스킬을 사용한다.
kangraemin/claude-inspector 114
build Build and package Claude Inspector as a distributable Electron app (.dmg / .exe)
kangraemin/claude-inspector 114
memory-engine Memory management system for Claude Code — Student Loop, Smart Context, Auto Learn, Session Handoff, Correction Cycle. Triggered by memory commands (/save, /reflect, /handoff, /check) or memory-related questions. Not for general programming tasks.
HelloRuru/claude-memory-engine 114
dev-standards Enforces development workflows, quality gates, coding standards, and release processes for the deterministic-agent-control-protocol project. Use when implementing features, fixing bugs, refactoring architecture, adding integrations, updating policies, writing tests, updating documentation, or preparing releases.
elliot35/deterministic-agent-control-protocol 109