Loading...
Loading...
Found 247 Skills
This skill should be used when the user wants to "dca into" a token, "buy X every day", set up a "recurring buy", "dollar cost average" into an asset, "schedule a buy", or "auto-buy on a dip". Buys a fixed amount into a token on a schedule, optionally only when a condition holds (for example only when ETH is below a price threshold). The host agent's scheduler wakes the skill on a cadence; each wake is one self-contained run.
Design, review, prototype, measure, and troubleshoot electronic circuits using component evidence, worst-case calculations, interface contracts, and staged bench verification. Use for component selection, analog or digital building blocks, power and protection, sensor conditioning, schematic-to-wiring review, instrumented diagnosis, and I2C electrical integration. Do not use as a substitute for exact device documentation, ESP32 firmware operations, FPGA RTL development, named CAD-tool operation, or regulated design certification.
Client-facing red-team deliverable format — codifies the Subject / Observations / Description / Impact / Recommendation / PoC structure used for external red-team engagements (not bug-bounty platform reports). Different audience, different tone, different cadence. Built from an authorized engagement deliverable where 14 findings were packaged into a 52KB MD + 2.2MB DOCX with 16 embedded screenshots. Use when the engagement is "external red team for an enterprise client" (not H1/Bugcrowd/Intigriti), when generating the final report, when the client has specified a custom report format, or when packaging findings into DOCX/PDF.
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.
The Threads account-growth strategy skill -- the channel layer above threads-post. Use when someone wants to grow a Threads account, understand the Threads algorithm, fix reach, plan cadence, or set a Threads strategy. Threads is conversation-first, and the #1 growth lever is Mosseri's "reply more than you post": replies are weighted heaviest and first-hour engagement velocity is the top ranking factor. Uses the TALKS framework. Reads brand-profile + goals-and-kpis first. The agent strategizes the channel + drafts original posts (published via WoopSocial) and suggested replies; BUT the reply flywheel is human/community-management (no reply surface in WoopSocial), and Communities/DMs/dashboards/analytics are native. No engagement-bait, original not recycled, positive tone, metrics never fabricated, growth compounds over 60-90 days. Distinct from threads-post (the single-post craft) and community-management (the reply execution); uses Threads as a discovery funnel into instagram-growth.
Constrói uma base de conhecimento (KB) que a IA consegue consultar de verdade: organiza o que você sabe sobre um domínio em conceitos (para entender) e receitas (para fazer), com porta de entrada, consulta rápida e limites de tamanho que mantêm o material utilizável. Cria o índice do projeto na primeira vez e registra cada domínio novo. Recomendada antes de iniciar um fluxo SDD, para as fases seguintes partirem do terreno já mapeado. A revisão do conteúdo é sempre do profissional — a IA organiza e redige, mas quem responde pelo que fica registrado é quem tem a responsabilidade técnica. Use quando o usuário quiser ensinar seu contexto à IA, catalogar leis, normas, manuais, instruções ou políticas internas, documentar um processo, ou reclamar que precisa reexplicar as mesmas coisas em toda conversa.
Produce 3D assets with Meshy (meshy.ai) through its REST API and web platform — text-to-3D, image-to-3D, multi-image-to-3D, AI texturing/PBR, remesh/topology control, UV, and auto-rigging/animation. Use this skill when an agent must generate a mesh from a prompt or reference image, control polygon count and topology, apply or restyle textures, rig a humanoid for animation, export to GLB/FBX/OBJ/USDZ/STL for Unity/Unreal/Blender, drive Meshy's asynchronous job API (auth, polling, streaming, webhooks, credits, rate limits), review generated meshes for game/film/print readiness, or decide whether Meshy is the right tool at all. Not for editing an existing hand-modeled asset's geometry, hard-surface CAD with exact dimensions, or guaranteed-watertight manufacturing parts.
This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation. NOT for outline-first drafting, or mysteries and other clue-dependent genres where setup must come before payoff (use chapter-writing), or a reverse outline of an existing linear draft, a subplot cut, or another revision pass on existing chapters (use revision-continuity).
Workspace Things: Use `ae-cli things` to create, query, update, and advance things in an explicitly specified AgentSpace. Proactively use this whenever a conversation contains work assignments (who is responsible for what), expected deliverables, execution cadence, to-dos, next steps, milestones, or phased plans—there is no need for the user to explicitly say “create a thing.”
When the user wants to create or optimize a sales outreach sequence, follow-up cadence, or prospecting campaign. Also use when the user mentions "outreach sequence," "follow-up cadence," "prospecting campaign," "drip sequence," "touch pattern," or "outbound sequence." For individual email writing, see copywriting.
The audio-to-social pipeline skill -- turn a podcast episode into short, branded, captioned clips and audiograms that drive people back to the full episode. Use when someone wants to repurpose a podcast, make podcast clips, create audiograms, or promote an episode on social. Uses the WAVES framework. Reads brand-profile + the episode first. Select clips by listener-retention data + timestamped transcript, not just an AI virality score, plus a strategic CTA back to the episode. The agent plans the clip strategy, briefs the clip/audiogram creation, plans the cadence, and writes hooks/CTAs; a clip or audiogram tool produces the clips; the creator finalizes; WoopSocial publishes on a schedule and does NOT record/edit/transcribe the podcast, generate clips, or host it. Captions are non-optional (85% sound-off). Never fabricates virality or clips someone's copyrighted podcast. Distinct from captions-and-clipping, content-recycling, and youtube-long-form.
Classifica comentários de Instagram e escreve a resposta pública e a DM de cada um. Use quando a pessoa colar ou exportar comentários de um post ou reel, pedir "responde esses comentários", "quem pediu o material", "monta as DMs", ou usar uma palavra-chave de isca (como "comenta GUIA"). Identifica a intenção (pediu o material, dúvida, elogio, objeção, hater, spam) e entrega tudo em tabela e CSV prontos para copiar. A skill escreve as respostas; ela não envia nada sozinha.