@anysiteio/agent-skills 1.3.0 → 2.0.0

package/skills/anysite-mcp-migration/SKILL.md

@@ -0,0 +1,290 @@
+---
+name: anysite-mcp-migration
+description: Migrate anysite MCP skills, prompts, and agent instructions from v1 (individual tools like search_linkedin_users, get_linkedin_profile) to v2 (universal meta-tools execute, discover, get_page, query_cache, export_data). Automatically rewrites tool references, adds pagination/filtering/export capabilities, and validates migrated output. Use when users need to update existing skills or prompts for the new anysite MCP v2 API, convert old tool calls to execute() format, or adapt workflows to use new v2 features like server-side filtering and data export.
+---
+
+# anysite MCP Migration Assistant
+
+Migrate your anysite MCP skills, prompts, and agent instructions from v1 (individual tools) to v2 (universal meta-tools).
+
+## Overview
+
+Anysite MCP v2 replaces 70+ individual tools with 5 universal meta-tools. This skill helps you:
+- **Rewrite tool references** from old format (`search_linkedin_users`, `get_linkedin_profile`) to new `execute()` calls
+- **Add new v2 capabilities** like pagination, server-side filtering, aggregation, and file export
+- **Validate migrated output** to ensure nothing was missed
+- **Preserve workflow logic** while updating only the tool interface layer
+
+## When to Use
+
+- User says "migrate my skill to v2", "update for new anysite API", "convert to execute format"
+- User pastes a skill or prompt that contains old-style tool names (`search_*`, `get_*`, `find_*`)
+- User asks how to use new anysite MCP features (pagination, cache queries, export)
+
+---
+
+## Migration Workflow
+
+### Step 1: Receive Input
+
+Ask the user for one of:
+1. **A skill file path** — read the SKILL.md and any files in `references/`
+2. **Pasted prompt text** — the raw text of their prompt or instruction
+3. **A description** of what the skill does — you'll help build it from scratch using v2 format
+
+### Step 2: Identify Old Tool References
+
+Scan the input for any of these v1 tool name patterns:
+
+| Pattern | Example |
+|---------|---------|
+| `search_linkedin_*` | `search_linkedin_users`, `search_linkedin_companies`, `search_linkedin_jobs`, `search_linkedin_posts` |
+| `get_linkedin_*` | `get_linkedin_profile`, `get_linkedin_company`, `get_linkedin_user_posts` |
+| `find_linkedin_*` | `find_linkedin_email`, `find_linkedin_user_email` |
+| `google_linkedin_*` | `google_linkedin_search` |
+| `search_twitter_*` / `get_twitter_*` | `search_twitter_users`, `get_twitter_user`, `get_twitter_user_tweets` |
+| `search_instagram_*` / `get_instagram_*` | `search_instagram_users`, `get_instagram_user`, `get_instagram_post` |
+| `search_youtube_*` / `get_youtube_*` | `search_youtube`, `get_youtube_channel`, `get_youtube_video` |
+| `search_reddit_*` / `get_reddit_*` | `search_reddit`, `get_reddit_user`, `get_reddit_posts` |
+| `search_yc_*` / `get_yc_*` | `search_yc_companies`, `get_yc_company` |
+| `search_sec_*` / `get_sec_*` | `search_sec_filings`, `get_sec_document` |
+| `scrape_webpage` | `scrape_webpage` |
+| `mcp__anysite__*` | Any tool with the MCP prefix — strip prefix and match above |
+
+Also look for references to **Crunchbase** — this source is disabled in v2 and must be removed.
+
+### Step 3: Apply Tool Mapping
+
+Replace each old tool call using this mapping:
+
+#### LinkedIn
+
+| Old tool | New execute() call |
+|----------|-------------------|
+| `search_linkedin_users(keywords, location, count, ...)` | `execute("linkedin", "search", "search_users", {"keywords": ..., "location": ..., "count": ...})` |
+| `get_linkedin_profile(user)` | `execute("linkedin", "user", "get", {"user": ...})` |
+| `get_linkedin_company(company)` | `execute("linkedin", "company", "get", {"company": ...})` |
+| `search_linkedin_companies(keywords, count)` | `execute("linkedin", "search", "search_companies", {"keywords": ..., "count": ...})` |
+| `search_linkedin_jobs(keywords, location, count)` | `execute("linkedin", "job_search", "search_jobs", {"keywords": ..., "count": ...})` |
+| `search_linkedin_posts(keywords, count)` | `execute("linkedin", "post", "search_posts", {"keywords": ..., "count": ...})` |
+| `get_linkedin_user_posts(user)` | `execute("linkedin", "post", "get_user_posts", {"user": ...})` |
+| `find_linkedin_email(user)` | `execute("linkedin", "email", "find", {"user": ...})` |
+| `google_linkedin_search(query, count)` | `execute("linkedin", "google", "search", {"query": ..., "count": ...})` |
+
+#### Twitter/X
+
+| Old tool | New execute() call |
+|----------|-------------------|
+| `search_twitter_users(query)` | `execute("twitter", "search", "search_users", {"query": ...})` |
+| `get_twitter_user(username)` | `execute("twitter", "user", "get", {"username": ...})` |
+| `get_twitter_user_tweets(username)` | `execute("twitter", "user_tweets", "get", {"username": ...})` |
+
+#### Instagram
+
+| Old tool | New execute() call |
+|----------|-------------------|
+| `search_instagram_users(query)` | `execute("instagram", "search", "search_users", {"query": ...})` |
+| `get_instagram_user(username)` | `execute("instagram", "user", "get", {"username": ...})` |
+| `get_instagram_post(url)` | `execute("instagram", "post", "get", {"url": ...})` |
+
+#### YouTube
+
+| Old tool | New execute() call |
+|----------|-------------------|
+| `search_youtube(query, count)` | `execute("youtube", "search", "search_videos", {"query": ..., "count": ...})` |
+| `get_youtube_channel(channel_id)` | `execute("youtube", "channel", "get", {"channel_id": ...})` |
+| `get_youtube_video(video_id)` | `execute("youtube", "video", "get", {"video_id": ...})` |
+
+#### Reddit
+
+| Old tool | New execute() call |
+|----------|-------------------|
+| `search_reddit(query)` | `execute("reddit", "search", "search", {"query": ...})` |
+| `get_reddit_user(username)` | `execute("reddit", "user", "get", {"username": ...})` |
+| `get_reddit_posts(subreddit)` | `execute("reddit", "posts", "get", {"subreddit": ...})` |
+
+#### YC / SEC / Web
+
+| Old tool | New execute() call |
+|----------|-------------------|
+| `search_yc_companies(query)` | `execute("yc", "search", "search", {"query": ...})` |
+| `get_yc_company(slug)` | `execute("yc", "company", "get", {"slug": ...})` |
+| `search_sec_filings(query)` | `execute("sec", "search", "search", {"query": ...})` |
+| `get_sec_document(url)` | `execute("sec", "document", "get", {"url": ...})` |
+| `scrape_webpage(url)` | `execute("webparser", "parse", "parse", {"url": ...})` |
+
+### Step 4: Handle Unknown Endpoints
+
+If the input references a tool name **not in the mapping above**:
+
+1. Try to infer the source and category from the tool name (e.g., `get_instagram_user_friendships` → source `"instagram"`, category `"user"` or `"friendship"`)
+2. **IMPORTANT: Actually call `discover()` yourself right now** — do NOT leave placeholder `{endpoint}` in the migrated output. Run `discover("{source}", "{category}")` via the MCP tool to get the real endpoint names and parameter schemas.
+3. If the first category guess returns "Category not found", try alternative categories (e.g., if `"friendship"` fails, try `"user"` — the endpoint may be nested under a different category)
+4. Once you get the real endpoint list from `discover()`, use the exact endpoint name and params in the migrated `execute()` call
+
+**Example — resolving an unknown tool:**
+```
+Old tool: get_instagram_user_friendships(user, type, count)
+→ Not in mapping table
+→ You call: discover("instagram", "friendship") → error "Category not found"
+→ You call: discover("instagram", "user") → returns endpoints including "user_friendships"
+→ Migrated: execute("instagram", "user", "user_friendships", {"user": "...", "count": 100, "type": "followers"})
+```
+
+**Rules:**
+- NEVER leave `discover()` as a placeholder instruction in the final migrated skill. The migrated output must contain exact `execute()` calls with real endpoint names and params.
+- Only include `discover()` in the migrated skill text if the skill's workflow genuinely needs runtime discovery (e.g., the skill works with user-specified sources where the endpoint can't be known at migration time).
+- If the mapping above covers the tool, use `execute()` directly — no discover needed.
+- Run discover for ALL sources and categories used by the skill to verify that endpoint names and params in the mapping table are still accurate.
+
+### Step 5: Add v2 Capabilities
+
+Review the migrated skill for opportunities to add new v2 features:
+
+#### Pagination
+When the workflow processes large result sets or needs "more results":
+```
+Results from execute() include cache_key. If more data exists, use:
+get_page(cache_key="{cache_key}", offset=10, limit=10)
+```
+
+#### Server-side Filtering
+When the workflow filters results after fetching (e.g., "only show people in SF"):
+```
+After execute(), filter without consuming context tokens:
+query_cache(cache_key="{cache_key}", conditions=[{"field": "location", "op": "contains", "value": "San Francisco"}])
+```
+
+#### Aggregation
+When the workflow computes statistics or groups data:
+```
+query_cache(cache_key="{cache_key}", aggregate={"field": "followers", "op": "avg"}, group_by="industry")
+```
+
+#### Export to File
+When the workflow outputs structured data (CSV, JSON) or the user needs downloadable results:
+```
+export_data(cache_key="{cache_key}", output_format="csv")
+→ returns download URL
+```
+
+### Step 6: Update Error Handling
+
+Replace old-style error handling:
+
+**Before:**
+```
+If search_linkedin_users returns an error, try with different keywords.
+```
+
+**After:**
+```
+If execute() returns an error with "llm_hint", follow the hint.
+If execute() returns {"error": "Source not found", "available_sources": [...]}, check source name.
+If execute() returns {"error": "Endpoint not found", "available_endpoints": [...]}, call discover() to find correct endpoint names.
+```
+
+### Step 7: Remove Disabled Sources
+
+Remove any references to **Crunchbase** — this source is disabled in v2. If the skill relies on Crunchbase data, suggest alternatives:
+- Company data → LinkedIn company profiles or Y Combinator
+- Funding data → SEC filings or web scraping of funding databases
+- Startup research → Y Combinator database
+
+### Step 8: Validate
+
+Run through this checklist on the migrated output:
+
+- [ ] No remaining `search_linkedin_*`, `get_linkedin_*`, `find_linkedin_*` references
+- [ ] No remaining `search_twitter_*`, `get_twitter_*` references
+- [ ] No remaining `search_instagram_*`, `get_instagram_*` references
+- [ ] No remaining `search_youtube_*`, `get_youtube_*` references
+- [ ] No remaining `search_reddit_*`, `get_reddit_*` references
+- [ ] No remaining `search_yc_*`, `get_yc_*` references
+- [ ] No remaining `search_sec_*`, `get_sec_*` references
+- [ ] No remaining `scrape_webpage` references
+- [ ] No remaining `mcp__anysite__` prefixed tool names (old MCP format)
+- [ ] No Crunchbase references
+- [ ] `discover()` added only where endpoint/params are genuinely unknown
+- [ ] `get_page` / `query_cache` / `export_data` added where beneficial
+- [ ] Error handling updated to v2 format
+- [ ] Original workflow logic preserved — same steps, same data flow
+
+### Step 9: Output
+
+Present the migrated skill in the same format as the input:
+- If the input was a SKILL.md file → output the full migrated SKILL.md
+- If the input was a prompt → output the migrated prompt text
+- If the input was pasted text → output the migrated version
+
+Always show a **migration summary** after the output:
+
+```
+## Migration Summary
+- Tool calls replaced: N
+- discover() calls added: N
+- New v2 features added: [list]
+- Crunchbase references removed: N
+- Warnings: [any issues found]
+```
+
+---
+
+## Examples
+
+### Example 1: Simple Tool Replacement
+
+**Input:**
+```
+Use search_linkedin_users to find CTOs in Berlin, then get_linkedin_profile for each result.
+```
+
+**Output:**
+```
+Use execute("linkedin", "search", "search_users", {"title": "CTO", "location": "Berlin", "count": 10}) to find CTOs in Berlin, then execute("linkedin", "user", "get", {"user": "{alias}"}) for each result.
+```
+
+### Example 2: Multi-Step Workflow
+
+**Input:**
+```
+1. Use search_linkedin_users to find the person
+2. Use get_linkedin_profile to get their full profile
+3. Use find_linkedin_email to get their email
+4. Use get_twitter_user to check their Twitter
+```
+
+**Output:**
+```
+1. Use execute("linkedin", "search", "search_users", {"first_name": ..., "last_name": ..., "count": 5}) to find the person
+2. Use execute("linkedin", "user", "get", {"user": "{alias from step 1}"}) to get their full profile
+3. Use execute("linkedin", "email", "find", {"user": "{alias from step 1}"}) to get their email
+4. Use execute("twitter", "user", "get", {"username": "..."}) to check their Twitter
+```
+
+### Example 3: Adding v2 Features
+
+**Input:**
+```
+Search for 50 marketing managers and filter by location.
+```
+
+**Output:**
+```
+1. Use execute("linkedin", "search", "search_users", {"title": "Marketing Manager", "count": 50}) to search
+2. If more results exist, use get_page(cache_key="{cache_key}", offset=10, limit=10) to load additional pages
+3. Use query_cache(cache_key="{cache_key}", conditions=[{"field": "location", "op": "contains", "value": "..."}]) to filter by location server-side
+4. Use export_data(cache_key="{cache_key}", output_format="csv") to download the filtered list
+```
+
+---
+
+## Quick Reference: v2 Meta-Tools
+
+| Tool | Purpose | When to use |
+|------|---------|-------------|
+| `discover(source, category)` | Learn available endpoints and params | Before execute() when endpoint name or params are unknown |
+| `execute(source, category, endpoint, params)` | Fetch data from any source | Every data retrieval — replaces all v1 tools |
+| `get_page(cache_key, offset, limit)` | Load more items from previous execute() | When execute() returned next_offset |
+| `query_cache(cache_key, conditions, sort_by, aggregate, group_by)` | Filter/sort/aggregate cached data | When you need to slice results without re-fetching |
+| `export_data(cache_key, format)` | Save dataset as downloadable file | When user needs CSV/JSON/JSONL export |

