SuperAPI AI Directory

post

Writing & research

View repository

Updated 10-15 21:03

About this skill

Post

The skill's task is to write or strengthen a short post with one clear idea. A post rests on the first movement of attention, a dense body, and an ending that leaves meaning, action, or a twist.

The method is based on the practices of Lyudmila Sarycheva (gladlax.ru) and was assembled together with Nikita Arkhipov (niar42.com).

Step 0. Context

If the project has a file .agents/redpolitika.md — read it first: it contains the project's audience, register, vocabulary, and factual supports. If there is no file and the user is writing for a permanent project, suggest creating it with the skill redpolitika.

Find out at minimum:

  • platform: Telegram, LinkedIn, Instagram, another social network;
  • who the reader is;
  • one idea of the post;
  • source material: article, note, news, observation, story, announcement;
  • what the reader should feel, understand, or do;
  • constraints: length, prohibited topics, mandatory facts, links, CTA, tone.

The default register is authorial: lively, concrete, with a position. If the task is business, branded, or cautious, adapt to the editorial policy and platform.

Take facts only from the user's message, attached materials, or editorial policy. Do not invent dates, numbers, quotes, names, results, or links.

Modes

  • draft — write a post from scratch or from a large amount of material.
  • rewrite — rewrite a finished post, the first line, the ending, or the density of the text.

If the user asks “the first line doesn't hook,” work in mode rewrite and focus on the hook.

Process

  1. Formulate one idea: references/odna-mysl.md.
  2. Choose a hook: situation, statement, question, conflict, observation, short intrigue — references/khuk.md.
  3. Assemble the body: example, explanation, turn, conclusion — references/telo-i-final.md.
  4. Check the platform and register: references/ploshchadki.md.
  5. Read aloud: remove repetition, loose introductory phrases, generic words, an unnecessary second thought. 5a. Clean out traces of the neural network — they are immediately visible in a short post. Check every pattern:
    • antitheses "not X, but Y" — in a post of up to 1000 words, at most one and never as the first line of a paragraph; keep factual negations and limitations; turns like "this is about…" / "this is not about…" — are completely forbidden;
    • choppy verdict phrases for weight: "The symptom is familiar.", "This is a signal.", "Sound familiar?";
    • evaluative announcements and pointers: "An honest caveat", "An important nuance", "The most interesting thing is …", "And here's what's important" — remove the label and state the content right away;
    • a bow-like metaphor in the finale ("like a little time capsule");
    • a question and the answer to it yourself, triples of homogeneous items on autopilot, a staccato of short sentences for weight. The full catalog of neural network traces — ../redaktura/references/neirotekst.md; analyze judgments without substance using otsenki.md, clichés using shtampy.md in the same folder (if the set is installed in full).
  6. Check the finale: it should close the thought, invite action, or give the reader new support.

If the user gives a long article and asks for a post, don't retell everything. Choose one idea, one example, and one conclusion.

Response format in draft mode

## Бриф
Площадка:
Читатель:
Одна мысль:
Фактура:
Действие:
Регистр:

## Пост
...

## Почему так
- ...

## Что ещё нужно узнать
- ...

The post itself usually doesn't need subheadings, a table of contents, or the large structure of an article. The exception is a list, checklist, or announcement, where the format helps to read the post.

Response format in rewrite mode

## Диагноз
...

## Варианты первой строки
1. ...
2. ...
3. ...

## Переписанный пост
...

## Почему так
- ...

If the task concerns only the first line, don't rewrite the whole post unnecessarily. Give 3–5 hook options and briefly explain the difference.

Quality criteria

  • The post has one main idea.
  • The first line gives a reason to read further.
  • The body rests on a fact, scene, example, or observation.
  • The finale completes the thought.
  • There is no mechanical retelling of a large article.
  • There are no subheadings or table of contents where a lively short post is needed.
  • Facts are not invented.
  • No concentration of neuropatterns: contrasts, triples, pseudo-depth.
  • The register matches the author, platform, and editorial policy.

Related skills

  • redaktura — final editing of a finished post.
  • redpolitika — the project's voice, vocabulary, audience, and editorial rules.
  • statya — articles, longreads, expert materials.
  • promo — landing pages, promo pages, about-me texts, press releases.
  • ux-copy — interface texts, forms, errors, empty states.