Receber por email
← Voltar para o catálogo

write-linkedin-post

Write or develop a LinkedIn post. Use ALWAYS for LinkedIn content - writing, drafting, developing ideas into drafts, or editing.

83estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add techwolf-ai/ai-first-toolkit

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/write-linkedin-post/svg)](https://www.skillteca.com.br/skills/write-linkedin-post)
#ai

Alerta por categoria

Receba novas skills de Escrita e Conteúdo toda segunda

1 email curto, só com as skills novas de Escrita e Conteúdo. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Write LinkedIn Post

You are helping write a LinkedIn post for the author.

Before Writing (MANDATORY)

You MUST complete these steps before writing ANY content:

  1. Run ./scripts/print-published.sh linkedin-post to read ALL published posts in one call
  2. This is critical to avoid repeating topics or angles already covered
  3. Note the core insights and data points already used
  4. Identify opportunities to reference or build on previous posts
  5. Pay attention to recent patterns (last 5-10 posts) to avoid repetitive structures, hooks, or phrases
  6. Read guidelines/linkedin.md for style rules
  7. Read references/professional-profile.md for background

If developing an idea-stage post: Check if the idea's core insight or data points overlap with published posts. If so, either:

  • Find a genuinely different angle
  • Explicitly build on the previous post ("In my last post I discussed X. Here's the flip side...")
  • Recommend against developing the idea

Avoid Repetitive Patterns

When reading recent posts, actively note and vary:

Hooks: If recent posts start with similar patterns, try a different structure Sentence patterns: Vary rhythm - don't always use short punchy sentences or always use longer flowing ones Closing lines: Don't repeat formulas Transition phrases: Rotate between "Here's what...", "The pattern...", "This matters because...", etc. Structure: If recent posts all use problem-solution-takeaway, try a different arc

The goal is a consistent voice with varied execution. Each post should feel fresh while still sounding like the author.

Style Requirements

  • Target word count per guidelines/linkedin.md (typically 150-250 words)
  • Personal hook first (under 210 characters before "see more")
  • Specific > abstract
  • Conversational tone
  • No hype words ("revolutionary", "game-changing")

Hook Priority

  1. Personal anecdote
  2. Company experience
  3. Surprising outcome
  4. Counterintuitive framing

Process

  1. If given a topic, develop it into a draft
  2. If given an existing idea file (search with ./scripts/search-posts.sh), develop the content
  3. Always check word count against target
  4. Save to content/posts/ with type: linkedin-post, stage: 02-drafts

Validation

After saving the draft, run the word count checker:

scripts/check-word-count.sh <yaml-file>

Adjust the content if the word count is outside the 150-250 target.

Sub-Agent Review

Before presenting the final draft, spawn a sub-agent to review with fresh eyes. The reviewer should:

  • Check voice consistency against guidelines/linkedin.md
  • Verify the hook works in the first 210 characters
  • Flag any overlap with recently published posts
  • Check for hype words or generic phrasing

Incorporate the reviewer's feedback before finalizing.

Creating New Files

Get timestamp first:

date -u +"%Y%m%d-%H%M%S"  # For slug
date -u +"%Y-%m-%dT%H:%M:%S.000Z"  # For created/lastUpdated
Compartilhar X LinkedIn