anysite-mcp-migration

What this skill does

# 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 afte