Manages open-ended project explorations, known as quests, through file-based memory updates.
Install
mkdir -p .claude/skills/quest && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17492" && unzip -o skill.zip -d .claude/skills/quest && rm skill.zipInstalls to .claude/skills/quest
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Manage Egregore quests from Codex when the user invokes /quest or $quest, or asks to manage quests, using memory-first files and optional connected-mode graph updates.Key capabilities
- →List active and paused quests
- →Show quest details from markdown files
- →Create new quests with frontmatter
- →Append contribution entries to quests
- →Set quest priority or status (pause, complete)
How it works
The skill syncs with agent.sh, detects the mode, and dispatches actions based on user requests to manage quest files, updating frontmatter and an index file, then committing changes.
Inputs & outputs
When to use quest
- →Manage exploration
- →Prioritize work
- →Complete quest
About this skill
Egregore quest Adapter
This adapter runs the canonical Egregore workflow for quest. Its one
maintained body is .claude/skills/quest/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/quest/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
textfenced 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
textfenced 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.
- Read
.claude/skills/quest/SKILL.mdfor the workflow details. - Run the referenced
bin/scripts directly from Codex. - Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
- 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. - Keep local-mode behavior filesystem-first and avoid graph or notification
calls when
egregore.jsondeclares"mode": "local". - Never call the deprecated
egregore-handoffCLI for Egregore project handoffs.
When not to use it
- →When the user wants graph failure to block a filesystem quest update
Limitations
- →Do not use graph or notification calls in local mode
- →Do not let graph failure block a filesystem quest update
How it compares
This skill manages quests as memory-first markdown files with structured frontmatter, providing a durable and shared exploration record, unlike informal task tracking.
Compared to similar skills
quest side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| quest (this skill) | 0 | 4mo | Review | Beginner |
| cto-engineering-metrics | 5 | 1y | No flags | Advanced |
| source-management | 4 | 7mo | No flags | Beginner |
| office-hours | 0 | 7mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by egregore-labs
View all by egregore-labs →You might also like
cto-engineering-metrics
rinaldofesta
Expert methodology for defining, tracking, and interpreting engineering performance metrics including DORA, team health, productivity, and executive reporting.
source-management
anthropics
Manages connected MCP sources for enterprise search. Detects available sources, guides users to connect new ones, handles source priority ordering, and manages rate limiting awareness.
office-hours
alexandervashurin
|
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
task-analyzer
shinpr
Metacognitive task analysis and skill selection. Analyzes task essence, estimates scale, and returns appropriate skills with metadata.
micro-saas-launcher
davila7
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.