Manage shared open-ended quests through one canonical Markdown lifecycle.

MITAuto-check passed

Install Quest

skills CLI
$ npx skills add egregore-labs/egregore --skill quest -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install egregore-labs/egregore quest --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/egregore-labs/egregore.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/quest .claude/skills/quest && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quest
GitHub stars
291
Token cost
~649 tokens
SKILL.md length
331 words
Files
1
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

Manage shared open-ended quests through one canonical Markdown lifecycle.

  • Works in 6 steps: Read .claude/skills/quest/SKILL.md for… → Run the referenced bin/ scripts directly… → Treat graph and publish steps as… → …
  • Starting an exploration
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Completing a quest

What it does

Quest is an agent skill from egregore-labs/egregore. Manage shared open-ended quests through one canonical Markdown lifecycle. Use for /quest, listing or opening quests, starting an exploration, contributing, prioritizing, pausing, or completing a quest.

Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Shared intelligence layer for organizations. The licence is MIT.

When your agent uses it

  • Starting an exploration
  • Completing a quest

Example prompts

  • “/quest”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read .claude/skills/quest/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
  4. For every external notification, follow
  5. Keep local-mode behavior filesystem-first and avoid graph or notification
  6. Never call the deprecated egregore-handoff CLI for Egregore project

What it can do on your machine

Read from SKILL.md and the folder at commit 05b8672. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quest loads about 649 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 331 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~649

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from egregore-labs/egregore at commit 05b8672, republished under its MIT licence (© egregore-labs). 331 words, ~649 tokens.

Download SKILL.mdSave it as .claude/skills/quest/SKILL.md (or your agent's skills folder).
name
quest
description
Manage shared open-ended quests through one canonical Markdown lifecycle. Use for /quest, listing or opening quests, starting an exploration, contributing, prioritizing, pausing, or completing a quest.
<!-- generated-by: bin/codex-sync-skills.sh -->

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 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/quest/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.

© egregore-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/quest of egregore-labs/egregore.

Open the folder on GitHubat commit 05b8672

Compare with similar skills

Quest next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quest compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quest this skillegregore-labs/egregore291—~649Automated safety check: PassMIT
Implementing End To End Encryption For Messagingmukul975/Anthropic-Cybersecurity-Skills34k—~843Automated safety check: PassApache-2.0
Dead End Pagesthedaviddias/Front-End-Checklist74k—~683Automated safety check: PassMIT
Perform Task End To Endrazorpay/blade656—~667Automated safety check: PassMIT
Ma End To Endhtlin222/meta-pipe139—~2.3kAutomated safety check: PassCustom licence
Antigravity SDK End-to-End Testingomnigent-ai/omnigent11k—~2.7kAutomated safety check: PassApache-2.0

Similar skills

  • Implementing End To End Encryption For Messaging

    mukul975/Anthropic-Cybersecurity-Skills

    Implements a simplified Signal Protocol-style end-to-end encryption scheme for messaging, covering key exchange, forward secrecy, and the core cryptographic components so no server or intermediary…

    34k GitHub stars~843 tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Dead End Pages

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing a site's internal link graph for dead-end pages, suggesting related-content links to add to thin or standalone pages, or reviewing CMS templates that produce…

    74k GitHub stars~683 tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed
  • Perform a task end-to-end when intent is set to 'perform-task-end-to-end' by checking existence of GITHUBRZPSWEAGENTAPPAPPID environment variable in the session.

    656 GitHub stars~667 tokensUpdated today
    Testing & QAAuto-check passed
  • Ma End To End

    htlin222/meta-pipe

    End-to-end AI-assisted meta-analysis pipeline orchestration from TOPIC.txt to final manuscript and reviewer responses.

    139 GitHub stars~2.3k tokensUpdated 17 days ago
    Research & ScienceAuto-check passed
  • Spins up a local Omnigent server and exercises the Antigravity (Gemini) SDK harness end to end: building agents, running real turns, smoke tests and bug-bashing.

    11k GitHub stars~2.7k tokensUpdated today
    Testing & QAAuto-check passed

More from egregore-labs/egregore

All 43 skills in this repo
  • Ingest User Interview

    egregore-labs/egregore

    Analyze a user interview from Granola, pasted text, or a file into an evidence-backed briefing, journey insights, product findings, patterns, and actions.

    291 GitHub stars~689 tokensUpdated 8 days ago
    Auto-check passed
  • Meeting

    egregore-labs/egregore

    Analyze a Granola meeting into an evidence-backed briefing, decisions, findings, patterns, actions, and continuity.

    291 GitHub stars~652 tokensUpdated 8 days ago
    Auto-check passed
  • View

    egregore-labs/egregore

    Generate a branded HTML artifact from Egregore data (quest, handoff, activity, board, network, or any document) and open it in the browser.

    291 GitHub stars~646 tokensUpdated 8 days ago
    Auto-check passed
  • Activity

    egregore-labs/egregore

    Explicit Activity card only. An agent skill from egregore-labs/egregore.

    291 GitHub stars~677 tokensUpdated 8 days ago
    Auto-check passed
  • Checkup

    egregore-labs/egregore

    Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible.

    291 GitHub stars~656 tokensUpdated 8 days ago
    Auto-check passed
  • Dashboard

    egregore-labs/egregore

    Explicit personal-status surface for /dashboard or a direct request for the whole personal overview.

    291 GitHub stars~666 tokensUpdated 8 days ago
    Auto-check passed

Questions about Quest

What does Quest do?

Manage shared open-ended quests through one canonical Markdown lifecycle. Quest is an agent skill from egregore-labs/egregore. Manage shared open-ended quests through one canonical Markdown lifecycle.

When should I use Quest?

Quest fits situations like: starting an exploration; completing a quest.

How do I install Quest in Claude Code?

Run `npx skills add egregore-labs/egregore --skill quest -a claude-code`. Or copy the skill folder (.codex/skills/quest in egregore-labs/egregore) into .claude/skills/quest in your project. Claude Code loads it when a task matches its description.

How do I install Quest in Codex?

Run `npx skills add egregore-labs/egregore --skill quest -a codex`. Or copy the skill folder (.codex/skills/quest in egregore-labs/egregore) into .agents/skills/quest in your project. Codex loads it when a task matches its description.

Can I use Quest in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add egregore-labs/egregore --skill quest -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quest, .gemini/skills/quest, .github/skills/quest and .opencode/skills/quest in your project.

What does Quest need to run?

SKILL.md names no scripts, command-line tools or credentials: Quest is instructions for the agent only.

Does Quest access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quest safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quest use?

Quest is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quest use?

About 649 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Quest?

Skills that share tags, products or a category with Quest: Implementing End To End Encryption For Messaging (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Dead End Pages (thedaviddias/Front-End-Checklist, 74k stars), Perform Task End To End (razorpay/blade, 656 stars) and Ma End To End (htlin222/meta-pipe, 139 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quest?

egregore-labs (a GitHub organization) maintains it in egregore-labs/egregore, which has 291 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 1, 2026.

Source: egregore-labs/egregore on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.