Skip to content
Skills Library
Marketing & content · Writing

plain-post

/plain-post

Review, rewrite or interview towards a public post or web page that earns the reader's attention without hype or engagement bait. Use for posts, articles and web copy.

Licence
MIT
Last repository change
29.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Review, rewrite or interview towards a public post or web page that earns the reader's attention without hype or engagement bait. Use for posts, articles and web copy.

Original author description

Review, rewrite or interview towards a public post or web page that earns the reader's attention without hype or engagement bait. Use for posts, articles and web copy.

How it works

  1. The rules
  2. Public posts and web pages
  3. Review
  4. Rewrite
  5. Interview
  6. House formatting
  7. What you must not do
Original SKILL.md headings · 100 lines, 1,212 words
SKILL.md preview
---
name: plain-post
description: Review, rewrite or interview towards a public post or web page that earns the reader's attention without hype or engagement bait. Use for posts, articles and web copy.
---

# Plain Post

You do not need to install anything to try this once. Copy this whole file, paste it into any AI chat, then paste your text underneath. The lines between the dashes at the very top are just this file's label. Leave them in.

This skill reviews or rewrites a public post or web page so the first line earns the second, and the piece says something only the writer could say. It can also interview the writer first.

## The rules

These apply to every kind of writing.

1. **Write for one reader.** Picture the person. Say it the way you would say it to them across a desk.
2. **Put the point first.** Start with what the reader needs most, then give the support.
3. **One idea to a sentence.** Break the long sentence. A reader should not have to hold a clause open while they wait for its end.
4. **Use the short, everyday word.** "Use", not "utilise". "Help", not "facilitate". Jargon only when your reader uses it themselves.
5. **Cut what does no work.** If a sentence still works without a word, cut the word. If the piece still works without a sentence, cut the sentence.
6. **Name who did it.** Put a person in the sentence. "I sent the proposal", not "the proposal was sent".
7. **Drop stock phrases and filler.** Openers and sign-offs that say nothing, and metaphors you have read so often you no longer see them.
8. **Be specific enough to be checked.** Name the person, the number, the date. If you do not know, say what you do not know. Never invent a detail to fill a gap.
9. **Keep real uncertainty and cut the rest.** A hedge that honestly marks what you are unsure of stays. A hedge that hides a claim goes.
10. **Say how two things relate.** Use "because", "although", "so" or "once". Do not leave the link to the rhythm of two sentences side by side.
11. **Claim no more than you know.** Do not turn an impression into a result, a reading into a fact, or two things that happened together into one causing the other.
12. **Break any rule before you write something clumsy.**

## Public posts and web pages

The reader chose nothing. They are scrolling, and they will leave after one line unless that line earns the next.

- **Make the first line earn the second.** Open with a fact, a number, a scene or a claim. Do not open with a greeting, a definition, or how you feel about sharing.
- **Make one claim someone could argue with.** A subject lets you ramble. A claim makes you do the work.
- **Say something only you could say.** A detail you saw, a number you measured, a mistake you made. If the paragraph could appear nearly word for word in anyone else's post, it is filler.
- **Keep the cost of being wrong visible.** Say what is a finding, what is a guess, and what you tried only once.
- **No engagement bait.** Do not end by asking for comments, likes or follows.
- **No hype openers.** "Thrilled to announce", "humbled", "in today's fast-paced world".
- **Few hashtags and few emojis,** and only where they help a reader.
- **Stop where the thought stops.** If the point is made, end. Do not add a quotable line.

## Review

Use this when the person wants a critique and wants their text left alone.

Reply with these four parts, in this order:

1. **Does it do its job?** Two sentences: who the reader is, and whether this text gives them what they need.
2. **What to change.** The seven changes that would help the reader most, most important first. For each one, quote the exact words, say in one sentence what is wrong, and say what to do instead. Do not rewrite the text.
3. **What already works.** One or two things to keep.
4. **What I could not tell.** Any facts you would need from the writer to judge a sentence. Ask for them. Do not guess.

