AI Registry¶

Skills for building a structured registry of your AI workflows and skills — naming conventions, documentation templates (SOPs and process guides), Notion registration, and GitHub syncing. These are plain-text Markdown files that work in any AI tool. Download them from GitHub, install as a Claude Code plugin, or paste directly into your system prompt to give any AI assistant your registry conventions.

Get These Skills¶

These skills are plain-text Markdown files that work in any AI tool. Choose how you want to get them:

/plugin install ai-registry@handsonai

Slash Commands¶

All skills can be invoked directly as slash commands in Claude Code:

Components¶

Skills¶

naming-workflows¶

Command: /ai-registry:name-workflow

What it does: Generates consistent, outcome-focused names and descriptions for business workflows, then creates entries in your Notion Workflows database. Follows domain-specific naming patterns so your registry stays organized as it grows.

When to use it: Use this when you have a new workflow to document, need to standardize existing workflow names, or want to add a workflow entry to Notion. Also useful when you're not sure what to call a workflow.

How it works:

1. You describe the workflow (what it does, what domain it's in)
2. Claude identifies the domain (Sales, Marketing, Product, Education, Operations, etc.)
3. Claude generates 2-3 name options following the naming pattern for that domain
4. Claude writes a 1-2 sentence description (action + outcome) and suggests a process outcome (the concrete deliverable)
5. Claude searches your Notion Business Processes database to suggest where the workflow fits
6. After you confirm, Claude creates the entry in Notion with all properties filled in

Naming conventions:

Names are always 2-4 words, noun phrases (not verb phrases), in Title Case.

Example prompts:

"Name a workflow for drafting email responses"
→ Suggests options like "Email Response Drafting" with description
  and process outcome, then creates the Notion entry

"I need to name a workflow for turning lesson recordings into
social media content"
→ Suggests "Content Repurposing" (Marketing pattern), writes the
  description, and creates the entry

What you'll get: A named workflow entry in your Notion Workflows database with: name, description, process outcome, business process link, sequence number, status, type, and trigger.

Platform compatibility: Claude Code ✓ | Claude.ai ✓ (Notion MCP required)

writing-workflow-sops¶

Command: /ai-registry:workflow-sop

What it does: Writes Standard Operating Procedure documentation for workflows and saves it directly to the Notion workflow page body. Adapts the SOP template based on whether the workflow is Manual, Augmented, or Automated.

When to use it: Use this when you have a workflow entry in Notion and need to document how it's actually executed — step-by-step procedures, prerequisites, quality checks, and troubleshooting guidance.

How it works:

1. Claude fetches the workflow from Notion to get context (name, description, type, trigger, apps, assets used)
2. Claude asks clarifying questions about the procedure details
3. Claude writes the SOP using a template adapted for the workflow type:
   • Manual: Detailed human steps with time estimates and exact UI paths
   • Augmented: Steps marked as (AI) or (Human) with clear handoff points
   • Automated: Focus on monitoring, intervention points, and error handling
4. After your review and approval, Claude updates the workflow page body in Notion

SOP sections:

Example prompts:

"Write an SOP for the Email Response Drafting workflow"
→ Fetches the workflow from Notion, asks about procedure details,
  produces a complete SOP, and saves it to the workflow page

"Document how the Student Onboarding workflow works"
→ Walks through the SOP writing process, produces Manual-type
  documentation with detailed steps and time estimates

What you'll get: A complete SOP saved directly to your Notion workflow page body, with all sections filled in and adapted for the workflow type.

Platform compatibility: Claude Code ✓ | Claude.ai ✓ (Notion MCP required)

writing-process-guides¶

Command: /ai-registry:process-guide

What it does: Writes Business Process Guide documentation that explains the strategic context and rhythm of a complete business process — when to execute it, why it matters, and how its component workflows fit together. This is the strategic companion to the tactical SOPs.

When to use it: Use this when you need to document how multiple workflows connect into a larger business process. Process guides answer "when, why, and what order" while SOPs answer "how."

How it works:

1. Claude fetches the business process from Notion to get context and linked workflows
2. Claude fetches each linked workflow for sequence and trigger details
3. Claude asks clarifying questions about timing and decision points
4. Claude writes the Process Guide using a structured template
5. After your review, Claude updates the business process page body in Notion

Process Guide sections:

Example prompts:

"Write a process guide for the Email Management business process"
→ Fetches the process and its workflows from Notion, documents
  the end-to-end flow, decision points, and success criteria

"How do the Student Enrollment and Student Onboarding workflows
connect? Document the full process."
→ Creates a process guide showing the workflow sequence,
  handoffs, and timing

What you'll get: A complete Business Process Guide saved to your Notion business process page body. Scannable in 2 minutes, focused on the strategic "when/why/what order" rather than tactical how-to details.

Platform compatibility: Claude Code ✓ | Claude.ai ✓ (Notion MCP required)

registering-building-blocks¶

Command: /ai-registry:register-block

What it does: Registers or updates any AI building block — Skills, Agents, Prompts, or Context MDs — in your Notion AI Building Blocks database. Automatically resolves the asset type from your request, extracts metadata from the appropriate source file, generates a Quick Start Prompt, checks for duplicates, and creates or updates the registry entry.

When to use it: Use this immediately after creating, packaging, or updating any Claude building block to keep your AI Building Blocks database current. Also useful for batch-registering multiple building blocks at once (which can mix asset types).

How it works:

1. Claude resolves the asset type from your request (keywords, file paths, or asks if ambiguous)
2. Claude reads metadata from the appropriate source — SKILL.md frontmatter for skills, agent .md files for agents, or user input for prompts and context MDs
3. Claude generates a Quick Start Prompt — a single, copy-paste-ready sentence that demonstrates the building block's primary use case (Context MDs typically skip this)
4. Claude searches your Notion AI Building Blocks database for an existing entry with the exact same name (to prevent duplicates)
5. If found: updates the existing entry with the latest description and Quick Start Prompt
6. If not found: creates a new entry with name, description, asset type, platform (Claude), and Quick Start Prompt

For batch registration, Claude searches for each building block individually first, builds separate update and create lists, then processes them.

Example prompts:

"Register the email-response-drafting skill in Notion"
→ Reads the SKILL.md, generates a Quick Start Prompt, checks for
  duplicates, and creates or updates the AI Building Blocks entry

"Register the cookbook-question-answerer agent in Notion"
→ Reads the agent .md file, generates a Quick Start Prompt, and
  creates an entry with Asset Type = "Agent"

"Register all skills and agents in Notion"
→ Batch processes every building block, reporting X created and
  Y updated (broken down by asset type)

What you'll get: An entry (or updated entry) in your Notion AI Building Blocks database with: name, description, asset type (Skill, Agent, Prompt, or Context MD), platform, Quick Start Prompt, and GitHub URL (if applicable).

Platform compatibility: Claude Code ✓ | Claude.ai ✓ (Notion MCP required)

syncing-skills-to-github¶

Command: /ai-registry:sync-skills

What it does: Syncs Claude Skills from your local ~/.claude/skills/ directory to a GitHub repository. Detects changes, generates semantic commit messages, pushes to remote, and updates Notion AI Building Blocks with GitHub URLs.

When to use it: Use this after creating or updating skills locally, after exporting skills from cloud to local, or as part of a weekly batch sync. This is Part 2 of the export-to-sync workflow (Part 1 is exporting skills from the cloud to your local machine).

How it works:

1. Detect changes in ~/.claude/skills/ using git status
2. Review what changed — new files, modifications, deletions
3. Identify which skill directories are affected
4. Generate semantic commit messages with prefixes: [CREATE], [UPDATE], [FIX], [SYNC], [RETIRE]
5. Commit changes to the local git repository
6. Push to GitHub remote
7. Update Notion AI Building Blocks database with GitHub URLs and set status to "Deployed"
8. Regenerate the README.md skill index

Three usage modes:

• Single skill sync — "Sync the writing-linkedin-posts skill to GitHub" — commits and pushes just that skill
• Batch sync — "Sync all changed skills to GitHub" — detects all changes, commits everything, updates Notion for each
• Dry run — "Show what would sync to GitHub" — previews changes and commit message without actually committing

Example prompts:

"Sync all changed skills to GitHub"
→ Detects 3 changes (1 new, 2 modified), generates a batch
  commit message, pushes, updates Notion for all 3 skills,
  and regenerates the README

"Show what would sync to GitHub"
→ Previews the changes and generated commit message, asks for
  confirmation before proceeding

What you'll get: Skills committed and pushed to GitHub with descriptive commit messages, Notion AI Building Blocks entries updated with GitHub URLs, and an auto-generated README index.

Platform compatibility: Claude Code ✓ (requires terminal access and git credentials)

Recommended Workflow¶

These skills work best in sequence, building from naming through to version control:

1. Name your workflow — Use naming-workflows to create a consistent entry in Notion
2. Document the procedure — Use writing-workflow-sops to write the SOP for the workflow
3. Connect workflows — Use writing-process-guides to document how workflows fit together in a business process
4. Register your building blocks — Use registering-building-blocks to track Skills, Agents, Prompts, and Context MDs in the AI Building Blocks database
5. Version control everything — Use syncing-skills-to-github to push skills to GitHub with Notion tracking

FAQ¶

Do I need all five skills? No. Each skill works independently. Start with naming-workflows if you're building a registry from scratch, or registering-building-blocks if you just want to track your existing Claude building blocks (skills, agents, prompts, etc.).

What if I don't have Notion set up? Claude will still follow the naming conventions, SOP templates, and documentation patterns — it just won't save to Notion. See Notion Registry Setup to configure the MCP connector.

What's the difference between a Process Guide and an SOP? A Process Guide is strategic: when to execute, why it matters, what order the workflows go in. An SOP is tactical: step-by-step instructions for executing a single workflow. Think of the Process Guide as the playbook and SOPs as the play pages.