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
Native Codex Egregore skill. Quests are shared, open-ended explorations stored
under memory/quests/.
Flow
- Run
bin/agent.sh sync. - Detect mode from
egregore.jsonmode, defaulting toconnected. - Dispatch from the user request:
- no argument: list active and paused quests from
memory/quests/*.md. - name or slug: show quest details from the markdown file.
new: create a quest.contribute: append a contribution entry.prioritize: setpriorityto0,1,2, or3.pause: setstatus: paused.complete: setstatus: completedand record an outcome.
- no argument: list active and paused quests from
- Filesystem writes are canonical. Quest files use frontmatter:
---
title: Example Quest
slug: example-quest
status: active
projects: []
started: YYYY-MM-DD
started_by: handle
priority: 0
completed:
---
- Update
memory/quests/index.mdafter create, status changes, and priority changes. - Commit and push memory immediately:
git -C memory add quests
git -C memory commit -m "quest: $SLUG $ACTION" --quiet
git -C memory push origin main --quiet
- In connected mode only, mirror changes best-effort with
bin/graph.shand notify named people withbin/notify.sh send. If graph or notification fails, report that the quest was saved to memory and continue.
Interaction
Use structured Codex question tooling when available for new quest fields and
status confirmations. Otherwise ask one short numbered question at a time with
an Other: option.
Output
Structured UX parity is required:
/questlist mode renders the active quest table:| Quest | Project | Artifacts | Contributors |, followed by paused quest state and entry-point hints./quest <name>detail mode renders the same sectioned view as Egregore: title rule, status, projects, started metadata, question, threads, artifacts, todos when available, contributors, and entry points.- Create/update routes use compact structured confirmations with the quest file path and memory push state. Do not substitute a loose prose summary.
- In local mode, omit graph/notification wording while preserving the same list/detail layout.
Rules
- Do not use graph or notification calls in local mode.
- Do not let graph failure block a filesystem quest update.
- Do not use Claude Code commands.
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 | 1mo | Review | Beginner |
| cto-engineering-metrics | 5 | 9mo | No flags | Advanced |
| source-management | 4 | 4mo | No flags | Beginner |
| office-hours | 0 | 4mo | 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.