ComputerConnection/resume
skills/resume/SKILL.md
Pick up exactly where we left off on a project. Reconstructs context from handoffs, git history, and project state. Use when starting a session on existing work.
tools
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add ComputerConnection/zach-pack resumeInstall 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 22, 2026, 11:07 PM14.8s1 file scanned
SKILL.md
- name:
- resume
- description:
- Pick up exactly where we left off on a project. Reconstructs context from handoffs, git history, and project state. Use when starting a session on existing work.
- context:
- fork
- agent:
- Explore
- allowed-tools:
- Read, Grep, Glob, Bash(git *), Bash(ls *), Bash(find *)
- argument-hint:
- [project-name-or-path]
Project Resume: $ARGUMENTS
Reconstruct full context so we can continue without re-explaining anything.
Phase 1: Locate Project State
Search for context in this order:
1. NEXUS Project Structure
~/nexus/projects/*/CURRENT_STATE.yaml
~/nexus/projects/*/ORIGINAL_BRIEF.md
~/nexus/projects/*/handoff_log/
~/nexus/projects/*/decisions/DECISION_LOG.md
2. Project Root Files
$ARGUMENTS/CURRENT_STATE.yaml
$ARGUMENTS/.claude/state.yaml
$ARGUMENTS/HANDOFF.md
$ARGUMENTS/TODO.md
$ARGUMENTS/README.md
3. Git History
- Recent commits (last 10)
- Branches and current branch
- Uncommitted changes
- Recent file modifications
4. Common Zach Patterns
~/AGENT_CONTEXT.md
~/PROACTIVE_PLAN.md
~/.claude/projects/
Phase 2: Reconstruct Context
Build a complete picture:
Original Intent
- What was the goal?
- Who requested it?
- What problem does it solve?
Current State
- What's been built?
- What's working?
- What files exist?
Decisions Made
- Key architectural choices
- Why things are the way they are
- What was explicitly rejected
Scope Boundaries
- What's in scope?
- What's explicitly out?
Blockers & Questions
- What's stuck?
- What needs Zach's input?
Next Steps
- What's the immediate next action?
- What's the suggested approach?
Phase 3: Generate Resume Brief
Output a structured brief:
# Resume: [Project Name]
**Last Active**: [date/time from git or handoff]
**Status**: [complete | in-progress | blocked]
**Branch**: [git branch]
## Original Intent
[What we're building and why]
## Where We Left Off
[Specific point of progress - be concrete]
## Key Decisions (Don't Redo These)
| Decision | Rationale |
|----------|-----------|
| ... | ... |
## Current Blockers
- [ ] [blocker and what's needed to unblock]
## Immediate Next Steps
1. [First thing to do]
2. [Second thing]
3. [Third thing]
## Files to Know About
- `path/to/key/file.ts` - [what it does]
- `path/to/another.ts` - [what it does]
## Out of Scope (Don't Drift Into)
- [thing to avoid]
- [another thing]
## Open Questions for Zach
- [question needing human input]
Phase 4: Verify Understanding
Before continuing work, confirm:
- Restate the goal in one sentence
- Confirm scope - what's in, what's out
- Identify the single next action
- Flag any confusion - ask before assuming
If No Context Found
If we can't find project state:
- Check if project exists at all
- List what we DID find (any relevant files)
- Ask Zach to provide context:
- "What were we building?"
- "Where did we leave off?"
- "What's the next step?"
Then create a fresh CURRENT_STATE.yaml to prevent this next time.
Output Format
- Show the Resume Brief (markdown)
- Show confidence level: High / Medium / Low (based on how much context was found)
- If Low confidence, list what's missing
- End with: "Ready to continue. What's first?"
Related Skills
ComputerConnection/zach
data-ai
VerifiedTrustedCommunity
Inject Zach's full identity, business context, and working preferences. Use at session start to eliminate cold starts. Lightweight context load — not a full agent like Vision, just who Zach is and how to work with him.
SKILL.mdUpdated Apr 22, 2026
ComputerConnection/skills/vision
tools
VerifiedTrustedCommunity
--- name: vision description: "Zach's personal AI — his Jarvis. NOT a store agent. This is the owner's private command center that sits above everything else. Handles anything Zach needs — business, personal, technical, strategic, creative. High-systems AI: precise, anticipatory, authoritative. Invoke for ANY task." context: fork allowed-tools: Read, Grep, Glob, Bash, Edit, Write, Task, TodoWrite argument-hint: [what-do-you-need] — freeform. Vision figures out the rest. --- # VISION — Zach's Ja
SKILL.mdUpdated Apr 22, 2026
ComputerConnection/tauri
development
VerifiedTrustedCommunity
Tauri-specific development patterns for NEXUS. Use when building desktop app features, handling IPC, or working with Rust backend.
SKILL.mdUpdated Apr 22, 2026
ComputerConnection/store-sop
development
VerifiedTrustedCommunity
Document Computer Connection store processes in AI-queryable format. Use to capture SOPs for the store AI server POC.
SKILL.mdUpdated Apr 22, 2026