Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From pensyve
Loads relevant Pensyve memories at session start for cross-session continuity. Use when switching projects or needing historical context.
npx claudepluginhub major7apps/pensyve --plugin pensyveHow this skill is triggered — by the user, by Claude, or both
Slash command
/pensyve:context-loaderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Load relevant memories from Pensyve at the start of a session to provide cross-session continuity. Respects the `context_loading` configuration setting.
Persistently stores and retrieves cross-session context via MCP server. Search prior work, ingest meeting notes, and get synthesized summaries of identity, projects, and priorities.
Classifies user recall intents (resume, decisions, known issues, recent sessions, keyword search) and routes to the appropriate harness-mem MCP tool or SSOT file.
Recalls past context, decisions, and discussions from Memsy memory. Activates on retrieval-intent queries like "what did we decide" or "search past conversations."
Share bugs, ideas, or general feedback.
Load relevant memories from Pensyve at the start of a session to provide cross-session continuity. Respects the context_loading configuration setting.
When this skill is invoked (typically at session start), follow these steps:
Check the mode argument if provided. Otherwise, respect the context_loading setting from the plugin configuration (pensyve-plugin.local.md):
/recall to search memories on demand."If no mode is specified and no configuration is found, default to summary.
Run the following pensyve_recall queries to gather session context:
pensyve_recall with query "decided" (limit: 5)pensyve_recall with query "issue OR bug OR error OR problem" (limit: 5)pensyve_recall with query "workflow OR pattern OR process" (limit: 5)pensyve_recall with query "*" (limit: 10) -- broad query to capture recent memories by recencyDeduplicate results across queries (same memory ID should appear only once).
Present a concise briefing with the most important items:
Session Context (from Pensyve memory)
Recent Decisions:
- auth-service: Using RS256 for JWT signing to support key rotation
- api-design: POST endpoints return 201 with created resource
Known Issues:
- database: Migration script requires Python 3.11+
Active Patterns:
- testing: Integration tests need tmpdir cleanup after filesystem operations
Use
/recall <query>to search for specific memories.
Rules for summary mode:
Present a detailed briefing with scores and metadata:
Session Context (from Pensyve memory)
Recent Decisions (3 found):
Entity Decision Confidence When auth-service Using RS256 for JWT signing 0.9 2026-03-15 api-design POST endpoints return 201 0.9 2026-03-14 database SQLite for MVP, migrate to Postgres later 0.9 2026-03-12 Known Issues (2 found):
Entity Issue Confidence Score database Migration requires Python 3.11+ 0.8 0.91 cache Invalidation race condition on concurrent writes 0.8 0.85 Workflow Patterns (1 found):
Entity Pattern Confidence Score testing Integration tests need tmpdir cleanup 0.7 0.78 Recent Activity (5 unique memories, most recent first):
Type Entity Summary Score semantic auth-service RS256 JWT signing 0.92 episodic database Debugged migration failure 0.88 procedural deploy Run tests before deploy 0.75 Total memories loaded: 11 | Use
/recall <query>for targeted search |/inspect <entity>for entity details
Rules for full mode:
.claude/ memory files. All memory operations go through the Pensyve MCP tools exclusively./remember to start building context."pensyve_recall queries fail but others succeed, present the successful results and note the failures briefly.