notion-doc

Solid

Notion design skill that MUST be used whenever creating documents. When the user asks for a document, report, summary, meeting notes, or review write-up in HTML/Markdown, load this skill first. The content decides the document's structure and outline; this skill only governs the Notion blocks (callouts, toggles, tables, checklists, code, columns, etc.) and visual style.

Data & Documents 106 stars 13 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
68
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Creating documents with Notion's design **This skill governs only how the document *looks*.** The outline, sections, and flow are decided by the content and the request — no particular document format (proposal, etc.) is imposed. Instead, every document is rendered with the blocks and design language Notion provides. ## 1. Header area (required) 1. **Page icon**: one emoji matching the document's topic, large, above the title (Notion page icon) 2. **Title**: a short noun phrase 3. **Meta line**: date · author · 1–2 tag pills 4. A thin divider below the meta line ## 2. Notion block dictionary — pick the block that fits the content | Content | Block | |---|---| | Key takeaway, the one line to emphasize | Callout (blue 💡) | | Reference, supplementary info | Callout (gray) | | Done, success, what went well | Callout (green ✅) | | Caution, constraints | Callout (yellow ⚠️) | | Warning, incident, risk | Callout (red 🚨) | | Opening of a long document (4+ h2s) | Table of contents (`toc`) | | Parent document, location context | breadcrumb | | Comparable, listable facts | simple table | | Two chunks that belong side by side | 2-column layout | | Long details or logs that break the flow | `<details>` toggle | | Tasks, progress | checkbox list (done items get strikethrough) | | Code | code block + `class="language-<lang>"` syntax highlighting (required) | | One striking sentence | quote (bold left bar) | | Introducing an external link | bookmark card | | A single call-to-action ...

Details

Author
heyman333
Repository
heyman333/agent-notion-template-docs
Created
3 weeks ago
Last Updated
3 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

notion-writing

Write Notion pages in Notion-flavored Markdown: XML tables with fixed column widths, and edits that never delete child pages. Use when creating or editing a Notion page(Notionページ作成・Notionテーブル・Notionに書き出す・子ページ).

1 Updated today
devbasex
Data & Documents Listed

writing-documents

Write structured software-delivery and consultancy documents as Markdown in the repo by default. Use for canonical decision, contract, procedure, learning, system, incident, suite, plan, assurance, and brief types, including design and architecture docs, requirements, delivery plans, reviews, status, release, support, and service documentation. Produce designed HTML or PDF only when asked. Do not use for casual edits, metric-led reports (analytical-document-design), slides (presentation-design), standalone charts or diagrams, legal boilerplate, back-office commercial records, or unprompted restyling.

2 Updated 6 days ago
Avinava
AI & Automation Listed

dark-terminal-doc

Use when a single-file HTML technical document should carry a dark developer / terminal aesthetic — monospace, terminal-green on near-black. Trigger on: "dark terminal doc", "terminal-style HTML", "developer-terminal aesthetic", "make it look like a terminal", "dark developer-facing HTML page", or a comparison table, reference sheet, changelog, release notes or API cheatsheet in that look, or one matching a document already in this style. Not for a doc with no stated aesthetic.

2 Updated yesterday
Tamircohen28