Team Knowledge Base

Why this exercise?

Team knowledge gets lost in Slack threads, meeting notes, and people's heads. Here you create a living knowledge base in Google Drive — and teach ToqanClaw to consult it whenever it needs team context.

Prerequisite

TC3 (Google Workspace MCP connected). ToqanClaw needs to read and write in your Drive. Slack MCP is optional but allows the knowledge base to be populated with conversation data.

Step 1 — Create the document in Drive

Ask ToqanClaw to create the structured document:

Create a new Google Doc called "Team Knowledge Base"
in my Google Drive.

Structure it with these sections:

# Team Knowledge Base — [Team Name]
Last updated: [date]

## Who we are
- Team:
- Leader:
- Mission:
- Main KPIs:

## Important decisions
| Date | Decision | Context | Who decided |
|------|---------|----------|-------------|

## Processes and playbooks
### [Process name 1]
- When to use:
- Steps:
- Owner:

## Frequently asked questions
### [Question 1]
Answer...

## Useful links
- [Dashboard X](link)
- [Documentation Y](link)

Make the document editable. Give me the link.

Step 2 — Populate with real context

Now ask ToqanClaw to fill it with real information. If you have Slack MCP connected, use this prompt:

Search my Slack channels for the last 2 weeks.
Find:
1. Any decisions that were made in threads
2. Processes or playbooks that were shared
3. Recurring questions people ask
4. Important links that were shared

Add everything you find to the Team Knowledge Base
document you just created. Use the right sections.

Keep the original language of each item.

Without Slack MCP? You can manually add content to the document, or ask ToqanClaw to populate it from your emails and calendar notes: "Search my recent emails and calendar notes for decisions, processes, and key information. Add them to the Team Knowledge Base."

Step 3 — Teach ToqanClaw to consult it

Create a skill that makes ToqanClaw consult the KB automatically:

Create a skill called "team_kb".

This skill should:
1. When anyone asks a question about our team's
   processes, decisions, or context — first check
   the "Team Knowledge Base" document in Google Drive
2. If the answer is there, cite it
3. If the answer is NOT there, answer from available context
   and then ADD the new information to the KB document
4. The KB should grow organically — every time the team
   learns something new, it gets documented

Save this as a skill.

Step 4 — Test

Using team_kb, answer this:
What were the main decisions our team made this week?

Ideas to expand the Knowledge Base

Content	Source	How to capture
Meeting summaries	TC12 outputs	Redirect summaries to the doc
Team glossary	Conversations	Terms and acronyms the team uses
Onboarding	Manual	"What I wish I knew on day 1"
Retrospectives	Meetings	Wins, mistakes, lessons learned