coopersimson96/ai-content-system/notion-setup

Claude Code and agent skill by coopersimson96/ai-content-system

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

One-time setup that creates the Script Library database in Notion with all production pipeline properties, views, and configuration.

Install

npx vskill@latest install coopersimson96/ai-content-system/notion-setup

SKILL.md

Notion Content Pipeline Setup

Creates the full content production infrastructure in Notion using the Notion MCP tools.


Pre-flight Check

Before anything, verify the Notion MCP is connected:

  1. Use notion-get-teams to check which workspace is connected
  2. If it returns a workspace → proceed
  3. If it fails or returns an error → STOP and tell the user:
The Notion MCP isn't connected. To fix this:
2. Find Integrations > Notion
3. Click Connect and authorize with your Notion account
4. Then run /notion-setup again.

Step 1: Create Parent Page

Use notion-search to check if a "Content Production Hub" page already exists.

If not, use notion-create-pages to create a new page:

  • Title: "Content Production Hub"
  • Content: Brief description: "Central hub for all content production — scripts, pipeline, analytics."

Save the page ID — the database will be created inside this page.


Step 2: Create Script Library Database

Use notion-create-database to create a database inside the Content Production Hub page with these properties:

Database title: "Script Library"

Properties:

Property NameTypeConfiguration
Script Titletitle(default title property)
Script Numbernumbernumber format: number
StatusselectOptions: Ideas/Topics, Scripts, Filming, Filmed, Editing, Ready To Post, Posted
Platformmulti_selectOptions: Instagram Reels, TikTok, YouTube Shorts, Facebook Reels
Seriesselect(empty — populated as scripts are added)
Topicrich_text
Hook Framework AselectOptions: Curiosity Gap, Proof-First, Pain Point, Contrarian, This Cost Me Thousands, Unexpected Confession, Question Hook, Pattern Interrupt, Before vs After, Test / Experiment
Hook Framework BselectSame options as Hook Framework A
Hook Framework CselectSame options as Hook Framework A
Pain Point Sourcerich_text
Batchrich_text
Post Datedate
Google Doc URLurl
Viewsnumbernumber format: number_with_commas
3s Retentionnumbernumber format: percent
Likesnumbernumber format: number_with_commas
Commentsnumbernumber format: number_with_commas
Sharesnumbernumber format: number_with_commas
Savesnumbernumber format: number_with_commas
Notesrich_text

Step 3: Save Configuration

After creating the database, save the IDs for other skills to use:

bash
mkdir -p ~/.config/notion-content

Write ~/.config/notion-content/config.json:

json
{
"workspace": "YOUR_WORKSPACE_NAME",
"hub_page_id": "{THE_HUB_PAGE_ID}",
"script_library_db_id": "{THE_DATABASE_ID}"
}

Replace YOUR_WORKSPACE_NAME with the actual workspace name returned from the pre-flight check.

Also run notion-update-data-source with the database ID so the MCP can query it efficiently.


Step 4: Explain Manual View Setup

Tell the user:

The Script Library database is created! Now set up these views in Notion for the best experience:
### Board View (Production Pipeline)
1. Open the Script Library database in Notion
2. Click + Add a view → Board
3. Group by: Status
4. This gives you a kanban board: Ideas/Topics → Scripts → Filming → Filmed → Editing → Ready To Post → Posted
### Calendar View (Content Calendar)
1. Click + Add a view → Calendar
2. Date property: Post Date
3. Now you can see your posting schedule visually
### Table View (Performance Dashboard)
1. Click + Add a view → Table
2. Filter: Status is Posted
3. Show columns: Script Title, Platform, Views, 3s Retention, Likes, Comments, Shares, Saves
4. Sort by: Views (descending)
These views are best set up manually in Notion since the API doesn't support creating views directly.

Step 5: Verify

Confirm everything worked:

  1. Use notion-search to find the "Script Library" database
  2. Verify the config file exists at ~/.config/notion-content/config.json
  3. Tell the user:
Notion pipeline is ready! Your Script Library database is set up with all properties.
When you run /content-master, scripts will automatically flow into Notion as individual entries with status tracking.
Use /content-pipeline to manage your production pipeline — update statuses, log metrics, manage your posting calendar.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
17
Repository forks
4
7-day trend score
0

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/coopersimson96/ai-content-system/notion-setup/badge)](https://verified-skill.com/skills/coopersimson96/ai-content-system/notion-setup)

Something wrong with this skill or its page? Tell us.