Menu
Session start context priming — loads relevant memories from Pensyve to provide continuity across sessions
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user types @pensyve, asks for an @-mention workflow, wants mention-style Pensyve memory access in Codex, or asks whether Pensyve supports Codex mentions.
Use when the user explicitly invokes Pensyve, asks what the agent remembers, wants Codex to recall or store project memory, requests memory health review, or wants memory grounded work.
Pre-refactor context loading -- queries Pensyve memory for past decisions, failures, and patterns related to a refactoring target, then compiles a briefing. Use when starting a refactor to avoid repeating past mistakes.
End-of-session memory capture -- analyzes session for decisions, outcomes, and patterns worth remembering, then stores confirmed items via Pensyve. Use when ending a work session or when the user wants to capture what was learned.
Session start context priming -- loads relevant memories from Pensyve at the beginning of a session to provide continuity across sessions. Use when switching projects or needing historical context.
Long-running multi-session work (research, eval loops, iterative benchmarks) with continuity -- resume prior lessons, capture per-run outcomes, build up stable truths over time. Use for eval/research/benchmark work that spans sessions.
| name | context-loader |
| description | Session start context priming — loads relevant memories from Pensyve to provide continuity across sessions |
Load relevant memories from Pensyve at the start of a session to provide cross-session continuity. Supports summary and full loading modes.
When this skill is invoked (typically at session start via the SessionStart hook), follow these steps:
Check for a mode argument if provided:
pensyve_recall to search memories on demand."If no mode is specified, 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
pensyve_recallto 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
pensyve_recallfor targeted search |pensyve_inspectfor entity details
Rules for full mode:
pensyve_remember to start building context."pensyve_recall queries fail but others succeed, present the successful results and note the failures briefly.PENSYVE_API_KEY environment variable and MCP configuration."