Skip to content

sergebulaev/linkedin-skills

linkedin-marketing

Verified

Plan, draft, audit, and publish LinkedIn posts and comments. Use when the user wants to write a viral LinkedIn post, draft a comment or reply on any LinkedIn post URL, audit a draft against 2026 algorithm heuristics, remove AI tells, extract hook formulas from viral posts, or plan a week of content. Powered by the Publora API for publishing. User provides post/comment URLs, skill drafts content, user approves, then publishes.

references/voice-profile.md

View on GitHub
# Voice & Brand Profile

Your voice, niche, and rules in one place. Fill this once (or let
`linkedin-humanizer` build it from a few of your real posts), and every writing
skill in this bundle reads it before drafting, so you stop re-explaining who you
are on every request. This file is yours: edit it freely, keep it as long or
short as you like. Nothing here is sent to us or to any service; it only steers
the drafts.

> **It is a file in this repository, though, so git can carry it.** If you
> cloned or forked this repo and you push, a filled profile goes wherever you
> push it, including a public fork. Either add `references/voice-profile.md` to
> your `.gitignore`, or keep the filled copy outside the repo and paste it in
> when you need it. The shipped template is empty; what you add is yours to
> protect.

Skills only load this profile when `filled: yes` below. An empty template is
ignored, so drafts fall back to the generic voice rules until you populate it.

## Status

- filled: no
- source: template
- updated: --

## 1. Voice fingerprint

How your writing actually sounds. Be specific; examples beat adjectives.

- Sentence rhythm: (e.g. mostly short, one long every few lines; or steady medium)
- Signature openers: (lines/phrases you tend to start with)
- Punctuation habits: (e.g. you use `..` as a soft pause; you never use em dashes)
- Words and phrases you use a lot:
- Words and phrases you NEVER use: (banned vocab, cliches you hate)
- Emoji: (none / one occasionally / which ones)
- Formatting: (one idea per line? lists? no hashtags?)

## 2. Who you are and who you write for

- You are: (role, what you build/do, one line)
- Your audience (ICP): (who you want reading and engaging)
- Your content pillars: (2-4 recurring themes you post about)

## 3. Hard rules (always / never)

- Always: (e.g. one concrete number per post; first-person; end on a real question)
- Never: (e.g. no engagement-bait, no "in today's fast-paced world", no naming competitors)

## 4. Links and CTA

- Primary link you point people to:
- Where it goes: (in the first comment, in bio, etc.)
- Your CTA style: (soft invite / direct ask / none)

## 5. Signature examples

Paste 2-4 of your own real lines or short posts that sound most like you. The
writing skills mirror the rhythm and word choice of these, not a generic voice.

-
-
-

## 6. Brand assets (for illustrations)

Used by the illustration step (`lib.illustrate`) to keep every generated image
on-brand via a pixel-exact overlay. All optional; leave blank to skip the overlay.

- Handle to stamp on images: (e.g. @yourname)
- Brand color (hex): (e.g. #0A66C2)
- Logo: (path or Pixfaro `logo_id`, if you have one — a path can be uploaded
  once with `lib.brand_logo(path)`, which returns the `logo_id` to record here)
- Overlay position: (e.g. bottom-right)
- Visual style default: (e.g. minimal flat vector; bold editorial; muted photo)
- Card style: (quote-card `style` — "brand", "auto", or a fixed palette/font)
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall