How this command is triggered — by the user, by Claude, or both
Slash command
/mb:recordThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Record Knowledge to MindBase Current date: !`date +%Y-%m-%d` ## Resolve MindBase Path First, read `~/.claude/plugins/mindbase/config.json` to get the `mindbase_path`. If the file does not exist, tell the user to run `/kb:setup` first and STOP. ## Your Task Analyze the current conversation and extract valuable knowledge to save into the MindBase knowledge base using the PARA method. ## Process ### Step 1: Extract Knowledge Points Review the entire conversation and identify distinct pieces of knowledge worth recording. Look for: - Technical concepts explained or discovered → **03_Re...
Current date: !date +%Y-%m-%d
First, read ~/.claude/plugins/mindbase/config.json to get the mindbase_path. If the file does not exist, tell the user to run /kb:setup first and STOP.
Analyze the current conversation and extract valuable knowledge to save into the MindBase knowledge base using the PARA method.
Review the entire conversation and identify distinct pieces of knowledge worth recording. Look for:
For each knowledge point, determine:
Show the user a summary of what you plan to record:
I found N knowledge points to record:
1. [Title] → 03_Resources/filename.md
Tags: [tag1, tag2]
Summary: one line
2. [Title] → 02_Areas/filename.md
Tags: [tag1, tag2]
Summary: one line
Ask the user to confirm, modify, or skip any entries.
For each confirmed entry:
After writing all entries:
_index.md — add new entries in alphabetical orderindex.md — increment count, update date, add to category section and recent entriesShow the user a final summary:
Recorded N entries to MindBase:
- 03_Resources/filename.md
- 02_Areas/other-filename.md
Updated indexes: 03_Resources/_index.md, index.md
If the user provides $ARGUMENTS, use it as a hint for what to focus on:
npx claudepluginhub foresx/mindbase-plugin --plugin mb/recordRecords network traffic from a web app at <url> [--duration <minutes>] [--mitmproxy] using Playwright or fallback, saving raw capture to traffic-capture/raw-traffic.json without generating a CLI.
/recordRecords browser interactions to generate test YAML files; also supports AI-assisted editing of existing tests.
/recordStarts recording browser actions for <action-name> [--input key=value ...] to generate replayable API skills. Perform actions in browser, say 'stop' to process HAR and generate skills.