remind-implement
Systematic task execution using Remind as the work queue. Use when the user wants to implement tasks, build from a plan, work through a backlog, or says "let's build this" after planning/speccing.
Systematic task execution using Remind as the work queue. Use when the user wants to implement tasks, build from a plan, work through a backlog, or says "let's build this" after planning/speccing.
Systematic task execution using Remind as the work queue. Use when the user wants to implement tasks, build from a plan, work through a backlog, or says "let's build this" after planning/speccing.
This skill should be used when the user asks about "job status", "check if request completed", "cancel request", "why is my request taking so long", "poll for result", "batch requests", "retry failed request", "request timeout", "async operations", "job lifecycle", "manual polling", or needs advanced control over SDK async operations, manual job polling, batch processing, retry logic, or job cancellation.
Write Clayscript formulas, conditional runs, and credit-saving logic in Clay. Use when the user asks about Clayscript, Clay formulas, conditional runs, saving credits with logic, data manipulation, if/then logic, JavaScript formulas in Clay, or the AI formula generator. Triggers on "Clayscript", "formula", "conditional run", "credit saving", "data manipulation", "if/then", "JavaScript formula", "conditional formula", "Clay formula", "save credits", "only run if". Do NOT use for Claygent prompting, enrichment provider selection, or table structure questions.
Troubleshoot Clay workflow issues, fix common mistakes, resolve auto-update problems, and stop credit waste. Use when the user reports something not working in Clay, credits being wasted, auto-update issues, wrong enrichment results, empty columns, or workflow errors. Triggers on "not working", "error", "troubleshoot", "debug", "credits wasted", "auto-update issue", "Clay problem", "wrong results", "fix my workflow", "common mistakes", "empty results", "credits burning". Do NOT use for building new workflows from scratch, learning Clay basics, or pricing questions.
This skill should be used when the user asks to "scaffold a Bankr project", "create new Bankr bot", "build a Bankr web service", "create Bankr dashboard", "build Bankr CLI tool", "project structure for Bankr", "Bankr project types", or needs guidance on directory structures and templates for different types of Bankr API integrations.
This skill should be used when the user asks to "scaffold a Bankr SDK project", "create new SDK bot", "build a Bankr web service", "create Bankr dashboard", "build Bankr CLI tool", "project structure for SDK", "x402 project types", or needs guidance on directory structures and templates for different types of Bankr SDK integrations.
Break down a high-level objective from the Orchestrator into specific, actionable sub-tasks for workers. Creates task files in the project's .crewly/tasks/ directory.
Expert n8n workflow automation consultant for B2B sales and GTM teams. Use when the user asks about n8n workflows, n8n nodes, n8n triggers, n8n webhooks, n8n credentials, n8n self-hosting, n8n Docker setup, n8n queue mode, n8n error handling, n8n sub-workflows, Clay + n8n integration, n8n CRM automation, n8n pricing, n8n vs Zapier vs Make, or building automations with n8n. Also triggers on "n8n workflow", "n8n automation", "n8n webhook", "n8n node", "n8n self-host", "n8n Docker", "n8n queue", "n8n Clay", "n8n HubSpot", "n8n Salesforce", "n8n vs Zapier", "n8n pricing", "workflow automation". Do NOT use for Clay-only questions without n8n context or general automation strategy without n8n.
Design n8n workflow architectures for B2B GTM automations. Use when the user asks about building n8n workflows, choosing nodes, designing data flows, sub-workflows, or structuring multi-step automations. Triggers on "design workflow", "n8n workflow", "node sequence", "data flow", "sub-workflow", "workflow architecture". Do NOT use for trigger/webhook setup (use triggers-webhooks) or error handling (use error-handling).
This skill should be used when executing Bankr requests, submitting prompts to Bankr API, polling for job status, checking job progress, using Bankr MCP tools, or understanding the submit-poll-complete workflow pattern. Provides the core asynchronous job pattern for all Bankr API operations.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Requires a bash tool that supports pty:true.
Create .md skill files for Output framework's lazy-loaded instruction system. Use when adding skills to prompts, configuring skill loading, or debugging skill resolution.
Prepares Pine Scripts for publication in TradingView's community library with proper documentation and compliance. Use when preparing to publish, adding documentation, ensuring House Rules compliance, writing descriptions, or finalizing scripts for release. Triggers on "publish", "release", "documentation", "House Rules", or preparation requests.
Orchestrates Pine Script development by coordinating workflows and planning complex projects. Use when building complete trading systems, managing multi-step projects, planning indicator/strategy development, or coordinating multiple capabilities. Triggers on complex requests mentioning multiple features, "build a complete", "trading system", or project planning needs.
Execute pending daily punishments by sending Pavlok stimuli via scripts/repentance.py. Use when you need to run the punishment cycle.
Long-horizon robot task execution workflow for multi-step manipulation tasks. Use this skill when one user goal must be decomposed into ordered subtasks, each subtask needs explicit success checks, retries, or recovery, and every prompt-driven policy rollout should be executed through $monitored-subtask-execution instead of calling raw MCP robot tools directly.
会話中に行った作業を再利用可能なスキル(SKILL.md)に変換する。引数不要で起動し、会話履歴から手順・判断・スクリプトを抽出して、暗黙知を徹底的に言語化した高品質なスキルを生成する。Use When: 「スキル化して」「この作業をスキルにして」「/create-skill」で起動。作業完了後に「これスキルにしたい」と言われた場合にも使用。
Use when writing Python code for ERPNext/Frappe Server Scripts including Document Events, API endpoints, Scheduler Events, and Permission Queries. Prevents the #1 AI mistake: using import statements in Server Scripts (sandbox blocks ALL imports). Covers frappe.* methods, event name mapping, and correct v14/v15/v16 syntax. Keywords: Server Script, frappe, ERPNext, sandbox, import, doc event, validate, on_submit, before_save, server script example, import not allowed, sandbox rules, which script type to use.
Reddit automation with CamoFox CLI — login, browse, post, comment, reply with anti-detection. Use when the user needs to automate Reddit interactions, post to subreddits, comment on threads, or browse Reddit programmatically. Triggers include "reddit", "post to reddit", "reddit comment", "reddit automation", or any request to interact with Reddit via browser automation.
Run a Python fuzzer script (provided as a string) for a fixed duration.
Creates structured Taskplane task packets (PROMPT.md, STATUS.md) for autonomous agent execution via the task-orchestrator extension (/orch). Use when asked to "create a task", "create a taskplane task", "stage a task", "prepare a task for execution", "write a PROMPT.md", "set up work for the agent", "queue a task", or whenever the user wants to define work that will be executed autonomously by another agent instance.