Skip to content
cccskills
FreePublished on GitHub

connections-optimizer

Review X and LinkedIn relationships against current priorities. Receive ranked suggestions for accounts to remove, keep, or add, plus outreach drafts in your own voice for X, LinkedIn, or Apple Mail, ready for review.

OriginalShow the original description

Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice. Use when the user wants to clean up following lists, grow toward current priorities, or rebalance a social graph around higher-signal relationships.

Works withLinkedIn
See how to install

Good for

  • Reviewing X accounts to unfollow
  • Rebalancing LinkedIn relationships
  • Finding people to follow for current priorities
  • Drafting messages to reconnect with contacts

Files included (1)

  • SKILL.md5.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Connections Optimizer

Reorganize the user's network instead of treating outbound as a one-way prospecting list.

This skill handles:

  • X following cleanup and expansion
  • LinkedIn follow and connection analysis
  • review-first prune queues
  • add and follow recommendations
  • warm-path identification
  • Apple Mail, X DM, and LinkedIn draft generation in the user's real voice

When to Activate

  • the user wants to prune their X following
  • the user wants to rebalance who they follow or stay connected to
  • the user says "clean up my network", "who should I unfollow", "who should I follow", "who should I reconnect with"
  • outreach quality depends on network structure, not just cold list generation

Required Inputs

Collect or infer:

  • current priorities and active work
  • target roles, industries, geos, or ecosystems
  • platform selection: X, LinkedIn, or both
  • do-not-touch list
  • mode: light-pass, default, or aggressive

If the user does not specify a mode, use default.

Tool Requirements

Preferred

  • x-api for X graph inspection and recent activity
  • lead-intelligence for target discovery and warm-path ranking
  • social-graph-ranker when the user wants bridge value scored independently of the broader lead workflow
  • Exa / deep research for person and company enrichment
  • brand-voice before drafting outbound

Fallbacks

  • browser control for LinkedIn analysis and drafting
  • browser control for X if API coverage is constrained
  • Apple Mail or Mail.app drafting via desktop automation when email is the right channel

Safety Defaults

  • default is review-first, never blind auto-pruning
  • X: prune only accounts the user follows, never followers
  • LinkedIn: treat 1st-degree connection removal as manual-review-first
  • do not auto-send DMs, invites, or emails
  • emit a ranked action plan and drafts before any apply step

Platform Rules

X

  • mutuals are stickier than one-way follows
  • non-follow-backs can be pruned more aggressively
  • heavily inactive or disappeared accounts should surface quickly
  • engagement, signal quality, and bridge value matter more than raw follower count

LinkedIn

  • API-first if the user actually has LinkedIn API access
  • browser workflow must work when API access is missing
  • distinguish outbound follows from accepted 1st-degree connections
  • outbound follows can be pruned more freely
  • accepted 1st-degree connections should default to review, not auto-remove

Modes

light-pass

  • prune only high-confidence low-value one-way follows
  • surface the rest for review
  • generate a small add/follow list

default

  • balanced prune queue
  • balanced keep list
  • ranked add/follow queue
  • draft warm intros or direct outreach where useful

aggressive

  • larger prune queue
  • lower tolerance for stale non-follow-backs
  • still review-gated before apply

Scoring Model

Use these positive signals:

  • reciprocity
  • recent activity
  • alignment to current priorities
  • network bridge value
  • role relevance
  • real engagement history
  • recent presence and responsiveness

Use these negative signals:

  • disappeared or abandoned account
  • stale one-way follow
  • off-priority topic cluster
  • low-value noise
  • repeated non-response
  • no follow-back when many better replacements exist

Mutuals and real warm-path bridges should be penalized less aggressively than one-way follows.

Workflow

  1. Capture priorities, do-not-touch constraints, and selected platforms.
  2. Pull the current following / connection inventory.
  3. Score prune candidates with explicit reasons.
  4. Score keep candidates with explicit reasons.
  5. Use lead-intelligence plus research surfaces to rank expansion candidates.
  6. Match the right channel:
    • X DM for warm, fast social touch points
    • LinkedIn message for professional graph adjacency
    • Apple Mail draft for higher-context intros or outreach
  7. Run brand-voice before drafting messages.
  8. Return a review pack before any apply step.

Review Pack Format

CONNECTIONS OPTIMIZER REPORT
============================

Mode:
Platforms:
Priority Set:

Prune Queue
- handle / profile
  reason:
  confidence:
  action:

Review Queue
- handle / profile
  reason:
  risk:

Keep / Protect
- handle / profile
  bridge value:

Add / Follow Targets
- person
  why now:
  warm path:
  preferred channel:

Drafts
- X DM:
- LinkedIn:
- Apple Mail:

Outbound Rules

  • Default email path is Apple Mail / Mail.app draft creation.
  • Do not send automatically.
  • Choose the channel based on warmth, relevance, and context depth.
  • Do not force a DM when an email or no outreach is the right move.
  • Drafts should sound like the user, not like automated sales copy.

Related Skills

  • brand-voice for the reusable voice profile
  • social-graph-ranker for the standalone bridge-scoring and warm-path math
  • lead-intelligence for weighted target and warm-path discovery
  • x-api for X graph access, drafting, and optional apply flows
  • content-engine when the user also wants public launch content around network moves

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

accessibility

FreeSummary

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

  • Adding descriptive labels to icon-only buttons
  • Reviewing keyboard navigation and modal focus
  • Checking contrast and control sizes
affaan-m/ECC283.3KUpdated Oct 16, 2026

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

  • Investigating failures that appear only inside an agent application
  • Tracing old conversation content leaking into new sessions
  • Checking skipped or falsely claimed tool execution
affaan-m/ECC283.3KUpdated Oct 16, 2026

agent-eval

FreeSummary

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

  • Comparing coding agents on real development tasks
  • Evaluating a new tool or model before adoption
  • Checking performance after agent updates
affaan-m/ECC283.3KUpdated Oct 16, 2026

Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.

  • Define an AI agent’s tool set and input formats
  • Make tool results and next steps easier to interpret
  • Specify safe retries and stopping conditions
affaan-m/ECC283.3KUpdated Oct 16, 2026

Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.

  • Diagnosing repeated tool calls with no progress
  • Investigating quality loss as context grows
  • Checking file paths and environment mismatches
affaan-m/ECC283.3KUpdated Oct 16, 2026

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

  • Diagnosing repeated failures in an agent run
  • Investigating loops through the same tool calls
  • Reviewing output degradation as context grows
affaan-m/ECC283.3KUpdated Oct 5, 2026

See all skills by affaan-m

Report a problem with this skill