本文へ移動
cccskills
無料GitHub で公開

connections-optimizer

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology. Defines scope, samples representative pages and flows, runs the automated tier (`accessibility-scan`) and the hands-on manual tier (`accessibility-inspect`), and produces one conformance report. Grades each finding by severity and evidence basis, and states per-criterion conformance as pass, fail, or undetermined (needs a human). Use it for 'audit my site for accessibility', 'is this product accessible', 'a11y audit', 'WCAG or Section 508 conformance report', or any multi-page assessment. Assesses; does not fix (use `accessibility-fix`) or diff (use `accessibility-diff`). For a single page use `accessibility-scan`; for hands-on keyboard and screen-reader checks use `accessibility-inspect`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Regression check — diff a live page's web accessibility (a11y) violations against a baseline. By default it compares your uncommitted changes (stash-based); pass `--branch [<name>]` to compare against a branch. Reports the new WCAG violations introduced, the ones fixed, and the count of pre-existing ones. Use it for 'did my change break accessibility', 'what a11y issues did this PR add', or as a CI gate. For a full scan of one page use `accessibility-scan`; for a whole site use `accessibility-audit`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop. Takes a target (URL, files, directory) or a findings worklist from `accessibility-scan`/`accessibility-inspect`/`accessibility-audit`, applies mechanical fixes as given, leaves TODOs for visual or contextual judgment, and verifies by re-running the baseline check. It only fixes. To find issues use `accessibility-scan` (one page, automated), `accessibility-inspect` (one page, manual), or `accessibility-audit` (whole site, WCAG-EM); to check for regressions use `accessibility-diff`. Use it for 'fix the a11y issues in X', 'make this accessible', 'add missing alt text and labels', 'apply these accessibility fixes', 'remediate these violations'.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

tensology のスキルをすべて見る

このスキルの問題を報告する