一键导入
apify-trend-analysis
Discover and track emerging trends across Google Trends, Instagram, Facebook, YouTube, and TikTok to inform content strategy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Discover and track emerging trends across Google Trends, Instagram, Facebook, YouTube, and TikTok to inform content strategy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", ...
This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise comparison, position bias, evaluation pipelines, or automated quality assessment.
Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines,...
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
| name | apify-trend-analysis |
| description | Discover and track emerging trends across Google Trends, Instagram, Facebook, YouTube, and TikTok to inform content strategy. |
| risk | unknown |
| source | community |
Discover and track emerging trends using Apify Actors to extract data from multiple platforms.
(No need to check it upfront)
.env file with APIFY_TOKEN--env-file support)mcpc CLI tool: npm install -g @apify/mcpcCopy this checklist and track progress:
Task Progress:
- [ ] Step 1: Identify trend type (select Actor)
- [ ] Step 2: Fetch Actor schema via mcpc
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the analysis script
- [ ] Step 5: Summarize findings
Select the appropriate Actor based on research needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Search trends | apify/google-trends-scraper | Google Trends data |
| Hashtag tracking | apify/instagram-hashtag-scraper | Hashtag content |
| Hashtag metrics | apify/instagram-hashtag-stats | Performance stats |
| Visual trends | apify/instagram-post-scraper | Post analysis |
| Trending discovery | apify/instagram-search-scraper | Search trends |
| Comprehensive tracking | apify/instagram-scraper | Full data |
| API-based trends | apify/instagram-api-scraper | API access |
| Engagement trends | apify/export-instagram-comments-posts | Comment tracking |
| Product trends | apify/facebook-marketplace-scraper | Marketplace data |
| Visual analysis | apify/facebook-photos-scraper | Photo trends |
| Community trends | apify/facebook-groups-scraper | Group monitoring |
| YouTube Shorts | streamers/youtube-shorts-scraper | Short-form trends |
| YouTube hashtags | streamers/youtube-video-scraper-by-hashtag | Hashtag videos |
| TikTok hashtags | clockworks/tiktok-hashtag-scraper | Hashtag content |
| Trending sounds | clockworks/tiktok-sound-scraper | Audio trends |
| TikTok ads | clockworks/tiktok-ads-scraper | Ad trends |
| Discover page | clockworks/tiktok-discover-scraper | Discover trends |
| Explore trends | clockworks/tiktok-explore-scraper | Explore content |
| Trending content | clockworks/tiktok-trends-scraper | Viral content |
Fetch the Actor's input schema and details dynamically using mcpc:
export $(grep APIFY_TOKEN .env | xargs) && mcpc --json mcp.apify.com --header "Authorization: Bearer $APIFY_TOKEN" tools-call fetch-actor-details actor:="ACTOR_ID" | jq -r ".content"
Replace ACTOR_ID with the selected Actor (e.g., apify/google-trends-scraper).
This returns:
Before running, ask:
Quick answer (display in chat, no file):
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT'
CSV:
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT' \
--output YYYY-MM-DD_OUTPUT_FILE.csv \
--format csv
JSON:
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT' \
--output YYYY-MM-DD_OUTPUT_FILE.json \
--format json
After completion, report:
APIFY_TOKEN not found - Ask user to create .env with APIFY_TOKEN=your_token
mcpc not found - Ask user to install npm install -g @apify/mcpc
Actor not found - Check Actor ID spelling
Run FAILED - Ask user to check Apify console link in error output
Timeout - Reduce input size or increase --timeout
Use this skill when tackling tasks related to its primary domain or functionality as described above.