Slash Command

/SKILL

Searches team knowledge across messages, project state, and task history. Compiles relevant context from TeamMCP sources to answer questions.

developer-tools

npx claudepluginhub cookjohn/teammcp

Details

Namespaceskills/search-context/

Allowed Tools

mcp__teammcp__search_messagesmcp__teammcp__get_statemcp__teammcp__list_tasksmcp__teammcp__get_historymcp__teammcp__get_state_historymcp__teammcp__get_agents

Prompt Preview

# Search Team Knowledge

## Instructions

1. **Parse the query**
   - Extract the search query from `$ARGUMENTS`.
   - If no query is provided, ask the user what they want to search for.
   - Identify key terms, agent names, project IDs, or date ranges mentioned.

2. **Search messages**
   - Call `search_messages` with the query terms to find relevant conversations.
   - Note the channel, sender, timestamp, and content of matching messages.
   - If results are sparse, try alternative phrasings or broader terms.

3. **Check project state**
   - If the query relates to a specific project, cal...

Command Content

Other plugins with /SKILL

/search

Searches CORE memory for past conversations, user preferences, project context, and decisions using a provided query. Displays relevant episodes, facts, and timestamps.

core-memory

/recall

119

Loads the spectre-recall skill to search and retrieve project knowledge using the provided query.

spectre

/onboarding

Generates onboarding guide for a team or project: overview via Glean, key people, vetted essential docs, and recent priorities.

glean-docs

/ask

Answers questions about past work by searching memories using the provided question, combining with current context, and delivering a structured response citing sources.

evermem

/search-historian

539

Searches past Claude conversation history for solutions, decisions, and context matching a query. Retrieves up to 5 relevant results via historian MCP.

claude-historian

/status

Displays concise team planning status from planning files, showing phase progress, active teammates, key findings, blockers, and next actions.

planning-with-teams

Stats

Stars37

Forks3

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Search Team Knowledge ## Instructions 1. **Parse the query** - Extract the search query from `$ARGUMENTS`. - If no query is provided, ask the user what they want to search for. - Identify key terms, agent names, project IDs, or date ranges mentioned. 2. **Search messages** - Call `search_messages` with the query terms to find relevant conversations. - Note the channel, sender, timestamp, and content of matching messages. - If results are sparse, try alternative phrasings or broader terms. 3. **Check project state** - If the query relates to a specific project, cal...

Search Team Knowledge

Instructions

Parse the query

Extract the search query from $ARGUMENTS.
If no query is provided, ask the user what they want to search for.
Identify key terms, agent names, project IDs, or date ranges mentioned.

Search messages

Call search_messages with the query terms to find relevant conversations.
Note the channel, sender, timestamp, and content of matching messages.
If results are sparse, try alternative phrasings or broader terms.

Check project state

If the query relates to a specific project, call get_state with the project ID.
If the query mentions status, progress, or blockers, check relevant state fields.
Call get_state_history if the query is about how something changed over time.

Check task history

Call list_tasks and filter results relevant to the query.
Look for tasks matching the topic, assigned to mentioned agents, or in the queried status.

Check channel history (if needed)

If message search is insufficient, call get_history for specific channels that are likely relevant.

Compile results

Organize findings into a structured response:

Search Results for: "<query>"

Messages:
- [timestamp] #channel @sender: relevant excerpt
- ...

Project State:
- [project_id] field: value (if relevant)

Tasks:
- [task_id] title — status — assignee

Summary:
- Brief synthesis of what was found and how it answers the query

Highlight gaps

If the search did not find sufficient information, note what is missing.
Suggest who to ask or where to look next.

$ARGUMENTS

/search-context <query>

Example: /search-context authentication implementation decision

Example: /search-context what did CEO say about launch timeline

Search Team Knowledge

Instructions

Parse the query
- Extract the search query from $ARGUMENTS.
- If no query is provided, ask the user what they want to search for.
- Identify key terms, agent names, project IDs, or date ranges mentioned.
Search messages
- Call search_messages with the query terms to find relevant conversations.
- Note the channel, sender, timestamp, and content of matching messages.
- If results are sparse, try alternative phrasings or broader terms.
Check project state
- If the query relates to a specific project, call get_state with the project ID.
- If the query mentions status, progress, or blockers, check relevant state fields.
- Call get_state_history if the query is about how something changed over time.
Check task history
- Call list_tasks and filter results relevant to the query.
- Look for tasks matching the topic, assigned to mentioned agents, or in the queried status.
Check channel history (if needed)
- If message search is insufficient, call get_history for specific channels that are likely relevant.

Compile results

Organize findings into a structured response:

Search Results for: "<query>"

Messages:
- [timestamp] #channel @sender: relevant excerpt
- ...

Project State:
- [project_id] field: value (if relevant)

Tasks:
- [task_id] title — status — assignee

Summary:
- Brief synthesis of what was found and how it answers the query

Highlight gaps
- If the search did not find sufficient information, note what is missing.
- Suggest who to ask or where to look next.

$ARGUMENTS

/search-context <query>
Example: /search-context authentication implementation decision
Example: /search-context what did CEO say about launch timeline