From the-space-memory
Search the cross-workspace knowledge base using hybrid FTS5 + vector search. Use when: user asks about past research, notes, decisions, or anything that might be in the knowledge base. Examples: "前に調べたLoRaの件どうなってた?", "ナレッジから探して", "〜について調べた記録ある?", "〜あったっけ?", "以前まとめた〜", "Search for anything about X", "What did I write about X?"
How this skill is triggered — by the user, by Claude, or both
Slash command
/the-space-memory:searchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search the knowledge base using `tsm search`.
Search the knowledge base using tsm search.
cd "$CLAUDE_PROJECT_DIR" && "${CLAUDE_PLUGIN_ROOT}/bin/tsm" search -q "$ARGUMENTS" -k 5 -f json --include-content 3
| Flag | Description |
|---|---|
-q <query> | Search query |
-k <n> | Number of results (default: 5) |
-f json | JSON output format |
--include-content <n> | Include content for top N results |
--recent <duration> | Filter by recency (e.g., 30d, 7d) |
--after <date> | Filter after date (e.g., 2025-01) |
--year <year> | Filter by year |
--path <prefix> | Filter by file path prefix |
--fallback fts-only | Use FTS-only mode if embedder is down |
$ARGUMENTS is empty, do nothing — do not guess or infer a querydeep-research agentParse the JSON results and present them like this:
### Knowledge Search: "<query>"
1. **[Section Title]** — `source/file.md`
> snippet of matching content...
2. **[Section Title]** — `source/file.md`
> snippet of matching content...
_N results found. For deeper investigation, delegate to the deep-research agent._
npx claudepluginhub yutaro1985/the-space-memory --plugin the-space-memoryGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.