Medium Writer

Medium Writer

Goal

Help an author turn original experience, expertise, notes, research, or a defensible idea into a Medium-native story that rewards the reader's time.

This skill reuses the parent writer workflow for fact checking, source discipline, humanization, local images, and optional Cloudflare R2 delivery, but it does not treat Medium as a generic SEO blog, a LinkedIn article host, or an automated content-distribution channel.

Medium-native work prioritizes:

• a clear reason this author should tell this story;
• an original insight, experience, experiment, case, or synthesis;
• a title, subtitle, and preview image that accurately represent the story;
• narrative movement and section-to-section continuity;
• reader value over traffic capture, product promotion, or keyword coverage;
• relevant Medium Topics and a realistic Publication fit;
• transparent AI assistance and image labeling;
• a publishing pack separated from the public story.

Default language follows the user's request. Medium's current distribution guidance treats English and non-English stories differently, so record the target language and do not imply equal eligibility for General Distribution or Boost without current verification.

Platform Routing

If the user says only “Medium article,” default to a Medium story published from the author's profile. Recommend a Publication only after checking its current theme, submission rules, open status, and story fit.

Required References

Read every relevant file completely before acting:

• Medium search, Topic discovery, current topic seeds, and Publication research: references/medium-topic-research.md
• New story, rewrite, or reusable result format: references/medium-article-template.md
• Editorial review, distribution readiness, and revision gate: references/medium-review-rubric.md
• Current claims, comparisons, or fact-heavy subjects: ../references/fact-check-and-style.md
• Final natural-language edit after factual and structural revision: ../references/humanization.md
• Local images, file packaging, and optional R2 delivery: ../references/output-packaging.md
• R2 upload tasks only: ../references/r2-image-upload.md and ../references/r2-security.md

Do not load unrelated references merely because they exist.

Medium AI Authorship and Disclosure Boundary

Medium currently distinguishes human-created writing, AI-assisted writing, and primarily AI-generated writing. This skill is an author-assistance and editorial workflow, not a way to disguise automated writing as human work.

Apply these rules:

1. Build the story around user-provided experience, expertise, examples, decisions, observations, or an explicitly approved editorial thesis whenever possible.
2. Never invent first-hand experience, emotions, scenes, dialogue, customers, experiments, failures, results, or personal stakes.
3. If generated prose from this workflow remains in the story, add a clear AI-assistance disclosure within the first two paragraphs, following Medium's current policy.
4. If images were generated or materially modified by AI, identify that in each affected image caption.
5. Do not mark a primarily AI-generated story as paywall-ready. Medium currently excludes primarily AI-generated writing from Partner Program paywall eligibility.
6. Do not call any draft “Boost-ready.” Boost is a Medium curation decision, and current guidance emphasizes human-created work, first-hand experience, originality, value, and craft.
7. Humanization may improve readability but must not erase required disclosure, manufacture an author voice, or simulate lived experience.
8. If the author has not supplied enough original material, deliver a research brief, interview prompts, outline, and clearly labeled working draft that requires substantive author revision before publication.

The publishing pack must record:

• author material supplied;
• AI assistance used;
• required disclosure text;
• human review status;
• paywall eligibility status: not eligible, needs author verification, or eligible based on verified human authorship;
• Boost status: always not claimed unless Medium has already assigned a verified badge after publication.

Other Non-Negotiable Boundaries

1. Do not invent data, sources, quotes, product capabilities, prices, rankings, or Publication acceptance.
2. Do not copy another Medium writer's hook, structure, story, metaphor, examples, voice, or ending.
3. Do not call a Topic hot, trending, or popular from one story or one search result.
4. Do not use irrelevant Topics or mass mentions to chase distribution.
5. Do not produce link roundups, affiliate-first reviews, PR copy, or product announcements disguised as editorial stories.
6. Disclose affiliations, affiliate relationships, product ownership, sponsorship, or other material interests.
7. Do not guarantee indexing, General Distribution, Boost, Publication acceptance, earnings, reads, or engagement.
8. Writing, generating images, uploading assets, submitting to a Publication, applying a paywall, and publishing are separate permissions.

Medium Story Brief

Before research or writing, create or infer a brief in 14 lines or fewer and save it as medium-brief.md:

• Author and authority basis: supplied experience, expertise, research, or viewpoint.
• Target reader: who they are and why they would choose this story.
• Reader tension: the unresolved problem, feeling, decision, or curiosity.
• Core idea: the one insight or transformation the story must deliver.
• Reader after-state: what changes in understanding, feeling, or action.
• Story type: essay / tutorial / explainer / review / comparison / case study / reported analysis / listicle.
• Original contribution: what is new beyond a search summary.
• Primary Medium Topic: the clearest discovery category.
• Supporting Topics: up to four, each with a direct content reason.
• Publication target: named Publication or profile-only; unknown is acceptable.
• Evidence requirement: 3-6 factual or comparative claims to verify.
• Narrative material: scenes, examples, data, code, screenshots, or approved anecdotes.
• Target length: determined by the story; normally 900-2,000 words for substantial nonfiction, not a platform rule.
• AI/disclosure status: assistance type, required disclosure, and author-review requirement.

