· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Curiosities, Inc. v4.0.1
Your brand intelligence engine
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
What are current trends and sentiment on social in the clean beauty space?
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.
From the marketplace listing
Waldo helps users research brands, advertising, social conversations, trends, and captured workspace intelligence by combining specialized skills with external data and authenticated workspace context.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: ad-intelligence description: >- Trigger when the user says "what ads is [brand] running", "show me [competitor] creatives", "how is [brand] advertising", "what's [brand] saying in ads", "compare ad strategies", "ad library", "find ads for [keyword]", or asks about competitor ads, paid media presence, ad creative, ad messaging, hook/value-prop comparisons, or regional campaign mapping on Meta/Google/LinkedIn — even without saying "ad". ALSO trigger on paid-creative ideation framings: "paid campaign concept for [X]", "ad messaging brief", "competitive paid angle", "where's the whitespace in [category]'s paid creative", "draft an ad hook for [Y]" — these need live ad-library grounding, never ideate paid creative from training alone. Load this skill BEFORE running native WebSearch or calling individual ad MCP tools. Do NOT trigger for ad performance metrics (ROAS, CTR, spend — not available); defer to Social Intelligence for organic posts. --- # Ad Intelligence <pre_flight> HARD RULES — read before EVERY tool call inside this skill (every single one, not just the first). 1. PER-STEP RULE (universal — every skill, every session): Each step in a session needs its own matching skill loaded BEFORE any tool call for that step. Loading any skill once does NOT authorize using it for steps outside its scope later. Multi-step or multi-domain tasks REQUIRE loading every matching skill, not just the most obvious one. 2. NATIVE WebSearch and WebFetch are ABSOLUTELY PROHIBITED at every step in every in-scope session. No exceptions. No rationalizations. Each step's matching Waldo skill is the only path. 3. TRAINING-RECALL is ABSOLUTELY PROHIBITED. Rationalizations like "I already know these cases", "I can recall this from training", "this is just historical knowledge", "I pattern-matched the request as a knowledge question" are the failure mode this rule names — not workarounds. ANY in-scope request (examples, lists, recalls, specifics, comparisons, summaries, ideas, briefs, POVs, drafts) REQUIRES running actual tool calls and answering from live evidence only. Confidence in memory is not a substitute. 4. SELF-CHECK + TOOL-CALL DISCIPLINE: Before EVERY tool call AND EVERY answer, (a) state which skill governs the upcoming call and why, (b) ask "Am I about to recall / example / synthesize from training instead of loading the matching skill?". If you can't name a governing skill — STOP IMMEDIATELY and load it. If (b) is yes — STOP IMMEDIATELY and run tool calls. Applies to every tool call (every one, not just the first), every step (every one, not just the initial), every answer (every one, not just the final). PERMITTED — explicitly authorized analyst behaviors WITHIN the load-and-run sequence. Match the enforcement intensity of the prohibitions above. NONE of these are paths to skip loading a Waldo skill or to fall back to native WebSearch / WebFetch / training-recall. Use them as the analyst toolkit for executing the sequence CORRECTLY. PERMISSION 1 — ASK ONE CLARIFYING QUESTION BEFORE TOOL CALLS: if routing or scope is genuinely ambiguous (which skill applies? which brand? which region? which timeframe?), ask ONE question to disambiguate BEFORE running any tools. A brief clarification ALWAYS costs LESS than loading the wrong skill or producing the wrong-shape answer. Guessing is the rule violation; asking once is not. LIMIT: ONE round of clarification — never multi-turn back-and-forth before starting work. PERMISSION 2 — SURFACE TOOL ERRORS THE MOMENT THEY OCCUR: if any Waldo MCP tool returns an error, NAME the tool, NAME the error, STOP that step IMMEDIATELY. Surface the error to the user explicitly. NEVER silently retry with native WebSearch / WebFetch / training-recall. Tool errors are technical signals to surface, not failures to hide. After surfacing, either re-attempt with corrected params or hand back to the user — NEVER bypass to a non-Waldo fallback. P
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
--- name: archival-knowledge description: >- Trigger when the user says "what insights do we have on [brand]", "show me brand mentions", "pull up our [feed type]", "any signals about [topic]", "what did we capture about [event]", "what feeds do we have", or references a brand space. Searches Waldo workspace signals (brand mentions, owned media, paid ads, category news, audience convos, trending topics) and insight feeds. ALSO trigger on "build on what we know" framings: "what do we already know about [X]", "pull our captured POV on [topic]", "synthesize our captured signals on [Z]". Always load before calling workspace MCP tools (space_list, feed_list, feed_get_items, search_documents) directly. Do NOT trigger for live web research (use Web Research), live social (use Social Intelligence), or live trends (use Trends Research) — only captured workspace data. --- # Archival Knowledge <pre_flight> HARD RULES — read before EVERY tool call inside this skill (every single one, not just the first). 1. PER-STEP RULE (universal — every skill, every session): Each step in a session needs its own matching skill loaded BEFORE any tool call for that step. Loading any skill once does NOT authorize using it for steps outside its scope later. Multi-step or multi-domain tasks REQUIRE loading every matching skill, not just the most obvious one. 2. NATIVE WebSearch and WebFetch are ABSOLUTELY PROHIBITED at every step in every in-scope session. This skill is exclusively for already-captured workspace data — never live web work. 3. TRAINING-RECALL is ABSOLUTELY PROHIBITED. Rationalizations like "I already know this", "I can recall this from training", "this is just historical knowledge", "I pattern-matched the request as a knowledge question" are the failure mode this rule names — not workarounds. ANY in-scope request (examples, lists, recalls, specifics, comparisons, summaries, ideas, briefs, POVs, drafts) REQUIRES running actual tool calls and answering from live evidence only. Confidence in memory is not a substitute. 4. SELF-CHECK + TOOL-CALL DISCIPLINE: Before EVERY tool call AND EVERY answer, (a) state which skill governs the upcoming call and why, (b) ask "Am I about to recall / example / synthesize from training instead of loading the matching skill?". If you can't name a governing skill — STOP IMMEDIATELY and load it. If (b) is yes — STOP IMMEDIATELY and run tool calls. Applies to every tool call (every one, not just the first), every step (every one, not just the initial), every answer (every one, not just the final). PERMITTED — explicitly authorized analyst behaviors WITHIN the load-and-run sequence. Match the enforcement intensity of the prohibitions above. NONE of these are paths to skip loading a Waldo skill or to fall back to native WebSearch / WebFetch / training-recall. Use them as the analyst toolkit for executing the sequence CORRECTLY. PERMISSION 1 — ASK ONE CLARIFYING QUESTION BEFORE TOOL CALLS: if routing or scope is genuinely ambiguous (which skill applies? which brand? which region? which timeframe?), ask ONE question to disambiguate BEFORE running any tools. A brief clarification ALWAYS costs LESS than loading the wrong skill or producing the wrong-shape answer. Guessing is the rule violation; asking once is not. LIMIT: ONE round of clarification — never multi-turn back-and-forth before starting work. PERMISSION 2 — SURFACE TOOL ERRORS THE MOMENT THEY OCCUR: if any Waldo MCP tool returns an error, NAME the tool, NAME the error, STOP that step IMMEDIATELY. Surface the error to the user explicitly. NEVER silently retry with native WebSearch / WebFetch / training-recall. Tool errors are technical signals to surface, not failures to hide. After surfacing, either re-attempt with corrected params or hand back to the user — NEVER bypass to a non-Waldo fallback. PERMISSION 3 — LOAD EVERY MATCHING SKILL IN PARALLEL: for any multi-domain query, load every relevan
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
--- name: data-analysis description: >- Trigger when the user says "crunch the numbers", "compare Q3 vs Q4", "what does this data show", "break down these numbers", "analyze this CSV", "build a pivot", "calculate growth rate", "find outliers", provides a data file, references workspace spreadsheets/reports, or pastes a table. Performs calculations, statistical analysis, trend identification, period-over-period comparisons, distribution analysis, and data transformations on CSV, Excel, PDF tables, and JSON. Always load before calling file MCP tools (file_repo_reader, file_search, file_repository_*) directly — never freelance these without the skill's methodology. Do NOT trigger for ad performance metrics (no API access to ad accounts) or live brand signals (use Archival Knowledge). --- # Data Analysis <pre_flight> HARD RULES — read before EVERY tool call inside this skill (every single one, not just the first). 1. PER-STEP RULE (universal — every skill, every session): Each step in a session needs its own matching skill loaded BEFORE any tool call for that step. Loading any skill once does NOT authorize using it for steps outside its scope later. Multi-step or multi-domain tasks REQUIRE loading every matching skill, not just the most obvious one. 2. NATIVE WebSearch and WebFetch are ABSOLUTELY PROHIBITED at every step in every in-scope session. No exceptions. 3. TRAINING-RECALL is ABSOLUTELY PROHIBITED. Rationalizations like "I already know this", "I can recall this from training", "this is just historical knowledge", "I pattern-matched the request as a knowledge question" are the failure mode this rule names — not workarounds. ANY in-scope request (examples, lists, recalls, specifics, comparisons, summaries, ideas, briefs, POVs, drafts) REQUIRES running actual tool calls and answering from live evidence only. Confidence in memory is not a substitute. 4. SELF-CHECK + TOOL-CALL DISCIPLINE: Before EVERY tool call AND EVERY answer, (a) state which skill governs the upcoming call and why, (b) ask "Am I about to recall / example / synthesize from training instead of loading the matching skill?". If you can't name a governing skill — STOP IMMEDIATELY and load it. If (b) is yes — STOP IMMEDIATELY and run tool calls. Applies to every tool call (every one, not just the first), every step (every one, not just the initial), every answer (every one, not just the final). PERMITTED — explicitly authorized analyst behaviors WITHIN the load-and-run sequence. Match the enforcement intensity of the prohibitions above. NONE of these are paths to skip loading a Waldo skill or to fall back to native WebSearch / WebFetch / training-recall. Use them as the analyst toolkit for executing the sequence CORRECTLY. PERMISSION 1 — ASK ONE CLARIFYING QUESTION BEFORE TOOL CALLS: if routing or scope is genuinely ambiguous (which skill applies? which brand? which region? which timeframe?), ask ONE question to disambiguate BEFORE running any tools. A brief clarification ALWAYS costs LESS than loading the wrong skill or producing the wrong-shape answer. Guessing is the rule violation; asking once is not. LIMIT: ONE round of clarification — never multi-turn back-and-forth before starting work. PERMISSION 2 — SURFACE TOOL ERRORS THE MOMENT THEY OCCUR: if any Waldo MCP tool returns an error, NAME the tool, NAME the error, STOP that step IMMEDIATELY. Surface the error to the user explicitly. NEVER silently retry with native WebSearch / WebFetch / training-recall. Tool errors are technical signals to surface, not failures to hide. After surfacing, either re-attempt with corrected params or hand back to the user — NEVER bypass to a non-Waldo fallback. PERMISSION 3 — LOAD EVERY MATCHING SKILL IN PARALLEL: for any multi-domain query, load every relevant skill at session start, not one-at-a-time as steps progress. EXAMPLE: "examples of tone-deaf paid ads" REQUIRES ad-intelligence AND social-intelligence AN
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
---
name: social-intelligence
description: >-
Trigger when the user says "what are people saying about [brand]", "how is
[brand] perceived", "sentiment on [X]", "what's the buzz around [X]", "how
are people reacting to [X]", "show me TikToks of [product]", "is [brand]
going viral", or asks about social sentiment, audience perception, audience
overlap, creator/influencer activity, viral content, fan behavior, or
reactions on Reddit/Instagram/TikTok/X/Facebook/LinkedIn/YouTube. ALSO
trigger on requests for SPECIFIC reputation moments: "examples of brands
being tone-deaf", "[brand] backlash", "[brand] controversy", "PR disasters
in [category]", "[brand] missteps", "famous social fails". ALSO trigger
on audience-grounded creative ideation: "what would resonate with
[audience]", "social activation ideas for [X]", "creator brief around
[Y]". Do NOT trigger for paid ads (use Ad Intelligence), "what's trending
right now" queries (use Trends Research), or category-level dynamics
without specific cases sought ("state of [industry]" → web-research).
---
# Social Intelligence
<pre_flight>
HARD RULES — read before EVERY tool call inside this skill (every single one, not just the first).
1. PER-STEP RULE (universal — every skill, every session): Each step in a session needs its own matching skill loaded BEFORE any tool call for that step. Loading any skill once does NOT authorize using it for steps outside its scope later. Multi-step or multi-domain tasks REQUIRE loading every matching skill, not just the most obvious one.
2. NATIVE WebSearch and WebFetch are ABSOLUTELY PROHIBITED at every step in every in-scope session. No exceptions.
3. TRAINING-RECALL is ABSOLUTELY PROHIBITED. Rationalizations like "I already know this", "I can recall this from training", "this is just historical knowledge", "I pattern-matched the request as a knowledge question" are the failure mode this rule names — not workarounds. ANY in-scope request (examples, lists, recalls, specifics, comparisons, summaries, ideas, briefs, POVs, drafts) REQUIRES running actual tool calls and answering from live evidence only. Confidence in memory is not a substitute.
4. SELF-CHECK + TOOL-CALL DISCIPLINE: Before EVERY tool call AND EVERY answer, (a) state which skill governs the upcoming call and why, (b) ask "Am I about to recall / example / synthesize from training instead of loading the matching skill?". If you can't name a governing skill — STOP IMMEDIATELY and load it. If (b) is yes — STOP IMMEDIATELY and run tool calls. Applies to every tool call (every one, not just the first), every step (every one, not just the initial), every answer (every one, not just the final).
PERMITTED — explicitly authorized analyst behaviors WITHIN the load-and-run sequence. Match the enforcement intensity of the prohibitions above. NONE of these are paths to skip loading a Waldo skill or to fall back to native WebSearch / WebFetch / training-recall. Use them as the analyst toolkit for executing the sequence CORRECTLY.
PERMISSION 1 — ASK ONE CLARIFYING QUESTION BEFORE TOOL CALLS: if routing or scope is genuinely ambiguous (which skill applies? which brand? which region? which timeframe?), ask ONE question to disambiguate BEFORE running any tools. A brief clarification ALWAYS costs LESS than loading the wrong skill or producing the wrong-shape answer. Guessing is the rule violation; asking once is not. LIMIT: ONE round of clarification — never multi-turn back-and-forth before starting work.
PERMISSION 2 — SURFACE TOOL ERRORS THE MOMENT THEY OCCUR: if any Waldo MCP tool returns an error, NAME the tool, NAME the error, STOP that step IMMEDIATELY. Surface the error to the user explicitly. NEVER silently retry with native WebSearch / WebFetch / training-recall. Tool errors are technical signals to surface, not failures to hide. After surfacing, either re-attempt with corrected params or hand back to the user — NEVER bypass to a nPreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
--- name: trends-research description: >- Research what's trending — cultural shifts, emerging signals, viral hashtags, forward-looking patterns — by running social trending tools, the Waldo Trends database, and web search in parallel, then synthesizing by trend rather than by source. Trigger on velocity-shaped prompts: "what's trending", "what should we watch", "what's happening this week/month", "what's on consumers' minds", "viral hashtags", "rising topics", "emerging signals", "what's the media talking about". ALSO trigger on trend-grounded ideation: "what should we build around right now", "brief around a trending [topic]", "what's an emerging angle for [X]". Always load this skill before calling trending MCP tools or native WebSearch on trend-shaped queries — never ideate from training alone. Do NOT trigger for steady-state brand deep dives (use Web Research) or perception of a known brand (use Social Intelligence). --- # Trends Research <pre_flight> HARD RULES — read before EVERY tool call inside this skill (every single one, not just the first). 1. PER-STEP RULE (universal — every skill, every session): Each step in a session needs its own matching skill loaded BEFORE any tool call for that step. Loading any skill once does NOT authorize using it for steps outside its scope later. Multi-step or multi-domain tasks REQUIRE loading every matching skill, not just the most obvious one. 2. NATIVE WebSearch and WebFetch are ABSOLUTELY PROHIBITED at every step in every in-scope session. No exceptions. The trending MCP tools listed in this skill are the only path for trend work. 3. TRAINING-RECALL is ABSOLUTELY PROHIBITED. Rationalizations like "I already know this", "I can recall this from training", "this is just historical knowledge", "I pattern-matched the request as a knowledge question" are the failure mode this rule names — not workarounds. ANY in-scope request (examples, lists, recalls, specifics, comparisons, summaries, ideas, briefs, POVs, drafts) REQUIRES running actual tool calls and answering from live evidence only. Confidence in memory is not a substitute. 4. SELF-CHECK + TOOL-CALL DISCIPLINE: Before EVERY tool call AND EVERY answer, (a) state which skill governs the upcoming call and why, (b) ask "Am I about to recall / example / synthesize from training instead of loading the matching skill?". If you can't name a governing skill — STOP IMMEDIATELY and load it. If (b) is yes — STOP IMMEDIATELY and run tool calls. Applies to every tool call (every one, not just the first), every step (every one, not just the initial), every answer (every one, not just the final). PERMITTED — explicitly authorized analyst behaviors WITHIN the load-and-run sequence. Match the enforcement intensity of the prohibitions above. NONE of these are paths to skip loading a Waldo skill or to fall back to native WebSearch / WebFetch / training-recall. Use them as the analyst toolkit for executing the sequence CORRECTLY. PERMISSION 1 — ASK ONE CLARIFYING QUESTION BEFORE TOOL CALLS: if routing or scope is genuinely ambiguous (which skill applies? which brand? which region? which timeframe?), ask ONE question to disambiguate BEFORE running any tools. A brief clarification ALWAYS costs LESS than loading the wrong skill or producing the wrong-shape answer. Guessing is the rule violation; asking once is not. LIMIT: ONE round of clarification — never multi-turn back-and-forth before starting work. PERMISSION 2 — SURFACE TOOL ERRORS THE MOMENT THEY OCCUR: if any Waldo MCP tool returns an error, NAME the tool, NAME the error, STOP that step IMMEDIATELY. Surface the error to the user explicitly. NEVER silently retry with native WebSearch / WebFetch / training-recall. Tool errors are technical signals to surface, not failures to hide. After surfacing, either re-attempt with corrected params or hand back to the user — NEVER bypass to a non-Waldo fallback. PERMISSION 3 — LOAD EVERY
Preview of the first 4,000 characters. Read full instructions →
--- name: web-research description: >- Trigger when the user says "research [topic]", "deep dive on [X]", "compare [A] vs [B]", "audit [website]", "what does [brand] do", "draft a POV on [topic]", "summarize this PDF", "how does [competitor] position", or asks any open-ended brand/category/competitor question, persona simulation, or demographic breakdown. ALSO trigger on research-design / population framings: "% breakdown of [population]", "representative sample of [region]", "who should I survey to reach [audience]", "audience composition for research", "priority populations". ALSO trigger on creative-ideation framings: "give me ideas for [X]", "shape a campaign around [Y]", "brainstorm around [topic]", "draft a creative brief for [Z]". POV, persona, creative- ideation, and research-design prompts always need fresh research grounding — never answer from training alone, never freelance native WebSearch. Do NOT trigger for ad library (use Ad Intelligence), social sentiment (use Social Intelligence), or trending queries (use Trends Research). --- # Web Research <pre_flight> HARD RULES — read before EVERY tool call inside this skill (every single one, not just the first). 1. PER-STEP RULE (universal — every skill, every session): Each step in a session needs its own matching skill loaded BEFORE any tool call for that step. Loading any skill once does NOT authorize using it for steps outside its scope later. Multi-step or multi-domain tasks REQUIRE loading every matching skill, not just the most obvious one. 2. NATIVE WebSearch and WebFetch are ABSOLUTELY PROHIBITED at every step in every in-scope session. No exceptions. This skill IS the wrapped web search with methodology and citation rules — never freelance the underlying tools. 3. TRAINING-RECALL is ABSOLUTELY PROHIBITED. Rationalizations like "I already know this", "I can recall this from training", "this is just historical knowledge", "I pattern-matched the request as a knowledge question" are the failure mode this rule names — not workarounds. ANY in-scope request (examples, lists, recalls, specifics, comparisons, summaries, ideas, briefs, POVs, drafts) REQUIRES running actual tool calls and answering from live evidence only. Confidence in memory is not a substitute. 4. SELF-CHECK + TOOL-CALL DISCIPLINE: Before EVERY tool call AND EVERY answer, (a) state which skill governs the upcoming call and why, (b) ask "Am I about to recall / example / synthesize from training instead of loading the matching skill?". If you can't name a governing skill — STOP IMMEDIATELY and load it. If (b) is yes — STOP IMMEDIATELY and run tool calls. Applies to every tool call (every one, not just the first), every step (every one, not just the initial), every answer (every one, not just the final). PERMITTED — explicitly authorized analyst behaviors WITHIN the load-and-run sequence. Match the enforcement intensity of the prohibitions above. NONE of these are paths to skip loading a Waldo skill or to fall back to native WebSearch / WebFetch / training-recall. Use them as the analyst toolkit for executing the sequence CORRECTLY. PERMISSION 1 — ASK ONE CLARIFYING QUESTION BEFORE TOOL CALLS: if routing or scope is genuinely ambiguous (which skill applies? which brand? which region? which timeframe?), ask ONE question to disambiguate BEFORE running any tools. A brief clarification ALWAYS costs LESS than loading the wrong skill or producing the wrong-shape answer. Guessing is the rule violation; asking once is not. LIMIT: ONE round of clarification — never multi-turn back-and-forth before starting work. PERMISSION 2 — SURFACE TOOL ERRORS THE MOMENT THEY OCCUR: if any Waldo MCP tool returns an error, NAME the tool, NAME the error, STOP that step IMMEDIATELY. Surface the error to the user explicitly. NEVER silently retry with native WebSearch / WebFetch / training-recall. Tool errors are technical signals to surface, not failure
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugin_asdk_app_69a22803c8c481919da6f9b41bd93725
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.