context-save

Save session-derived insights into a local context-dictionary via POST requests.

Updated Aug 14, 2025
One-click install
npx skills add https://github.com/kaikojima05/ai-agent-rules --skill context-save-kaikojima05
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/kaikojima05/ai-agent-rules/tree/main/skills/context-save
Command: npx skills add https://github.com/kaikojima05/ai-agent-rules --skill context-save-kaikojima05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context generated during a coding session often gets lost after the work is done, making it hard to reuse hard-won decisions, discoveries, and caveats later.

Core Features & Use Cases

  • Insight capture from session context: Converts the user’s summary (or a single clarification question when the user omits arguments) plus current session context into one or more structured insights.
  • Typed knowledge records: Registers insights as discovery, decision, solution, issue, or caveat, with required/optional fields such as rationale, detail, tags, and followUps.
  • Bulk registration for multiple insights: Uses the bulk API when a single session yields multiple independent insights.
  • Operational safety check: Presents a confirmation message to the user before sending data to the local API.

Quick Start

Use /context-save with a short description of the problem cause and solution to store the resulting insight(s) in the context-dictionary API for later reuse.

Frequently Asked Questions about context-save

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save session context and development decisions for future retrieval?▼

You can save session context by transforming a user-provided summary into structured insights, then persisting them into a local context-dictionary via API POST requests for future retrieval.

Can I bulk register multiple development discoveries from a single coding session?▼

Yes, when a single session yields multiple independent insights, the tool uses a bulk API endpoint to register all development discoveries, decisions, and solutions at once.

What types of knowledge records can I capture from my developer workflow?▼

You can capture typed knowledge records categorized as discovery, decision, solution, issue, or caveat, including optional fields like rationale, detail, tags, and followUps.

Do I need a local API available to store session memory and insights?▼

Yes, storing session memory requires local API availability to send POST requests, and the system enforces user confirmation before transmitting required JSON fields like type, content, and agent.

What happens if I omit arguments when trying to capture session insights?▼

If you omit arguments, the system asks a single clarification question to gather the needed summary, converts it along with current session context into structured insights, and proceeds with the capture.

Is there a way to prevent accidental overwrites when saving session memory to the context store?▼

Yes, an operational safety check presents a confirmation message to the user before sending any data to the local API, preventing accidental or unintended insight registrations.