Loading...
Loading...
Found 247 Skills
Use to set a brand's overall social media strategy — which channels to focus on (and which to ignore), what to achieve, the angle to win, and a realistic operating cadence. The top-level plan that sits above content pillars and the calendar. Run when the user says "social strategy," "social media strategy," "which platforms should I be on," "what's my plan," "should I be on TikTok/LinkedIn," or is starting or resetting their social presence. Reads brand-profile, audience-research, and content-pillars first. Makes real choices and trade-offs — especially what NOT to do — ties goals to the business not vanity metrics, and is honest that WoopSocial has no analytics (measurement is the platforms' native analytics). Produces a social-strategy.md. It names the objective; to turn it into SMART targets, KPIs, and North Star metrics, use goals-and-kpis. Works for any business.
Plan and orchestrate a product launch or social media campaign end to end — the multi-week arc, channel by channel. Use when someone wants to plan a launch, product drop, campaign, big announcement, waitlist/pre-launch push, or coordinated multi-platform moment. Plans a time-boxed campaign as ONE story across three phases (tease -> launch -> sustain) toward a single goal, and schedules the coordinated social posts via WoopSocial. Uses the STORY framework. Reads brand-profile + goals-and-kpis first. WoopSocial schedules + publishes the social posts on the timeline; the waitlist/hub, email sequence, checkout, paid ads, press/creator outreach, and livestream are external/native, and conversion/ROI come from native analytics + the store (never fabricated). Urgency must be credible (no fake countdowns/scarcity). Distinct from content-calendar (the ongoing always-on cadence) and goals-and-kpis (the targets a campaign serves).
Anti-slop 3D for Blender. Use whenever building, editing, lighting, texturing, or rendering a Blender scene (bpy scripts, blender-mcp, .blend files, product shots, props, environments, stylized scenes) so the result looks authored by a 3D artist instead of AI/procedural-default. Triggers on Blender, bpy, 3D modeling, 3D render, lookdev, "make it look less CG / less fake / less AI". Not for game-engine shader code, CAD tolerancing, or 2D image generation.
/cs:execute <decision> — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.
Competitor analysis for social media — public-data competitive reconnaissance to find the gap a brand can own. Use when someone wants to "analyse/research our competitors," "see what rivals are doing on social," "benchmark against competitors," "find content gaps / white space," or "do a competitive landscape / SWOT." Reads the PUBLIC competitive field — positioning, pillars, formats, cadence, share of voice — to find the gap the brand can own, then feeds social-strategy and content-pillars. Reads brand-profile + audience-research first. Advisory and public-data only: no scraping private data, no fake monitoring accounts, no fabricated competitor metrics, no copying. Distinct from viral-reverse-engineering (single-post teardown) and audience-research (your own audience).
This skill should be used when the user asks to "create an index", "build a basket of top assets", "buy a weighted basket", "make a portfolio of assets", "equal-weight basket", "rebalance my portfolio", "track the top N tokens", or wants an automated, weighted multi-asset basket that buys in one pass and rebalances on a cadence. Builds the basket spec, delegates each buy and rebalance swap to the swap-integration Trading API flow, and records target weights in state.
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.
When the user wants to build or improve a sales bot's ability to adjust sequence timing based on engagement signals. Also use when the user mentions "drip pacing," "sequence timing," "adaptive sequences," "engagement-based timing," or "smart cadence."
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.
Dicta el veredicto de una unidad de trabajo cuando el TESTER y el DEV ya entregaron - corre las pruebas del TESTER contra el código del DEV, verifica punto por punto la Definition of Done con evidencia, comprueba que cada rol tocó solo sus rutas y decide a quién se devuelve cada rojo. Use when the LEAD has received both deliveries (ENTREGA TESTER and ENTREGA DEV) for a unit of work, or when asked to verify, judge, or give the verdict on a team delivery.
Escribe el contrato observable de una Historia de Usuario para que el TESTER y el DEV puedan trabajar al mismo tiempo sin verse - arma el paquete de contexto (HU + ADRs de historia + sección del Tech Design), define entrada, salida por caso, errores y nombres que no se negocian con el origen de cada línea, lista las decisiones que la HU no tomaba y se detiene para aprobación humana. Use when the LEAD takes a user story to build, or when asked to write, draft, or version the contract/spec of a user story.
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.