agentleFS
MuvonMuvon/octomind-tap/skills/browser-social-account-maintenance/SKILL.md

browser-social-account-maintenance

Skill6 starsChanged 8 months agoApache-2.0View on GitHub

Recurring social account upkeep via headless browser: bio sync, cross-posting, post audits, follower cleanup. Use for maintenance, not new copy.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If diff is empty → log noop and skip.

    line 81
  2. Very specific:

    If schedule is a future timestamp, use the platform's native scheduler.

    line 110
  3. Distinctive:

    Always present sample + count + irreversible-warning, ask user to confirm.

    line 158
  4. Distinctive:

    If confirmed: action one by one, ≥ 2 s spacing, screenshot per action, log.

    line 159
  5. Distinctive:

    Stop on any platform error or rate-limit warning.

    line 160
  6. Distinctive:

    Use existing browser sessions if available.

    line 164
  7. Distinctive:

    Never persist cookies or tokens to disk after the run.

    line 166

≈ “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

Overview

Drive recurring social-account operations across X, LinkedIn, Mastodon, Bluesky, Threads, Instagram, YouTube, TikTok, Reddit and similar — when the work is mechanical hygiene, not voice work. The skill covers six operations: profile sync, cross-post, scheduled-post audit, follower/connection cleanup, notification triage, archive/delete.

This skill explicitly does NOT write new posts. New copy is supplied as input; this skill takes already-written copy and ships it.

Mental model

Treat each social network as a target with three things: (1) a profile surface (display name, bio, links, avatar, banner), (2) a publish surface (compose box / scheduler), (3) an admin surface (followers, notifications, archive). Every operation is the same loop: read current state → compare to spec → drive the UI to converge → screenshot → log. Per-platform quirks live in a small lookup table; the loop stays identical.

Three immovable invariants:

  1. One source of truth per operation. Profile sync reads profile.json; cross-post reads post.json; cleanup reads cleanup-rules.json. Never invent values; never paraphrase the user's bio.
  2. Confirm-before-destructive. Delete, unfollow, archive, mass-block — confirm the count and a sample with the user before executing, even if the rules file says "auto".
  3. Per-platform compliance > convenience. X 280-char limit, Bluesky 300, Mastodon CW conventions — honor each. If a piece doesn't fit, log and skip that platform; do NOT silently truncate.

Platform automation terms bound every operation. LinkedIn's User Agreement (section 8.2) bans bots and browser automation of on-site activity, X prohibits bulk or automated following and unfollowing, and Meta's terms bar accessing or collecting Instagram data by automated means without permission — driving these with a browser risks restriction of the user's account. Before the first action on such a platform, tell the user that risk once and get their yes; keep every action user-confirmed and human-paced. Prefer official channels where they exist: native schedulers, the X API, LinkedIn's posting API, the Threads API, and the open Bluesky (AT Protocol) and Mastodon APIs, which permit disclosed automation.

Rules

Per-network compose limits and quirks

NetworkCompose limitLink handlingImage / videoNotes
X (Twitter)280 chars (free) / 25k (premium)Counts as ~23 chars4 imgs / 1 video / 1 GIFThreads: post 1, then reply with 2..N to own root
LinkedIn3000 chars; ~210-char "see more" foldThird-party studies measure lower reach for posts with external links (estimates vary widely; LinkedIn has not confirmed a penalty)Multi-image / 1 video / documentPersonal profile vs page have different composers
Mastodon500 chars (instance default; varies)No penalty4 imgs / 1 videoCW (content warning) is a culture norm, not optional for sensitive content
Bluesky300 charsNo penalty4 imgs / 1 videoThreads via reply-to-self
Threads500 charsNo penaltyUp to 20 imgs/videosCross-post toggle to Instagram exists
InstagramCaption 2200 chars; bio 150 charsUp to 5 bio links (only the first shows); caption URLs aren't clickableUp to 20 items per carousel; Feed / Reels / Stories separate composersWeb composer supports feed posts and Reels; Stories need the app
YouTube (community / Shorts metadata)Community 500 charsURLs allowedN/A for communityUse Studio composer, not the consumer site
RedditTitle 300 / body 40kAllowed; subreddit rules varyImage galleries or 1 video per postNEVER mass-post; subreddit-by-subreddit only
TikTokCaption 2200 charsBio link onlyVertical video recommended; photo posts supportedCaptions accept hashtags, no clickable URLs

Operation 1 — Profile sync

Input: profile.json source-of-truth.

{
  "display_name": "Jane Doe",
  "bio": "Building things. Writing things.",
  "bio_per_platform": { "x": "...", "linkedin": "..." },   // optional override
  "links": ["https://janedoe.com"],
  "location": "Berlin",
  "pronouns": "she/her",
  "avatar_path": "./assets/avatar.png",
  "banner_path": "./assets/banner.png",
  "platforms": ["x", "linkedin", "mastodon", "bluesky", "threads"]
}

For each listed platform:

  1. Open settings / edit-profile route.
  2. Read current values.
  3. Diff against spec; build a change set.
  4. If diff is empty → log noop and skip.
  5. Apply changes one field at a time; verify each landed.
  6. Save, screenshot the post-save profile page.
  7. Log row: { platform, fields_changed, status, screenshot_path }.

Per-platform bio cap: truncate ONLY if the user supplied bio_per_platform.<platform>; otherwise skip platforms where the bio doesn't fit and log skipped:bio-too-long.

Operation 2 — Cross-post

Input: post.json — one piece, multiple targets.

