Bundle a finished John workspace from Codex. Use when the user wants to archive, package, hand off, or preserve a John project, or wants the Claude command equivalent of /john:archive.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add kitchen-engineer42/joharnessburg --skill archive-workspace --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Archive Workspace?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/kitchen-engineer42-archive-workspace)More formats (shields.io, HTML) on the badges page.
---
name: archive-workspace
description: Bundle a finished John workspace from Codex. Use when the user wants to archive, package, hand off, or preserve a John project, or wants the Claude command equivalent of /john:archive.
---
# archive-workspace
This is the Codex equivalent of Claude Code's `/john:archive` command.
## Procedure
1. Parse the user's request:
- optional label: used in the default archive filename
- optional `--output PATH`: write to a specific zip path
- optional `--force`: overwrite an existing archive
2. Resolve the plugin root:
- In a Codex plugin install, this skill lives under `<plugin-root>/skills/archive-workspace/SKILL.md`.
- The script is at `<plugin-root>/scripts/archive_workspace.py`.
- In a source checkout, use `plugins/joharnessburg/scripts/archive_workspace.py`.
3. Run the script from the user's project directory:
```bash
python3 "<plugin-root>/scripts/archive_workspace.py" <label-if-any> <--output PATH> <--force>
```
4. Parse the JSON on stdout and tell the user:
- archive path
- file count
- archive size
The archive includes durable John artifacts such as `PLAN.md`, `CLAUDE.md`,
`AGENTS.md`, `.john/`, `.claude/skills/`, and `.agents/skills/`. It excludes
git metadata, dependency folders, Python bytecode, and other local noise.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
