LinkedIn Posts

Prioritize clarity, precision, and usefulness. Preserve the author's voice; the text should be publishable without explanations about how it was written.

Writing and formatting

• When describing security tests, use “a controlled environment” (and “un entorno controlado” in Spanish), rather than dev/staging.

• Open with the fact or idea that is worth telling. Avoid grandiose headlines, filler questions, and promises the content does not demonstrate.

• Use short paragraphs separated by blank lines. To list items, use simple bullets such as "•" and one idea per line; do not force a list if the text reads better in prose.

• The body of a post is plain text: do not paste Markdown headings, bold asterisks, Markdown-syntax links, or code blocks. Keep technical identifiers legible without typographic embellishments that make them hard to copy.

• Use real line breaks, never literal sequences such as "\n". Avoid Unicode alphabets that simulate bold or italics. Emojis are optional and should provide guidance, not replace content.

• Explain exactly what the reader can do and under what condition. Distinguish between viewing, downloading, installing, and pinning versions when these are different actions.

• If the post refers to an article, present one useful idea and leave the development to the article. Do not turn the post into a copy or an empty announcement.

• Include a concrete call to action when it makes sense and a relevant link. Do not invent benefits, results, metrics, or pending features.

• Use few hashtags, relevant and without duplicates, preferably at the end. Do not add unrelated popular tags or claim that a guaranteed reach formula exists.

Bilingual posts

When several languages are requested, deliver each version in a complete block and separate them with a neutral divider such as “──────────”, with a blank line before and after. Do not use language labels such as “English”, “Español” or “— English —”, or headings announcing the translation. Keep the same meaning, links, and conditions; adapt expressions naturally. Do not alternate the translation sentence by sentence. Avoid duplicating common hashtags.

Reviewing on LinkedIn

Check the visible opening, spacing, bullets, links, and language separation in the editor or the actual preview. Verify that the link card matches the destination and that images are legible on mobile. If you publish or edit with authorization, reread the saved result; a click or a success message does not replace that check.

Drafting a post does not authorize publishing it. Respect the authorization received and confirm the date, time, and time zone when scheduling a post. Do not edit posts outside the assignment.

Learning from corrections

Before modifying an existing text, read its current version to preserve the author's manual changes. Compare the corrections with the draft and extract only the reusable criterion.

Incorporate new corrections into the corresponding rule instead of accumulating exceptions or conversation transcripts. Distinguish a preference for that post from a general guideline. Remove redundant rules or rules that contradict later decisions.

Keep this skill generic: do not store names, accounts, post links, client data, credentials, or identifiable examples. Record editorial criteria, not the private history of whoever originated them.

Length, icons and mobile readability

Keep the entire post around 150–220 words, with roughly 250 words as an editorial ceiling rather than a target. Count both languages together. Leave explanations and examples in the linked resource; bilingual posts need shorter versions, not two full articles. Check visual height on mobile as well as word count, since links, lists and hashtags also take space.

Use two to five relevant icons across the whole post when they guide reading. Five is the maximum, not a quota. Do not decorate every sentence or repeat icons throughout the translation. Use fewer when they add no value.

Verify real blank lines in the native editor before saving. Separate paragraphs and links with empty paragraphs; consecutive paragraphs without visible spacing do not meet this requirement. If multiline pasting collapses spacing, insert the blank paragraphs using the editor itself.