mem search

Data Community

Skill notes

When to Use

Use when users ask about PREVIOUS sessions (not current conversation): "Did we already fix this?" "How did we solve X last time?" "What happened last week?"

3-Layer Workflow (ALWAYS Follow)

NEVER fetch full details without filtering first. 10x token savings.

Step 1: Search - Get Index with IDs

Use the search MCP tool: Returns: Table with IDs, timestamps, types, titles (~50-100 tokens/result) Parameters: query (string) - Search term limit (number) - Max results, default 20, max 100

Step 2: Timeline - Get Context Around Interesting Results

Use the timeline MCP tool: Or find anchor automatically from query: Returns: depth_before + 1 + depth_after items in chronological order with observations, sessions, and prompts interleaved around the anchor. Parameters: anchor (number, optional) - Observation ID to center around

Step 3: Fetch - Get Full Details ONLY for Filtered IDs

Review titles from Step 1 and context from Step 2. Pick relevant IDs. Discard the rest. Use the get_observations MCP tool: ALWAYS use get_observations for 2+ observations - single request vs N requests. Parameters: ids (array of numbers, required) - Observation IDs to fetch

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@thedotmack · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview mem-search.preview
# Step 2: Timeline - Get Context Around Interesting Results

timeline(anchor=11131, depth_before=3, depth_after=3, project="my-project")

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.