amhuppert/Save Current Context
claude/ai-resources-plugin/skills/save-current-context/SKILL.md
Save current session context to a handoff file so a future AI agent can continue with no prior context.
$ install --global
skillsauthnpx skillsauth add amhuppert/my-ai-resources Save Current ContextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 3:47 AM144.7s1 file scanned
SKILL.md
- name:
- Save Current Context
- description:
- Save current session context to a handoff file so a future AI agent can continue with no prior context.
- disable-model-invocation:
- true
Save Current Context
Create a markdown file capturing the current conversation's understanding, progress, and learnings so a future AI agent can continue the work with zero prior context.
Context Source
Derive all content from the current conversation history. Do not ask the user for input or a summary — read the conversation directly.
If the user provided additional direction (e.g., "focus on the API design decisions" or "emphasize the open questions"), weight the output toward that area.
Output File
Write the file to context-{YYYY-MM-DD}.md in the current working directory, using today's date, unless the user specifies a different path or filename.
Use the Write tool to create the file.
Process
-
Think through the conversation using a scratchpad before writing:
- What are the most critical pieces of information a future agent would need?
- What has been accomplished vs. what remains?
- What decisions were made, and why?
- What can be condensed without losing essential meaning?
- Has the user given direction about what to focus on?
-
Write the file with the structure below.
-
Tell the user the file path.
Output File Structure
Include these sections:
- Summary — Brief overview of what has been accomplished and the current state
- Key Learnings — Important insights, patterns, or discoveries made
- Background Context — Essential information needed to understand the situation
- Current Progress — What has been completed and what stage things are at
- Open Questions / Challenges — Unresolved issues or areas needing attention
- Next Steps — Clear, actionable guidance on what to do next
Writing Guidelines
- Be concise but don't omit critical information
- Use markdown formatting (headers, bullets, code blocks where appropriate)
- Write as if explaining to someone who knows nothing about this context
- Focus on actionable, concrete details rather than vague statements
- Avoid unnecessary verbosity while ensuring continuity
Related Skills
amhuppert/hotkey-helper
tools
VerifiedTrustedCommunity
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
2SKILL.mdUpdated Jun 2, 2026
amhuppert/knip
development
VerifiedTrustedCommunity
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
1SKILL.mdUpdated May 27, 2026
amhuppert/react-scan
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
1SKILL.mdUpdated May 20, 2026
amhuppert/knowledge-base-ingest
documentation
VerifiedTrustedCommunity
This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".
1SKILL.mdUpdated May 17, 2026