Loading...
Loading...
Found 283 Skills
Use to build a content calendar — a sustainable, repeatable posting rhythm and recurring structure (which pillars/formats post on which days, on which platforms), derived from strategy and pillars. Run when the user says "content calendar," "editorial calendar," "social media calendar," "posting schedule," "content plan" (ongoing), "what should I post each week," "build me a posting routine/cadence," or wants a repeatable system rather than one period's posts. Reads social-strategy, content-pillars, and brand-profile first; sizes cadence to real capacity; builds a recurring skeleton of buckets and named series with room reserved for reactive/trend content; sets the planning rhythm (batch, buffer, review). Hands a period's briefs to batch-content-plan, content to the writing skills, and scheduling to scheduling-and-queue. For filling one specific week/month with actual posts use batch-content-plan; for higher-level channel/goal choices use social-strategy.
Route broad, ambiguous, or cross-domain Mermail requests to the narrowest current workflow across MCP connection, CLI automation, agent inbox identity, inbox management, email composition, workspace admin, triage, mailbox-agent delegation, Composio integrations, scheduling/GTM/support/research/x402/xStocks personas, and Agent Wallet. Use when the user does not already name a focused skill or combines multiple Mermail jobs in one request.
Book time, check calendar availability, and handle scheduling email through a Mermail mailbox plus Google Calendar. Use when the job is scheduling, meeting booking from inbound email, free/busy checks, or calendar holds with email confirmation. Do not use for generic inbox search, outbound GTM, support tickets, Gmail/Outlook Composio, or Agent Wallet.
Stop and consult this skill whenever your response would involve any fact or code related to ZIO core or the ZIO ecosystem. Covers: ZIO effects and type aliases (ZIO, Task, UIO, UEffect), fibers and fiber management, concurrency primitives (Hub, Queue, Ref, Semaphore), Software Transactional Memory (STM), ZIO Streams (ZStream, ZSink, ZPipeline, ZChannel), ZIO Test framework and test utilities, ZLayer and dependency injection patterns, error management and error types, scheduling and retries, resource management and scoping, ZIO Config, ZIO Schema, ZIO JSON, ZIO Kafka, and all official ZIO libraries and integrations. Trigger this for any ZIO coding task, type signatures, library features, architectural patterns, or comparisons involving ZIO. Any time you would otherwise rely on memory for ZIO details, verify here instead — your training data may be outdated or wrong.
Adapt a novel into a five-component short drama outline kit: adaptation notes, character list, highlight points table, episode synopses, and asset list. Outputs outline.json, Markdown, and a single-page review report (with KPI bands, key decisions, highlight timeline, scheduling matrix, scene overview, and quality gates). All 14 quality gates are deterministically checked by scripts (including character tier limits, dynamic main scene limits based on episode count, highlight interval ≤ 3 episodes, mandatory hook/suspense for each episode, etc.), with no reliance on model self-regulation. Supports a checkup mode: paste an existing outline and run only the quality gates for diagnosis. Zero dependencies, zero API keys, uses current session quota. Use when requested for: adaptation outline, short drama outline, outline breakdown, novel-to-short-drama adaptation.
Turns a full inbox into a short, ranked list of what actually needs the owner. Reads the mail, sorts it into needs-you, drafted-and-waiting, and handled, writes replies in the owner's own voice, pulls out the action items and deadlines buried in long threads, files what is finished, and hands bills, leads, and scheduling requests to the skills that own them. Works from pasted or forwarded email text when no mailbox is connected. Use this whenever the owner mentions email at all — including "drowning in email," "I have 300 unread," "what emails need me," "go through my inbox," "clean up my email," "did I miss anything," "who am I supposed to get back to," "draft a reply to this," or "catch me up on my mail." Reach for it for one forwarded message as readily as for a whole morning's backlog.
The research-and-sourcing craft — verify the substance of a piece before it publishes: trace stats to primary sources, kill zombie stats, catch AI-hallucinated citations, and attribute properly on social. Use when someone has a stat-heavy draft to make publish-ready, wants to check if a viral statistic is real, asks how to cite sources, used AI research output, or is making health/finance claims. Uses the FACTS framework. Reads brand-profile + the piece's format skill first. AI-supplied citations are guilty until verified; a working link is not verification; aggregators are leads, not the source; where none exists, reframe as owned observation or commission data. The agent verifies where it has search; the human clicks links where it doesn't; verification happens before scheduling; WoopSocial publishes. Never invents studies or reuses retracted stats. Distinct from idea-generation, data-and-original-research, quote-cards, and infographic-and-data-viz.
Use to build a hashtag and discoverability strategy for social posts — the modern (2026) approach, not the outdated "30 hashtags to go viral" playbook. Run when the user says "hashtags," "what hashtags should I use," "how many hashtags," "hashtag strategy," "help me get discovered/reach," asks "do hashtags still work / are hashtags dead," or asks how to tag a post. Reads brand-profile and audience first. Sets the keyword/social-SEO layer first (caption, on-screen text, spoken audio) because that — plus engagement and the content itself — drives discovery far more than hashtags now; then picks a tight, relevant, per-platform hashtag set (respecting caps like Instagram's enforced 5-tag limit), favors niche/mid-tier tags over generic mega-tags, and designs branded/campaign hashtags for community and tracking. Rotates sets rather than copy-pasting one block, and hands placement/publishing to scheduling-and-queue. Sets honest expectations: hashtags categorize and aid search; they are not a reach hack.
Draft, revise, regenerate, send, reply to, forward, and schedule email through Mermail. Use when the main job is composing a message, saving or revising a draft, replying, forwarding, scheduling delivery, or approving an exact send. Do not use for ordinary inbox organization, verification-mail correlation, mailbox-agent chat, or task-triager configuration.
Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatically.
You Can Book Me integration. Manage data, records, and automate workflows. Use when the user wants to interact with You Can Book Me data.
OnceHub integration. Manage Leads, Persons, Organizations, Deals, Pipelines, Activities and more. Use when the user wants to interact with OnceHub data.