Skip to content
Skills Library
Management & product · Planning

quest

/quest

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.

Repository
egregore ↗
Licence
MIT
Last repository change
16.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

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.

Original author 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.

How it works

  1. Structured UX parity
Original SKILL.md headings · 46 lines, 345 words
SKILL.md preview
---
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.

Versions

RepositoryScoreLicence
This page · egregore-labs/egregore100MIT
egregore-labs/egregore100MIT
justinjdev/fellowship100Apache-2.0

Database snapshot: 13.11.2026 · package version ade71aff69f5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ro-questdesign
    Design quests, quest chains, dailies and events for an RO server as a spec - premise, steps, pacing, rewards, failure states, client needs - ready for implementation. Use when the user says "design a quest", "quest chain idea", "daily quests", "event design", "what makes a good…
  • 100quest-setup
    Create, edit, list, activate, pause, delete or debug Xsolla Quest Platform quests: conditions, rewards (Web3 included) and quest events. Also the Quests block on a Shop Builder site: add, move, hide or show it, and change its heading, card count, or card titles, text, images and…
  • 95design-quest-mission-design
    Use when designing quests, missions, objectives, quest trees, or reward structures. Requires quest-narrative-coherence check before any quest creation. Triggers: quest, mission, objectives, quest tree, rewards.
  • 95rind-quest-run
    Use when working rind's planned `quest/` backlog with `quest skill spawn` or `quest skill run`.
  • 100quest-list
    仅在用户消息被明确认为产生了新需求时使用。用 quest_read / quest_write 两个工具维护任务清单:记录需求、拆分为可执行子任务,并管理 open、running、awaiting、done 四种状态。
  • 90narrative-and-quest-design
    Use when designing quests, reactivity, and factions — quest structure beyond fetch-and-return, branching that honors player choice, reactivity systems on a budget (the "facts database"), procedural/radiant quests as a supplement to hand-authored ones, and faction allegiance…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.