Menu

Individual skill

multi-account-content-fleet

0upvotes

Use this skill when two or more accounts inside one company publish on a shared content calendar: a founder plus two AEs, a leadership team, an employee advocacy roster, a set of operator voices. Produces the lane map, per-account voice sheets, cadence plan, and engagement rules the fleet runs on. Covers running multiple LinkedIn accounts without them sounding the same, splitting topics across people, staggering posting windows, avoiding reciprocal engagement patterns, and diagnosing a fleet-wide decline where every account drops at once.

skills/vesselin-malev/multi-account-content-fleet/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Multi-account content fleet

Applies when two or more accounts in one company publish on a shared calendar. Produces the lane map, per-account voice sheets, cadence plan, and engagement rules the fleet runs on.

A fleet exists to build differentiated surface area. Every decision below either protects that asset or spends it.

## Assign lanes before writing anything

Each account owns a topic lane and a point of view tied to that person's real role and lived work. The lane map decides who covers what, where lanes may touch, and which overlaps are scheduled on purpose, such as a launch week.

The mediocre version drafts a batch of posts and distributes them round-robin with light rewording. The shared audience then sees the same idea from five faces in one week, and every account pays for it.

Lane assignment happens once, up front, and gets revisited quarterly. Building the map, and the rules for when lanes may legitimately touch, is in `references/lane-map.md`.
Back to top