Total 44,738 skills, Automation has 1353 skills
Showing 12 of 1353 skills
Monitor sBTC balance and auto-route excess above a reserve threshold to Zest yield
Dollar Cost Averaging (DCA) for Stacks DeFi — automate recurring buys or sells of any Bitflow token pair via direct swaps. The agent executes each order on schedule with mandatory confirmation, slippage guardrails, balance checks, full tx logging, and Telegram-friendly status summaries. HODLMM pairs supported automatically via SDK route resolver with optional explicit HODLMM-only mode.
Cross-protocol yield rotator for Stacks mainnet. Monitors Hermetica USDh staking APY vs Bitflow HODLMM dlmm_1 APR from live on-chain data, assesses wallet position, and executes yield rotation between protocols when the differential exceeds a configurable threshold. Write-capable: outputs MCP commands for stake, initiate-unstake, complete-unstake, and cross-protocol rotate actions.
Griffin integration. Manage data, records, and automate workflows. Use when the user wants to interact with Griffin data.
Shows the status of all active SDD changes and orchestrator state. Uses engram for persistence. Trigger: /sdd-status, show active changes, what changes are in progress, SDD status, orchestrator status.
Implements the corrections found by /project-audit. Reads audit-report.md as spec and executes each required action. Trigger: /project-fix, apply audit corrections, fix claude project.
A/B Tasty integration. Manage data, records, and automate workflows. Use when the user wants to interact with A/B Tasty data.
Auto-detect project tech stack and configure language-specific references
Parent skill marker for JS Eyes browser automation and extension skill dependencies.
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.
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.