メニュー
PROACTIVELY used for routing meeting items to Brain CLAUDE.md files. Discovers Brains dynamically, matches items by confidence, handles unmatched content. Works with analyzing-meetings and summarizing-meetings skills.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/samarv/Shanon --skill routing-brainsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | routing-brains |
| description | PROACTIVELY used for routing meeting items to Brain CLAUDE.md files. Discovers Brains dynamically, matches items by confidence, handles unmatched content. Works with analyzing-meetings and summarizing-meetings skills. |
Route meeting items to appropriate Brain CLAUDE.md files:
For product-specific context, see CLAUDE.local.md.
CRITICAL: Never hardcode Brain names. Always discover dynamically.
1. List all subdirectories in /Brains/
2. For each subdirectory:
a. Check if CLAUDE.md exists
b. If yes, read and parse the file
c. Extract keywords and context for matching
3. Build Brain registry with:
- Brain name (folder name)
- Core objective (from CLAUDE.md)
- Key terms (extracted from all sections)
- Status (Active/Paused/Completed)
From each Brain's CLAUDE.md, extract:
| Section | What to Extract |
|---|---|
| Core Objective | Main nouns, verbs, product names |
| Key Decisions | Decision topics, technical terms |
| Documents | Document names, feature names |
| Stakeholders | Team names, product areas |
| Open Questions | Problem domains, blockers |
Brain: "[Brain-name]"
Keywords: [relevant terms extracted]
Core Theme: "[one-line description]"
Status: Active
| Level | Threshold | Action |
|---|---|---|
| High | >= 0.8 | Auto-route to Brain |
| Medium | 0.6 - 0.8 | Route with [Review] flag |
| Low | 0.4 - 0.6 | Flag as potential, ask user |
| None | < 0.4 | Mark as unmatched |
For each meeting item:
Keyword Match Score (0-0.5):
Semantic Match Score (0-0.5):
Combined Score: Keyword + Semantic
Items CAN match multiple Brains if:
Extract discrete items from meeting content:
| Item Type | How to Identify |
|---|---|
| Decision | "We decided...", "Let's go with...", "The approach is..." |
| Action Item | "I'll...", "Can you...", "[Name] will...", "TODO:" |
| Discussion Point | Topic shifts, extended back-and-forth |
| Blocker | "We can't proceed...", "Waiting on...", "Blocked by..." |
| Open Question | "We need to figure out...", "TBD:", "?" |
| Status Update | "Update on...", "Progress:", metrics discussion |
For each item:
1. Run matching algorithm
2. If High confidence (>= 0.8) → Route to Brain
3. If Medium confidence (0.6-0.8) → Route with [Review] flag
4. If Low confidence (0.4-0.6) → Add to potential matches
5. If No match (< 0.4) → Add to unmatched list
If item matches multiple Brains:
CRITICAL: Ask ONE question at a time. Do not overwhelm the user.
Step 1: Announce count
I found [N] items that don't clearly match any existing Brain.
Let me walk through each one with you.
Step 2: Present FIRST item only
**Item 1 of [N]**: [Brief summary]
**Type**: [Decision/Action/Discussion/Blocker/Question]
**Content**: [Full item - 1-2 sentences]
**Context**: [Why this came up]
**Potential match**: [Brain] (low confidence) OR "No matching Brain"
What would you like to do?
a) Assign to [Brain 1]
b) Assign to [Brain 2]
c) Create a new Brain
d) Leave in temp folder
e) Discard (not relevant)
Step 3: Wait for response before continuing
Step 4: Proceed to next item
Got it - [acknowledge choice].
**Item 2 of [N]**: [Next summary]...
If user chooses to create new Brain:
Step 1: "What should this Brain be called? (Suggested: '[name]')" → Wait for response
Step 2: "In one sentence, what's the core objective?" → Wait for response
Step 3: Create folder, generate CLAUDE.md, route item, confirm
Items to route:
1. Decision: "Use React for dashboard migration"
2. Action: "Update API documentation before launch"
3. Discussion: "Potential partnership with external vendor"
## Routing Results
### High Confidence Routes
- **Decision: React migration** → frontend-modernization (0.92)
### Medium Confidence Routes
- **Action: API documentation** → api-platform (0.71) [Review]
### Unmatched Items
1 item requires user input:
**Item 1 of 1**: Partnership discussion
**Type**: Discussion Point
**Content**: Potential collaboration with external vendor
**Potential match**: No matching Brain
What would you like to do?
a) Assign to frontend-modernization
b) Assign to api-platform
c) Create a new Brain
d) Leave in temp folder
e) Discard