Skip to content

egregore-labs/egregore / .codex/skills/archive

archive

Unverified

Capture an effective prompting or steering technique as a reusable canonical pattern. Use when a prompt chain worked especially well; use /reflect for insight about the work and /note for a private thought.

Egregore archive Adapter

This adapter runs the canonical Egregore workflow for archive. Its one maintained body is .claude/skills/archive/SKILL.md; read that file completely and follow it here.

Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an Other: option and wait for the user.

Structured UX parity

This workflow has a Claude skill with user-visible structured output. After reading .claude/skills/archive/SKILL.md, reproduce the same visible UX in Codex:

  • Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering, exact confirmation blocks, and "no preamble" rules from the source skill.
  • Use the source skill's frame width, section order, labels, status footer, and examples as the contract for the final response.
  • Never replace a required box/table/card/artifact view with a prose summary unless the user explicitly asks for a summary.
  • When the source says to output a TUI box directly, paste that box as the visible response, preferably in a text fenced block.
  • If the canonical body says the command's stdout is the card and must not be repeated, that rule assumes a host that displays command output in full; in Codex, paste the card once as the visible response in a text fenced block and do not print it a second time.
  • Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output.
  1. Read .claude/skills/archive/SKILL.md for the workflow details.
  2. Run the referenced bin/ scripts directly from Codex.
  3. Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
  4. For every external notification, follow .claude/context/notification-consent.md: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval.
  5. Keep local-mode behavior filesystem-first and avoid graph or notification calls when egregore.json declares "mode": "local".
  6. Never call the deprecated egregore-handoff CLI for Egregore project handoffs.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall