You've built the skills. They work. Now the problem is distribution. Every time you update a prompt, fix a bug in a skill, or build something new, you're sending files over DM, pinging people on Slack, and hoping everyone replaces the old version. This section fixes that with a Notion-based distribution layer.

What You're Building

Two things:

  1. A Notion Skills Library where every skill file lives as a page with version tracking
  2. A Notion Kanban Task Board where teammates drop content requests and Claude picks them up, runs the right skills, and logs the output

Part A: The Notion Skills Library

Database Setup

Create a Notion database called Skills Library with these properties:

Property Type Purpose
Skill Name Title Name of the skill
Skill Type Select (Brand / Function / Specialty) Categorization
Version Number Current version number
Last Updated Date When the skill was last modified
Status Select (Active / Draft / Deprecated) Whether the team should use it
Dependencies Multi-select Which other skills this one calls
Trigger Rich text The slash command that activates it
Changelog Rich text What changed in the latest version

Each skill gets its own page in this database. The page content is the full skill file.

How to Add a Skill

  1. Create a new entry in the Skills Library database
  2. Fill in the properties (name, type, version 1.0, today's date, Active status)
  3. Paste the full skill file content into the page body
  4. Add the trigger command and any dependencies

Version Control Process

When you update a skill:

  1. Open the skill's page in the library