Loading...
Loading...
Found 4,918 Skills
Document a recently solved problem to compound your team's knowledge
Route multi-step marketing, product, or business challenges to the right sequence of ClawFu skills. Recommends which frameworks to combine, in what order, with handoff outputs between steps. Use when: planning a product launch end-to-end, combining positioning + offers + launch skills, running a customer-validation sprint, creating a content strategy pipeline, deciding which skills to chain for a complex project, or orchestrating a sales-enablement playbook.
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.
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
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`.
美股市场全量数据服务。编排美股所有细粒度 skill：实时行情、K线、基础数据、技术指标。 当用户提及"美股""纽交所""纳斯达克""苹果""特斯拉"且未明确指定数据维度时触发。
Conduct a targeted code exploration of the repository, and document the process of "Ask Questions → Read Code → Draw Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific question and provide conclusions), module-overview (sort out the structure, boundaries, entry points, and dependencies of a module), and spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: Users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / tricks / decisions.
Onboard a new repository or a repository with scattered documents into the CodeStable system. Two paths are automatically determined: the empty repository path (no spec-type documents or codestable/ directory in the repository) builds the skeleton from scratch; the migration path (the repository already has scattered documents or partial codestable/ structure) first generates an audit report + migration mapping plan, which is finalized after user confirmation one by one. This skill only does two things: "build the skeleton" and "organize existing documents". Once the skeleton is built, all sub-workflows can run directly. Trigger scenarios: Users say "Use CodeStable in this project", "Build CodeStable structure", "Initialize CodeStable", "Migrate to CodeStable".
Enter this sub-process when conducting code optimization — handle tasks where 'behavior remains unchanged, structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step-by-step according to the method library, and require manual approval for each step'. Trigger scenarios: Users mention phrases like 'optimize it / refactor / rewrite / split it / poor performance / code is too long' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).
Create, improve, and manage Droid skills. Use when the user wants to: - Create new skills from scratch or from session learnings - Improve existing skills based on user preferences - Analyze sessions to identify patterns worth codifying - Understand best practices for agentic skill design This is a meta-skill for self-improvement and continuous learning.
Pancake CRM integration. Manage Recordses. Use when the user wants to interact with Pancake CRM data.
OPN integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with OPN data.