Productivity

rwilson504 Skill

Port an OpenSCAD parametric script to build123d (Python) cleanly and incrementally. Covers OpenSCAD↔build123d operator equivalence, the SCAD idioms that trip up a literal port (hull/loft, intersection, taper, ternary chains), phased-bundle workflow with a deferred-features tracker, sentinel-based smoke testing for parametric scripts, and naming hygiene when source labels are misleading. USE FOR: "port this SCAD to build123d", "convert OpenSCAD to Python", "rewrite this .scad file", "I have a community OpenSCAD generator I want to extend in Python", "translate hull() to loft()", "bridge SCAD scale=[sx,sy] to build123d taper".

rwilson504 Skill

Foundational Stream Deck plugin workflow: prerequisites (Node 24+, Stream Deck 7.1+, @elgato/cli), `streamdeck create` scaffold, .sdPlugin / src project layout, the dual runtime (Node.js plugin + Chromium property inspector), hot-reload + watch, debugging via Node inspector, logging, linting. USE FOR: starting a new Stream Deck plugin, project file layout, .sdPlugin directory, src/plugin.ts entry, hot reload, watch script, attaching VS Code debugger, streamDeck.logger, ESLint/Prettier config, plugin lifecycle, plugin runtime architecture, Node version pinning, what file goes where.

rwilson504 Skill

Clone a Dataverse Classic Workflow safely, using the Process Template path that works around the platform bug where a naively copied workflow will not activate. Use when user says "make a copy of this workflow", "clone this workflow", "duplicate this workflow", "fork this workflow as a starting point", "copy via Process Template", "save as template", "my copied workflow will not activate", or "why can I not turn on the workflow I duplicated". Covers the template create / instantiate / rename sequence, which identifiers must be regenerated versus preserved, and the trigger and scope settings that silently do not carry across. Do NOT use for editing an existing workflow in place (use dataverse-classic-write) or for moving a workflow between environments (use dataverse-classic-publish).

rwilson504 Skill

Make round-trip-safe edits to Dataverse Classic Workflow XAML so the classic designer still opens the result. Use when user says "add a step to this workflow", "remove this step", "change this condition", "modify this workflow", "edit this XAML", "insert an update step", "change the email body", "add a branch", or asks for any change to a `.xaml` workflow file. Enforces the rules that break workflows when ignored: the mandatory ConditionSequence to ConditionBranch to Composite nesting, wrapping control-flow activities in `mxswa:ActivityReference` rather than emitting them directly, preserving `UserData` and `mva:VisualBasicValue` designer blobs, and the CreateCrmType payload shape required for write operations. Do NOT use for authoring a C# activity assembly (use dataverse-classic-custom-activity) or for activating and importing (use dataverse-classic-publish).

rwilson504 Skill

Get a Dataverse Classic Workflow back into an environment and switched on, using the Power Platform CLI. Use when user says "publish this workflow", "activate this workflow", "deactivate this workflow", "import this solution", "export the solution", "push this to my org", "promote this from DEV to TEST", "pack the solution", "my workflow imported but is not running", or works with `pac solution pack` / `unpack` / `import` / `export`. Covers the pack and import sequence, activation ordering and why activation fails when dependencies are missing, managed versus unmanaged considerations, and the AsyncOperation lifecycle to check after a workflow starts running. Do NOT use for editing XAML (use dataverse-classic-write) or cloning a workflow within one environment (use dataverse-classic-copy).

rwilson504 Skill

Scaffold a custom workflow activity for Dataverse Classic Workflows - a C# `CodeActivity` class that XAML can call through `mxswa:ActivityReference`. Use when user says "create a custom workflow activity", "scaffold a CodeActivity", "write a C# workflow step", "I need a step that does X and the platform has no built-in", "register my workflow assembly", "my custom activity does not show up in the designer", or works with `Microsoft.CrmSdk.Workflow` or spkl `[CrmPluginRegistration]`. Covers the .NET Framework 4.6.2 target, `[Input]` / `[Output]` / `[RequiredArgument]` / `[Default]` / `[ReferenceTarget]` / `[AttributeTarget]` parameter attributes, the sandbox constraints, and assembly registration. Do NOT use for editing workflow XAML (use dataverse-classic-write) or for Dataverse plugins registered on SDK message steps.

zephyrwang6 Bundle

AI 任务钻头 - 任务拆解助手，能够指导人类按任务类型进行任务拆解，分配哪些任务应该给AI做，哪些任务应该是人类自己来做。支持四种任务类型：直接问题解决、直接输出生成、协作问题解决、协作输出生成，并为每种类型提供详细的工作流程和提示词策略。当用户提出任何任务、需要帮助制定计划或要求拆解工作时使用此技能。

acaprino Skill

Deep reference for the data layer of a production service. TRIGGER WHEN: writing or refactoring Pydantic v2 models in Python 3.10+; migrating a codebase from Pydantic v1 to v2; choosing between `Annotated[Decimal, ...]` and `condecimal` for money; hitting v2 validator, serialization or performance surprises; designing FastAPI request/response schemas or error envelopes. DO NOT TRIGGER WHEN: the task is Python testing (use python-tdd) or non-Python schema work (use typescript-development).

acaprino Bundle

Restructure tangled code into a clear equivalent, preserving behavior. TRIGGER WHEN: the user asks for "readable", "maintainable" or "clean" code, a review flags comprehension issues, or the task is legacy modernization or onboarding cleanup.

acaprino Bundle

Structure asyncio code: task management, cancellation, rate limiting, blocking calls kept off the event loop. TRIGGER WHEN: building async APIs, concurrent or I/O-bound systems needing non-blocking operations, or choosing between asyncio, threading and multiprocessing.

baggat236 Bundle

