Your First Skills: Enriching the Workspace

You have your workspace set up. Now it is time to feed it.

The core pattern behind every enrichment skill is the same:

Unstructured input (a transcript, a document, a quick thought) --> Structured context spread across multiple files in your knowledge base.

A single meeting transcript might update three people profiles, log two decisions, note a political dynamic, and add four action items to the work board -- all in one pass. That is the leverage. You do not file things manually; the skill reads the input, extracts the signals, and writes them where they belong.

---

The Three Enrichment Skills

There are three skills, each tuned for a different kind of input. All three write to the same knowledge base structure, so context compounds no matter which entry point you use.

Skill	Input	Best For
/process-meeting	Meeting transcript, call notes, 1:1 summaries	Richest extraction -- people, decisions, dynamics, actions
/pkb-file	Documents, slide decks, research articles, proposals	Filing formal artifacts with extracted insights
/pkb-note	A sentence or two, a quick observation	Capturing hallway conversations, shower thoughts, ad-hoc context

<div style="max-width:720px;margin:24px auto;font-family:-apple-system,BlinkMacSystemFont,'Segoe UI',Roboto,sans-serif;">
  <div style="display:flex;gap:12px;justify-content:center;flex-wrap:wrap;">
    <div style="flex:1;min-width:180px;max-width:220px;">
      <div style="background:#003580;color:#fff;border-radius:10px;padding:16px;text-align:center;">
        <div style="font-size:24px;margin-bottom:4px;">🎙️</div>
        <div style="font-weight:700;font-size:14px;">/process-meeting</div>
        <div style="font-size:11px;opacity:0.8;margin-top:4px;">Meeting transcript, call notes</div>
      </div>
    </div>
    <div style="flex:1;min-width:180px;max-width:220px;">
      <div style="background:#0071c2;color:#fff;border-radius:10px;padding:16px;text-align:center;">
        <div style="font-size:24px;margin-bottom:4px;">📄</div>
        <div style="font-weight:700;font-size:14px;">/pkb-file</div>
        <div style="font-size:11px;opacity:0.8;margin-top:4px;">Documents, decks, articles</div>
      </div>
    </div>
    <div style="flex:1;min-width:180px;max-width:220px;">
      <div style="background:#4a90d9;color:#fff;border-radius:10px;padding:16px;text-align:center;">
        <div style="font-size:24px;margin-bottom:4px;">💬</div>
        <div style="font-weight:700;font-size:14px;">/pkb-note</div>
        <div style="font-size:11px;opacity:0.8;margin-top:4px;">Quick thoughts, hallway chats</div>
      </div>
    </div>
  </div>
  <div style="text-align:center;margin:12px 0 4px;">
    <span style="font-size:20px;color:#003580;">↓ ↓ ↓</span>
  </div>
  <div style="display:flex;gap:8px;flex-wrap:wrap;justify-content:center;">
    <div style="background:#f5f2ee;border:1px solid #e0dbd4;border-radius:6px;padding:8px 14px;font-size:12px;"><strong style="color:#003580;">People/</strong> <span style="color:#8a8580;">George.md, Elaine.md</span></div>
    <div style="background:#f5f2ee;border:1px solid #e0dbd4;border-radius:6px;padding:8px 14px;font-size:12px;"><strong style="color:#003580;">Decisions/</strong> <span style="color:#8a8580;">gateway-arch.md</span></div>
    <div style="background:#f5f2ee;border:1px solid #e0dbd4;border-radius:6px;padding:8px 14px;font-size:12px;"><strong style="color:#003580;">Meetings/</strong> <span style="color:#8a8580;">structured notes</span></div>
    <div style="background:#f5f2ee;border:1px solid #e0dbd4;border-radius:6px;padding:8px 14px;font-size:12px;"><strong style="color:#003580;">Work-Board</strong> <span style="color:#8a8580;">actions for George, Elaine</span></div>
  </div>
  <p style="text-align:center;color:#8a8580;font-size:12px;margin-top:10px;">All three skills extract signals and write them to the same KB structure. Context compounds.</p>
</div>

---

/process-meeting -- The Richest Entry Point

This is the skill you will use most often and the one that generates the most value per invocation. Hand it a meeting transcript (or even rough notes from a call) and it will:

1. Detect the meeting type -- standup, 1:1, planning session, review, etc.
2. Validate speaker names against people already in your KB.
3. Extract and file:
   • Meeting notes with summary, key discussion points, and attendees --> Meetings/
   • Decisions with context and rationale --> Decisions/
   • Action items assigned to specific people --> Work-Board
   • People updates -- new context about what someone cares about, their positions, communication style --> People/
   • Dynamics -- political signals, alliances, tensions --> Dynamics/

A single 30-minute meeting transcript can touch a dozen files across your knowledge base. After a week of processing your meetings, Claude has a remarkably detailed picture of your working world.

Example Usage

/process-meeting

<paste your transcript or notes here>

That is it. The skill handles the rest.

---

/pkb-file -- Filing Formal Documents

Use this when you encounter a document worth remembering: a strategy deck, a research report, an architecture proposal, a competitor analysis.

The skill will:

• Summarize the document and extract key insights
• Cross-reference people, projects, and decisions mentioned
• Update people profiles if the document reveals new context about someone
• Log decisions if the document captures or proposes any
• File the artifact with metadata so you can find it later

Example Usage

/pkb-file

<paste document content, or provide a file path>

---

/pkb-note -- Quick Capture

Sometimes you just need to jot something down. A comment someone made in passing. A realization you had while reading. A connection between two things that clicked.

/pkb-note is designed for these moments. It takes minimal input and figures out where it belongs:

• A note about a person? Updates their profile.
• A decision you heard about? Logs it in Decisions/.
• A task you need to track? Adds it to the work board.
• Just general context? Files it appropriately.

Example Usage

/pkb-note George mentioned he's moving to the platform team next quarter.
He's worried about the migration timeline.

That two-line note updates George's profile with his upcoming move, flags his concern about the migration, and might add a follow-up item to the work board.

---

What Happens After a Few Days

After processing five or six meetings, filing a couple of documents, and dropping in a handful of quick notes, your knowledge base starts to look like this:

• People/ contains profiles for 10-15 colleagues, each with their role, what they care about, their communication preferences, and recent context
• Decisions/ has a growing log of architectural choices, process changes, and strategic directions -- each with rationale and who was involved
• Meetings/ holds structured, searchable notes from every conversation
• Work-Board tracks open action items, who owns them, and what is blocked
• Dynamics/ captures the unwritten context -- who aligns with whom, where tension exists, what the real priorities are beneath the official ones

This is the web of connected context that makes Claude genuinely useful as a thought partner. When you ask a question, Claude does not just know the answer from a single source -- it can synthesize across everything it has seen.

---

Start Here, Then Explore

If you are just getting started, begin with /process-meeting. It is the highest-value skill because meetings are where the most context lives -- decisions get made, people reveal their priorities, action items get assigned, and dynamics play out.

Process three or four of your recent meetings and you will immediately see the knowledge base come alive. From there, layer in /pkb-file for important documents and /pkb-note for the small moments that would otherwise be lost.

---

Next: Daily and Weekly Rituals