SocialKit Skills

Build competitor trackers, research creators, analyze public comments, and turn video URLs into transcripts or downloadable files. These eight skills help coding agents choose supported SocialKit REST or MCP operations and preserve incomplete results and unknown metrics.

Install All SocialKit Skills

npx skills add SocialKit-API/skills --all

Run this in your project directory. --all installs all eight skills for all supported agents without a picker. To target one client, use npx skills add SocialKit-API/skills --skill '*' --agent codex -y (or claude-code / cursor). Start a new agent session after installation.

Try one of these prompts with your own public URLs:

• “Build a bounded competitor tracker for these Instagram and YouTube profiles.” → social-media-scraping
• “Get this video's captions and metadata as source-linked JSON.” → video-transcripts
• “Research this creator's public profile and ten recent videos.” → channel-research
• “Find TikToks tagged coldplunge and rank the returned sample by known views.” → content-discovery
• “Summarize themes in the comments returned for this Reel; state the sample limits.” → engagement-analysis

Prefer to clone instead:

git clone https://github.com/SocialKit-API/skills.git

Then point your agent at the skills/ directory, or copy the folders you want into your project's skills path.

Set Your Access Key

Copy .env.example to .env and fill in your key:

cp .env.example .env

SOCIALKIT_API_KEY=your_access_key_here

Get a key from the SocialKit dashboard under the Access Keys tab. The same key works for REST and MCP.

Verify authentication with zero credits:

export SOCIALKIT_API_KEY="your_access_key_here"

curl --fail-with-body -sS "https://api.socialkit.dev/test" \
  -H "x-access-key: $SOCIALKIT_API_KEY"

Hosted MCP config:

{
  "mcpServers": {
    "socialkit": {
      "url": "https://mcp.socialkit.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SOCIALKIT_ACCESS_KEY"
      }
    }
  }
}

Verification prompt: “Check my configured API key with the free test endpoint. Do not print it. Report whether authentication worked.”

Then try one small public-data task from the prompts above. Data requests consume credits. See client-specific setup for Claude Code, Codex CLI/IDE, Cursor, and MCP.

Runnable examples and workflows

See the 0.1.0 release manifest. These optional examples are separate from installing the skill instructions. The starter needs no runtime package installation; the recurring workflow requires your n8n, PostgreSQL and Slack configuration.

Available Skills

Install with --all so you receive every skill in one command.

Platform Coverage

Reddit REST provides public submissions and community metadata (/reddit/post, /reddit/subreddit/details). X includes public author threads and native Articles. MCP covers a subset of REST: Reddit, bulk requests, credits, and status are REST-only. No posting, private-account access, or general website scraping is included.

Claude Code plugin

The repository also supplies a Claude marketplace. After this release is merged, install from Claude Code:

/plugin marketplace add SocialKit-API/skills
/plugin install socialkit-skills@socialkit

Restart Claude Code or run /reload-plugins. The marketplace is called socialkit; the plugin remains socialkit-skills. This is a repository-hosted marketplace, not a claim of inclusion in Anthropic's official directory. Keep your key in the process environment as above. Choose skills installation or the plugin to avoid duplicate skill copies.

To validate a checkout without changing your normal Claude configuration:

claude plugin validate .
claude plugin validate .claude-plugin/marketplace.json

How the Skills Work Together

social-media-scraping
  |- socialkit-api (REST/auth reference)
  |- video-transcripts
  |- video-summaries
  |- channel-research
  |- content-discovery
  |- engagement-analysis
  `- video-download

Use socialkit-api as the shared routing and reference layer. The workflow skills produce useful outcomes, not raw endpoint dumps.

Design Principles

1. Treat docs.socialkit.dev as the source of truth for endpoint shapes.
2. Workflow first, API second. Answer the user's real question, do not just echo raw JSON.
3. Prefer MCP tools when a client is configured; fall back to REST with curl.
4. Use the input the operation expects: public content/profile URL, query, hashtag, or returned job ID. Preserve source URLs.
5. Use bulk endpoints when processing more than a few URLs of the same type.
6. Respect credits. Test authentication for free; bound data requests and account for item/duration pricing.
7. Never expose the access key in output, logs, or committed files.

Maintainer checks

npm ci && npm test validates YAML, plugin paths, route/tool references, and runnable examples, including JavaScript/Python parity. Runtime examples remain dependency-free; the YAML package is only for validation. Reviewed contracts in contracts/ come from API route registration and the MCP publication inventory. Update those snapshots together when capabilities change; do not add a route merely to make a reference pass.

Codex / OpenAI plugin package

This repository includes a portable plugin.json and a Codex marketplace pointing to the same eight skills. See package validation and optional OAuth MCP setup. The default package uses skills and your environment key. Codex and Claude Code can also connect to MCP with browser login. A combined skills/MCP archive requires a deployed OAuth URL and the host's registered client configuration. Repository packaging is separate from marketplace submission.