package/skills/anysite-person-analyzer/SKILL.md

@@ -7,6 +7,22 @@ description: Deep multi-platform intelligence analysis combining LinkedIn (profi
 
 Comprehensive multi-platform intelligence analysis combining LinkedIn, Twitter/X, Reddit, GitHub, and web presence data to create actionable intelligence reports with cross-platform personality insights.
 
+## v2 Tool Interface
+
+All data fetching uses the unified v2 MCP tools:
+
+- **`execute(source, category, endpoint, params)`** - Fetch data. Returns first page + `cache_key`.
+- **`get_page(cache_key, offset, limit)`** - Load more items from a previous execute (when `next_offset` is returned).
+- **`query_cache(cache_key, conditions?, sort_by?, aggregate?, group_by?)`** - Filter, sort, or aggregate cached data without new API calls.
+- **`export_data(cache_key, format)`** - Export full dataset as CSV, JSON, or JSONL. Returns download URL.
+
+### v2 Error Handling
+
+All `execute()` calls may return structured errors with `llm_hint` fields. When an error occurs:
+- **412 errors**: Resource not found (e.g., user alias incorrect). Follow the `llm_hint` to resolve (typically: search first, then use the returned alias/URN).
+- **422 errors**: Wrong parameter format (e.g., passed alias instead of URN). Check `llm_hint` for the correct format.
+- **Rate limits**: Continue with data from other sources. Note limitations in report.
+
 ## Analysis Workflow
 
 Execute phases sequentially, adapting depth based on available data and user requirements.
@@ -14,17 +30,17 @@ Execute phases sequentially, adapting depth based on available data and user req
 ### Phase 1: Initial Data Collection
 
 **Starting with LinkedIn Profile URL:**
-1. Use `get_linkedin_profile` with full parameters (education, experience, skills)
-2. Extract and save the **full URN** (format: `urn:li:fsd_profile:ACoAAABCDEF`) - this is critical for all subsequent API calls
+1. Use `execute("linkedin", "user", "user", {"user": "<profile_url_or_alias>", "with_experience": true, "with_education": true, "with_skills": true})` with full parameters
+2. Extract and save the **full URN** (format: `urn:li:fsd_profile:ACoAAABCDEF`) from the response - this is critical for all subsequent API calls
 3. Also extract: company URN, current role, location, connections count
 4. Record profile completeness for confidence scoring
+5. Save the `cache_key` from the response for later use with `query_cache()` or `export_data()`
 
-**IMPORTANT - URN Format:** 
-Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the profile response for all subsequent calls to `get_linkedin_user_posts`, `get_linkedin_user_comments`, and `get_linkedin_user_reactions`. Do not use shortened versions or profile URLs.
+**IMPORTANT - URN Format:**
+Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the profile response for all subsequent calls to `execute("linkedin", "user", "user_posts", ...)`, `execute("linkedin", "user", "user_comments", ...)`, and `execute("linkedin", "user", "user_reactions", ...)`. Do not use shortened versions or profile URLs.
 
 **Starting with Name + Context:**
-1. Use `search_linkedin_users` with all available filters:
-   - Name, title, company keywords, location, school
+1. Use `execute("linkedin", "search", "search_users", {"query": "<name>", "title": "<title>", "company": "<company>", "location": "<location>"})` with all available filters
 2. If multiple matches: present top 3-5 candidates with distinguishing details
 3. After user confirmation, proceed with confirmed profile
 
@@ -39,28 +55,28 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
 ### Phase 2: Activity & Engagement Analysis
 
 **Content Analysis (Posts):**
-1. Use `get_linkedin_user_posts` with the full URN (format: `urn:li:fsd_profile:ACoAAABCDEF`)
+1. Use `execute("linkedin", "user", "user_posts", {"urn": "<full_fsd_profile_URN>", "count": 20, "posted_after": <unix_timestamp>})` with the full URN (format: `urn:li:fsd_profile:ACoAAABCDEF`)
    - Count: 20-50 depending on activity level
-   - Posted after filter: last 90 days for active users, 180 days if low activity
-2. Analyze for:
+   - posted_after: Unix timestamp for last 90 days for active users, 180 days if low activity
+2. If response includes `next_offset`, use `get_page(cache_key, offset, limit)` to load additional posts
+3. Analyze for:
    - Topics and themes (use clustering: technical, leadership, industry trends, personal)
    - Engagement metrics (likes, comments per post - calculate averages)
    - Posting frequency (calculate posts per week/month)
    - Content style (thought leadership, sharing, personal stories, company updates)
    - Language and tone
+4. Use `query_cache(cache_key, sort_by={"field": "reactions", "order": "desc"})` to find their most engaging posts
 
 **Engagement Analysis (Comments & Reactions):**
-1. Use `get_linkedin_user_comments` with the full URN (format: `urn:li:fsd_profile:ACoAAABCDEF`)
-   - Count: 30
-2. Use `get_linkedin_user_reactions` with the full URN (format: `urn:li:fsd_profile:ACoAAABCDEF`)
-   - Count: 50
+1. Use `execute("linkedin", "user", "user_comments", {"urn": "<full_fsd_profile_URN>", "count": 30})` with the full URN (format: `urn:li:fsd_profile:ACoAAABCDEF`)
+2. Use `execute("linkedin", "user", "user_reactions", {"urn": "<full_fsd_profile_URN>", "count": 50})` with the full URN (format: `urn:li:fsd_profile:ACoAAABCDEF`)
 3. Analyze for:
    - Who they engage with (seniority levels, industries)
    - Topics that spark their engagement
    - Engagement style (supportive, challenging, informational)
    - Response patterns (quick reactions vs thoughtful comments)
 
-**CRITICAL:** All three tools (`get_linkedin_user_posts`, `get_linkedin_user_comments`, `get_linkedin_user_reactions`) require the complete URN in the format `urn:li:fsd_profile:ACoAAABCDEF` obtained from Phase 1. Using LinkedIn profile URLs or partial URNs will result in errors.
+**CRITICAL:** All three tools (`execute("linkedin", "user", "user_posts", ...)`, `execute("linkedin", "user", "user_comments", ...)`, `execute("linkedin", "user", "user_reactions", ...)`) require the complete URN in the format `urn:li:fsd_profile:ACoAAABCDEF` obtained from Phase 1. Using LinkedIn profile URLs or partial URNs will result in 422 errors (check `llm_hint` in error response for guidance).
 
 **Output: Engagement Profile**
 - Primary content themes (ranked by frequency)
@@ -71,19 +87,21 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
 ### Phase 3: Company Intelligence
 
 **Current Company Deep Dive:**
-1. Use `get_linkedin_company` with company URN from profile
+1. Use `execute("linkedin", "company", "company", {"company": "<company_alias_or_url>"})` with company alias/URL from profile
 2. Extract:
    - Company size, industry, specialties
    - Growth indicators (employee count trends if available)
    - Company description and mission
    - Recent updates/news
+   - Save `cache_key` for later filtering with `query_cache()`
 
-3. Use `get_linkedin_company_posts` (count: 20)
+3. Use `execute("linkedin", "company", "company_posts", {"urn": "<company_URN_with_company_prefix>", "count": 20})` (count: 20)
+   - Note: Company sub-endpoints require `company:{id}` prefix, NOT `fsd_company`. Convert: `urn:li:fsd_company:1441` -> use `company:1441`
    - Analyze company communication themes
    - Identify strategic priorities
    - Note any mentions of funding, hiring, expansion
 
-4. Use `duckduckgo_search` for recent news:
+4. Use `execute("duckduckgo", "search", "search", {"query": "<search_terms>"})` for recent news:
    - "[Company name] funding news"
    - "[Company name] expansion launch product"
    - Prioritize results from last 6 months
@@ -91,22 +109,23 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
 **Company Social Media Presence:**
 
 5. **Company Twitter/X Analysis:**
-   - Use `search_twitter_users` to find official company account: "[Company Name] official"
-   - If found, use `get_twitter_user` for profile stats
-   - Use `get_twitter_user_posts` (count: 20-30) to analyze:
+   - Use `execute("twitter", "search", "search_users", {"query": "[Company Name] official", "count": 5})` to find official company account
+   - If found, use `execute("twitter", "user", "user", {"user": "<username>"})` for profile stats
+   - Use `execute("twitter", "user", "user_posts", {"user": "<username>", "count": 20})` (count: 20-30) to analyze:
      - Product announcements and launches
      - Company culture and values
      - Engagement with customers and community
      - Hiring announcements (growth signals)
      - Technical content (if tech company)
-   - Use `search_twitter_posts` for company mentions: "[Company Name]"
+   - Use `execute("twitter", "search", "search_posts", {"query": "[Company Name]", "count": 20})` for company mentions:
      - Customer sentiment (complaints vs praise)
      - Industry discussion about the company
      - Competitor comparisons
      - Notable tweets from employees
+   - Use `query_cache(cache_key, sort_by={"field": "favorite_count", "order": "desc"})` to surface most-engaged tweets
 
 6. **Company Reddit Presence:**
-   - Use `search_reddit_posts` for company mentions: "[Company Name]"
+   - Use `execute("reddit", "search", "search_posts", {"query": "[Company Name]", "count": 20})` for company mentions
    - Look for:
      - r/startups discussions about the company
      - Industry-specific subreddit mentions (r/SaaS, r/artificial, etc.)
@@ -114,6 +133,7 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
      - Technical discussions about their product/platform
      - Hiring experiences (Glassdoor-like insights)
      - Founder/team AMAs or discussions
+   - Use `query_cache(cache_key, aggregate={"field": "subreddit", "function": "count"}, group_by="subreddit")` to see which subreddits discuss the company most
    - Sentiment analysis: positive/negative/neutral community perception
    - Pain points mentioned by users/customers
 
@@ -134,16 +154,17 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
 
 1. **Find Twitter Handle:**
    - Check LinkedIn profile bio/description for @username
-   - Use `search_twitter_users` with name if not found: "[First Name] [Last Name] [Company]"
+   - Use `execute("twitter", "search", "search_users", {"query": "[First Name] [Last Name] [Company]", "count": 5})` with name if not found
    - Verify match by checking bio, profile description
 
 2. **Profile Analysis:**
-   - Use `get_twitter_user` with username
+   - Use `execute("twitter", "user", "user", {"user": "<username>"})` with username
    - Extract: follower count, following count, tweet count, bio, location
    - Note: verification status, profile creation date
 
 3. **Content Analysis:**
-   - Use `get_twitter_user_posts` (count: 50-100 recent tweets)
+   - Use `execute("twitter", "user", "user_posts", {"user": "<username>", "count": 50})` (count: 50-100 recent tweets)
+   - If response includes `next_offset`, use `get_page(cache_key, offset, limit)` to load more tweets up to 100
    - Analyze for:
      - Technical expertise signals (code snippets, tech discussions)
      - Industry opinions and hot takes
@@ -151,9 +172,10 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
      - Engagement with other thought leaders
      - Retweets vs original content ratio
    - Calculate: tweets per day, avg engagement rate
+   - Use `query_cache(cache_key, aggregate={"field": "favorite_count", "function": "avg"})` to compute average engagement
 
 4. **Topic Discovery:**
-   - Use `search_twitter_posts` with person's key interests: "[topic] from:@username"
+   - Use `execute("twitter", "search", "search_posts", {"query": "[topic] from:@username", "count": 20})` with person's key interests
    - Identify recurring themes and expertise areas
    - Note controversial or strongly-held opinions
 
@@ -161,19 +183,20 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
 
 1. **Find Reddit Presence:**
    - Search for username from other platforms
-   - Use `search_reddit_posts` with name/company mentions
+   - Use `execute("reddit", "search", "search_posts", {"query": "<name_or_company>", "count": 20})` with name/company mentions
    - Look for: "AMA" posts, technical discussions, community contributions
 
 2. **Content Analysis:**
-   - Use `search_reddit_posts` with username if known: "author:[username]"
+   - Use `execute("reddit", "search", "search_posts", {"query": "author:[username]", "count": 20})` with username if known
    - Analyze for:
      - Subreddit preferences (which communities they're active in)
      - Technical depth of contributions
      - Helping behavior vs self-promotion ratio
      - Community reputation indicators
+   - Use `query_cache(cache_key, aggregate={"field": "subreddit", "function": "count"}, group_by="subreddit")` to identify most active subreddits
 
 3. **Topic Expertise:**
-   - Use `search_reddit_posts` for specific topics: "[topic] [username or company]"
+   - Use `execute("reddit", "search", "search_posts", {"query": "[topic] [username or company]", "count": 20})` for specific topics
    - Identify where they're seen as expert/helpful
    - Note any popular posts or discussions they started
 
@@ -181,36 +204,37 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
 
 1. **Profile Discovery:**
    - Check if mentioned in LinkedIn or Twitter
-   - Use `search_instagram_posts` with hashtags: "#[name] #[company]"
-   - Use `get_instagram_user` if handle known
+   - Use `execute("instagram", "search", "search_posts", {"query": "#[name] #[company]", "count": 10})` with hashtags
+   - Use `execute("instagram", "user", "user", {"user": "<handle>"})` if handle known
 
 2. **Content Style:**
-   - Use `get_instagram_user_posts` (count: 20-30)
+   - Use `execute("instagram", "user", "user_posts", {"user": "<handle>", "count": 20})` (count: 20-30)
+   - If more posts needed, use `get_page(cache_key, offset, limit)` to continue
    - Analyze for: personal brand vs professional content
    - Note: visual style, posting frequency, engagement rate
 
 **D. Web Intelligence & Media Presence:**
 
 1. **Professional Presence:**
-   - `duckduckgo_search`: "[Name] [Company] speaker conference"
-   - `duckduckgo_search`: "[Name] interview podcast"
-   - `duckduckgo_search`: "[Name] article blog post"
+   - `execute("duckduckgo", "search", "search", {"query": "[Name] [Company] speaker conference"})`
+   - `execute("duckduckgo", "search", "search", {"query": "[Name] interview podcast"})`
+   - `execute("duckduckgo", "search", "search", {"query": "[Name] article blog post"})`
 
 2. **Expertise & Thought Leadership:**
-   - `duckduckgo_search`: "[Name] expertise [primary topic from posts]"
+   - `execute("duckduckgo", "search", "search", {"query": "[Name] expertise [primary topic from posts]"})`
    - Check for: publications, talks, media mentions
-   - `duckduckgo_search`: "[Name] [key topic] site:medium.com OR site:dev.to OR site:substack.com"
+   - `execute("duckduckgo", "search", "search", {"query": "[Name] [key topic] site:medium.com OR site:dev.to OR site:substack.com"})`
 
 3. **Company-Specific Context:**
-   - `duckduckgo_search`: "[Name] [Company] announcement"
+   - `execute("duckduckgo", "search", "search", {"query": "[Name] [Company] announcement"})`
    - Look for: press releases, product launches, executive quotes
 
 4. **GitHub/Tech Presence (if technical role):**
-   - `duckduckgo_search`: "[Name] site:github.com"
+   - `execute("duckduckgo", "search", "search", {"query": "[Name] site:github.com"})`
    - Look for: open source contributions, personal projects
 
 **E. Parse Key Pages:**
-- Use `parse_webpage` for high-value sources:
+- Use `execute("webparser", "parse", "parse", {"url": "<page_url>"})` for high-value sources:
   - Personal blog/website (if mentioned in any profile)
   - Recent interviews or podcast appearances
   - Conference speaker profiles
@@ -235,6 +259,11 @@ Always use the complete URN format `urn:li:fsd_profile:ACoAAABCDEF` from the pro
 
 ### Phase 5: Cross-Platform Strategic Analysis & Report Generation
 
+**Data Export (optional):**
+- Use `export_data(cache_key, "csv")` or `export_data(cache_key, "json")` to save collected datasets for the user
+- Useful for: LinkedIn posts dataset, Twitter tweets dataset, Reddit mentions dataset
+- Returns download URL the user can share or archive
+
 **Connection Strategy:**
 1. **Conversation Topics** (ranked by relevance, synthesized across all platforms):
    - Top 3-5 topics from their LinkedIn posts/comments
@@ -335,7 +364,7 @@ Generate comprehensive markdown report with sections:
 
 2. **[Theme 2]** (30% of posts)
    - Key topics: [list]
-   
+
 3. **[Theme 3]** (20% of posts)
 
 #### Engagement Patterns
@@ -523,12 +552,13 @@ Generate comprehensive markdown report with sections:
 
 ## Analysis Metadata
 - **Platforms Analyzed:**
-  - LinkedIn: [✓ Profile, Posts, Comments, Reactions]
-  - Twitter/X: [✓ Found and analyzed / ✗ Not found / - Not searched]
-  - Reddit: [✓ Activity found / ✗ No activity / - Not searched]
-  - GitHub: [✓ Projects found / ✗ Not found / - Not applicable]
-  - Web: [✓ Articles/interviews found]
-- **Data Sources:** [List specific tools used]
+  - LinkedIn: [Profile, Posts, Comments, Reactions]
+  - Twitter/X: [Found and analyzed / Not found / Not searched]
+  - Reddit: [Activity found / No activity / Not searched]
+  - GitHub: [Projects found / Not found / Not applicable]
+  - Web: [Articles/interviews found]
+- **Data Sources:** [List specific execute() calls made]
+- **Cache Keys:** [List cache_key values for re-query or export]
 - **Data Freshness:**
   - LinkedIn posts: [date range analyzed]
   - Twitter: [date range if analyzed]
@@ -553,8 +583,11 @@ Generate comprehensive markdown report with sections:
 - Always confirm with user before proceeding with deep analysis
 - Present distinguishing factors clearly
 
-**Rate Limiting / API Errors:**
-- Continue with available data from other sources
+**v2 Error Handling:**
+- Check `llm_hint` field in error responses for resolution guidance
+- **412 errors**: Resource not found -- search first to find correct alias/URN
+- **422 errors**: Wrong parameter format -- typically alias passed where URN required
+- Continue with available data from other sources on error
 - Note limitations in report
 - Suggest manual verification steps
 
@@ -596,9 +629,9 @@ Users may request analysis depth adjustment:
 
 **Platform-Specific Focus:**
 Users can also request focus on specific platforms:
-- "Focus on Twitter presence" → Deep Twitter analysis for person AND company, standard LinkedIn
-- "Technical profile only" → LinkedIn + GitHub + Reddit + Stack Overflow (person focused)
-- "Business profile" → LinkedIn + web presence + media, skip Reddit/GitHub
-- **"Company deep dive" → Extended company social analysis across all platforms** (NEW)
+- "Focus on Twitter presence" -> Deep Twitter analysis for person AND company, standard LinkedIn
+- "Technical profile only" -> LinkedIn + GitHub + Reddit + Stack Overflow (person focused)
+- "Business profile" -> LinkedIn + web presence + media, skip Reddit/GitHub
+- **"Company deep dive" -> Extended company social analysis across all platforms** (NEW)
 
 Default to **Standard Analysis** unless specified.