alchemy
Skill88 starsChanged 3 days agoMITView on GitHub
Runs a lightweight change preflight, then routes non-trivial design, refactor, and audit work through only the needed requirements and A.L.C.H.E.M.Y. skills. Explicitly trigger with `/alchemy`, `$alchemy`, or natural phrases such as "do some alchemy", "run alchemy on this", "use alchemy", or "give this an alchemy pass". Use for architecture, complexity, enforcement, shift-left, optimization, subsystems, increments (vertical slices), abstractions, cross-boundary refactors, consolidation, and over-engineering audits. Explicit invocation on a local bug fix, content or CSS edit, dependency bump, or trivial rename returns a cheap `SKIP` or `DIRECT` dispatch instead of loading every gate. Defines no new domain rules; routes to core sibling skills and task-matched companion skills.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- darjss/alchemy-skilltheir own version, first seen Nov 16, 2026
- cill-i-am/skillstheir own version, first seen Oct 20, 2026
- 0xvikram/backboard-skillstheir own version, first seen Oct 20, 2026
- Eskyee/agentbot-opensourcetheir own version, first seen Oct 13, 2026
- BankrBot/openclaw-skillstheir own version, first seen Oct 8, 2026
- wyattjoh/skillstheir own version, first seen Sep 27, 2026
Used with
Projects with it also use quicknode, neynar and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BankrBotSkillquicknode
Blockchain RPC and data access via Quicknode. Use when an agent needs to read onchain data (balances, token prices, transaction status, gas estimates, block data) across Base, Ethereum, Polygon, Solana, or Unichain. Supports both API key access and x402 wallet-based pay-per-request access with no account needed. Triggers on mentions of RPC, blockchain data, onchain queries, token balances, gas estimation, block number, transaction receipt, Quicknode, or x402.
Also in 4 projects that use this
basezhSkillneynar
Interact with Farcaster via Neynar API. Use when the user wants to read Farcaster feeds, look up users, post casts, search content, or interact with the Farcaster social protocol. Requires NEYNAR_API_KEY.
Also in 4 projects that use this
BankrBotSkillaeon-autoresearch
Evolve any installed skill by generating four variations along separate theses (better inputs / sharper output / more robust / rethink), scoring them on a weighted rubric, and applying the winner. Never downgrades a working skill — aborts cleanly if no variation improves the original. Use when an installed skill is producing low-signal output, hitting deprecated APIs, or feels stale. Triggers: "improve this skill", "evolve $skill", "auto-research my X", "regenerate variations".
Also in 3 projects that use this
- +9 more from BankrBot
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- BankrBot/openclaw-skills★ 1.2ksame name
- BankrBot/skills★ 1.2ksame name
- Eskyee/agentbot-opensource★ 17same name
- wyattjoh/skills★ 3same name
- 0xvikram/backboard-skills★ 1same name
- cill-i-am/skills★ 1same name
- lesliewangwyc-dev/prompt-alchemy★ 1same name
- darjss/alchemy-skill★ 0same 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 repository52 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alchemy-orchestrateSkill
- alchemySkill
- architecture-as-code-javascriptSkill
- architecture-as-code-pythonSkill
- architecture-as-codeSkill
- architecture-guidelinesSkill
- bring-downSkill
- ci-cd-reliability-architectureSkill
- continuous-improvementSkill
- defect-shift-leftSkill
- dependency-lifecycleSkill
- evolutionary-database-designSkill
- functionality-complexity-tradeoffSkill
- gate-lifecycleSkill
- implementation-readinessSkill
- infrastructure-fitSkill
- morphogenetic-architectureSkill
- observability-designSkill
- push-outSkill
- requirements-groundingSkill
- requirements-topologySkill
- requirements-traceabilitySkill
- structural-simplificationSkill
- system-optimizationSkill
- test-strategySkill
- zero-copy-requirementsSkill
- alchemy-orchestrateSkill
- architecture-as-code-javascriptSkill
- architecture-as-code-pythonSkill
- architecture-as-codeSkill
- architecture-guidelinesSkill
- bring-downSkill
- ci-cd-reliability-architectureSkill
- continuous-improvementSkill
- defect-shift-leftSkill
- dependency-lifecycleSkill
- evolutionary-database-designSkill
- functionality-complexity-tradeoffSkill
- gate-lifecycleSkill
- implementation-readinessSkill
- infrastructure-fitSkill
- morphogenetic-architectureSkill
- observability-designSkill
- push-outSkill
- requirements-groundingSkill
- requirements-topologySkill
- requirements-traceabilitySkill
- structural-simplificationSkill
- system-optimizationSkill
- test-strategySkill
- zero-copy-requirementsSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 4 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Keep the default response terse: resume from the latest trustworthy decision, route to the smallest useful stage set, state the verdict, …
- Very specific: line 79
Do not run every gate by default: only explicit full language selects FULL, and Alchemy FULL is a traversal dispatch, not a gate's analysis …
- Very specific: line 110
When the subject decides where a fact, decision, or document belongs — a proposed document, a decision record, an architecture note, a …
- Very specific: line 117
When an advisory, drift, abandonment, license change, or end-of-life date names an owned dependency, select dependency-lifecycle.
- Very specific: line 120
When a risk survives verification into production, or alerts or telemetry are under review, select observability-design.
- Very specific: line 122
When infrastructure is chosen, inherited, or questioned, select infrastructure-fit.
- Very specific: line 124
When a gate is added over violations, narrowed, suspended, or removed, passes on a known-bad input, or cannot evaluate, or a baseline …
- Distinctive: line 153
Every stage describes change with four primitives: a Subsystem is where change lands, an Aspect is which dimension is touched, an Increment …
- Distinctive: line 184
Read references/failure-modes.md when a run's result looks wrong, an audit shows a symptom, or a trail has an unexplained skip.
- Distinctive: line 192
Default output for a single-gate or simple routed request:
- Very specific: line 241
Load each stage when the route reaches it: Read a stage's or companion pass's SKILL.md only once every stage before it has passed, never …
“Common” is measured: kept by at least 6 in 10 of the 8 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
Alchemy
Command entrypoint for the adaptive A.L.C.H.E.M.Y. gate system. Requirements qualification spans the Minimum gate without adding letters to the acronym. Keep the default response terse: resume from the latest trustworthy decision, route to the smallest useful stage set, state the verdict, and name the next action.
1. Command Grammar
Invoke as /alchemy <alias> <subject> in Claude Code or $alchemy <alias>
<subject> in Codex; the alias is optional. Natural language is equivalent:
do some alchemy, run alchemy on this, use alchemy, and give this an
alchemy pass all request adaptive dispatch on the active subject.
The subject is the invocation arguments. Where commands expand arguments,
$ARGUMENTS is that string; if it is empty or literally unexpanded, use the
surrounding request text. A natural phrase with no explicit subject uses the
active request or most recent unresolved task; never ask the user to restate
context already in the conversation or worktree. ?, help, --help, or an
empty command with no active subject returns only this table.
| Alias | Route |
| none | Run the dispatch preflight; infer Design, Refactor, or Audit mode |
audit | Start at the read-only C₀ structural baseline; recover requirements only when intent is missing, stale, contradictory, or disputed |
full, all, walk the gates, complete alchemy | FULL: traverse every justified stage; record why any conditional stage is skipped |
M, minimum, necessity, worth | functionality-complexity-tradeoff — worth it? |
A, architecture, first-principles | architecture-guidelines — sound design? |
L, locality, placement | morphogenetic-architecture — where does it belong? |
C, complexity, simplify | structural-simplification — simpler? |
E, enforcement, architecture-as-code | architecture-as-code, plus -javascript or -python only when rule files are written or changed — rules as code? |
H, hermetic, shift-left | defect-shift-left, plus ci-cd-reliability-architecture for pipeline reliability — catch earlier? |
Y, yield, optimize | system-optimization — optimize flow? |
left | defect-shift-left — detect defects earlier |
out, push-out | push-out — move toil out of humans |
down, bring-down | bring-down — move bespoke code down |
zero-copy, source-of-truth | zero-copy-requirements |
deps, dependency | dependency-lifecycle |
infra, infrastructure | infrastructure-fit |
signal, observability | observability-design |
left, out, and down form the DevOps improvement triad, outside the
seven-gate sequence: run a triad move only when the user names it. During
/alchemy Y, recommend out or down when the bottleneck is manual toil or
bespoke implementation, but do not run them unless the user asks.
Dispatch Preflight
Classify before reading any sibling skill body. Make dispatch the first observable checkpoint: decide from the request, already-loaded context, skill metadata, and the latest trustworthy decision artifacts; do not scan the repository or open sibling bodies merely to choose a dispatch. After emitting the dispatch, inspect only the artifacts and skills the route selects.
| Dispatch | Select when | Core route |
SKIP | Local behavior stays inside one governed boundary and asks no Alchemy question: copy/CSS, trivial rename, contract-preserving dependency bump, isolated in-boundary fix | None: load no gate skill; continue with matching companions and normal verification |
DIRECT | An alias, or one unambiguous gate question: worth, dead code, speculative abstraction, or "should this exist?" is M; a defect found late, check placement, or CI detection timing is H or left | Only that gate or triad skill |
ADAPTIVE | Structure, responsibility, data flow, abstraction, multiple requirements, or boundaries may change | The smallest justified set: a structural refactor inside one boundary is M, C, plus A when responsibility or public contract changes and H when verification placement changes; a new subsystem/service/library, cross-boundary dependency, increment cut through every layer (vertical slice), consolidation, or an aspect added or changed across several subsystems (auth, audit, logging, retry, i18n) is qualification as needed, M, A, L, C, E, H; an existing-code over-engineering audit is Audit mode from C₀ |
FULL | The user explicitly says full, all, walk the gates, or complete alchemy | Every justified stage, every skip recorded |
Do not run every gate by default: only explicit full language selects FULL,
and Alchemy FULL is a traversal dispatch, not a gate's analysis mode. Do not
convert uncertainty into FULL; select the smallest plausible route, state
the uncertain signal, and stop at the first missing prerequisite.
Gate and triad aliases are authoritative: use only that core gate or triad
move, even when the subject mentions subsystem boundaries, and expand the core
route only for explicit full, all, audit, walk the gates, or complete
alchemy. Focused aliases never silently run requirements qualification. If a
focused gate lacks a prerequisite, report the missing decision artifact and
stop at that gate unless the user asked for a broader pass. The prerequisites:
- Gate E remains blocked until Gate 3 records final acceptance; a
MOVE,SPLIT,MERGE, orINTRODUCE-BOUNDARYfirst runs the boundedL candidate → C measurement → L acceptancehandshake, re-entering L once. - Gate E also waits for a passing readiness decision in a full pass.
- Gate Y runs in iteration 2, the iteration after the increment ships, from its stable, measured baseline, unless the request is explicitly about an existing bottleneck.
ADAPTIVE, FULL, and audit read the route in §2 before selecting stages.
Companion Skill Routing
Alchemy owns the core qualification and gate route, not every task domain. From skill metadata and project instructions, select any non-Alchemy skill whose trigger independently matches the subject, and read only the selected companion bodies. A project profile may require companions for its domain, stack, UX, security, accessibility, API, release, or evidence rules; never hard-code project-specific companion names into this generic skill.
- When the subject decides where a fact, decision, or document belongs — a
proposed document, a decision record, an architecture note, a status page, or
a documentation-tree audit — select
zero-copy-requirements. It names the artifact that owns the question;push-outprunes prose already covered by an executable source, andrequirements-traceabilityanchors evidence once the location exists. None of the three is a qualification stage, gate, or acronym letter. - When an advisory, drift, abandonment, license change, or end-of-life date
names an owned dependency, select
dependency-lifecycle; it classifies the bump, and only a contract-preserving bump isSKIP. - When a risk survives verification into production, or alerts or telemetry
are under review, select
observability-design. - When infrastructure is chosen, inherited, or questioned, select
infrastructure-fit. - When a gate is added over violations, narrowed, suspended, or removed, passes
on a known-bad input, or cannot evaluate, or a baseline churns, select
gate-lifecycle; it never places a check or decides how it blocks. test-strategyandevolutionary-database-designare two-pass companions that bracket A/L/C/E; the route in §2 orders their passes.SKIPskips only the Alchemy core; it never suppresses a matching companion.DIRECTkeeps the core route focused while allowing independently triggered companions.- Report companions explicitly. Use
Nonewhen no companion trigger matches.
Execution Strategy
Execution is a second decision after dispatch, never a fifth dispatch: it
decides whether one agent or several carry out the selected route, and the
user never names agents. SKIP and DIRECT run single-agent and never load
orchestration. ADAPTIVE, FULL, and audit select multi-agent only when
the work changes or audits code and at least two parts are independent —
different subsystems, disjoint files, no ordering between them — or a
high-risk change (security, public contract, persisted shape) needs a
reviewer that did not write it. Count every agent: one writer and one
independent reviewer is multi-agent. The number of gates or skills on the
route is never a reason. Stay single-agent and say why when neither
holds, when the project's alchemy-workspace.json sets
execution.multi_agent to off, or when the runtime cannot launch agents.
On multi-agent, load alchemy-orchestrate before the first stage that
changes or audits code; it plans, launches, verifies, and gates the agents.
Change Primitives
Every stage describes change with four primitives: a Subsystem is where change lands, an Aspect is which dimension is touched, an Increment is what changes, and an Iteration admits, realizes, and measures one increment. Each sibling names its own term as a specialization of exactly one and never redefines them; references/change-primitives.md defines them and maps each sibling term. Decomposition and aspect extraction are different cuts: decomposition splits one subsystem into several; extraction pulls one aspect out of several subsystems into one mechanism. A design that models an aspect as a subsystem, or copies its mechanism per subsystem, has confused the two.
2. Adaptive Requirements Qualification
Requirements Grounding, when evidence or meaning is absent or stale
→ M — Minimum
→ Requirements Topology, when relationships are non-trivial
→ Implementation Readiness
→ A — Architecture → L → C → E → H → YQualification stages are conditional and never become acronym letters. Before
selecting stages for ADAPTIVE, FULL, or audit, read
references/adaptive-route.md: routing rules,
decision hand-offs, the gate table, the Gate 3–4 handshake, the two-pass
companion order, core directives, the pre-flight checklist, and the
retrospective order. SKIP and DIRECT never need it.
Read references/failure-modes.md when a run's result looks wrong, an audit shows a symptom, or a trail has an unexplained skip; route the recovery to the named stage instead of rerunning every gate.
3. Output Contract
Default output for a single-gate or simple routed request:
Dispatch: <SKIP | DIRECT | ADAPTIVE | FULL>
Core route: <None | M | A | L | C | E | H | Y | left | out | down | ordered set>
Companions: <None | task-matched skills>
Execution: <single-agent | multi-agent> — <independence or risk fact>
Verdict: Proceed | Redesign | Drop | Defer
Reason: <one or two lines>
Next: <one concrete action>For SKIP, emit this compact output alone with Core route: None; do not
load a core sibling merely to justify the skip.
Multi-stage runs, non-trivial design/refactor passes, audits, and explicit requests for detail emit one combined decision trail in execution order, including every stage used and every conditional stage skipped:
| Stage | Skill | Decision | Evidence / hand-off | Files/checks | Next action or skip rationale |
Then state:
Scope: <subsystem / service / refactor / PR>
Mode: Design | Refactor | Audit
Dispatch: SKIP | DIRECT | ADAPTIVE | FULL
Companions: <None | task-matched skills>
Execution: single-agent | multi-agent
Blocking stage: <first non-passing qualification decision or gate, or None>
Decision: Proceed | Redesign | Drop | Defer
Verification: <commands, lint rules, tests, or Not run + reason>Lead any run that reaches a verdict with the four report blocks the root instruction file defines, What I found, Why it matters, Do this first, and What I did not check, then emit the records unchanged: the trail and scope block, then each stage that ran in execution order, with the decision record its skill's output contract defines. The trail summarizes stages; it never replaces a stage's record. When implementing changes, add the normal coding summary after the verdict.
4. Discipline
- Skipped stages require a one-line rationale. A skip without one is a defect and an over-engineering risk for the next audit.
- Natural language stays adaptive. "Do some alchemy" never means
FULLwithout explicit full-traversal language. - Load each stage when the route reaches it. Read a stage's or companion
pass's
SKILL.mdonly once every stage before it has passed, never ahead. A blocking decision in the route's hand-off table ends the route for that candidate: the stages after it stay unloaded and appear in the trail asNot runwith that decision as the reason. Only candidates with a passing decision continue. - Claim only what ran.
Core routeand the trail name a stage's decision only when itsSKILL.mdwas read in this task; a selected stage that did not run appears in the trail asNot runwith the reason. - When a gate is consistently skipped across tasks, that's a signal for
continuous-improvementto update THIS skill — not paper over with case-by-case reminders.
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.

