@anysiteio/agent-skills 1.4.0 → 2.0.1

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.

package/skills/anysite-trend-analysis/SKILL.md

@@ -19,25 +19,42 @@ Discover emerging trends and track viral content across social platforms using a
 
 ## Supported Platforms
 
-- ✅ **Twitter/X**: Trending topics, viral tweets, hashtag tracking
-- ✅ **Reddit**: Trending posts, subreddit activity, upvote velocity
-- ✅ **YouTube**: Trending videos, search trends, rising channels
-- ✅ **LinkedIn**: Professional trends, industry discussions
-- ✅ **Instagram**: Trending hashtags, viral content
+- **Twitter/X**: Trending topics, viral tweets, hashtag tracking
+- **Reddit**: Trending posts, subreddit activity, upvote velocity
+- **YouTube**: Trending videos, search trends, rising channels
+- **LinkedIn**: Professional trends, industry discussions
+- **Instagram**: Trending hashtags, viral content
+
+## v2 Tool Interface
+
+All data fetching uses the universal `execute()` meta-tool. Always call `discover(source, category)` first if you need to verify endpoint names or available parameters.
+
+**Core tools**:
+- `execute(source, category, endpoint, params)` - Fetch data. Returns first page + `cache_key`.
+- `get_page(cache_key, offset, limit)` - Load more results from a previous execute.
+- `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.
+
+**Error handling**: If execute() returns an error with `llm_hint`, follow the hint to fix the request (e.g., correcting a parameter name or adjusting the query).
 
 ## Quick Start
 
 **Step 1: Search for Trending Content**
 
 By platform:
-- Twitter: `search_twitter_posts(query, count)` sorted by engagement
-- Reddit: `search_reddit_posts(query, count)` sorted by upvotes
-- YouTube: `search_youtube_videos(query, count)` by recent
-- LinkedIn: `search_linkedin_posts(keywords, count)`
-- Instagram: `search_instagram_posts(query, count)`
+- Twitter: `execute("twitter", "search", "search_tweets", {"query": "<topic>", "count": 100})` sorted by engagement
+- Reddit: `execute("reddit", "search", "search", {"query": "<topic>"})` sorted by upvotes
+- YouTube: `execute("youtube", "search", "search_videos", {"query": "<topic>", "count": 50})` by recent
+- LinkedIn: `execute("linkedin", "post", "search_posts", {"keywords": "<topic>"})` by engagement
+- Instagram: `execute("instagram", "search", "search_users", {"query": "<topic>"})` for hashtag/topic discovery
 
 **Step 2: Analyze Momentum**
 
+Use `query_cache()` to filter and sort cached results:
+```
+query_cache(cache_key, sort_by="engagement_desc", conditions=[{"field": "date", "op": ">", "value": "2024-01-01"}])
+```
+
 Check indicators:
 - Engagement velocity (growth rate)
 - Cross-platform presence
@@ -54,6 +71,8 @@ Monitor changes:
 
 **Step 4: Report Insights**
 
+Use `export_data(cache_key, "csv")` to generate downloadable reports.
+
 Deliver:
 - Trending topics list
 - Momentum indicators
@@ -71,23 +90,46 @@ Deliver:
 1. **Search Across Platforms**
 ```
 # Twitter
-search_twitter_posts(query="AI OR artificial intelligence", count=100)
-Filter for: Posted within 24-48h, high engagement
+execute("twitter", "search", "search_tweets", {"query": "AI OR artificial intelligence", "count": 100})
+→ Filter for: Posted within 24-48h, high engagement
+→ Save cache_key as twitter_cache
 
 # Reddit
-search_reddit_posts(query="artificial intelligence", count=100)
-Filter: r/technology, r/MachineLearning, r/singularity
+execute("reddit", "search", "search", {"query": "artificial intelligence"})
+→ Filter: r/technology, r/MachineLearning, r/singularity
+→ Save cache_key as reddit_cache
 
 # YouTube
-search_youtube_videos(query="AI news", count=50)
-Filter: Published this week, views >10k
+execute("youtube", "search", "search_videos", {"query": "AI news", "count": 50})
+→ Filter: Published this week, views >10k
+→ Save cache_key as youtube_cache
 
 # LinkedIn
-search_linkedin_posts(keywords="artificial intelligence", count=50)
-Filter: High engagement, recent
+execute("linkedin", "post", "search_posts", {"keywords": "artificial intelligence"})
+→ Filter: High engagement, recent
+→ Save cache_key as linkedin_cache
+```
+
+2. **Use query_cache to Filter Results**
 ```
+# Filter Twitter for high-engagement posts
+query_cache(twitter_cache, sort_by="engagement_desc", conditions=[{"field": "likes", "op": ">", "value": 100}])
+
+# Filter Reddit for specific subreddits
+query_cache(reddit_cache, conditions=[{"field": "subreddit", "op": "contains", "value": "technology"}])
 
