Loading...
Loading...
Found 523 Skills
Analyze complex systems from elements to relationships, from parts to the whole, and from static to dynamic perspectives. Suitable for scenarios where problems recur, where a single change affects the entire system, and where treating symptoms doesn't work. When you find that 'the harder you work, the worse it gets' or 'problems keep recurring', you need to switch to systematic thinking to find root solutions. Not applicable to simple single-cause problems or emergency scenarios requiring quick action. Key trigger signals: 'Why does this problem keep recurring?', 'Fixing A broke B instead', 'Feeling stuck in a loop'.
This skill is activated when users need to choose their own action rhythm based on the status of competitors. Typical trigger signals: Unsure whether to attack or defend against a strong competitor, being led by the competitor's rhythm, always one step behind in passive response. Scenarios where it is not called: Blue ocean markets with no clear competitors, stable competitive situations that do not require rhythm adjustments, users need strategic planning rather than action rhythm. Difference from the "Asymmetric Strategy" skill: This skill solves the problem of "whether to attack or defend at this moment" (rhythm level), while the latter solves the problem of "what paradigm to use for competition" (strategic level).
When the user wants to optimize for entity recognition, Knowledge Graph, or entity-based SEO. Also use when the user mentions "entity SEO," "entity optimization," "Knowledge Graph," "Knowledge Panel," "entity signals," "brand entity," "entity linking," "entity relationships," or "entity-first content."
Collect maker leads from Product Hunt — maker name, products, profile URL, website, contact signals. Use when the user wants to prospect active makers in the Product Hunt community.
Search for business contact signals on Instagram — username, bio email, website, category, phone. Use when the user wants to find contact information for business accounts on Instagram.
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".
Use to reverse-engineer why a piece of content went viral (or overperformed) — yours or someone else's — and extract the repeatable mechanism to apply to your own content. Run when the user says "why did this go viral," "break down this viral post/video," "reverse engineer," "what made this work," or wants to learn from viral content. Sources the observable signal first (intake, transcript, screenshots, top comments, visible stats — an agent usually can't watch a video from a link) and never fabricates what it can't see. Reads brand-profile and audience first, deconstructs the piece layer by layer, isolates the real driver, runs a replicability check, extracts the transferable principle, and applies it to the user's niche via the content skills. Mechanism, never a copy; flags non-replicable virality; visible signals only (no WoopSocial analytics). Single-POST teardown only: for the account-level competitive landscape use competitor-analysis; for riding a live trend use trend-jacking.
Generate enriched lead lists using Exa Agent. Finds companies matching an ICP, enriches with signals/news/scores, and outputs CSV. Use when generating leads, building prospect lists, finding companies to sell to, doing outbound research, or ICP-based company discovery. Triggers on "leads", "lead gen", "prospect list", "find companies", "ICP", "outbound list".
Finish the GitHub pull request attached to the current branch; resolve merge conflicts, diagnose and fix failed CI checks, action review feedback from every source without duplicating replies that are awaiting a reviewer response, push focused commits, and continue through Gitar review until its current-HEAD Core signals show a completed clean review. Use whenever the user asks to finish, complete, ready, resolve, fix, or address feedback/CI/conflicts on the current PR.
Investigate a topic across papers, articles, social-media posts, and industry signals, then deliver an indexed Markdown report. Use when the user asks to investigate, survey, gather sources, build an index, collect evidence, round up references, or otherwise wants a thorough cross-source roundup on a specific topic. Depends on documenting-with-sources and writing-quotation.
The idea-system craft — never run out of content ideas by running a system instead of waiting for inspiration. Use when someone is out of ideas, stares at a blank calendar, asks where good ideas come from, wants an idea bank/backlog, feels their AI-generated ideas sound like everyone else's, or thinks their niche is "boring." Uses the SPARK framework. Reads brand-profile + social-strategy + content-pillars + audience-research first. The audience is the idea engine (comments/DMs/FAQs clustered into themes); AI expands real signals, it doesn't discover them; systems beat muses; trends are a timing filter, not a source. The agent clusters/expands/scores; the HUMAN supplies proprietary signals and decides; WoopSocial publishes the content, not ideas. Never rewords competitor posts, invents audience questions, or fabricates probe results. Distinct from social-strategy/content-pillars, audience-research, cross-platform-repurposing/ content-recycling, and the format skills.
Review AI-generated or human-written code changes with fallow's graph-grounded review brief. Subtracts deterministic concerns (unused code, complexity, duplication, styling) from the loop, ranks what to look at by blast radius and risk, and surfaces the few consequential structural decisions (new public-API contracts, coupling/boundary crossings, new dependencies) as framed judgment questions anchored to verifiable signals. Drives a closed agent-contract loop: fetch the walkthrough guide, return a judgment, and have fallow post-validate it against the live graph (hallucinated or stale judgments are rejected). Use when asked to review a PR, review a branch, review a diff, do a code review, or check changed code before merge.