Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/night-market-collective-memory
Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything.
Passed 13 of 18 test cases with the skill, and 3 of 18 without it.
and 18 more in the full report
12 fixed4 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
How many fire emoji reactions on a [Learning] discussion post are required to automatically trigger promotion to a GitHub Issue via the abstract promotion script?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the promotion threshold as 3 fire emoji reactions. | Missed | Passed |
| Names promote_discussion_to_issue.py as the script handling discussion promotion. | Missed | Passed |
The instructions your model reads when the skill loads.
This repo treats GitHub Discussions as agent collective memory
(ADR-0007, docs/adr/0007-github-discussions-integration.md,
accepted 2026-02-19). Sessions are amnesiac by default. The memory
system fixes that with four layers: Discussions (cross-session,
searchable), the decision journal (append-only tradeoff and lesson
logs), numbered ADRs (architecture decisions), and dated research
syntheses in docs/research/. One caveat on the fourth layer:
docs/research/ is gitignored and machine-local, so it exists only
on the authoring machine and is empty on fresh clones. A synthesis
counts as collective memory only after promotion to a Discussion,
ADR, or rule. This skill tells you where each kind of knowledge
lives, how to read it, and how to write to it.
One hard fact first: there is NO gh discussion subcommand.
Discussions are GraphQL-only. Minister playbooks once referenced a
CLI that does not exist, and ADR-0007 replaced every reference with
gh api graphql calls. Never guess a gh discussion command.
| You have | Record or read it via |
|---|---|
| Settled battle, revert, dead end | night-market-failure-archaeology skill (read only, do not relitigate) |
| Tradeoff (chose A, sacrificed B) | Decision journal docs/tradeoffs.md, TR-NNN entry |
| Lesson, failed approach, rework | Decision journal docs/lessons-learned.md, LL-NNN entry |
| Architecture decision | Numbered ADR in docs/adr/ (0001-0017 exist today) |
| Session insight, skill stats | [Learning] Discussion (auto-posted daily, see below) |
| Strategy debate, big design | [War Room] Discussion (Decisions category) |
| Durable synthesis, audit result | [Knowledge] Discussion (Knowledge category) |
| PR review finding worth keeping | [PR Finding] Discussion (Learnings category) |
| Multi-source research output | Dated file in docs/research/ (LOCAL ONLY: gitignored, absent on fresh clones). Promote durable syntheses to a [Knowledge] Discussion, ADR, or rule to make them collective memory |
Before investigating any question about this repo's history, design, or past failures, run these searches first. Re-deriving a settled answer wastes a session and risks contradicting an accepted decision.
test cases passed, vs 3 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.