-2. **Extract Common Themes**
+# Aggregate YouTube view counts
+query_cache(youtube_cache, aggregate={"field": "views", "op": "avg"})
+```
+
+3. **Load More Results if Needed**
+```
+# If execute() returned next_offset, paginate
+get_page(twitter_cache, offset=10, limit=50)
+get_page(reddit_cache, offset=10, limit=50)
+```
+
+4. **Extract Common Themes**
 ```
 Analyze content for recurring:
 - Keywords and phrases
@@ -96,7 +138,7 @@ Analyze content for recurring:
 - Questions or concerns
 ```
 
-3. **Calculate Trend Score**
+5. **Calculate Trend Score**
 ```
 For each theme:
 - Platform count (how many platforms)
@@ -105,7 +147,7 @@ For each theme:
 - Sentiment distribution
 ```
 
-4. **Identify Breakout Trends**
+6. **Identify Breakout Trends**
 ```
 Trends with:
 - Presence on 3+ platforms
@@ -128,21 +170,27 @@ Trends with:
 
 1. **Search by Hashtag**
 ```
-# Instagram
-search_instagram_posts(query="#sustainability", count=100)
-Group by: Last 24h, last week, last month
+# Instagram - discover users/content around the hashtag
+execute("instagram", "search", "search_users", {"query": "sustainability"})
+→ Save cache_key as ig_cache
 
 # Twitter
-search_twitter_posts(query="#sustainability", count=100)
-Track tweet volume over time
+execute("twitter", "search", "search_tweets", {"query": "#sustainability", "count": 100})
+→ Track tweet volume over time
+→ Save cache_key as tw_cache
 
 # LinkedIn
-search_linkedin_posts(keywords="sustainability", count=50)
-Check professional adoption
+execute("linkedin", "post", "search_posts", {"keywords": "sustainability"})
+→ Check professional adoption
+→ Save cache_key as li_cache
 ```
 
-2. **Calculate Velocity**
+2. **Calculate Velocity with query_cache**
 ```
+# Sort by recency and engagement
+query_cache(tw_cache, sort_by="date_desc")
+query_cache(ig_cache, sort_by="followers_desc")
+
 Hashtag velocity:
 - Posts in last 24h vs. previous 24h
 - Engagement rate change
@@ -159,7 +207,14 @@ Compare early vs. recent posts:
 - Commercial adoption
 ```
 
-4. **Predict Peak**
+4. **Export Results**
+```
+export_data(tw_cache, "csv")
+export_data(ig_cache, "json")
+→ Share downloadable reports
+```
+
+5. **Predict Peak**
 ```
 Based on growth curve:
 - Early stage (accelerating)
@@ -181,18 +236,22 @@ Based on growth curve:
 
 1. **Search Target Subreddits**
 ```
-search_reddit_posts(
-  query="",
-  subreddit="technology"
-)
+execute("reddit", "posts", "get", {"subreddit": "technology"})
 → Get top posts from last week
+→ Save cache_key as reddit_tech_cache
 ```
 
 2. **Analyze Post Momentum**
 ```
-For each post:
-  get_reddit_post(post_url)
-  get_reddit_post_comments(post_url)
+# Sort cached posts by engagement
+query_cache(reddit_tech_cache, sort_by="upvotes_desc")
+
+# Aggregate engagement metrics
+query_cache(reddit_tech_cache, aggregate={"field": "upvotes", "op": "avg"})
+
+For each high-momentum post:
+  execute("reddit", "search", "search", {"query": "<post topic>"})
+  → Deeper analysis
 
 Calculate:
 - Upvotes per hour
@@ -213,9 +272,9 @@ From high-momentum posts:
 4. **Track Cross-Pollination**
 ```
 Check if trending Reddit topics appear on:
-- Twitter (mainstream awareness)
-- LinkedIn (professional discussion)
-- YouTube (explainer content)
+- Twitter: execute("twitter", "search", "search_tweets", {"query": "<topic>"})
+- LinkedIn: execute("linkedin", "post", "search_posts", {"keywords": "<topic>"})
+- YouTube: execute("youtube", "search", "search_videos", {"query": "<topic>"})
 ```
 
 **Expected Output**:
@@ -224,29 +283,34 @@ Check if trending Reddit topics appear on:
 - Mainstream potential
 - Early mover opportunities
 
-## MCP Tools Reference
+## MCP Tools Reference (v2)
 
 ### Twitter/X
-- `search_twitter_posts(query, count)` - Find tweets, filter by engagement
-- `get_twitter_user(user)` - Check influencer adoption
+- `execute("twitter", "search", "search_tweets", {"query": ..., "count": N})` - Find tweets, filter by engagement
+- `execute("twitter", "user", "get", {"username": ...})` - Check influencer adoption
 
 ### Reddit
