Notion Article Writer

Write blog articles based on context and publish them to the Notion Articles database.

Your Task

  1. Gather context from one of these sources:
    • Current conversation (default if no argument provided)
    • A file path passed as argument
    • A topic/description passed as argument
  2. Ask the user using AskUserQuestion:
    • Title suggestion (propose one based on context, let them edit)
    • Any specific angle or focus they want
  3. Write the article in English first following the tone guidelines below

  4. Publish English version to Notion using the Articles database:
    • Database ID: ac7ebcbdc95543a288361516f2043e8b
    • Data Source ID: 410f70e5-33d0-434f-86b2-ef36dd1398d0
  5. Set properties for English version:
    • Title: the article title
    • Language: EN
    • Date: today’s date
    • Author: 8aaaff03-f1fc-4020-b3aa-2b6f1e7016e2 (Nicolas)
  6. Always translate to French - create the French version with:
    • Translated title
    • Language: FR
    • Same date and author
  7. Link both articles via the Translation property (both directions)

Tone Guidelines

DO:

  • Write in first person, conversational (“I wanted to…”, “J’ai essayé…”)
  • State the goal clearly in the opening paragraph
  • Share genuine insights and what you learned
  • Include code snippets and concrete examples
  • Be honest about limitations and what didn’t work
  • Keep paragraphs short (2-4 sentences)

DON’T:

  • Write clickbait titles (“The Future of X is Here”, “X Will Change Everything”)
  • Use rhetorical questions as dramatic hooks (“Can AI really…?”)
  • Be grandiose about simple things - match the tone to the scope
  • Pad with filler or unnecessary backstory
  • Use buzzwords (“game-changer”, “revolutionize”, “leverage”, “unlock”)

Article Structure

**Author:** Nicolas Rouanne
**Date:** [Today's date in format: January 22, 2026 / 22 janvier 2026]
---

[Opening: what you wanted to achieve and why, in 1-2 short paragraphs]

## [Setup / How it works]

[Code snippets, steps, or explanation]

## [What works]

[Results, with concrete examples]

## [What doesn't work / Limitations]

[Be honest about gaps]

## [Practical use / Takeaways]

[When is this actually useful, what you'd do differently]

Keep the scope honest. A small hack is a small hack - don’t frame it as a breakthrough.

Example Prompts for Context

If the user says /notion-article with no arguments, summarize the current conversation into an article.

If they provide a file: /notion-article ./notes/meeting-notes.md - transform those notes into a polished article.

If they provide a topic: /notion-article "How we set up our CI/CD pipeline" - write about that topic, asking clarifying questions as needed.

Translation Workflow

Since we always create both versions:

  1. Create the English article first, note its page ID
  2. Create the French article, note its page ID
  3. Update English article’s Translation property to link to French
  4. Update French article’s Translation property to link to English

Use the relation property format:

{"Translation": "https://www.notion.so/[page-id]"}

Important

  • Always write English first - this is the source language
  • Always translate to French - no need to ask, just do it
  • Always link both articles - bidirectional Translation property

Cross-Posting to Social Media

After publishing both Notion articles, invoke the /cross-post skill with the English article’s Notion URL to offer cross-posting to LinkedIn, Twitter/X, and Slack.


This site uses Just the Docs, a documentation theme for Jekyll.