If the text is already clear, say so and stop. Do not invent faults to look useful.

## Rewrite

Use this when the person wants an edited version.

Reply with the rewritten text first, then three short parts:

1. **What I changed.** A short list.
2. **What I kept on purpose.** Hedges that mark real uncertainty, figures, names, and any sentence that was rough but sounded like the writer.
3. **What I need from you.** Anything missing, written as a question. Never fill a gap with an invented fact, number, name or date.

A rewrite changes how the text reads and leaves what it claims exactly where it was. After you rewrite, check that the new text keeps the original's scope, certainty, emphasis and cause. If a clearer sentence would claim more than the original did, keep the weaker claim. Keep the writer's voice. Smoothing a rough sentence into a bland one is not an improvement.

If the person does not say which mode, ask once: "Review it, or rewrite it?"

## Interview

Use this when the person has an idea but no draft, or only a thin one.

Ask up to five questions, one at a time, and wait for each answer before you ask the next:

1. Who is the reader, and what do they already know?
2. What should they believe or do when they finish?
3. What is the one claim you would stand behind?
4. What detail, number or story do only you have?
5. What is the strongest objection, and where is your position weak?

Then draft from what they told you. Use only their words and facts. Where something is missing, write "[ASK: ...]" in the draft and say what you need. Do not invent a detail to make the draft read better.

## House formatting

These are the author's own preferences, not rules of good writing. Apply them only if the person asks for "house formatting" or asks for these rules by name. Otherwise leave their formatting alone.

- No em dashes. Use a comma, a colon or a full stop.
- Straight quotes and apostrophes only. No curly ones.
- Dates with an ordinal suffix, day first: 21st May, 3rd July.
- Spell out numbers one to nine in prose. Use numerals for 10 and above.
- Percentages in numerals: 95%, not ninety-five per cent.
- Currency in full figures: £18,000, not £18k or eighteen thousand pounds.
- No emojis in writing for customers.
- No headings inside an email.
- Sign off an email on two lines: "Best," then the name.

## What you must not do

- Never invent a fact, number, name, date or quote. If something is missing, ask for it.
- Never make the writing sound more certain, more complete or more important than the original did.
- Do not praise the writer or pad your reply. Follow these rules in your own reply too.
- If the text is not what this skill is for, say so in one sentence, then use the general rules above.
- If the text is too thin to judge, ask for what you need and stop.

Versions

The database has no other skills named plain-post.

Database snapshot: 13.11.2026 · package version 9fd1dbb56152 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100x-post
    Write a single X (Twitter) post, quote post or reply that earns attention on its own. Covers hooks, the 280-character edit, quote and reply tactics, algorithm signals and a pre-post checklist. Use for "write a tweet", "draft an X post", "quote tweet", "reply to this post". For…
  • 86launch-post
    Use when announcing a product, a project or a release in a post or on a manual page.
  • 85linkedin-posts
    When the user wants to create LinkedIn post copy or optimize for LinkedIn. Also use when the user mentions "LinkedIn post," "LinkedIn article," "professional post," "post to LinkedIn," "LinkedIn content," "LinkedIn copy," "B2B LinkedIn," "LinkedIn engagement," "LinkedIn feed,"…
  • 100fb-post
    Write a Facebook post or Reel caption - the line that survives the "See more" cut on mobile, the body, the single ask, links handled properly, no engagement bait - and lint it before it goes out. Use when the user says "write a Facebook post", "caption this for Facebook", "post…
  • 100research-to-post
    Turn a paper, PDF, arXiv/DOI, GitHub repo, or project page into 2-3 short, catchy X/Twitter hook posts in plain language, plus a simple copy-first HTML card. Use when the user wants a creative post about a paper or repo, not a technical summary. No claim ledger, no verification…
  • 100seo-article
    Plan and write a blog article meant to rank in Google for a keyword. Use when the user gives a keyword or topic and asks for a blog post, SEO article, "content that ranks", or to rewrite an existing post for search.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.