@mohammadhprp/system-prompt 0.12.2 → 0.12.4

package/framework/skills/notion-mcp/references/comments.md

@@ -1,112 +0,0 @@
-# Comments & Discussions
-
-## Overview
-
-Notion supports page-level comments, content-targeted comments on specific blocks, and discussion threads with replies. Use `fetch` with `include_discussions: true` first to see where discussions are anchored, then `get-comments` for full threads.
-
-## Create Comment
-
-### Page-level comment
-
-```
-create-comment
-  page_id: "abc123..."
-  markdown: "Comment with **important** context and a [link](https://example.com)."
-```
-
-### Comment on specific content
-
-Target content by providing a unique start/end snippet:
-
-```
-create-comment
-  page_id: "abc123..."
-  markdown: "This section needs updating."
-  selection_with_ellipsis: "# Meeting No...es heading"
-```
-
-The snippet format: first ~10 characters, `...`, last ~10 characters. Must uniquely identify the content.
-
-### Reply to discussion thread
-
-```
-create-comment
-  page_id: "abc123..."
-  discussion_id: "discussion://pageId/blockId/discussionId"
-  markdown: "Fixed this in the latest update."
-```
-
-Get `discussion_id` from `fetch` (with `include_discussions`) or `get-comments` output.
-
-### Using rich_text instead of markdown
-
-For features that markdown cannot express (mentions, custom emoji, colors):
-
-```
-create-comment
-  page_id: "abc123..."
-  rich_text:
-    - text:
-        content: "Assigned to "
-    - mention:
-        type: "user"
-        user:
-          id: "user-uuid"
-    - text:
-        content: " for review"
-```
-
-### Comment formatting
-
-- **Markdown**: inline formatting only (bold, italic, strikethrough, underline, code, links)
-- **Inline math**: `$Equation$`
-- **Mention tags**: `<mention-date start="2024-12-25"/>`, `<mention-page id="..."/>`, `<mention-user id="..."/>`, `<mention-database id="..."/>`
-- ❌ No block-level markdown (headings, lists, tables, blockquotes) — these render as plain text
-- ❌ No UI shortcuts like `@today`, `@name`, `[[page]]`
-
-## Read Comments
-
-```
-get-comments
-  page_id: "abc123..."
-```
-
-Returns all discussions on the page with full thread content.
-
-### Include child block comments
-
-```
-get-comments
-  page_id: "abc123..."
-  include_all_blocks: true
-```
-
-### Include resolved discussions
-
-```
-get-comments
-  page_id: "abc123..."
-  include_resolved: true
-```
-
-### Get specific discussion by ID
-
-```
-get-comments
-  page_id: "abc123..."
-  discussion_id: "discussion://pageId/blockId/discussionId"
-```
-
-## Workflow
-
-1. `fetch` with `include_discussions: true` — see discussion anchors and `<page-discussions>` summary
-2. `get-comments` with `discussion_id` — read full thread
-3. `create-comment` with `discussion_id` — reply
-4. `create-comment` with `selection_with_ellipsis` — start a new thread on specific content
-5. `create-comment` with just `page_id` — add a general page-level comment
-
-## Limitations
-
-- **No edit/update** — comments cannot be modified after creation
-- **No delete** — comments cannot be removed via this server
-- **No resolution** — cannot mark discussions as resolved via this server

package/framework/skills/notion-mcp/references/databases.md

