alchemy
/alchemy
Use when the user mentions Alchemy, their research notebooks, or wants sources (URLs, files, pasted text) collected, searched, or written up in a local notebook. Alchemy is their local-first research notebook app; this Python-backed skill exposes its notebooks, sources, notes, and hybrid search in the kernel.
- Author
- thrashr888 ↗
- Repository
- alchemy ↗
- Licence
- MPL-2.0
- Last repository change
- 11.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 11.10.2026, without references to retired models or APIs.
MPL-2.0, otwarta.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: __init__.py
What it does and when to use it
Use when the user mentions Alchemy, their research notebooks, or wants sources (URLs, files, pasted text) collected, searched, or written up in a local notebook. Alchemy is their local-first research notebook app; this Python-backed skill exposes its notebooks, sources, notes, and hybrid search in the kernel.
Original author description
Use when the user mentions Alchemy, their research notebooks, or wants sources (URLs, files, pasted text) collected, searched, or written up in a local notebook. Alchemy is their local-first research notebook app; this Python-backed skill exposes its notebooks, sources, notes, and hybrid search in the kernel.
How it works
- Calling from the kernel
- Workflow
- Filling a notebook from a list
- Sharp edges
SKILL.md preview
---
name: alchemy
description: Use when the user mentions Alchemy, their research notebooks, or wants sources (URLs, files, pasted text) collected, searched, or written up in a local notebook. Alchemy is their local-first research notebook app; this Python-backed skill exposes its notebooks, sources, notes, and hybrid search in the kernel.
---
# Alchemy — the user's local research notebook
Alchemy is a local-first NotebookLM-style app. A **notebook** holds **sources**
(fetched URLs, imported files, watched folders, pasted text — auto-chunked and
embedded on device) and **notes** (markdown the user or you write). Sources
can also be living Mac items the user connected (Apple Notes, Reminders
lists, Calendar windows, Stocks watchlists via `cider://` origins) — these
re-sync automatically. Everything runs on the user's machine; nothing you
store or search leaves it.
## Calling from the kernel
This is a Python-backed MCP integration: Alchemy's tools are async methods on
the auto-imported `alchemy` module. Discover before you call — the tool set
comes from the app, not this file:
```python
import alchemy
for tool in await alchemy.list_tools():
print(tool["name"], "-", tool["description"])
hits = await alchemy.search(notebookId="…", query="…")
```
Every tool is `async` — always `await`. Results arrive as parsed Python
(dicts/lists), no `json.loads` needed.
A connection error means the Alchemy app isn't running or its private local
credential needs refreshing — its MCP server lives inside the app at
`http://127.0.0.1:41414/mcp`. Ask the user to open Alchemy and use
Settings → Agents → Connect if needed. (No Alchemy at all? It's a free
macOS app: https://github.com/thrashr888/alchemy/releases — this skill is
useless without it.)
## Workflow
1. `list_notebooks` to find the right notebook; `create_notebook` if the topic
deserves its own. Prefer reusing an existing notebook over creating
near-duplicates.
2. `add_source` for each URL, file path, or block of text worth keeping.
Ingestion extracts, titles, chunks, and embeds automatically.
3. `search` to ground claims before writing — hybrid vector + keyword
retrieval over the notebook's chunks. It runs on a local embedder and is
effectively free; make several small queries rather than one broad one.
When you don't know WHICH notebook holds something ("where did the user
save X?"), use `ask_everything` — the same retrieval across the entire
corpus, each passage tagged with its notebook. It returns raw passages;
synthesize the answer yourself.
4. Write findings with `create_note` (markdown). Cite which sources informed
each claim by title so the user can verify.
5. Mac-item write-back, when the user asks for it: `update_mac_note` replaces
the body of an Apple Notes source (writes to the real note, then
re-syncs); `add_reminder` appends to the Apple Reminders list behind a
Reminders source. Both work only on sources the user already connected —
find them in `list_sources` by a `url` starting with `cider://notes/note/`
or `cider://reminders/list/`.
## Filling a notebook from a list
When the user hands you a list of things to cover, the work is finding the
right page for each. Prefer each item's official page and check unsure
URLs first (a quick search, or a HEAD request) instead of guessing paths.
Read every result: a `title` like "Page Not Found", "Access Denied", or
"Attention Required", or a `charCount` of a few hundred, is not content
even when `status` says ready — delete it and try an alternate page, a
support-center article, or a `text` source you write and label as your
own summary. A two-segment path on an unfamiliar host can be mistaken for
a git repo; if an add comes back with a clone error, re-add the URL with a
`#fragment`. Add three to five at a time, then finish with an index note
mapping each item the user named to its sources and gaps. Covers, tags,
and notes on sources are yours to set (`set_source_image`,
`set_source_tags`, `set_source_note`).
## Sharp edges
- **Duplicates are rejected, not silently merged.** Adding the same URL or
identical content errors with the existing source's title. Treat that as
success and move on.
- **URL imports can fail soft.** Bot-walled or login-gated pages land as a
source with `status: "error"` and a reason. Report it; don't retry the same
URL blindly — try an alternate URL or paste the content as text instead.
- **`search` returns passages, not documents.** When you need full context,
call `get_source` with the passage's `sourceId`.
- **Notes are shared with the user.** `update_note` replaces the whole note —
`get_note` first, and preserve the user's edits. Never `delete_notebook` or
delete notes/sources the user didn't explicitly ask to remove.
- **Mac write-back edits the user's real Apple Notes/Reminders.**
`update_mac_note` replaces the entire note body — `get_source` first and
preserve their content; the first line is the note's title, keep it there.
Only write when the user asked for the change.
- The user sees changes live in the app as you work — no need to tell them to
refresh.
Files in this package (3)
- SKILL.md 5 KB
- __init__.py 2 KB
- pyproject.toml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · thrashr888/alchemy | 95 | MPL-2.0 |
| bankrbot/openclaw-skills | 100 | MIT |
| 0xvikram/backboard-skills | 100 | MIT |
| thrashr888/alchemy | 90 | MPL-2.0 |
| thrashr888/alchemy | 85 | MPL-2.0 |
Database snapshot: 13.11.2026 · package version 518a969643cf (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
- 100alchemy-prod-checklist
Make an evidence-backed go or no-go decision for an Alchemy-backed production release. Use when reviewing a launch or material integration change. Trigger with "Alchemy production checklist", "Alchemy go-live review", or "is this Alchemy integration ready". - 100alchemy-ci-integration
Gate Alchemy integration changes with deterministic unit, contract, fork, secret, and negative-path checks. Use when adding Alchemy to CI or hardening an existing pipeline. Trigger with "Alchemy CI", "Alchemy GitHub Actions", or "test Alchemy in CI". - 100alchemy-webhooks
Receive and verify Alchemy Notify webhooks. Use when setting up Alchemy webhook handlers, debugging X-Alchemy-Signature verification, or handling onchain events like ADDRESS_ACTIVITY, NFT_ACTIVITY, or GRAPHQL (Custom Webhook). - 100notebooklm
Interact with Google NotebookLM (notebook.google.com) notebooks — chat with the AI, generate artifacts (slides, audio, video, mind maps, quizzes, flashcards, infographics, reports, data tables), manage sources (add URLs, YouTube, files, text), run research (fast/deep web… - 100alchemy-mcp
Use the Alchemy MCP server (`https://mcp.alchemy.com/mcp`) for live blockchain data and admin work when MCP is wired into your AI client. Exposes 150+ tools across 100+ chains for token prices, NFT metadata, transactions, simulation, tracing, account abstraction, Solana DAS, and… - 100alchemy-mcp
Use the Alchemy MCP server (`https://mcp.alchemy.com/mcp`) for live blockchain data and admin work when MCP is wired into your AI client and the Alchemy CLI is NOT installed locally. Exposes 159 tools across 100+ chains for token prices, NFT metadata, transactions, simulation,…