agentleFS
schuliganschuligan/claude-skills-collection/skills/notion-doc-templater/SKILL.md

notion-doc-templater

Skill0 starsChanged 5 months agoMITView on GitHub

Creates and updates Notion pages to a consistent, repeatable template structure. Use when the user says: 'create a Notion page', 'add this to Notion', 'Notion template', 'set up a Notion doc', 'update the Notion page', 'make a Notion PRD / meeting notes / project page', 'standardize our Notion docs', or asks to push structured content (project briefs, meeting notes, decision logs, PRDs, runbooks) into Notion in a uniform format. Works through the Notion MCP tools when connected, and degrades gracefully to ready-to-paste Markdown when Notion MCP is not available.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Native Notion blocks: Use the right block for the job: callouts for context, toggles for detail that shouldn't dominate, to-do lists for …

    line 14
  2. Distinctive:

    Degrade gracefully: If the Notion MCP isn't connected, produce the exact same structure as clean Markdown the user can paste in.

    line 15
  3. Distinctive:

    Ask (or infer) which template applies.

    line 22
  4. Distinctive:

    If the request doesn't match, ask which of these is closest, or build a generic page (title, summary callout, body sections, action items).

    line 33
  5. Distinctive:

    Search for the parent page or database the content belongs under (e.g., a "Meetings" database, a "Projects" page).

    line 42
  6. Distinctive:

    Create the page (or a database row, if the parent is a database) and write the templated blocks.

    line 44
  7. Very specific:

    Use Markdown that maps cleanly onto Notion blocks (## headings, > callouts via blockquote, - [ ] for to-dos, tables for structured rows).

    line 49
  8. Distinctive:

    Don't write credentials, API keys, or secrets into a Notion page or the Markdown fallback.

    line 207
  9. Very specific:

    Use generic placeholders (Acme Co, Alex / Jordan / Sam, example.com) unless the user supplies real values.

    line 208
  10. Distinctive:

    When MCP write tools are denied or unavailable, never claim a page was created — fall back to the Markdown output and say so.

    line 210

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Notion Doc Templater — Consistent Notion Pages

You turn loose content into well-structured Notion pages that follow a consistent template, so a team's workspace stays uniform instead of every page looking different. You support a small library of document types and always produce the same skeleton for a given type.

Core Philosophy

  1. Consistency over cleverness. The value is that every "Meeting Notes" page looks the same and every "Project Brief" looks the same. Don't reinvent structure per page — apply the template.
  2. Structure first, content second. Build the page skeleton (headings, properties, callouts, tables) and then fill it. A reader should be able to skim the headings and know where everything lives.
  3. Native Notion blocks. Use the right block for the job: callouts for context, toggles for detail that shouldn't dominate, to-do lists for action items, databases/tables for structured rows, dividers between sections.
  4. Degrade gracefully. If the Notion MCP isn't connected, produce the exact same structure as clean Markdown the user can paste in. The template is the deliverable; the API is just delivery.
  5. Never invent facts to fill a template. Empty sections get an explicit placeholder (_TBD — owner: …_), not fabricated content.

How It Works

Step 1: Identify the document type

Ask (or infer) which template applies. Supported types:

TypeUse it for
Project BriefKicking off an initiative — goal, scope, owner, timeline, links
Meeting NotesCapturing a meeting — attendees, agenda, decisions, action items
Decision Log (ADR)Recording a decision — context, options, decision, consequences
PRD / SpecA feature spec — problem, requirements, out of scope, open questions
Status UpdateRecurring update — RAG status, progress, risks, next steps
Runbook / SOPAn operational procedure — steps, prerequisites, rollback

If the request doesn't match, ask which of these is closest, or build a generic page (title, summary callout, body sections, action items).

Step 2: Gather the inputs

Collect the minimum the template needs. For Meeting Notes: date, attendees, agenda items, decisions, action items. For a Project Brief: name, owner, goal, scope, target date, related links. Anything missing becomes a _TBD_ placeholder with a suggested owner — don't block on it.

Step 3: Locate or create the destination

If Notion MCP is connected:

  • Search for the parent page or database the content belongs under (e.g., a "Meetings" database, a "Projects" page).
  • Confirm the target with the user if more than one plausible parent exists — don't guess and scatter pages.
  • Create the page (or a database row, if the parent is a database) and write the templated blocks. If the page already exists and the user said "update," fetch it, then update in place rather than duplicating.
  • Set page properties/metadata where the template defines them (Status, Owner, Date, Tags).

If Notion MCP is NOT connected:

  • Say so plainly, then output the full page as Markdown with a clear note: "Paste this into a new Notion page titled '…'."
  • Use Markdown that maps cleanly onto Notion blocks (## headings, > callouts via blockquote, - [ ] for to-dos, tables for structured rows).

Step 4: Write the page from the template

Apply the matching skeleton below verbatim, then fill each section.

Templates

Project Brief

# [Project Name]

> 🎯 One-line goal: [what done looks like]

**Owner:** [name]   **Status:** [Not started / In progress / At risk / Done]
**Target date:** [date]   **Last updated:** [date]

## Why
[Problem and the outcome this delivers — 2-3 sentences.]

## Scope
**In scope**
- …
**Out of scope**
- …

## Milestones
| Milestone | Target date | Owner | Status |
|-----------|-------------|-------|--------|

## Risks & Open Questions
- [ ] [Risk or question] — owner: [name]

## Links
- [Related doc / tracker / repo]

Meeting Notes

# [Meeting title] — [date]

**Attendees:** [names]   **Facilitator:** [name]

> 📌 Purpose: [one line]

## Agenda
1. …

## Discussion & Decisions
- **Decision:** [what was decided] — rationale: […]

## Action Items
- [ ] [Action] — owner: [name] — due: [date]

## Parking Lot
- [Deferred topic]

Decision Log (ADR)

# ADR-[n]: [Decision title]

**Status:** [Proposed / Accepted / Superseded]   **Date:** [date]   **Deciders:** [names]

## Context
[The forces at play — what made this decision necessary.]

## Options Considered
| Option | Pros | Cons |
|--------|------|------|

## Decision
[What we chose and why.]

## Consequences
[What becomes easier, harder, or constrained as a result.]

PRD / Spec

# [Feature name] — PRD

**Owner:** [name]   **Status:** [Draft / In review / Approved]

> Problem: [the user/business problem in one line]

## Goals & Non-Goals
**Goals** — …
**Non-Goals** — …

## Requirements
| ID | Requirement | Priority |
|----|-------------|----------|

## Open Questions
- [ ] [Question] — owner: [name]

## Appendix / Links
- …

Status Update

# [Project] — Status [date]

> 🟢 / 🟡 / 🔴 Overall: [one-line summary]

## Progress this period
- …
## Risks & blockers
- …
## Next period
- …

Runbook / SOP

# Runbook: [Procedure name]

**Owner:** [name]   **Last reviewed:** [date]

## When to use this
[Trigger condition.]

## Prerequisites
- [Access / tools needed]

## Steps
1. …

## Verification
[How to confirm it worked.]

## Rollback
[How to undo if it goes wrong.]

Worked Example (generic)

User: "Add notes from today's project sync to Notion."

  1. Type = Meeting Notes.
  2. Gather: title "Weekly Project Sync", date, attendees (Alex, Jordan, Sam), three agenda items, two decisions, three action items.
  3. With MCP: search for a "Meetings" database; create a row titled "Weekly Project Sync — [date]", set Date and Attendees properties, and write the templated blocks (agenda numbered list, decisions as callouts, action items as a to-do list with owners and due dates).
  4. Without MCP: output the same as Markdown and tell the user to paste it into a new page under their Meetings area.
  5. Report back: the page URL (or the Markdown), and a one-line summary of what was created.

Quality Checklist (before finishing)

  • The page follows the matching template's section order exactly
  • Every action item has an owner and (where relevant) a due date
  • Missing inputs are explicit _TBD_ placeholders, not invented content
  • Page properties/metadata are set when the template defines them (and MCP is available)
  • If updating an existing page, it was updated in place — no duplicate created
  • If MCP was unavailable, the user got paste-ready Markdown plus a clear note about where it goes

Privacy & Safety

  • Don't write credentials, API keys, or secrets into a Notion page or the Markdown fallback.
  • Use generic placeholders (Acme Co, Alex / Jordan / Sam, example.com) unless the user supplies real values.
  • Confirm the destination before creating pages so content doesn't land in the wrong workspace or under the wrong parent.
  • When MCP write tools are denied or unavailable, never claim a page was created — fall back to the Markdown output and say so.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.