원클릭으로 Manus에서 모든 스킬 실행

context-continuity

스타0

포크0

업데이트2026년 4월 6일 21:28

This skill activates when the user mentions "what was I working on", "continue from last session", "restore context", "what did we decide", "pick up where I left off", "compaction happened", "lost context", "session context", "resume work", "what's the status", "where did we leave off", "prior session", "context lost", or when resuming work after a break. Provides session continuity by accessing bookmark snapshots via MCP tools.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

tyroneross

tyroneross/RossLabs-AI-Toolkit

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Context Continuity Workflow

This skill restores and maintains context across Claude Code sessions and compactions using the Bookmark MCP tools.

When to Activate

User asks about prior session work or decisions
User wants to continue a previous task
After compaction when context was compressed
User reports "losing" context or decisions
Session start when prior context exists

Restoration Flow

1. Check snapshot inventory

Use the bookmark status MCP tool to check if snapshots exist and how fresh they are.

The status tool returns: snapshot count, last capture time, freshness, compaction count, and current threshold.

2. Restore context

Use the bookmark restore MCP tool to load the latest session context. This returns a structured summary optimized for continuation:

Current Status: What was being worked on
Decisions Made: Key choices with rationale
Open Items: What still needs doing
Unknowns: Blockers or questions
Files Changed: What was modified

3. Present and continue

Summarize the restored context to the user. Ask which open item to continue with, or if the user has a new direction.

Browsing History

To list available snapshots and view a specific one:

Use the bookmark list MCP tool to see all snapshots with timestamps and triggers
Use the bookmark show MCP tool with a snapshot_id to view full content of a specific snapshot

Manual Snapshot

If the user wants to explicitly save context before a break:

Use the bookmark snapshot MCP tool with trigger "manual" to capture current session state.

After Restoration

Once context is restored, continue working normally. The automatic hooks handle future snapshots — no manual intervention needed.

MCP Tools Reference

Tool	Purpose
`status`	Snapshot inventory — count, freshness, thresholds
`restore`	Load latest or specific snapshot context for continuation
`list`	Browse all snapshots with metadata
`show`	View full content of a specific snapshot
`snapshot`	Capture a manual snapshot of current session

bookmark — session continuity

이 저장소의 다른 Skills

같은 저장소

marketplace-maintenance

tyroneross/RossLabs-AI-Toolkit

Operational lessons for maintaining a Claude Code plugin marketplace. Load whenever making changes to `.claude-plugin/marketplace.json`, bumping a plugin version that's listed in a marketplace, adding/removing plugins from a marketplace, or troubleshooting "add marketplace" failures. Prevents schema rejection, stale manifests, CDN-lag false negatives, and install-command drift.

2026-05-300

publish-packages

tyroneross/RossLabs-AI-Toolkit

How to publish a public npm package to GitHub Packages for any project under the @tyroneross scope — Claude Code plugins, build-loop subsystems, prompt-builder, etc. Load whenever the user asks to "publish to GitHub Packages", "publish the plugin", "ship as an npm package", "make this installable", "release this to npm", or whenever bumping a package version that needs to ship. Covers single-package repos (build-loop pattern) and monorepo per-plugin publishing (RossLabs-AI-Toolkit pattern). Includes the GitHub Actions workflow template, the release ritual, and the verification checklist that catches the 403 / version-drift / scope-missing failures already seen in this account.

2026-05-300

agent-eval-harness

tyroneross/RossLabs-AI-Toolkit

Use when building an evaluation harness for an LLM agent, RAG pipeline, or prompt — when the question is "is this actually working?" Encodes Anthropic and OpenAI's published 2025–2026 eval guidance — start with 20–50 real-failure tasks (not synthetic happy-paths), use three grader types in the right places (deterministic code / LLM judge / human review), measure pass@k vs pass^k for production reliability, grade outcomes not reasoning paths, calibrate the LLM judge against human review before trusting it, and detect eval saturation. Triggers on "build an eval", "build evals", "eval harness", "is this prompt working", "regression test for LLM", "how do I know my agent is better", "LLM judge", "pass@k", "compare two prompts on real data", "the prompt looks fine but production is broken". Vendor-neutral with starter templates.

2026-05-130

agent-tool-design

tyroneross/RossLabs-AI-Toolkit