-- `search_reddit_posts(query, subreddit, count)` - Find discussions
-- `get_reddit_post(url)` - Get post details and momentum
-- `get_reddit_post_comments(url)` - Analyze discussion depth
+- `execute("reddit", "search", "search", {"query": ...,})` - Find discussions
+- `execute("reddit", "posts", "get", {"subreddit": ...})` - Get subreddit posts and momentum
+- `execute("reddit", "user", "get", {"username": ...})` - Get user details
 
 ### YouTube
-- `search_youtube_videos(query, count)` - Find trending videos
-- `get_youtube_video(video)` - Track view velocity
-- `get_youtube_video_comments(video, count)` - Gauge interest
+- `execute("youtube", "search", "search_videos", {"query": ..., "count": N})` - Find trending videos
+- `execute("youtube", "video", "video", {"video": ...})` - Track view velocity
+- `execute("youtube", "video", "video_comments", {"video": ..., "count": N})` - Gauge interest
 
 ### LinkedIn
-- `search_linkedin_posts(keywords, count)` - Professional trends
-- `get_linkedin_company_posts(urn, count)` - Corporate adoption
+- `execute("linkedin", "post", "search_posts", {"keywords": ...})` - Professional trends
+- `execute("linkedin", "company", "get", {"company": ...})` - Company details
 
 ### Instagram
-- `search_instagram_posts(query, count)` - Hashtag trends
-- `get_instagram_post(post_id)` - Engagement metrics
+- `execute("instagram", "search", "search_users", {"query": ...})` - Discover users/hashtags
+- `execute("instagram", "post", "post", {"post": ...})` - Engagement metrics
+
+### Pagination & Analysis
+- `get_page(cache_key, offset, limit)` - Load additional results from any execute() call
+- `query_cache(cache_key, conditions, sort_by, aggregate, group_by)` - Filter, sort, aggregate cached data
+- `export_data(cache_key, "csv"|"json"|"jsonl")` - Export datasets for reporting
 
 ## Trend Identification Framework
 
@@ -291,12 +355,12 @@ Check if trending Reddit topics appear on:
 - Platform breakdown
 - Strategic recommendations
 
-**CSV Export**:
+**CSV Export** (via `export_data(cache_key, "csv")`):
 - Trend name, platforms, volume
 - Growth rate, sentiment
 - Key influencers mentioning
 
-**JSON Export**:
+**JSON Export** (via `export_data(cache_key, "json")`):
 - Complete trend data
 - Time-series metrics
 - Cross-platform correlations

package/skills/anysite-vc-analyst/SKILL.md

@@ -28,7 +28,7 @@ AskUserQuestion:
 
 ### Step 2: Fetch & Analyze Project
 
-1. **Website**: Use `mcp__anysite__parse_webpage(url=website)` to understand:
+1. **Website**: Use `execute("webparser", "parse", "parse", {"url": website})` to understand:
    - Product/service description
    - Target market
    - Key features
@@ -163,11 +163,13 @@ After onboarding, analyze investors from CSV or list.
 ### 1. Fetch LinkedIn Profile (ALWAYS FIRST)
 
 ```
-mcp__anysite__get_linkedin_profile(user="linkedin-url-or-username")
+execute("linkedin", "user", "get", {"user": "linkedin-url-or-username"})
 ```
 
 CSV data has ~20% error rate. Always verify actual role before scoring.
 
+> **v2 tip:** The `execute()` call returns a `cache_key`. Use `query_cache(cache_key, ...)` to filter/sort results without re-fetching. Use `get_page(cache_key, offset, limit)` if paginated results exist. Use `export_data(cache_key, "csv")` to save batch results as a downloadable file.
+
 ### 2. Score Investor (0-100)
 
 | Factor | Weight | Check |
@@ -253,6 +255,14 @@ Best,
 }
 ```
 
+### v2 Batch Features
+
+- **Pagination**: When `execute()` returns `next_offset`, use `get_page(cache_key, offset, limit)` to fetch additional results without re-running the query.
+- **Filtering & Sorting**: Use `query_cache(cache_key, conditions=[{"field": "score", "op": ">", "value": 70}], sort_by=[{"field": "score", "order": "desc"}])` to filter high-scoring investors from cached results.
+- **Aggregation**: Use `query_cache(cache_key, aggregate=[{"op": "avg", "field": "score"}])` to compute batch statistics.
+- **Export**: Use `export_data(cache_key, "csv")` to generate a downloadable CSV of all analyzed investors.
+- **Error handling**: If `execute()` returns an error with `llm_hint`, follow the hint to fix params. Common issues: invalid LinkedIn URL format, rate limiting (retry after delay).
+
 ---
 
 ## Quick Commands