Load and persist LaightDB MCP context across sessions.
npx skills add https://github.com/gtrig/LaightDB --skill laightdb-rolling-context
Please help me install this Agent Skill. Skill: laightdb-rolling-context Source: https://github.com/gtrig/LaightDB/tree/main/.cursor/skills/laightdb-rolling-context Command: npx skills add https://github.com/gtrig/LaightDB --skill laightdb-rolling-context
Proactively loads relevant LaightDB context at the start of substantive work and persists concise rolling notes before wrapping up, using LaightDB MCP tools without waiting for the user to say "store" or "search". Use whenever this workspace has the LaightDB MCP server enabled and the user is doing multi-step implementation, debugging, or design that should survive across sessions.
At the start of a task, call search_context with keywords to retrieve prior context, then use store_context to persist progress when milestones are reached.
High-intent search queries and answers about installing and using this skill.
To keep context alive across sessions, this Skill proactively loads relevant prior context at task start and persists concise rolling notes using MCP tools, ensuring your multi-step debugging continuity is preserved.
The best way to persist rolling notes during multi-step implementation is using the store_context MCP tool to save progress at milestones, preventing context loss when sessions end or switch.
Yes, this context persistence approach works exclusively with the LaightDB MCP server, relying on its store_context and search_context tools to load and persist contextual metadata automatically.
To retrieve prior context at the start of a new design task, the Skill automatically calls search_context with relevant keywords to load existing metadata before you begin your work.
Yes, you can automatically store context without manual triggers because this Skill proactively persists rolling notes before wrapping up tasks, using store_context without waiting for explicit user commands.
You should not use automatic context loading for session persistence when the LaightDB MCP server is not enabled in your workspace or when tasks are single-step and do not require continuity.
gtrigStores and retrieves LaightDB MCP context for Cursor sessions via store_context and get_context.
CES-LtdCreate, checkpoint, and resume multi-step workflows with task states.
ovachieverOrchestrate 600+ scientific tools into multi-step research workflows via MCP.
davidmoneilAutomate Claude Code session checkpoints with YAML frontmatter and MCP-safe state.
