Portfolio Agent Skills Library & Knowledge Sync

CLAUDE CODE · CODEX · GIT · NOTION · Cork AI Consulting

Skills Library

Agent Skills Library & Knowledge Sync

2026 2026 3 min read

A two-founder consultancy runs on prompts, scripts and agent workflows. Ours had grown into 28 separate ones, living in different folders and tools, so every improvement helped one person once. I turned them into a library both of us — and every coding agent we use — load the same way.

  • 28 → 1 workflows consolidated into one library
  • Git ⇄ Notion synced automatically, one source of truth
  • Multi-agent same skills for Claude Code and Codex
Skills Library 2026 Mock · rendered from this write-up
  • Value 28 Workflows turned into skills
  • Time Shared Improvements compound
  • Effort Internal Built for our own delivery
  • Quality Versioned Reviewed like code
  1. Gate One library, one format
  2. Step 02 Version-controlled like code
  3. Step 03 Git and Notion kept in sync
  4. Output 28 Workflows turned into skills
28 Workflows turned into skills28 → 1 workflows consolidated into one library

01 — Context

The problem.

Agent workflows multiply quickly. Without structure they end up duplicated, slightly different on each machine, and impossible to improve together.

The company’s knowledge was split between Git, where the agents work, and Notion, where people work — so one of them was always out of date.

02 — Method

The approach.

The build, in the order it happened.

  1. One library, one format

    Every workflow became a skill with the same structure — purpose, inputs, steps, guardrails — so any agent can discover and run it.

  2. Version-controlled like code

    Skills live in a shared Git repository. Changes are reviewed, history is kept, and nothing is lost when a laptop is replaced.

  3. Git and Notion kept in sync

    An automatic sync keeps the knowledge base consistent across both, so people and agents read the same truth.

Flow · from the approach steps
  1. Sources Claude CodeCodex CLIMCP
  2. Gate One library, one format
  3. Step 02 Version-controlled like code
  4. Step 03 Git and Notion kept in sync
  5. Output 28 Workflows turned into skills

03 — A run

What one run looks like.

The steps above, played as the agent would walk them. A reading of the write-up, not a recording of a real run.

How a run looks · illustrative, not a log

run skills-library

[plan] 3 steps

[gate] ✓ One library, one format

↳ Every workflow became a skill with the same structure

[step 02] Version-controlled like code

↳ Skills live in a shared Git repository

[step 03] Git and Notion kept in sync

↳ An automatic sync keeps the knowledge base consistent across both, so p…

[tools] Claude Code · Codex CLI · MCP · Git / GitHub · Notion API · Node · Markdown

[handoff] 28 standalone AI workflows consolidated into one shared skills library

[exit 0]

04 — Outcome

What changed.

  • 28 standalone AI workflows consolidated into one shared skills library.
  • A knowledge base that syncs Git and Notion automatically as one source of truth.

05 — Screens

What it looks like.

Generated from the write-up rather than captured from a client's screen — the shape of the thing, not a leaked one.

06 — Stack & role

Built with.

  • Claude Code
  • Codex CLI
  • MCP
  • Git / GitHub
  • Notion API
  • Node
  • Markdown
Role
Co-founder — design and build
Duration
2026
Client
Cork AI Consulting
Period
2026

Got a report that takes two days to assemble?

That is usually a one-week fix. Tell me what you are reconciling by hand and I will tell you what I would automate first.