Translation editorial

Skill dzhokhov/markdown-agent-vault/skills/translation-editorial

Agent-ready Markdown vault methodology with AGENTS.md, templates, skills, logs, and file-safe workflows.

Install

npx -y skills add dzhokhov/markdown-agent-vault --skill translation-editorial

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

SKILL.md

2.1 KB, as published. Nobody here has run it

Translation and Editorial

Navigation: Skill index

Overview

Convert technical inputs into understandable application content:

without jargon,
with a clear practical effect,
with 7-day action.

Skill is responsible for the signal -> message map -> card/post -> editorial QA phase.

Workflow

1) Pick Audience

Assign primary audience:

entrepreneur
operator
specialist

If the audience is mixed, select one primary and specify secondary.

2) Build Message Map

For each signal / case, fix 5 reference points:

What happened (fact)
What does it change in work (mechanics of effect)
For whom it is useful / risky
What to do in 7 days
What not to do

3) Produce Artifacts

Use the templates from card-templates.

Minimum:

Short card (for digest)
Blog block (expanded paragraph)

4) Editorial QA

Run the checklist out editorial-checklist.

If there is a complicated term, add a short explanation at the practice level.

Output

Return 2 blocks:

Digest Card
Blog Paragraph

For each block, indicate:

primary audience
actionable

Quality Gates

The main idea is clear from the first 2 sentences.
There is no objectless revolution/breakthrough evaluation without mechanics.
There is a specific step for 7 days.
There's a "what not to do" block.
There is no internal contradiction with the original signal.

Anti-Patterns

Do not retell changelog instead of applied meaning.
Don't write "for everyone."
Do not publish without a specific next step.
Do not inflate the format: one card = one central thought.