Screen post-earnings gap-up stocks for PEAD (Post-Earnings Announcement Drift) patterns. Analyzes weekly candle formation to detect red candle pullbacks and breakout signals. Supports two input modes - FMP earnings calendar (Mode A) or earnings-trade-analyzer JSON output (Mode B). Use when user asks about PEAD screening, post-earnings drift, earnings gap follow-through, red candle breakout patterns, or weekly earnings momentum setups.

zephyrwang6 Bundle

播客处理一站式工作流。支持两种入口： (1) 直接处理：提供 YouTube 链接，直接进入处理流程 (2) 更新检查：获取关注博主的最新更新，用户挑选后处理 功能：字幕提取 → content-digest 处理 → 自动保存飞书知识库。 触发词："获取播客更新"、"处理这个播客"、"播客工作流"、"有什么新播客"。

waterplanai Skill

Release workflow: branch, changelog, PR, tag, GH release. Triggers on keywords: release, create release, publish release, tag release

waterplanai Skill

Thin package-owned alias for `ac-workflow-mux`. Uses `pimux` as the runtime-only control plane for mux-style tmux orchestration.

waterplanai Skill

Thin trigger alias for the package-owned pimux runtime extension. Use for tmux-backed Pi agents with explicit bridge messaging and notify-first supervision.

waterplanai Skill

Full release workflow including changelog validation, squash, rebase, push, merge to main, and GitHub release preparation. Triggers on keywords: release, create release, publish release, tag release

waterplanai Skill

Thin package-owned alias for `ac-workflow-mux-ospec`. Uses `pimux` as the runtime-only stage orchestration control plane.

waterplanai Skill

Rewrites git history safely with dry-run-first workflow. Supports commit amending, squashing, rewording, tag updates, and force pushing. Always proposes plan before execution. Triggers on keywords: git safe, rewrite history, squash commits, amend commit, fix commit, update tags, rebase history, clean history, fix tag

waterplanai Skill

pi-adapted mux coordinator. Uses pimux as the authoritative runtime while preserving shared mux foundation semantics.

waterplanai Skill

Use the say tool for short one-way spoken alerts to the user. Use when you finish a meaningful task, need attention, confirmation, approval, or input, or when the user explicitly asks for voice output. Keep spoken text brief and put the full details in writing.

waterplanai Skill

pi-adapted mux spec orchestrator. Uses pimux as the authoritative stage runtime while preserving mux-ospec semantics.

agentscope-ai Skill

Use for TeamHarness room classification and Matrix task-room setup: roomflow describe_room, roomflow create_task_room, source/requester room vs task room detection, project-scoped task-room reuse, and invite handling. Do not use for projectflow, taskflow, or message delivery.

agentscope-ai Skill

Use for TeamHarness shared workspace paths, filesync, artifact publication, and Matrix room file boundaries, including artifact publish_file and task/project deliverables. Do not use for message routing or project state changes.

agentscope-ai Skill

Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.

agentscope-ai Skill

Use for TeamHarness message delivery details after a flow has decided a message must be sent: current-session reply, NO_REPLY, cross-room/cross-channel message tool payloads, PROJECT_REQUESTED task-room handoff, and requester replyRoute reports. Do not use to choose work mode, create rooms, delegate, check, or accept tasks.

agentscope-ai Skill

Use when a Worker receives TASK_ASSIGNED, acknowledges the task, works inside shared/tasks/{task-id}/, submits with taskflow submit_task, publishes deliverables through submit_task, and reports TASK_COMPLETED or blockers in the Task room.

agentscope-ai Skill

Use when a Leader must choose Project Work boundaries, owners, dependency shape, DAG vs Loop, acceptance criteria, or follow-up strategy. Do not use for Quick Task execution after the mode is already selected.

genfeedai Bundle

Build editorial content strategy: audience, pillars, platform roles, cadence, calendar, and KPI framework. Triggers on content strategy, editorial calendars, content plans, posting schedules, and content pillars.

genfeedai Bundle

Improve outbound strategy and cold email or DM messaging with value-first personalization, prospecting systems, sequence diagnosis, and response-rate fixes. Triggers on cold outreach, outbound sequences, low replies, prospecting strategy, and sales DMs.

hk-hub Skill

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.

hk-hub Skill

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

k1lgor Skill

Unified debugging skill with two modes — Rapid Fix for pattern-matching known bug types, and Systematic for hypothesis-driven root cause analysis. Use for any debugging task: crash reports, stack traces, performance issues, race conditions, or multi-system failures. Distinguishes itself through a formal hypothesis-driven loop, reproduction-first discipline, and a regression test requirement that closes the loop.

fndlalit Bundle

Comprehensive n8n workflow testing including execution lifecycle, node connection patterns, data flow validation, and error handling strategies. Use when testing n8n workflow automation applications.

okhp3 Bundle

End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.

okhp3 Bundle

Navigate and build in a Replit pnpm multi-artifact monorepo without silent failures. Covers the non-obvious rules that cause blank previews, port conflicts, workflow naming errors, and broken cross-artifact imports: BASE_URL prefix discipline, PORT env var reading, managed workflow naming, pnpm catalog drift, and workspace:* shared library wiring. Activate for "add an artifact", "create a new app", "preview path", "port conflict", "blank preview", "shared package", "workflow naming", "pnpm catalog", "cross-artifact", or any time a second artifact is being added to an existing Replit project.

k1lgor Skill

Create detailed, step-by-step implementation plans with dependency annotations and verification checkpoints. Use after brainstorming to document the execution strategy, or when tasked with creating a plan for a feature or change. Differentiator: Every plan includes scope boundaries, dependency annotations, verification checkpoints per phase, and a rollback plan — not just a task list.