Use when designing the surface of a tool that an LLM agent will call — function declarations, MCP server methods, OpenAI function-calling schemas, Anthropic tool_use definitions, or Agent SDK tools. Encodes Anthropic and OpenAI's published 2025–2026 guidance — namespaced names (service_resource_verb), semantically specific parameters (user_id over user), signal-dense return formats with a response_format knob, prompt-engineered error strings that guide the model toward the fix, and the anti-pattern of wrapping every API endpoint 1:1. Triggers on "design a tool for an agent", "write a function declaration", "MCP server tool", "function calling schema", "tool_use definition", "Agents SDK tool", "the agent keeps calling my tool wrong", "the agent loops on a tool error", "list-all is blowing up context", "tool descriptions". Cross-vendor; vendor wire-format notes in references/.

2026-05-130

long-running-agent-harness

tyroneross/RossLabs-AI-Toolkit

Use when building or operating a coding agent that has to work across multiple context windows or multiple sessions — when one shot won't fit. Encodes Anthropic's published 2025 harness pattern — initializer/coding split, claude-progress.txt + feature-list JSON + git commits as cross-context state, mandatory session-init protocol (read logs → review features → run e2e → start dev server), edit-status-only contract on the feature file. Triggers on "long-running agent", "multi-session agent", "context window keeps filling up", "agent forgets between sessions", "session handoff", "Codex to Claude Code handoff", "Claude Code to Codex handoff", "harness for an agent", "what does the agent read on session start". Bridges bookmark (session snapshots) and build-loop (single-session orchestration).

2026-05-130

prompt-cache-shaping

tyroneross/RossLabs-AI-Toolkit

Use when designing a prompt or agent that will run at scale and you want to maximize prompt-cache hit rate. Encodes the cross-vendor invariant — order content static-to-dynamic so the cacheable prefix is stable — plus Anthropic's explicit cache_control breakpoint mechanics (4-breakpoint budget, 20-block lookback, 5m vs 1h TTL) and OpenAI's automatic prefix hashing (≥1024 token threshold, 128-token increments, 5–10min idle TTL, up to 24h on gpt-5.5+). Triggers on "prompt caching", "cache hit rate", "reduce LLM cost", "ephemeral cache", "cache_control", "prompt is slow on every call", "we're paying for the same tokens twice", "TTL", "cache breakpoint". Vendor-neutral spine plus per-vendor branches in references/.

2026-05-130

name	context-continuity
description	This skill activates when the user mentions "what was I working on", "continue from last session", "restore context", "what did we decide", "pick up where I left off", "compaction happened", "lost context", "session context", "resume work", "what's the status", "where did we leave off", "prior session", "context lost", or when resuming work after a break. Provides session continuity by accessing bookmark snapshots via MCP tools.
version	0.2.0
user-invocable	false
canonical	true
source-plugin	bookmark
source-repo	https://github.com/tyroneross/bookmark

Context Continuity Workflow

This skill restores and maintains context across Claude Code sessions and compactions using the Bookmark MCP tools.

When to Activate

User asks about prior session work or decisions
User wants to continue a previous task
After compaction when context was compressed
User reports "losing" context or decisions
Session start when prior context exists

Restoration Flow

1. Check snapshot inventory

Use the bookmark status MCP tool to check if snapshots exist and how fresh they are.

The status tool returns: snapshot count, last capture time, freshness, compaction count, and current threshold.

2. Restore context

Use the bookmark restore MCP tool to load the latest session context. This returns a structured summary optimized for continuation:

Current Status: What was being worked on
Decisions Made: Key choices with rationale
Open Items: What still needs doing
Unknowns: Blockers or questions
Files Changed: What was modified

3. Present and continue

Summarize the restored context to the user. Ask which open item to continue with, or if the user has a new direction.

Browsing History

To list available snapshots and view a specific one:

Use the bookmark list MCP tool to see all snapshots with timestamps and triggers
Use the bookmark show MCP tool with a snapshot_id to view full content of a specific snapshot

Manual Snapshot

If the user wants to explicitly save context before a break:

Use the bookmark snapshot MCP tool with trigger "manual" to capture current session state.

After Restoration

Once context is restored, continue working normally. The automatic hooks handle future snapshots — no manual intervention needed.

MCP Tools Reference

Tool	Purpose
`status`	Snapshot inventory — count, freshness, thresholds
`restore`	Load latest or specific snapshot context for continuation
`list`	Browse all snapshots with metadata
`show`	View full content of a specific snapshot
`snapshot`	Capture a manual snapshot of current session

bookmark — session continuity