---
name: notion-install-auth
description: >-
  Establish a least-privilege Notion connection and tested API contract without leaking credentials. Use when onboarding an internal connection, public OAuth connection, or personal access token. Trigger with "set up Notion auth", "create Notion connection", or "review Notion credentials".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<connection-type> <workspace> <environment>"
version: 1.41.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [ saas, notion, access ]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live Notion actions require network access and explicit approval"
title: notion-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/notion-install-auth
last_updated: 2026-10-23T06:01:00.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/notion-install-auth/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/notion-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/notion-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/notion-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/notion-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/notion-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/notion-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Notion Connection and Authentication Intake

## Overview

Establish a least-privilege Notion connection and tested API contract without leaking credentials.. This workflow produces an auditable decision or artifact before any live action.

## Prerequisites

- Current first-party Notion documentation and the selected integration's tested API-version contract.
- A named workspace owner, content or data owner, and operation owner.
- Synthetic or approved non-production fixtures with secrets and workspace content removed.

## Current Contract

Notion supports internal connections, public OAuth connections, and personal access tokens with different ownership and access behavior. REST calls require bearer authentication and an explicit tested Notion-Version contract. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior.

## Authentication

Record credential issuer, connection or user owner, workspace binding, capabilities, shared roots, expiry or refresh behavior, storage, rotation, and revocation without storing the secret value.

## Instructions

1. Choose the connection type from distribution, tenant, and user-context requirements.
2. Define the minimum content, comment, and user capabilities plus exact shared fixture roots.
3. Select and test an SDK and API-version combination against current upgrade guidance.
4. Provision the credential through the approved secret manager and record a fingerprint.
5. Run bot identity plus one explicitly shared read-only fixture check.
6. Document rotation, OAuth refresh if applicable, revocation, reauthorization, and production promotion.

## Tool Discipline

Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, workspace content, user data, file transfer, deployment, capability or sharing changes, writes, spend, or deletion.

## Approval Boundaries

Require the workspace owner for connection creation and sharing; require security review for public OAuth, user information, external distribution, or production secrets.

## Error Handling

- Never infer OAuth scopes or redirect behavior from an internal token example.
- A connection capability does not grant access until content is shared where required.
- Do not commit env files or access tokens.

## Output

Return the connection model, workspace binding, capability matrix, shared roots, secret reference, validation evidence, lifecycle owners, and gaps. Identify assumptions, owners, expirations, and evidence gaps explicitly.

## Examples

- Onboard a read-only internal connection to a synthetic data source.
- Document a public OAuth installation without persisting tokens in browser state.

## Validation

Exercise and record these paths with expected and observed results:

- least privilege
- workspace binding
- shared content
- secret storage
- revocation
- negative access

## Resources

- [Current first-party evidence map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/notion-install-auth/references/official-docs.md) — recheck dated sources before relying on mutable behavior.
- Treat observed tenant behavior as environment-specific evidence, never a universal Notion guarantee.