Make conservative assumptions when information is missing. Ask only when authorship material, thesis, target reader, or permission to use personal material is materially ambiguous.

Working Modes

Continuous mode (default)

Run brief -> topic research -> evidence -> outline -> draft -> audit -> rewrite -> humanize -> package. Deliver a reviewed local draft and state the author-review and disclosure requirements.

Topic-radar mode

When the user asks what to write, generate and rank topic opportunities only. Do not turn every topic into a shallow story.

Interview-first mode

Use this when the story needs lived experience but the user supplied only a topic. Produce 5-10 precise questions that can elicit scenes, decisions, mistakes, sensory details, evidence, and changed beliefs. Pause only if the missing answers would determine the truth of the story.

Interactive mode

Pause at the shortlist or outline when the user explicitly asks to choose first.

Audit mode

If the user asks only for review, do not overwrite the draft. If they ask to improve it, preserve the original, apply fixes, and re-audit.

End-to-End Workflow

1. Create an isolated story directory

Use:

writer/medium-writer/output/<story-slug>/

This Medium-specific output directory overrides the parent writer's default writer/output/<article-slug>/ location. Prefer a short ASCII, hyphen-separated slug under 80 characters. Do not mix multiple stories in one folder.

Recommended working files:

medium-brief.md
medium-topic-map.md
source-ledger.md
outline.md
draft.md
article-medium.md
medium-audit.md
medium-publishing-pack.md
image-plan.md

Create only what the task needs. Keep draft.md separate from article-medium.md.

article-medium.docx is optional and should be created only when the user requests Word handoff or offline editorial review. A .docx is not a native Medium publishing requirement.

2. Research Medium search, Topics, and Publications

Read references/medium-topic-research.md completely.

Research across:

• Medium search suggestions and result pages when accessible;
• established Medium Topic pages and their adjacent Topics;
• recent recommended stories, Staff Picks, and relevant Publications;
• Publication submission guidelines, topic requirements, read-time rules, image/subtitle requirements, and paywall conditions;
• original or authoritative external sources;
• the author's existing stories, audience interests, comments, support questions, or approved experiences.

Record query, date, surface, directly observed signal, editorial inference, and evidence strength in medium-topic-map.md.

Separate:

• Observed on Medium: visible Topic, recurring question, story angle, Publication pattern, or reader language.
• External evidence: primary report, official documentation, search demand, or source material.
• Author advantage: experience, access, data, case, or viewpoint this writer can legitimately add.
• Editorial inference: a proposed story angle that still needs validation.

Never convert Topic follower counts, story counts, claps, or recommendation placement into guaranteed demand.

3. Select Topics as editorial labels

Medium currently allows up to five Topics per story. Choose only relevant Topics:

• one broad reader-interest Topic;
• one field or craft Topic;
• one specific subject or technology Topic;
• one intent or outcome Topic when useful;
• one audience, experience, or adjacent Topic only when the body supports it.

Use fewer than five when additional Topics would dilute the story. Topic spamming can restrict distribution.

For every Topic, record:

• exact Topic name;
• why it describes the public story;
• which section supports it;
• whether it is broad, specific, or adjacent;
• whether it was verified as an available Medium Topic.

4. Evaluate Publication fit

Do not select a Publication solely by follower count.

Check:

• editorial theme and recent stories;
• target reader and tone;
• submission guidelines and whether submissions are open;
• whether the author is approved, following, or eligible to submit;
• required subtitle, image, topic match, read time, or paywall state;
• exclusivity, canonical, licensing, or prior-publication conditions;
• expected review status and editing control;
• whether the story adds something the Publication has not just published repeatedly.

Record best fit, possible fit, or profile-first, with evidence. Never claim acceptance before the Publication editor approves the story.

5. Build the source and authorship ledger

Create source-ledger.md for fact-heavy, current, comparative, reported, product, health, legal, financial, or policy-related stories.

Record for each material item:

• claim or narrative element;
• type: fact / inference / editorial judgment / user-provided experience / generated suggestion;
• source, date, URL, or user-provided provenance;
• status: verified, user_provided, needs_verification, softened, removed, or unsupported;
• intended section;
• caveat, expiry risk, or disclosure need.

Generated suggestions cannot become personal experience. Unsupported material cannot enter the final story.

6. Choose a Medium-native story architecture

Select one primary architecture:

• Personal essay: scene -> tension -> reflection -> changed understanding -> resonant ending.
• Practitioner essay: observed problem -> experience/evidence -> insight -> implications -> takeaway.
• Tutorial: reader problem -> prerequisites -> guided build -> failure points -> verification -> next step.
• Explainer: concrete question -> intuitive model -> evidence/examples -> misconception -> application.
• Review: use context -> criteria -> observed strengths -> limitations -> reader-specific judgment.
• Comparison: decision stakes -> criteria -> scenario comparison -> trade-offs -> conditional recommendation.
• Case study or teardown: context -> decision -> execution -> result/evidence -> what transfers -> what does not.
• Reported analysis: current signal -> thesis -> evidence -> competing interpretation -> implications.
• List essay: unifying thesis -> substantial items -> progression -> synthesis; not a link farm.

Avoid forcing every story into “introduction, benefits, challenges, future.”