{
  "platforms": ["x", "linkedin", "mastodon", "bluesky"],
  "variants": {
    "x": { "text": "...", "thread": ["...", "..."] },
    "linkedin": { "text": "...", "link_in_first_comment": "https://..." },
    "default": { "text": "...", "link": "https://..." }
  },
  "media": ["./assets/img1.png"],
  "schedule": "now" | "2026-05-10T18:00:00Z"
}

Per platform:

  1. Pick variant (variants[platform] else variants.default).
  2. Validate length against the table above. If too long and no platform variant is given → skip, log skipped:length.
  3. Open native composer (NOT a third-party scheduler unless the user specified one).
  4. Paste text; attach media; for LinkedIn, post link in first comment if link_in_first_comment set.
  5. If schedule is a future timestamp, use the platform's native scheduler; if now, publish.
  6. Capture the published-post URL (or scheduled-post id) — this is critical evidence.
  7. Log: { platform, post_url, scheduled_for, status, char_count, screenshot_path }.

For X threads: post root, capture URL, then post each reply against the captured root URL. If any reply fails, stop the thread (do not orphan replies).

Operation 3 — Scheduled-post audit

Pull the platform's scheduled queue, output a table: {platform, scheduled_for, preview, length, has_media, post_id}. Do not modify anything; this is a read operation. User decides what to delete / reschedule; if they say "execute the deletes" the skill confirms count + sample first.

Operation 4 — Follower / connection cleanup

Input: cleanup-rules.json.

{
  "platform": "x",
  "criteria": [
    { "field": "last_post_age_days", "op": ">", "value": 365 },
    { "field": "has_default_avatar", "op": "=", "value": true },
    { "field": "follower_count", "op": "<", "value": 5 },
    { "field": "bio_contains_any", "op": "in", "value": ["crypto signals", "DM for promo"] }
  ],
  "logic": "any | all",
  "action": "unfollow | block | mute | report",
  "max_actions": 50,
  "dry_run": true
}

Always start with dry_run: true regardless of input — produce a candidates list with reasons. Then ask the user to confirm before running with dry_run: false. Cap actions per session at 50 even if max_actions is larger; rate-limit one action per ~3 seconds; abort on first rate-limit warning from the platform. On X and LinkedIn, automated unfollowing is itself against the platform rules: default to handing the user the reviewed candidate list to act on, and drive the UI only on their explicit per-batch instruction.

Operation 5 — Notification triage

Input: triage-rules.json — patterns + intent (reply / like / archive / ignore).

For each notification:

  • Match against rules.
  • intent: reply → DO NOT compose here; collect into a queue and return it in the final report so the replies can be drafted upstream. This skill never writes the reply text itself.
  • intent: like → click like, log.
  • intent: archive / ignore → mark read, log.

Operation 6 — Archive / delete old posts

Input: archive-rules.json — age threshold, keyword excludes, platform.

  1. Page through user's post history.
  2. Build candidate list: {post_url, posted_at, preview, engagement, matches_rule}.
  3. Always present sample + count + irreversible-warning, ask user to confirm.
  4. If confirmed: action one by one, ≥ 2 s spacing, screenshot per action, log.
  5. Stop on any platform error or rate-limit warning.

Auth and session hygiene

  • Use existing browser sessions if available. If a platform requires login mid-run, prompt the user once for that platform and continue.
  • 2FA: prompt the user; never attempt to bypass.
  • Never persist cookies or tokens to disk after the run.
  • One identity per run. Don't switch accounts mid-operation.

Output artifacts

Write to ./out/social/<operation>/<UTC>/:

  • log.json — one row per platform/action.
  • <platform>-before.png and <platform>-after.png for sync/cleanup ops.
  • <platform>-published-<post_id>.png for cross-post ops.

Examples

Example 1: Bad → Good (cross-post length handling)

❌ Bad:

The post is 480 chars. For X, truncate silently to 280 and add an ellipsis. Move on.

✅ Good:

For X, the post is 480 chars and no x-variant was supplied → log `skipped:length` for X, continue with the other platforms,
report at the end: "X skipped — supply variants.x or shorten to ≤ 280 chars."

What changed: silent truncation publishes broken posts in the user's name.

Example 2: Edge case — LinkedIn link-in-first-comment

LinkedIn's treatment of links (in the body or the first comment) is unconfirmed and studies disagree, so follow the user's spec: if variants.linkedin.link_in_first_comment is set, post the body without the URL → capture the post URL → add the link as the first comment from the same account → screenshot. Log both actions in one row.

Example 3: Edge case — cleanup dry-run

User says "unfollow all bots, do it now." Skill still runs dry_run: true first, returns: "Found 117 candidates by your rules. Sample: @x, @y, @z. Confirm to execute (will action max 50 this session, ~3 s spacing)." Only after explicit confirmation does the skill execute.

Checklist

  • Inputs validated — profile.json / post.json / cleanup-rules.json / triage-rules.json / archive-rules.json exists and required fields are present
  • Authenticated session confirmed for every target platform; 2FA prompts handled by the user
  • Per-platform compose limits checked BEFORE driving the UI; over-limit posts skipped with a skipped:length row, not truncated
  • Destructive operations (delete, unfollow, block, archive) ran a dry-run first and got explicit user confirmation
  • Each action has evidence: post URL captured for publishes, screenshots for profile/cleanup, log row for everything
  • Platform automation terms respected: account-restriction risk stated and accepted for LinkedIn / X / Meta platforms, official APIs or native schedulers used where available
  • Rate limits honored: ≥ 2 s between actions, ≤ 50 destructive actions per session, abort on platform warning
  • Reply / comment composition was NOT done inside this skill — the reply queue was returned in the report
  • No credentials, cookies, or tokens persisted to disk after the run
  • Final report: per platform, what changed, what was skipped (with reason), what failed (with reason), artifact paths

Composition / References

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.