Loading...
Loading...
Found 530 Skills
Generate a personalized follow-up sequence for any creator chasing scenario — missing info, unsigned contract, late content, missing metrics, or incomplete whitelisting setup. This skill should be used when chasing a creator for a response, writing a follow-up message to an influencer, nudging a creator about a late deliverable, following up on an unsigned contract, requesting missing campaign metrics, chasing whitelisting or ad access setup, escalating a non-responsive creator, writing a reminder to a creator who ghosted, building a follow-up cadence for overdue items, drafting a polite but firm nudge to an influencer, or managing creator communication when deadlines slip. For writing initial outreach messages, see creator-outreach-sequence-generator. For classifying and triaging creator replies, see reply-triage-classifier. For negotiating rates after a creator responds, see creator-negotiation-assistant.
Autonomous build-phase orchestrator. Manages slice queue, TDD pair dispatch, full-team code review, mutation testing, CI integration, and auto-merge with quality gates. Replaces manual coordinator overhead during build phase. Activate when running factory mode with ensemble-team.
Tune Kubernetes HPA scale-up/down behavior, topology spread, and resource requests to reduce idle cluster capacity and ensure nodes can drain. This skill should be used when auditing cluster costs on a schedule, analyzing post-incident scaling behavior, or investigating why replicas or nodes do not scale down.
Scrape public posts from X.com (Twitter) users. Extracts text content, timestamps, engagement metrics (views, likes, retweets, replies), and generates direct post links. Use when user asks to scrape/fetch/analyze X.com posts or Twitter data, or mentions "整理@某人的发言" or "看看某人在X上说了什么".
Gmail via Composio API. Use when: (1) Sending emails with optional CC/BCC (2) Listing, searching, or reading inbox messages (3) Replying to messages (4) Creating drafts or managing labels Use Composio HTTP API only.
Email delivery patterns including single, batch, scheduled emails and attachment handling. Use when building transactional email systems, batch communication workflows, scheduled delivery, or implementing file/URL attachments with reply-to and CC/BCC functionality.
Fast X CLI for tweeting, replying, and reading via X/Twitter GraphQL (cookie auth). Supports: read tweets, search, thread/replies, bookmarks, likes, news/trending, user timelines, following/followers, lists. Can be used as a library. Note: Recommended for reading only. Writing will hit blocks quickly.
Replace old API keys with new ones across multiple configuration files, keystores, and logs. Use this skill when the user asks to rotate, replace, update, or refresh API keys across their system. Supports .env files, JSON keystores, and log files. Automatically creates backups before making changes.
General code quality and engineering discipline. Use on any code task to enforce minimal, clean, production-grade changes. Follow these rules when writing, editing, or reviewing code. Activates on: code, implement, fix, build, refactor, feature, bug, change, modify, add, create, develop, write, edit, improve, optimize, update, remove, delete, rename, move, extract, inline, migrate, convert, replace, rewrite.
Multi-agent coordination discipline: one-message-then-wait (send complete context, wait for reply before sending again), idle notifications are heartbeats (no action unless extended + blocking + user asked), no polling loops (event-driven only), never fabricate agent responses (wait for real system events), sequential agent spawning (acknowledge between each), and proper shutdown protocol (request, wait, respect rejection). Activate when orchestrating multiple agents, managing agent teams, coordinating handoffs between agents, spawning subagents, or building multi-agent workflows. Triggers on: "coordinate agents", "spawn multiple agents", "manage agent team", "agent keeps sending messages", "polling loop", "agent idle", "shut down agent", "multi-agent workflow", "agent handoff", "coordinate parallel work", "stop bothering the other agent". Also relevant when an agent is fabricating responses, sending follow-up messages before replies arrive, or reacting to idle notifications unnecessarily.
Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.
Use when constructing Nostr events from natural language descriptions, building kind-specific tag structures, implementing NIP-10 threading for kind:1 replies, creating NIP-22 comments on non-note content, or generating correct event JSON with proper e/p/a tag markers and serialization format.