Loading...
Loading...
Found 5,653 Skills
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
Conduct targeted code exploration on a repository, and document the process of "Asking Questions → Reading Code → Reaching Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific problem and provide conclusions), module-overview (organize the structure, boundaries, entry points, and dependencies of a module), spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: When users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". For the distinction from learning / tricks / decisions, refer to the root skill `easysdd`.
Break down a requirement that is "too large to be implemented as a single feature" into a list of sub-features with dependencies and statuses, and place it in the independent `codestable/roadmap/{slug}/` directory — serving as the seed and scheduling basis for subsequent multiple feature processes. Two modes: new (draft a new roadmap from a large requirement), update (refresh an existing roadmap: add items, modify dependencies, reorder, mark as drop). Division of labor with requirements / architecture — those two record "what the system is now", while the roadmap records "what we plan to do next". Trigger scenarios: Users say "I want an X system", "Help me break down this requirement", "Schedule this large requirement", "Create a roadmap", or it is found during the feature-design phase that the requirement is too large to fit into a single feature.
Help a PhD student intentionally choose which cognitive mode to enter right now (deep production, wide reading, or collaborative engagement) and plan their day around these modes to minimize context-switching costs. Use this skill whenever the user is at the start of a day or work block and unsure what to focus on, feels scattered across too many activities, asks "what should I do right now", wants to plan their day, or feels frustrated by constant context-switching. Trigger on phrases like "plan my day", "what should I work on now", "I feel scattered", "context switching", "deep work", "can't focus", "I have X hours", or whenever the user is trying to decide between substantively different kinds of work (writing vs reading vs meetings).
Clarify the user’s intent for vague, incomplete, or ambiguous clauses, statements, and requirements before modifying the code.
Canonical Zener HDL semantics, package rules, manifests, and high-value stdlib APIs. Covers `Module()`, `io()`, `config()`, imports, `pcb.toml`, `pcb.sum`, stdlib interfaces and units, and package APIs.
Use when preparing, submitting, polling, or debugging Seedance 2.0 video generation jobs from product images, storyboard images, UGC scripts, voiceover copy, or promptPlan request JSON. Use for splitting scripts into render segments, uploading references, creating request JSON, submitting jobs through the hosted capability, polling predictions, and handing off local render paths.
帮中文用户从当前已发布的 PostPlus skill surface 里找到合适技能，并给出公开安装命令。适合“有什么技能可以做 X”“我该装哪个技能”“帮我解释当前已发布技能范围”的场景。
Run Blacksmith Testbox for CI-parity checks, secrets, hosted services, migrations, or builds local cannot reproduce.
Send WhatsApp messages to users. After completing tasks, ask what they want next via WhatsApp and continue the conversation until they say they're done.
Stage 1 spec compliance review. Triggers: /review stage 1. Verifies implementation matches design specification — functional completeness, TDD compliance, and test coverage. Do NOT use for code quality checks — use quality-review instead. Do NOT use for debugging.
Heavy-ceremony orchestration for big work — research, planning, adversarial review, phased implementation, audit, delivery. Use when the user says "epic", "long task", "build this end to end", or wants a feature that runs all night.