@@ -1,193 +0,0 @@
-# Database Management
-
-## Overview
-
-Notion databases consist of views on top of data sources. A data source (collection) holds the actual schema and pages. A database can have multiple data sources (linked databases). Use `fetch` first to get the database structure and data source IDs from `<data-source>` tags.
-
-```
-fetch
-  id: "database-uuid-here"
-```
-
-## Create Database
-
-Uses SQL DDL syntax to define the schema:
-
-```
-create-database
-  title: "Tasks"
-  parent:
-    page_id: "abc123..."           # where to place the database
-  schema: |
-    CREATE TABLE (
-      "Task Name" TITLE,
-      "Status" SELECT('To Do':red, 'In Progress':yellow, 'Done':green),
-      "Priority" NUMBER FORMAT 'dollar',
-      "Due Date" DATE,
-      "Assignee" PEOPLE,
-      "Tags" MULTI_SELECT('eng':blue, 'design':pink),
-      "URL" URL,
-      "Email" EMAIL,
-      "Complete" CHECKBOX,
-      "Task ID" UNIQUE_ID PREFIX 'TASK'
-    )
-  description: "Team task tracker"
-```
-
-### Column types
-
-| Type | SQL Syntax |
-|------|------------|
-| Title | `TITLE` |
-| Rich text | `RICH_TEXT` |
-| Date | `DATE` |
-| People | `PEOPLE` |
-| Checkbox | `CHECKBOX` |
-| URL | `URL` |
-| Email | `EMAIL` |
-| Phone | `PHONE_NUMBER` |
-| Status | `STATUS` |
-| Files | `FILES` |
-| Number | `NUMBER [FORMAT 'dollar']` |
-| Select | `SELECT('opt1':red, 'opt2':blue)` |
-| Multi-select | `MULTI_SELECT('opt1':green, 'opt2':pink)` |
-| Formula | `FORMULA('prop("A") + prop("B")')` |
-| Relation | `RELATION('data_source_id')` or `RELATION('ds_id', DUAL)` |
-| Rollup | `ROLLUP('relation_prop', 'target_prop', 'function')` |
-| Unique ID | `UNIQUE_ID [PREFIX 'X']` |
-| Created time | `CREATED_TIME` |
-| Last edited | `LAST_EDITED_TIME` |
-
-Column colors: `default`, `gray`, `brown`, `orange`, `yellow`, `green`, `blue`, `purple`, ` pink`, `red`
-
-Add descriptions: `"Status" STATUS COMMENT 'Current task status'`
-
-### Self-referencing relation (two-step)
-
-1. Create the database without the relation
-2. Use `update-data-source` with the returned `data_source_id` to add the relation:
-
-```
-update-data-source
-  data_source_id: "abc123..."
-  statements: |
-    ADD COLUMN "Parent" RELATION('abc123...', DUAL 'Children' 'children');
-    ADD COLUMN "Children" RELATION('abc123...', DUAL 'Parent' 'parent')
-```
-
-## Update Data Source
-
-Modify a data source's schema, title, or description.
-
-```
-update-data-source
-  data_source_id: "f336d0bc-..."
-  title: "Project Tracker 2025"
-
-  statements: |
-    ADD COLUMN "Priority" SELECT('High':red, 'Medium':yellow, 'Low':green);
-    ADD COLUMN "Due Date" DATE;
-    RENAME COLUMN "Status" TO "Progress";
-    ALTER COLUMN "Priority" SET SELECT('P0':red, 'P1':orange, 'P2':green);
-    DROP COLUMN "Old Column"
-```
-
-### Statements
-
-- `ADD COLUMN "Name" <type>` — add a property
-- `DROP COLUMN "Name"` — remove a property (only if unused in views)
-- `RENAME COLUMN "Old" TO "New"` — rename a property
-- `ALTER COLUMN "Name" SET <type>` — change type/options
-- `ALTER COLUMN "Name" SET COMMENT 'new description'` — update description
-
-Cannot delete or create title properties. Max one `UNIQUE_ID` property.
-
-## Views
-
-### Create View
-
-```
-create-view
-  data_source_id: "abc123..."
-  name: "Sprint Board"
-  type: "board"                 # table, board, list, calendar, timeline, gallery, form, chart, map, dashboard
-  configure: |
-    GROUP BY "Status";
-    SORT BY "Due Date" ASC;
-    FILTER "Priority" != "Low"
-```
-
-Or add a view to an existing database:
-
-```
-create-view
-  database_id: "abc123..."
-  data_source_id: "abc123..."
-  name: "All Tasks"
-  type: "table"
-```
-
-Or create a linked database view on a page:
-
-```
-create-view
-  parent_page_id: "ghi789..."
-  data_source_id: "abc123..."
-  name: "Company tasks"
-  type: "table"
-  configure: |
-    FILTER "Company" = "Acme"
-```
-
-### View types and required directives
-
-| View type | Required |
-|-----------|----------|
-| table | — |
-| board | `GROUP BY "Property"` |
-| list | — |
-| calendar | `CALENDAR BY "DateProperty"` |
-| timeline | `TIMELINE BY "Start" TO "End"` |
-| gallery | — |
-| form | — |
-| chart | `CHART column\|bar\|line\|donut\|number` |
-| map | `MAP BY "LocationProperty"` |
-| dashboard | — |
-
-### View DSL directives
-
-```
-FILTER "Status" = "In Progress"           # filter rows
-SORT BY "Due Date" ASC                     # sort rows
-GROUP BY "Status"                          # group/board columns
-CALENDAR BY "Date"                         # calendar date property
-TIMELINE BY "Start" TO "End"               # timeline date range
-MAP BY "Location"                          # map location property
-CHART bar AGGREGATE count                  # chart type + aggregation
-SHOW "Name", "Status", "Due Date"          # visible properties
-HIDE "Internal Note"                        # hidden properties
-COVER "Image"                              # cover image property
-WRAP CELLS true                             # wrap cell content
-FREEZE COLUMNS 2                            # freeze first N columns
-FORM CLOSE | OPEN                           # form submissions
-FORM ANONYMOUS true | false                 # anonymous submissions
-FORM PERMISSIONS none | reader | editor    # form submission permissions
-```
-
-### Update View
-
-```
-update-view
-  view_id: "abc123..."          # view:// URI, Notion URL with ?v=, or bare UUID
-  name: "Q1 Sprint Board"
-  configure: |
-    CLEAR FILTER;
-    CLEAR SORT;
-    GROUP BY "Priority"
-```
-
-### Clear directives
-
-- `CLEAR FILTER` — remove all filters
-- `CLEAR SORT` — remove all sorts
-- `CLEAR GROUP BY` — remove grouping

