[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CGS3TFDRFAEK2EBVZAN86W":3,"skill-same:01M7CGS3TFDRFAEK2EBVZAN86W":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CGS3TFDRFAEK2EBVZAN86W","apify-content-analytics",null,"Track engagement metrics, measure campaign ROI, and analyze content performance across Instagram, Facebook, YouTube, and TikTok.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fapify-content-analytics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: apify-content-analytics\ndescription: Track engagement metrics, measure campaign ROI, and analyze content performance across Instagram, Facebook, YouTube, and TikTok.\nrisk: unknown\nsource: community\n---\n\n# Content Analytics\n\nTrack and analyze content performance using Apify Actors to extract engagement metrics from multiple platforms.\n\n## When to Use\n- You need engagement, growth, or ROI metrics for posts, reels, videos, ads, or hashtags.\n- The task is to use Apify Actors to collect cross-platform content performance data.\n- You need exported analytics results and a concise interpretation of what content is performing best.\n\n## Prerequisites\n(No need to check it upfront)\n\n- `.env` file with `APIFY_TOKEN`\n- Node.js 20.6+ (for native `--env-file` support)\n- `mcpc` CLI tool: `npm install -g @apify\u002Fmcpc`\n\n## Workflow\n\nCopy this checklist and track progress:\n\n```\nTask Progress:\n- [ ] Step 1: Identify content analytics type (select Actor)\n- [ ] Step 2: Fetch Actor schema via mcpc\n- [ ] Step 3: Ask user preferences (format, filename)\n- [ ] Step 4: Run the analytics script\n- [ ] Step 5: Summarize findings\n```\n\n### Step 1: Identify Content Analytics Type\n\nSelect the appropriate Actor based on analytics needs:\n\n| User Need | Actor ID | Best For |\n|-----------|----------|----------|\n| Post engagement metrics | `apify\u002Finstagram-post-scraper` | Post performance |\n| Reel performance | `apify\u002Finstagram-reel-scraper` | Reel analytics |\n| Follower growth tracking | `apify\u002Finstagram-followers-count-scraper` | Growth metrics |\n| Comment engagement | `apify\u002Finstagram-comment-scraper` | Comment analysis |\n| Hashtag performance | `apify\u002Finstagram-hashtag-scraper` | Branded hashtags |\n| Mention tracking | `apify\u002Finstagram-tagged-scraper` | Tag tracking |\n| Comprehensive metrics | `apify\u002Finstagram-scraper` | Full data |\n| API-based analytics | `apify\u002Finstagram-api-scraper` | API access |\n| Facebook post performance | `apify\u002Ffacebook-posts-scraper` | Post metrics |\n| Reaction analysis | `apify\u002Ffacebook-likes-scraper` | Engagement types |\n| Facebook Reels metrics | `apify\u002Ffacebook-reels-scraper` | Reels performance |\n| Ad performance tracking | `apify\u002Ffacebook-ads-scraper` | Ad analytics |\n| Facebook comment analysis | `apify\u002Ffacebook-comments-scraper` | Comment engagement |\n| Page performance audit | `apify\u002Ffacebook-pages-scraper` | Page metrics |\n| YouTube video metrics | `streamers\u002Fyoutube-scraper` | Video performance |\n| YouTube Shorts analytics | `streamers\u002Fyoutube-shorts-scraper` | Shorts performance |\n| TikTok content metrics | `clockworks\u002Ftiktok-scraper` | TikTok analytics |\n\n### Step 2: Fetch Actor Schema\n\nFetch the Actor's input schema and details dynamically using mcpc:\n\n```bash\nexport $(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\"\n```\n\nReplace `ACTOR_ID` with the selected Actor (e.g., `apify\u002Finstagram-post-scraper`).\n\nThis returns:\n- Actor description and README\n- Required and optional input parameters\n- Output fields (if available)\n\n### Step 3: Ask User Preferences\n\nBefore running, ask:\n1. **Output format**:\n   - **Quick answer** - Display top few results in chat (no file saved)\n   - **CSV** - Full export with all fields\n   - **JSON** - Full export in JSON format\n2. **Number of results**: Based on character of use case\n\n### Step 4: Run the Script\n\n**Quick answer (display in chat, no file):**\n```bash\nnode --env-file=.env ${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fscripts\u002Frun_actor.js \\\n  --actor \"ACTOR_ID\" \\\n  --input 'JSON_INPUT'\n```\n\n**CSV:**\n```bash\nnode --env-file=.env ${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fscripts\u002Frun_actor.js \\\n  --actor \"ACTOR_ID\" \\\n  --input 'JSON_INPUT' \\\n  --output YYYY-MM-DD_OUTPUT_FILE.csv \\\n  --format csv\n```\n\n**JSON:**\n```bash\nnode --env-file=.env ${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fscripts\u002Frun_actor.js \\\n  --actor \"ACTOR_ID\" \\\n  --input 'JSON_INPUT' \\\n  --output YYYY-MM-DD_OUTPUT_FILE.json \\\n  --format json\n```\n\n### Step 5: Summarize Findings\n\nAfter completion, report:\n- Number of content pieces analyzed\n- File location and name\n- Key performance insights\n- Suggested next steps (deeper analysis, content optimization)\n\n## Error Handling\n\n`APIFY_TOKEN not found` - Ask user to create `.env` with `APIFY_TOKEN=your_token`\n`mcpc not found` - Ask user to install `npm install -g @apify\u002Fmcpc`\n`Actor not found` - Check Actor ID spelling\n`Run FAILED` - Ask user to check Apify console link in error output\n`Timeout` - Reduce input size or increase `--timeout`\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Content Analytics\n\nTrack and analyze content performance using Apify Actors to extract engagement metrics from multiple platforms.\n\n## When to Use\n- You need engagement, growth, or ROI metrics for posts, reels, videos, ads, or hashtags.\n- The task is to use Apify Actors to collect cross-platform content performance data.\n- You need exported analytics results and a concise interpretation of what content is performing best.\n\n## Prerequisites\n(No need to check it upfront)\n\n- `.env` file with `APIFY_TOKEN`\n- Node.js 20.6+ (for native `--env-file` support)\n- `mcpc` CLI tool: `npm install -g @apify\u002Fmcpc`\n\n## Workflow\n\nCopy this checklist and track progress:\n\n```\nTask Progress:\n- [ ] Step 1: Identify content analytics type (select Actor)\n- [ ] Step 2: Fetch Actor schema via mcpc\n- [ ] Step 3: Ask user preferences (format, filename)\n- [ ] Step 4: Run the analytics script\n- [ ] Step 5: Summarize findings\n```\n\n### Step 1: Identify Content Analytics Type\n\nSelect the appropriate Actor based on analytics needs:\n\n| User Need | Actor ID | Best For |\n|-----------|----------|----------|\n| Post engagement metrics | `apify\u002Finstagram-post-scraper` | Post performance |\n| Reel performance | `apify\u002Finstagram-reel-scraper` | Reel analytics |\n| Follower growth tracking | `apify\u002Finstagram-followers-count-scraper` | Growth metrics |\n| Comment engagement | `apify\u002Finstagram-comment-scraper` | Comment analysis |\n| Hashtag performance | `apify\u002Finstagram-hashtag-scraper` | Branded hashtags |\n| Mention tracking | `apify\u002Finstagram-tagged-scraper` | Tag tracking |\n| Comprehensive metrics | `apify\u002Finstagram-scraper` | Full data |\n| API-based analytics | `apify\u002Finstagram-api-scraper` | API access |\n| Facebook post performance | `apify\u002Ffacebook-posts-scraper` | Post metrics |\n| Reaction analysis | `apify\u002Ffacebook-likes-scraper` | Engagement types |\n| Facebook Reels metrics | `apify\u002Ffacebook-reels-scraper` | Reels performance |\n| Ad performance tracking | `apify\u002Ffacebook-ads-scraper` | Ad analytics |\n| Facebook comment analysis | `apify\u002Ffacebook-comments-scraper` | Comment engagement |\n| Page performance audit | `apify\u002Ffacebook-pages-scraper` | Page metrics |\n| YouTube video metrics | `streamers\u002Fyoutube-scraper` | Video performance |\n| YouTube Shorts analytics | `streamers\u002Fyoutube-shorts-scraper` | Shorts performance |\n| TikTok content metrics | `clockworks\u002Ftiktok-scraper` | TikTok analytics |\n\n### Step 2: Fetch Actor Schema\n\nFetch the Actor's input schema and details dynamically using mcpc:\n\n```bash\nexport $(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\"\n```\n\nReplace `ACTOR_ID` with the selected Actor (e.g., `apify\u002Finstagram-post-scraper`).\n\nThis returns:\n- Actor description and README\n- Required and optional input parameters\n- Output fields (if available)\n\n### Step 3: Ask User Preferences\n\nBefore running, ask:\n1. **Output format**:\n   - **Quick answer** - Display top few results in chat (no file saved)\n   - **CSV** - Full export with all fields\n   - **JSON** - Full export in JSON format\n2. **Number of results**: Based on character of use case\n\n### Step 4: Run the Script\n\n**Quick answer (display in chat, no file):**\n```bash\nnode --env-file=.env ${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fscripts\u002Frun_actor.js \\\n  --actor \"ACTOR_ID\" \\\n  --input 'JSON_INPUT'\n```\n\n**CSV:**\n```bash\nnode --env-file=.env ${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fscripts\u002Frun_actor.js \\\n  --actor \"ACTOR_ID\" \\\n  --input 'JSON_INPUT' \\\n  --output YYYY-MM-DD_OUTPUT_FILE.csv \\\n  --format csv\n```\n\n**JSON:**\n```bash\nnode --env-file=.env ${CLAUDE_PLUGIN_ROOT}\u002Freference\u002Fscripts\u002Frun_actor.js \\\n  --actor \"ACTOR_ID\" \\\n  --input 'JSON_INPUT' \\\n  --output YYYY-MM-DD_OUTPUT_FILE.json \\\n  --format json\n```\n\n### Step 5: Summarize Findings\n\nAfter completion, report:\n- Number of content pieces analyzed\n- File location and name\n- Key performance insights\n- Suggested next steps (deeper analysis, content optimization)\n\n## Error Handling\n\n`APIFY_TOKEN not found` - Ask user to create `.env` with `APIFY_TOKEN=your_token`\n`mcpc not found` - Ask user to install `npm install -g @apify\u002Fmcpc`\n`Actor not found` - Check Actor ID spelling\n`Run FAILED` - Ask user to check Apify console link in error output\n`Timeout` - Reduce input size or increase `--timeout`\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"description":7},"unknown","community","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fapify-content-analytics",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill apify-content-analytics",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill apify-content-analytics",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill apify-content-analytics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fapify-content-analytics\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"reference\u002Fscripts\u002Frun_actor.js","SCRIPT","脚本",11747,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fapify-content-analytics\u002Freference\u002Fscripts\u002Frun_actor.js",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]