technicalpickles/snapshot
plugins/agent-meta/skills/snapshot/SKILL.md
Capture current session state without stopping
$ install --global
skillsauthnpx skillsauth add technicalpickles/pickled-claude-plugins snapshotInstall 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: Apr 18, 2026, 3:56 AM33.3s1 file scanned
SKILL.md
- name:
- snapshot
- description:
- Capture current session state without stopping
Snapshot
Capture current session state for review without parking.
Use Cases
- Session is getting long, want a checkpoint summary
- Want to share progress with someone
- Need to orient yourself on where you are
Output Format
━━━ Session Snapshot ━━━
Focus: [Current focus/goal]
Progress:
✓ [Completed item]
✓ [Completed item]
○ [In progress item]
○ [Pending item]
Key decisions:
- [Decision 1]
- [Decision 2]
Files touched:
- path/to/file.ts (new)
- path/to/other.ts (modified)
Current thread: [What we're actively discussing/working on]
Flags
--save
Write the snapshot to the parking location as a checkpoint file.
Filename: snapshot-[timestamp].md
Format when saved:
# Snapshot: [Focus]
**Captured:** [Date/time]
**Branch:** [branch-name]
## Progress
- [x] [Completed item]
- [x] [Completed item]
- [ ] [In progress item]
- [ ] [Pending item]
## Key Decisions
- [Decision 1]
- [Decision 2]
## Files Touched
- path/to/file.ts (new)
- path/to/other.ts (modified)
## Current Thread
[What we're actively discussing/working on]
Report: "Snapshot saved to [path]"
Difference from park
| Aspect | snapshot | park | |--------|----------|------| | Intent | Review progress | Stop work for later | | Output | Inline (default) | Always file | | Resume prompt | No | Yes | | Next steps | Current state | Future direction |
Related Skills
technicalpickles/plugins/writing-tools/skills/writing-for-scannability
tools
VerifiedTrustedCommunity
--- name: writing-for-scannability description: Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose hides the structure. Also use when explicitly asked to make something scannable or skimmable, convert prose to a list, surface a buried list, fix a wall of text, or decide whether bullets or prose fit. Strong signal: text with parallel sentence shapes, contrast markers ("that
10SKILL.mdUpdated Jun 2, 2026
technicalpickles/actually-lsp-ignore
development
VerifiedTrustedCommunity
Ignore actually-lsp nudges for an ecosystem in this project. Use when the user wants to silence, dismiss, or ignore the LSP setup nudges for a specific ecosystem (Rust, TypeScript, Ruby), or invokes `/actually-lsp-ignore` directly. Writes `dismissed=true` to `.claude/actually-lsp.json`. Persistent across sessions for this project only.
10SKILL.mdUpdated May 28, 2026
technicalpickles/actually-lsp-doctor
tools
VerifiedTrustedCommunity
Diagnose and fix LSP setup for the current project's detected ecosystems (Rust, TypeScript, Ruby). Use when the SessionStart hook nudged about a missing LSP plugin, when the env isn't ready (no `bundle install`, no `cargo build`, missing server binary), when LSP calls are failing, or when the user invokes `/actually-lsp-doctor` directly. Walks the per-ecosystem state machine, reports what's missing, then runs the fix.
10SKILL.mdUpdated May 28, 2026
technicalpickles/plugins/github-actions/skills/investigating-runs
tools
VerifiedTrustedCommunity
--- name: investigating-runs description: Use whenever the user mentions a GitHub Actions / GHA run, even casually — invoke this skill before reaching for raw `gh` commands, because the bundled `gha-snapshot` helper distills `gh run view --log-failed` (a firehose) into a readable block with per-job status, failed-step log tails, and annotations. Specific triggers (any one is enough): a `github.com/.../actions/runs/...` URL; the phrase "GitHub Actions" or "GHA"; the `gh run` CLI; a failing workfl
10SKILL.mdUpdated May 21, 2026