Skip to content
Skills Library
Documents & office · Tool integration

notion-summary

/notion-summary

Uploads Claude session summaries or markdown reports to Notion. Use for "노션 업로드", "결과 저장", "notion 정리", "세션 요약", "리포트 업로드", "보고서 작성" requests.

Licence
MIT
Last repository change
01.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/notion-upload.py, tests/test_notion_upload.py

What it does and when to use it

Uploads Claude session summaries or markdown reports to Notion. Use for "노션 업로드", "결과 저장", "notion 정리", "세션 요약", "리포트 업로드", "보고서 작성" requests.

Triggers from the description

노션 업로드결과 저장notion 정리세션 요약리포트 업로드보고서 작성
Original author description

Uploads Claude session summaries or markdown reports to Notion. Use for "노션 업로드", "결과 저장", "notion 정리", "세션 요약", "리포트 업로드", "보고서 작성" requests.

How it works

  1. Prerequisites
  2. Workflow
  3. Retry and lifecycle
  4. Report Templates
  5. Best Practices
Original SKILL.md headings · 142 lines, 597 words
SKILL.md preview
---
name: notion-summary
description: Uploads Claude session summaries or markdown reports to Notion. Use for "노션 업로드", "결과 저장", "notion 정리", "세션 요약", "리포트 업로드", "보고서 작성" requests.
---

# Notion Upload

Upload session summaries and reports to Notion with explicit classification,
redaction, retention metadata plus manual enforcement, and local retry protection.

## Prerequisites

```bash
# Resolve to the installed directory that contains this SKILL.md; do not assume
# a fixed install root. All examples below use this variable.
NOTION_SUMMARY_SKILL_DIR="<directory containing this SKILL.md>"
python3 "$NOTION_SUMMARY_SKILL_DIR/scripts/notion-upload.py" --help

# API actions only; --help and --dry-run do not need notion-client.
python3 -m pip install notion-client
export NOTION_TOKEN="secret_xxx"

# Configure a target in ~/.agents/NOTION.yaml, or use an environment override.
export NOTION_DATA_SOURCE_ID="xxx"
```

Never put the token, target ID, or document content on a command line shared with
other users. Prefer `--file` and protected environment/config files.

## Workflow

### 1. Prepare and classify

Write the report to a local Markdown file. Choose one classification: `public`,
`internal`, `confidential`, or `restricted`. Never guess; ask the data owner
when it is unknown.

### 2. Set retention

Ask the data owner to choose a positive retention period.

### 3. Preview and upload

Run the non-disclosing dry run, then run the upload with the same arguments.

```bash
python3 "$NOTION_SUMMARY_SKILL_DIR/scripts/notion-upload.py" \
  --file "/path/to/report.md" \
  --classification internal \
  --retention-days 30 \
  --dry-run

python3 "$NOTION_SUMMARY_SKILL_DIR/scripts/notion-upload.py" \
  --file "/path/to/report.md" \
  --classification internal \
  --retention-days 30
```

The uploader redacts recognized credentials and PII before block conversion. It
does not print the document, title, target ID, URL, matched values, or API error
body. An upload without explicit classification or retention fails closed.

## Retry and lifecycle

Each upload gets an opaque `nup-...` key. The script writes a mode-`0600` local
manifest at `${AGENTS_DIR:-$HOME/.agents}/notion-upload-manifest.json` before
each remote create.
Re-running a completed payload is a no-op. An interrupted or indeterminate key is
refused instead of creating duplicates. Use an opaque stable key chosen for the
run when the local file may be rendered differently across attempts:

```bash
python3 "$NOTION_SUMMARY_SKILL_DIR/scripts/notion-upload.py" \
  --file "/path/to/report.md" \
  --classification confidential \
  --retention-days 14 \
  --idempotency-key "opaque-run-20260810"
```

Keep the printed `nup-...` key. Lifecycle commands use only pages recorded in the
local manifest:

```bash
# Move known pages to the Notion trash.
python3 "$NOTION_SUMMARY_SKILL_DIR/scripts/notion-upload.py" --rollback "nup-<64-hex>"

# Archive known pages and remove their IDs/payload metadata from the manifest.
python3 "$NOTION_SUMMARY_SKILL_DIR/scripts/notion-upload.py" --erase "nup-<64-hex>"

# Archive expired known pages; schedule this command outside this skill if needed.
python3 "$NOTION_SUMMARY_SKILL_DIR/scripts/notion-upload.py" --enforce-retention
```

After a successful `--rollback`, use `--erase` only to scrub local manifest
metadata; the script does not call archive on those pages again.

Treat `--retention-days` as metadata only. Nothing runs automatically: invoke or
schedule `--enforce-retention` separately and review failures manually.

Notion's public API archives pages but does not guarantee immediate permanent
deletion. The workspace owner must empty trash when permanent erasure is
required. The API also has no create idempotency token: a process loss after a
remote create but before its response is persisted can leave an unknown orphan.
When the script reports an unknown remote state, have the workspace owner inspect
the configured target and trash, reconcile any orphan, then retry with a fresh
opaque `--idempotency-key`. Do not retry the old key. Do not delete or copy the
manifest while uploads are active.

## Report Templates

### Session Summary
```markdown
# Session: {date}

## Completed
- Task 1
- Task 2

## Decisions
- Chose approach X because Y

## Next Steps
- [ ] Follow-up task
```

### Technical Report
```markdown
# {Topic} Analysis

## Overview
...

## Findings
...

## Recommendations
...
```

## Best Practices

- Keep summaries concise.
- Include actionable next steps.
- Keep credentials out of source reports even though redaction is enforced.
- Ask the data owner to choose classification and retention before uploading.
Files in this package (3)
  • SKILL.md 5 KB
  • scripts/notion-upload.py 51 KB
  • tests/test_notion_upload.py 13 KB

Versions

The database has no other skills named notion-summary.

Database snapshot: 13.11.2026 · package version 3300833acdcf (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100notion-doc
    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…
  • 96notion
    Search, read, create and update pages and databases in your Notion workspace via the Notion API. Use when the user asks to find, read, or write Notion pages, notes, docs, or database rows.
  • 95notion-research-documentation
    Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
  • 90notion-export-to-markdown
    Turn a Notion "Markdown & CSV" export into clean Markdown, with ids stripped from names, databases as tables and pictures embedded, using TransformPipe's free converter. Use when the user is leaving Notion, backing it up, moving notes to Obsidian or Git, or asks why their Notion…
  • 100notion-docs
    Notion workspace management via MCP - create databases, pages, comments, and knowledge bases. Use when building Notion documentation, organizing project wikis, or managing Notion content.
  • 95notion-research-documentation
    Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.