npx claudepluginhub wanderingstan/vibe-checkWant just this skill?
Then install: npx claudepluginhub u/[userId]/[slug]
Search through Claude Code conversation history. Use when user says "search my conversations", "find when I talked about X", "what did claude say about Y", or "search claude history".
This skill uses the workspace's default tool permissions.
Search Claude Conversations
Purpose: Search through Claude Code conversation history using the vibe-check MCP server
Using the MCP Tool
The vibe-check MCP server provides a vibe_search tool that handles all database queries automatically.
Tool: mcp__vibe-check__vibe_search
Parameters:
query(required): Search term with FTS5 syntax support (see below)repo(optional): Filter to specific repository namedays(optional): Limit to last N dayssession_id(optional): Search within specific sessionlimit(optional): Maximum results (default: 20)
FTS5 Query Syntax (powerful full-text search with relevance ranking):
- Simple:
authentication- finds messages containing this word - Phrase:
"user authentication"- exact phrase match - Boolean:
auth AND oauth- both terms must be present - Exclude:
login NOT password- exclude certain terms - Prefix:
auth*- matches authentication, authorize, etc. - Multiple terms:
database schema- OR search (either term)
Results are automatically ranked by relevance with star indicators (⭐⭐⭐ = most relevant).
Usage Flow
When user requests a search:
-
Extract search criteria from user's question:
- Search term/keyword
- Date range (if specified) → convert to
daysparameter - Repository (if specified) → use
repoparameter - Session ID (if specified) → use
session_idparameter
-
Call the MCP tool with appropriate parameters
-
Present results to user - the tool already formats them nicely
-
Offer follow-up actions:
- View full session (use
vibe_sessiontool) - Narrow search (call
vibe_searchagain with more filters) - Open in browser (use
vibe_viewtool)
- View full session (use
Example Interactions
Example 1: Simple Keyword Search
User: "search my conversations for 'authentication'"
Claude: [Calls mcp__vibe-check__vibe_search with query="authentication"]
[Tool returns formatted results showing sessions and message previews]
Would you like to:
- View full details of a specific session
- Open a session in your browser
- Search for related terms
Example 2: Search with Repository Filter
User: "find when I worked on API endpoints in the vibe-check repo"
Claude: [Calls mcp__vibe-check__vibe_search with query="API endpoints", repo="vibe-check"]
[Tool returns filtered results]
Example 3: Recent Search
User: "what did I work on yesterday?"
Claude: [Note: For "recent work" queries, use the vibe_recent tool instead]
[Calls mcp__vibe-check__vibe_recent with period="yesterday"]
Example 4: Search Within Session
User: "search for 'database' in session 2d072129-d799-4aa5-b19d-5b5617f5a9de"
Claude: [Calls mcp__vibe-check__vibe_search with query="database", session_id="2d072129-d799-4aa5-b19d-5b5617f5a9de"]
Example 5: Advanced FTS5 Phrase Search
User: "find conversations about 'full text search'"
Claude: [Calls mcp__vibe-check__vibe_search with query='"full text search"']
[Tool returns exact phrase matches, ranked by relevance with star indicators]
Example 6: FTS5 Boolean Search
User: "find conversations about authentication but not OAuth"
Claude: [Calls mcp__vibe-check__vibe_search with query="authentication NOT oauth"]
[Tool returns results containing 'authentication' but excluding 'oauth']
Example 7: FTS5 Prefix Search
User: "find conversations mentioning anything related to auth"
Claude: [Calls mcp__vibe-check__vibe_search with query="auth*"]
[Tool returns results matching auth, authentication, authorize, authorized, etc.]
Related Tools
Use these complementary MCP tools:
mcp__vibe-check__vibe_recent: Show recent sessions by time period (today, yesterday, week, month)mcp__vibe-check__vibe_session: Get detailed info about a specific sessionmcp__vibe-check__vibe_view: Open a session in the local web viewermcp__vibe-check__vibe_stats: Show overall usage statistics
Error Handling
The MCP tool handles errors automatically and provides helpful messages:
- If no results found, it suggests broader search terms and checking if monitor was running
- If database not accessible, it provides file path information
- All database locking is handled internally with read-only mode
Tips
- For broad exploration of recent work, use
vibe_recentfirst - For targeted keyword searches, use
vibe_searchwith FTS5 syntax - Use FTS5 features for better results:
- Phrase search (
"exact phrase") for precise matches - Prefix search (
term*) to find variations - Boolean operators (
AND,OR,NOT) for complex queries
- Phrase search (
- Combine filters (repo + days) to narrow results
- Results are ranked by relevance - most relevant appear first with more stars
- Use
vibe_viewto open interesting sessions in browser for full context
Advanced: Custom SQL Queries
For complex queries not covered by vibe_search, use the mcp__vibe-check__vibe_sql tool:
mcp__vibe-check__vibe_sql(
query="SELECT ... FROM conversation_events WHERE ...",
limit=100 # optional, max 1000
)
This provides read-only access to the full database with custom SQL. See the vibe-check-sql skill for more examples.
For schema information, see ~/.vibe-check/SCHEMA.md (auto-generated) or use the Read tool.
Similar Skills
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Build apps with the Claude API or Anthropic SDK. TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`/`claude_agent_sdk`, or user asks to use Claude API, Anthropic SDKs, or Agent SDK. DO NOT TRIGGER when: code imports `openai`/other AI SDK, general programming, or ML/data-science tasks.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.