quest
Skill293 starsChanged 10 days agoMITView on GitHub
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.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- opum-ai/proof-skillstheir own version, first seen Nov 8, 2026
- bmaltais/skillstheir own version, first seen Nov 1, 2026
- karloows/orchrafttheir own version, first seen Sep 22, 2026
- Wondermonger-daydreaming/claude-skills-librarytheir own version, first seen May 30, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- opum-ai/proof-skills★ 27same name
- Wondermonger-daydreaming/claude-skills-library★ 7same name
- bmaltais/skills★ 2same name
- karloows/orchraft★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Run one list call and use that snapshot for display and name resolution.
- Distinctive: line 54
Do not run a graph query to enrich the view.
- Distinctive: line 92
Only an active quest accepts contributions, pause, or completion.
- Distinctive: line 109
Never edit quest files or their index directly.
- Distinctive: line 110
Never call Git, QMD, Neo4j, Supabase, or notification APIs from this skill.
- Distinctive: line 113
Do not include titles, questions, contributions, outcomes, or paths in telemetry.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Quest
Manage collaborative explorations without making a graph or harness prompt an authority.
When to invoke
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.
Runtime contract
memory/quests/<slug>.mdis canonical in Local and Connected modes.- Resolve identity and permissions through
ActorContextbefore reading or changing quest state. bin/quest.shis the only lifecycle adapter. It authorizes, validates, writes canonical Markdown, records Git provenance, refreshes retrieval, schedules changed-hash embedding, emits content-free telemetry, and may update an optional graph projection downstream.- A projection failure never rolls back or overrides canonical Markdown/Git.
memory/quests/index.md, dashboards, and graph records are rebuildable views, not state the ritual edits.
Arguments: $ARGUMENTS.
Routes
| Input | Runtime action |
| empty | bash bin/quest.sh list |
all | bash bin/quest.sh list --all |
<name> | resolve one listed slug, then bash bin/quest.sh show <slug> |
new | collect the minimum fields, then one new call |
contribute <name> | resolve the slug and record one contribution |
prioritize <name> <level> | set none, low, medium, or high |
pause <name> | explicitly pause one active quest |
complete <name> | require an outcome, then complete one active quest |
Suppress raw JSON. Render only the fields returned by the adapter.
List and show
Run one list call and use that snapshot for display and name resolution. Show
active quests first, ordered by priority and recency; show paused separately.
Include title, slug, projects, priority, starter, and canonical path. For a
detail request, call show once after resolution and render its question,
threads, contributions, artifacts, entry points, and outcome from the returned
canonical body.
Do not run a graph query to enrich the view. Linked todos and relationships may appear only when a future Runtime read model returns them with freshness and provenance.
Create
Collect:
- title
- the open question or goal
- optional slug, projects, and initial threads
Then make one call:
bash bin/quest.sh new \
--title "<title>" \
--question "<question>" \
[--slug "<slug>"] \
[--project "<project>"]... \
[--thread "<thread>"]...Confirm the stable quest id, canonical path, and writeback status. Do not run a second Git, index, graph, save, or publish action.
Update
Resolve a user-supplied name against one list snapshot. If ambiguous, show the bounded choices. Then mutate by stable slug:
bash bin/quest.sh contribute "<slug>" "<contribution>"
bash bin/quest.sh prioritize "<slug>" "<none|low|medium|high>"
bash bin/quest.sh pause "<slug>"
bash bin/quest.sh complete "<slug>" --outcome "<outcome>"Only an active quest accepts contributions, pause, or completion. Completion requires an explicit outcome. Never infer completion from inactivity, age, closed todos, or graph state.
Failure behavior
- Authorization denial: return no quest content and perform no write.
- Writeback partial: canonical Markdown/Git wins; surface projection, retrieval, or telemetry warnings without retrying the entire write.
- Concurrent edit: stop on the Runtime conflict, re-list, then retry only with current user intent.
- Graph/control-plane unavailable: quest lifecycle remains functional.
Rules
- Markdown/Git is authoritative in every mode.
- One list snapshot per route; one canonical write per transition.
- Never edit quest files or their index directly.
- Never call Git, QMD, Neo4j, Supabase, or notification APIs from this skill.
- Quest participation is not notification consent. Any later notification is a separate exact recipient/message approval after canonical writeback.
- Do not include titles, questions, contributions, outcomes, or paths in telemetry.
Emit content-free command telemetry only if Runtime writeback did not already record the operation:
bash bin/telemetry.sh emit "command" '{"command":"quest","subcommand":"<route>"}' 2>/dev/null &Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