package/framework/skills/notion-mcp/references/pages.md

@@ -1,235 +0,0 @@
-# Page Management
-
-## Read / Fetch
-
-Retrieve page, database, or data source details. Always `fetch` first before modifying anything.
-
-```
-fetch
-  id: "https://notion.so/workspace/My-Page-a1b2c3d4e5f67890"
-
-fetch
-  id: "a1b2c3-d4e5-..."    # bare UUID
-
-fetch
-  id: "collection://f336d0bc..."   # data source URL
-```
-
-Returns content in Notion-flavored Markdown. For the full spec, read `notion://docs/enhanced-markdown-spec` via your MCP resource reader.
-
-Pass `include_discussions: true` to see discussion markers and `<page-discussions>` tags correlating with `get-comments`.
-
-### Workflow
-
-Always start with `fetch` to:
-1. Get the correct page/database ID or data source URL
-2. View existing content before updating
-3. Discover property names and schema for database pages
-4. Find template IDs in `<templates>` section
-
-## Create
-
-```
-create-pages
-  parent:
-    page_id: "abc123..."          # or database_id, or data_source_id
-  pages:
-    - properties:
-        title: "Page title"
-      content: "# Section 1\n\nContent here"
-      icon: "🚀"
-      cover: "https://example.com/cover.jpg"
-```
-
-### Database pages
-
-When creating pages in a database, use the schema from fetch:
-
-```
-create-pages
-  parent:
-    data_source_id: "f336d0bc-..."
-  pages:
-    - properties:
-        Task Name: "New task"
-        Status: "In Progress"
-        Priority: 5
-        date:Due Date:start: "2024-12-25"
-        date:Due Date:is_datetime: 0
-```
-
-### Using templates
-
-```
-create-pages
-  parent:
-    data_source_id: "f336d0bc-..."
-  pages:
-    - template_id: "a5da15f6-..."
-      properties:
-        Task Name: "New urgent bug"
-```
-
-When using a template, do NOT provide `content` — the template supplies it.
-
-### Property formats
-
-| Type | Format | Example |
-|------|--------|---------|
-| Title | plain string | `"Task Name": "Fix login"` |
-| Text / Rich text | plain string | `"Description": "Detailed notes"` |
-| Number | number | `"Priority": 5` |
-| Checkbox | `"__YES__"` / `"__NO__"` | `"Complete": "__YES__"` |
-| Date | expanded keys | `"date:Due:start": "2024-12-25"` |
-| Date with time | expanded keys + `is_datetime: 1` | `"date:Due:start": "2024-12-25T14:00:00"` |
-| Place | expanded keys (name/address/lat/lng/google_place_id) | `"place:Office:name": "HQ"` |
-| Select | string matching an option | `"Status": "Done"` |
-| Multi-select | comma-separated | `"Tags": "eng,design"` |
-
-Properties named `id` or `url` (case insensitive) must be prefixed with `userDefined:`:
-- `"userDefined:URL": "https://..."`, `"userDefined:id": "custom-id"`
-
-## Update
-
-### Update properties
-
-```
-update-page
-  page_id: "abc123..."
-  command: update_properties
-  properties:
-    title: "New title"
-    Status: "In Progress"
-    date:Due:start: "2024-12-25"
-    date:Due:is_datetime: 0
-```
-
-Set a property to `null` to clear its value.
-
-### Update content (search-and-replace)
-
-```
-update-page
-  page_id: "abc123..."
-  command: update_content
-  content_updates:
-    - old_str: "# Old Section\nOld content"
-      new_str: "# New Section\nUpdated content"
-```
-
-### Replace entire content
-
-```
-update-page
-  page_id: "abc123..."
-  command: replace_content
-  new_str: "# Completely new page\n\nContent here"
-```
-
-⚠️ `replace_content` will fail if child pages/databases would be deleted. Include them in `new_str` using `<page url="...">` or `<database url="...">` tags from the fetch output. To intentionally delete children, confirm with the user first.
-
-### Insert content
-
-```
-update-page
-  page_id: "abc123..."
-  command: insert_content
-  content: "## Latest update\n\nStatus update"
-  position:
-    type: "start"     # or "end" (default)
-```
-
-### Apply template
-
-```
-update-page
-  page_id: "abc123..."
-  command: apply_template
-  template_id: "a5da15f6-..."
-```
-
-### Set icon and cover
-
-Can be set alongside any command:
-
-```
-update-page
-  page_id: "abc123..."
-  command: update_properties
-  properties:
-    title: "New title"
-  icon: "🚀"
-  cover: "https://example.com/cover.jpg"
-```
-
-Use `"none"` to remove icon or cover.
-
-### Verify a page (Business/Enterprise or wiki pages)
-
-```
-update-page
-  page_id: "abc123..."
-  command: update_verification
-  verification_status: "verified"    # or "unverified"
-  verification_expiry_days: 90       # optional, omit for indefinite
-```
-
-## Duplicate
-
-```
-duplicate-page
-  page_id: "abc123..."
-```
-
-Duplication completes asynchronously. The new page ID/URL is returned immediately, but content may take a moment to appear.
-
-## Move
-
-```
-move-pages
-  page_or_database_ids:
-    - "abc123..."
-    - "def456..."
-  new_parent:
-    page_id: "ghi789..."    # or workspace, or data_source_id
-```
-
-⚠️ **Irreversible** — permanently relocates pages. Cannot be undone programmatically.
-
-## Search
-
-```
-search
-  query: "quarterly report"
-  query_type: "internal"            # or "user"
-  page_size: 10
-  filters:
-    created_date_range:
-      start_date: "2024-10-01"
-    created_by_user_ids:
-      - "user-uuid-here"
-```
-
-### Search within a data source
-
-```
-search
-  query: "design review"
-  data_source_url: "collection://f336d0bc-..."
-```
-
-### Search by page ID (search content under a page)
-
-```
-search
-  query: "meeting notes"
-  page_url: "abc123..."
-```
-
-### User search
-
-```
-search
-  query: "john@example.com"
-  query_type: "user"
-```