agentleFS
Sign inStart free
aryaminusaryaminus/socials-assistant/skills/socials-connect/SKILL.md

socials-connect

Skill0 starsChanged 3 months agoMITView on GitHub

Connects a creator's TikTok, Instagram, Facebook, and YouTube accounts to the socials-assistant analytics vault via official OAuth. Use when the user wants to connect, link, or add social accounts, set up the vault for the first time, fix broken or expired connections, or store platform developer-app credentials.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call socials-mcp:connection_status.

    line 13
  2. Very specific:

    If a connect tool returns missing_app_credentials, walk the user through the matching guide (repo docs/):

    line 14
  3. Very specific:

    Call socials-mcp:connect_youtube / socials-mcp:connect_meta / socials-mcp:connect_tiktok.

    line 24
  4. Very specific:

    After they finish in the browser, call socials-mcp:connection_status to confirm ok: true.

    line 25
  5. Very specific:

    Call socials-mcp:snapshot (default 28-day lookback).

    line 30
  6. Very specific:

    Verify with socials-mcp:top_content (days: 7).

    line 32
  7. Distinctive:

    Never ask for passwords; never automate the logged-in TikTok Studio session (ToS + account risk).

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

socials-connect — guided onboarding

Goal: all of the user's platforms connected to the socials-mcp vault through official OAuth flows, plus the weekly TikTok Studio CSV habit for Studio-only data. The agent drives every step; the human only approves browser consent screens.

Prerequisites check

  1. Call socials-mcp:connection_status. Skip any platform already ok: true.
  2. If a connect tool returns missing_app_credentials, walk the user through the matching guide (repo docs/):
    • YouTube → docs/onboarding-google.md (Google Cloud project, 3 APIs, OAuth desktop client)
    • Instagram + Facebook → docs/onboarding-meta.md (Meta app; IG Business/Creator account linked to a FB Page)
    • TikTok → docs/onboarding-tiktok.md (TikTok developer app, Login Kit scopes)
  3. Have them store credentials (they paste; never ask them to email or DM secrets): socials-mcp config set googleClientId <id> — or env vars (see AGENTS.md).

Connect flow (per platform)

  1. Tell the user: "A consent screen will open — approve it and come back."
  2. Call socials-mcp:connect_youtube / socials-mcp:connect_meta / socials-mcp:connect_tiktok. Each replies immediately: ✅ done, or ⏳ pending with the consent URL in the server log.
  3. After they finish in the browser, call socials-mcp:connection_status to confirm ok: true.
  4. connect_meta connects Instagram AND Facebook in one flow.

First data pull

  1. Call socials-mcp:snapshot (default 28-day lookback). Report per-platform row counts.
  2. For TikTok depth: ask for their weekly TikTok Studio export (Studio → Analytics → export video-stats CSV), then call socials-mcp:import_tiktok_csv with the path. Explain why: retention, traffic sources, search terms, and follower-hours are Studio-only — no official API exposes them; CSV is the compliant path.
  3. Verify with socials-mcp:top_content (days: 7).

Finish: build the creator profile

After the first snapshot, offer to build the tuning profile (socials-mcp:profile_get → if empty): auto-fill audience_summary from socials-mcp:audience_overview and content_series from socials-mcp:top_content patterns, then ask only the 4 human-only questions — niche, tone, goals, rate floor — and save with socials-mcp:profile_set. This is what makes every other skill sound like it knows the creator.

Weekly rhythm to establish

  • socials-mcp:snapshot once a week — history accrues forever in the vault
  • socials-mcp:import_tiktok_csv with the fresh Studio export (≈5 min/week)
  • The weekly-digest skill reads it all

Gotchas

  • Never ask for passwords; never automate the logged-in TikTok Studio session (ToS + account risk).
  • Expired tokens usually self-heal on the next snapshot (auto-refresh); if not, re-run the connect tool.
  • TikTok app review can take days — the app owner's own account works immediately.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free