Mirket documentation
Mirket is a collection of reusable skills for Codex and Claude Code. Each skill gives an agent a way to approach a particular kind of work, from understanding a project to checking a change and handing it off.
Purpose
Use Mirket when you want the agent to follow a repeatable workflow: diagnose a bug before fixing it, plan a substantial change, design an interface, or review a result. You can ask for an outcome in plain language or name a skill directly: “Use Mirket Debug to reproduce this failure and find its cause.”
Installation and first prompts are in the project README. The plugin can be used one request at a time. The Codex and Claude Code instructions are optional if you want Mirket to guide work by default.
Philosophy
- Choose guidance for the job. Pick one primary skill for the requested result. Add another when it supplies a distinct result or check. A small task can stay small.
- Keep consequential choices with the human. A request to do work and approval of a written plan are separate. Ask for decisions that affect the outcome; proceed with routine choices within the agreed scope.
- Verify claims with evidence. Inspect the actual change, run checks that match the risk, and say what could not be verified. A review or hook reminder does not prove that the work was checked.
- Leave enough context to resume. Keep substantial plans, decisions, and handoffs in the project's workspace records. Keep the response focused on what happened and what comes next.
Skills
A skill is a Markdown workflow with a trigger, guidance, and sometimes more detailed references. The host can choose a skill from its description; you can also request one by name. See the routing guide when several skills sound relevant.
| What you need | Skills |
|---|---|
| Understand the project and its environment | Adapt, Preflight, Equip |
| Decide what to do and how to approach it | Focus, Curate, Architect, Plan |
| Make or improve something | Design, Imagine, Author, Debug, Refactor |
| Check the result and tidy up | Test, Audit, Critique, Clean |
| Coordinate and communicate | Orchestrate, Distill, Brief, Sleep |
Architecture
The plugin package is shared by both hosts. Separate Codex and Claude Code marketplace manifests point to it.
- Skills and references. Each packaged skill has a
SKILL.mdwith its trigger and workflow, plusagents/openai.yamlfor its Codex display metadata. Skill-specific and shared references cover details such as routing, workspace records, and review loops. - Plugin descriptor and hooks.
plugin.jsondescribes the package. On supported host events, lifecycle hooks request communication and cleanup reviews and guard certain commit paths. Hooks depend on host support and trust settings; they cannot guarantee compliance. - Optional memory. Local Hindsight is separate from the plugin's skills. It can preserve project context across sessions and is not required to use Mirket.
- Documentation. The website reads this guide and the packaged skill Markdown at build time. The documentation and the plugin workflows stay in the same repository.
Optional local Hindsight
Mirket works on its own. To carry project context across sessions, you can opt into Hindsight's local daemon in either host. Codex uses Mirket's guarded installer and project registry. Claude Code uses the upstream Coding Agents integration.
Before opting in, choose a model provider and decide which projects you want to capture. The daemon can store memory locally while a hosted model provider still processes captured context remotely. Review the guide's capture defaults before enabling the integration.
Codex setup prompt
Paste this into Codex to install Mirket and decide separately whether to set up Hindsight.
Install Mirket for Codex, then ask me: “Set up optional local Hindsight for Codex, or keep Mirket only?” Wait for an explicit yes before changing Hindsight. If I decline or don't answer, leave it unchanged.
For Mirket, add https://github.com/nazmirket/skills.git as a Codex plugin marketplace, install mirket@mirket, and verify the install.
If I opt in, follow https://github.com/nazmirket/skills/blob/main/memory/README.md. Confirm my model provider and capture preferences. Check for an existing setup and use the read-only preflight before a fresh install. Preserve existing memory and configuration.
In either case, tell me how to start a fresh Codex session and verify what was installed.
Claude Code setup prompt
Paste this into Claude Code. Hindsight is a separate, optional installation.
Install Mirket for Claude Code, then ask me: “Set up optional local Hindsight for Claude Code, or keep Mirket only?” Wait for an explicit yes before changing Hindsight. If I decline or don't answer, leave it unchanged.
For Mirket, add nazmirket/skills as a Claude Code plugin marketplace, install mirket@mirket, and verify the install.
If I opt in, follow the Claude Code setup at https://github.com/nazmirket/skills/blob/main/memory/README.md#claude-code-with-the-upstream-installer. Confirm my model provider and which projects to capture. Check for an existing daemon and shared runtime. If Mirket manages Hindsight for Codex, use the guide's existing-install path and verify the Codex adapters still work. Preserve existing banks and settings.
In either case, tell me how to start a fresh Claude Code session and verify what was installed.
Manual Hindsight setup
- Codex: Follow the local daemon guide and run
python3 memory/install.py --checkfrom a checkout before a fresh install. If you opt in and the check passes, runpython3 memory/install.py; for an existing install, follow the guide's wiring instructions. - Claude Code: Follow the upstream installer steps to use a local daemon and check for a shared Hindsight runtime before installing.
- Verify in the host you use: Restart it, review the hooks, check the resolved bank, and test recall with a harmless fact in a fresh session.