- Home
- Skills
- Productivity
- A Working Second Brain: Notes, Memory, and Retrieval That Survive
More screenshots
Works with the AI Agents you already use
A Working Second Brain: Notes, Memory, and Retrieval That Survive
Turn scattered notes into a system you can trust: thirty-second capture, four buckets by action, one curated map per subject, and maintenance loops that keep old notes honest.
$5
A Working Second Brain: Notes, Memory, and Retrieval That Survive
Example session with this skill installed
I am a freelance illustrator and my notes are everywhere: client feedback in email, color palettes in a notes app, contract details in chat messages, and ideas on paper. I can never find the feedback on my last project when a client asks about it. Build me a system I will actually keep using.
- Read your context and instructions
- Compiled the a working second
SYSTEM SETUP — one inbox (your phone notes app), four buckets, weekly triage every Friday, 30 minutes.
BUCKETS (first triage, 23 items filed): Projects — "Harbor Cafe mural" (goal: install by May 30), "Portfolio refresh" (goal: live by June 15). Areas — Clients, Money, Health. Resources — Color palettes, Reference images, Technique notes. Archive — last year's finished commissions. The lost feedback becomes one atomic note — "Harbor Cafe: client asked for warmer reds in the window panel, March 12, email" — filed under Projects, linked to the Clients map, source recorded. Decision rule applied: the contract details are an Area (ongoing), not a Project — no deadline, just care.
MAPS — Clients map (7 notes, ordered by active work), Color map (9 palettes, annotated with where each was used), each with a Gaps line. Gap found: no backup printer contact — now a Project note.
LOOPS — monthly contradiction scan (two palette notes disagreed on a supplier; resolved in a dated note, old note untouched), quarterly sweep, correction capture (a client's "less orange" correction recorded above your own inference). RETRIEVAL TEST — Harbor feedback, contract renewal date, favorite palette, printer quote, mural deadline: all five found within a minute each. Health rubric: 10 of 12. The one weak row is map freshness, with a named fix: rebuild the Color map next Friday.
Connects securely to your tools. The creator never sees your data.
About this skill
Most note systems fail the same way: enthusiastic capture, no retrieval, abandonment. This skill builds the system that survives contact with a real week, as habits rather than features, so it works in any tool. The organizing principle is action, not topic: every note goes into exactly one of four buckets — Projects (active efforts with a goal and an end), Areas (ongoing responsibilities), Resources (reference with no action attached), and Archive — with a decision rule for notes that could fit two. Capture takes under thirty seconds, one idea per note, source recorded, linked forward to an index map or left in the inbox; a weekly thirty-second triage files, actions, or deletes everything captured. For each live subject you keep one curated index map — a human-ordered, annotated list of the notes that matter, with gaps and stale items named — built from a copy-ready template. Four maintenance loops keep the system honest over years: a monthly contradiction scan that resolves conflicts in new dated notes without silently editing the old ones, a quarterly staleness sweep, continuous correction capture that weights explicit corrections above inferred knowledge, and occasional re-reading. Safe-evolution rules keep reorganizations logged and reversible, measured by a retrieval test. The same structure applies to an assistant's stored memory, with provenance and decay. It includes a six-row health rubric, a complete worked example following a fictional bakery owner for four months, edge cases, anti-patterns, and a ten-item quality gate.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Productivity.
- It is a personal system: it does not organize shared team archives, where actionability differs per person — keep a personal layer and link to the shared archive as a source.
- It needs thirty minutes a week of maintenance; with zero maintenance time, any system decays, and this one says so plainly instead of pretending otherwise.
- The health rubric and retrieval test measure whether the system works; they cannot force the weekly triage habit, which remains yours to keep.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 days ago
Permissions
No special permissions declared or detected