Loading...
Loading...
Found 1,037 Skills
The Facebook Groups strategy skill -- Groups as Facebook's real organic surface, deeper than what facebook-strategy routes to community-management. Use when someone wants to build/grow/run a Facebook Group, decide Group vs Page, or turn a community into leads. Groups reach 40-50% of members per post vs ~1.5% for Pages; Facebook deliberately favors Groups. Uses the TRIBE framework. Reads brand-profile + goals-and-kpis first. The agent designs the group strategy (niche, setup, content, growth, moderation, value-first monetization) and drafts group posts + the join-funnel content. CRUCIAL: WoopSocial does NOT post to Groups -- it publishes the Page + cross-channel content that funnels people to JOIN; in-group posting, admin, moderation, and Group analytics stay native/human, routed to community-management. No automation/spam or fake members; value-first, never fabricates metrics. Distinct from facebook-strategy (the Page play) and community-management (the engagement routine).
Installs and configures the Meta XR Simulator for testing Meta VR and Horizon OS apps without a physical device. Use when installing the simulator or integrating it with Unity, Unreal, or native OpenXR projects. For controlling a running simulator, use hz-xr-simulator-control. Build paths: Unity, Unreal, and native OpenXR; route Standard Android, Meta Spatial SDK, and WebXR work through hz-quest-verify-first.
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.
Use when producing game environments with Layer: background and environment concept art, a side-scroller parallax background split into scrolling layers, a 360 skybox or panorama, or a generated world. Also when parallax layers do not line up or loop, when a background is too busy to read gameplay against, or when exporting layers to Godot or Unity. Keywords: environment, background, parallax, layers, side-scroller, platformer, skybox, 360, equirectangular, panorama, world.
Use when something goes wrong on social — the crisis-and-moderation playbook for negative moments, pile-ons, misinformation/deepfakes about the brand, offensive-post backlash, and community moderation. Run when the user says "we're getting piled on," "someone's spreading false info about us," "should we delete/hide this," "a deepfake of our brand," or needs to moderate a community. Reads brand-profile/voice. Confirm facts and triage severity first; acknowledge fast; speak human, not legalese; correct misinformation with evidence, not an apology; moderate fairly (hide abuse, leave honest criticism). HIGH-STAKES and human-in-the-loop: a crisis is when the agent must NOT act autonomously — it triages, drafts holding statements, and can pause/reschedule posts via scheduling-and-queue, while a HUMAN (and legal/leadership for high-severity) approves everything and moderates in-platform. WoopSocial has no comment/inbox/moderation surface; never auto-respond or fabricate facts.
Deep-dive on a single opportunity - signal-adjusted health score, risks, gaps in qualification, and recommended next actions. Use when the user asks "review the [account] deal", "deal review on [opp]", "is [opp] going to close", or "what's the risk on [deal]".
Review a game for player impact, ethics, transformation, inclusion, monetization pressure, community risk, dark patterns, and hidden design agendas. Use before shipping manipulative loops, social systems, ads, monetization, retention mechanics, UGC, or player-generated communities.
Latest news articles, regulatory filings, community discussion topics for listed stocks, and SEC EDGAR filing analysis (10-K/10-Q/8-K/proxy/Form 4) via the stock data provider. Triggers: "新闻", "公告", "资讯", "话题", "社区讨论", "SEC", "10-K", "10-Q", "8-K", "Form 4", "新聞", "公告", "資訊", "話題", "社區討論", "news", "filing", "announcement", "topic", "community", "SEC filing", "annual report", "quarterly report", "proxy", "insider filing", "regulatory rules", "监管规则", "涨跌停", "漲跌停", "T+1", "PDT rule", "熔断", "熔斷", "circuit breaker", "margin rules", "保证金", "保證金", "監管規則"
Read-only audit of your CRM opportunities for missing fields, stale dates, and stage mismatches - outputs a fix checklist to apply by hand or through update-opportunity. Use when the user asks "check my CRM hygiene", "check my Salesforce or HubSpot data", "clean up my CRM", "audit my opps", "what's missing in the CRM", or "clean up my pipeline".
Forward-looking gap check on one opportunity - exactly what is missing to advance it to the next stage and to close, with who does what by when. Use when the user asks "what's missing to advance [deal]", "what do I need to move [opp] forward", "why is [deal] stuck", or "what's between [account] and a close".
Customer interview synthesis: raw transcripts to themed insights, an opportunity solution tree, and follow-up questions (Teresa Torres continuous discovery). Use for post-interview synthesis, opportunity mapping, and evidence gap analysis.
Decide who owns an unrouted lead or opportunity and manage the handoff - deterministic routing by the org's own rules, a routing card the human router accepts or overrides, and drafted handoff notes. Use when the user says "route this lead", "who should own [lead/opp]", "work the routing queue", "assign [company] to a rep", or on a scheduled intake sweep.