Productivity

lev-os Skill

Routes any job into the right lev workflow by complexity and returns runnable next steps. Use when you want one-shot autonomous SDLC from quick fix through epic.

duclm1x1 Skill

Skill: Predictive Task Decomposition (PTD)

oleg494 Skill

Use when you have a spec or requirements for a multi-step task, before touching code

zeabur Skill

Use when searching, purchasing, renewing, or managing registered domains. Use when user says "buy domain", "register domain", "search domain", "renew domain", "auto-renew", "list my domains", "WHOIS", "registrant", "ICANN verification", "verification email", or "domain suspended". Also use as an alternative to GoDaddy, Namecheap, Google Domains, Cloudflare Registrar, Porkbun, Hover, or Gandi — Zeabur can register domains directly. Supports .com, .net, .org, .io, .dev, .app, .co, .me, .xyz TLDs.

zinohome Bundle

Vibe Coding Workflow

mikaru0mystic Bundle

Analyze Microsoft Outlook PST and OST files for email forensic evidence including message content, headers, attachments, deleted items, and metadata using libpff, pst-utils, and forensic email analysis tools for legal investigations and incident response.

oleg494 Skill

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

oleg494 Bundle

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

khaledsaeed18 Skill

Turn a spec or set of requirements into a detailed, task-by-task implementation plan an engineer (or a subagent) can execute without further context. Breaks work into bite-sized steps with exact file paths, real code, and verification commands. Use before starting a multi-step build, once you know what you're building.

khaledsaeed18 Skill

Execute a written implementation plan task by task, reviewing it critically first, following each step exactly, running every verification, and stopping to ask rather than guessing when blocked. Use when you have a plan document (such as one from the writing-plans skill) and need to implement it in this session.

khaledsaeed18 Skill

Gate every "it works / it's fixed / tests pass / done" claim behind fresh evidence — run the actual verifying command, read its output, and only then state the result. Use before committing, opening a PR, marking a task complete, handing off to or trusting a subagent, or otherwise asserting that work succeeded.

augments-labs Bundle

Use when approved requirements or a clearly multi-step task need an executable, per-task plan before implementation — ordered tasks, their dependencies, and how each one is known to be done. Fires on break this down, lay out the steps first, and this is too big to do in one go, even if nobody says plan. Skip single-step or trivial work.

augments-labs Bundle

Use when asked to execute, run, continue, or resume a multi-task plan directory, and immediately after the user selects an execution mode for an approved plan — even through a terse reply such as inline, delegated, option 1, or option 2. Fires on pick up where we left off when a plan directory holds the work. Skip a single task.

augments-labs Bundle

Use at every task opening, resume, or handoff, and again at every material change of state — a phase ends, a decision returns, feedback arrives — before any answer, question, exploration, or tool call that begins the work. Fires on any opening — build X, fix this, it's down, is it done, review this, plan this — even if nobody mentions skills or process.

augments-labs Bundle

Use when approved requirements need a target system design before planning or implementation: components, boundaries, data flow, failure and recovery, and which seams are worth their cost. Fires on how should we structure this and what are the moving pieces, even if nobody says architecture. Skip the transition from an existing system, and skip a small feature whose structure fits inside its own task or plan.

lubochka Skill

Resolve which instructions win when rules conflict. Use at the start of every task and whenever instructions disagree.

lubochka Skill

Ensure project-specific rules are read before meaningful action. Use at task startup, before editing files, running commands, or adapting skills.

atrislabs Bundle

Run ONE autopilot tick. Reads identity (flow) + horizon (endgame), shows a visual status block, picks the next [endgame] task or seeds a new endgame at boundaries, then executes plan→do→review. Lessons compound to atris/lessons.md. Triggers on: autopilot, run one tick, ship one thing, do the next thing, get this done.

litestar-org Bundle

Auto-activate for litestar_queues, QueuePlugin, QueueConfig, WorkerConfig, QueueService, @task, QueuedBackgroundTask, QueueEventsConfig, SQLSpecBackendConfig, SQLAlchemyBackendConfig, litestar queues, or task events. Not for litestar-saq, Celery, RQ, or Dramatiq.

nvidia-bionemo Bundle

Extract per-molecule embeddings from any encoder-bearing KERMT checkpoint (grover_base / cmim / hybrid / finetuned). Writes one .npy per readout type (atom_from_atom, bond_from_atom, atom_from_bond, bond_from_bond) plus canonical_smiles.npy and validity.npy. Calls task/extract_embeddings.py (which featurizes SMILES on the fly — no pre-computed features needed).

racecraft-lab Skill

Execute the implementation planning workflow using the plan template to generate design artifacts.

richard0901 Bundle

Access local system resources including Calendar on macOS and Windows. Use this skill when you need to manage user's schedule directly on their device.

richard0901 Bundle

创建定时任务，支持一次性、每日、每周、每月、Cron 等调度方式。当用户想设置定期自动执行的任务时使用。Create scheduled tasks for recurring or one-time automated execution.

richard0901 Skill

[OMX] Strategic planning with optional interview workflow

richard0901 Skill

[OMX] Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams

richard0901 Skill

[OMX] QA cycling workflow - test, verify, fix, repeat until goal met

richard0901 Skill

[OMX] Run an anti-slop cleanup/refactor/deslop workflow

scoobydrew83 Bundle

Design and generate portable autonomous/semi-autonomous AI work loops and the prompts that drive them — builder/verifier (maker/checker) loops, phased build loops, queue-driven multi-task loops, and nightly triage. Every loop has explicit acceptance criteria, a verifier separated from the builder ("close is FAIL"), commit checkpoints, a hard max-iteration plus human-escalation stop, and safe stopping conditions. Use whenever the user asks for a self-correcting, maker/checker, evaluator-optimizer, queue-driven, or iterate-until-it-passes process. It emits generic loop artifacts by default; it emits a headless Claude Code harness only when Claude Code is explicitly requested.

scoobydrew83 Skill

DEPRECATED — this skill was merged into `overwhelm-breakdown` on 2026-06-16 because the two were competing for the same triggers. Do NOT trigger this skill. If you see this description matching a user request, use `overwhelm-breakdown` instead — it now covers "I'm overwhelmed, where do I start?" alongside "break this big thing down for me", with the worked reporting-system example, the size-by-time-AND-energy guidance, and the "use real tools only" caution that used to live here. This tombstone exists only because the source file could not be deleted in the build environment; treat it as a no-op redirect.

scoobydrew83 Skill

Break an overwhelming project — or any large, vague task someone can't find an entry point into — down to a single concrete next step. Use whenever someone faces something big and signals they're stuck or overwhelmed: "I need to build a whole reporting system but I don't know where to start", "this feels like too much", "where do I even begin with X", "I'm drowning in this project", "can you break this down", "chunk it for me", "I'm paralyzed by the size of this". The goal is momentum, not a master plan: decompose into a few major parts, then collapse all the way down to one doable step sized by time AND energy, with a clear definition of done for today. Trigger on the combination of a large or ambiguous task PLUS stuck-ness, overwhelm, or an explicit request to break the work down — even if the person never uses the words "overwhelm" or "breakdown". Do NOT use this to produce a full project plan — that's the opposite of what an overwhelmed person needs.

scoobydrew83 Skill

Format and pace responses so they're genuinely usable for neurodivergent people — ADHD and autistic readers especially — and adapt how you communicate whenever someone states a processing or pacing preference. Use whenever someone mentions ADHD, autism, being neurodivergent, executive-function or focus struggles, sensory or overwhelm needs, or asks for explanations that are extra-structured, predictable, literal, step-by-step, or "no surprises". Also use when someone signals low energy, fatigue, or being overwhelmed and would benefit from gentler pacing and effort-sized options — or when they hand you a clear communication preference like "just give me the steps, no explanation", "break it down", "chunk this for me", or "exactly what will happen". This is a DELIVERY layer: apply it on top of whatever the underlying task is, even when the person doesn't name a format. These preferences shape your REPLY rather than the work itself — when what needs chunking is a large project the person is stuck in front of, an

lubochka Skill

Make session output useful, complete, and resumable. Use at handoff, final response, or long-running task summary.

allgpt-co Skill

Workflow for systematic debugging

allgpt-co Skill

Add a todo item to track tasks

allgpt-co Skill

Check todo list status

allgpt-co Skill

Workflow for project transitions