- Home
- Skills
- Productivity
- Notes That Find Each Other: Graph-First Markdown Notes
More screenshots
Works with the AI Agents you already use
Notes That Find Each Other: Graph-First Markdown Notes
Write notes that can be found again: a fixed anatomy, links chosen by meaning, embeds used only where the reading flow needs them, and a maintenance ritual that keeps the graph connected.
$5
Notes That Find Each Other: Graph-First Markdown Notes
Example session with this skill installed
I run a fictional neighborhood tool library called Harborview Tool Library. Write me a durable note for its Saturday lending hours decision, linked to the volunteer rota and the lending rules, with the open questions marked for review. Invent the details.
- Read your context and instructions
- Compiled the notes that find
NOTE — Harborview Tool Library Lending Hours, invented details for this demo only.
Properties: title Harborview Tool Library Lending Hours; tags project/active; aliases Lending Hours, Saturday Hours; created 2026-11-04.
Summary: The Harborview Tool Library lends tools on Saturdays from 9 to 12. The open question is whether three hours covers demand on busy weekends; the rota covers staffing, not demand.
Decision, in an important callout with a block identifier: Saturday hours are 9 to 12, morning-only — the hall is booked in the afternoon.
Open question, in a question callout: Do we need a second lending day if Saturday demand keeps growing?
Links, each with a stated reason: Volunteer Rota — who staffs Saturday mornings, built around the morning hours; Tool Library section Borrowing Rules — the lending rules the hours must fit.
LIVE-FIRE NOTES: the first draft failed two quality-gate items and was fixed before this result was finalized. The decision was first buried in a prose sentence instead of an important callout; it was moved into the callout with a block identifier. The lending-rules link first pointed at the general Tool Library note, scoring 1 on the rubric because the reader had to hunt for the rules; it was narrowed to a section link scoring 2. The final note passes all ten gate items: summary present, properties complete, two outbound links scoring 2, callouts per the vault map, decision in a callout with an identifier, no whole-note embeds, no duplicate concept, a real open question, thirty-second relevance judgement, and links forward to the work the note enables.
Connects securely to your tools. The creator never sees your data.
About this skill
A vault full of notes is not a vault that works. This skill treats every durable note as a citizen of a graph: it states its own point in a one-paragraph summary, it points outward to the notes it depends on, it marks open questions so a search can recover them, and it gets pruned when it stops earning its place. Work follows five steps. First, every durable note gets the same anatomy: a properties block with title, broad-bucket tags, aliases, and creation date; a summary paragraph that lets a reader judge relevance in thirty seconds; and a links section written while writing, never in a later pass that never happens. Second, links are chosen by meaning, not by word — the concept as it applies here, scored against a three-level rubric, with display text keeping prose readable, section links for precision, and block references reserved for quoting an exact decision. Third, the embed-or-link choice follows the reading flow: link when the reader might want context, embed when the argument depends on the content being read here, and embed sections rather than whole long notes. Fourth, one fixed meaning per callout type turns callouts into a vault-wide scanning system, so every open question or decision is one search away. Fifth, a short maintenance ritual — search open questions, find orphans, merge duplicates, delete without guilt — runs monthly or quarterly and keeps the graph alive. Every durable note finishes against a ten-item quality gate, and a note that fails it is reworked, not filed.
- It cannot rescue a vault where notes have no summaries and no links without a pass of real editorial work; the skill guides that pass, it does not skip it.
- It assumes the vault tool supports wikilinks, backlinks, properties, and callouts; in a plain folder of files, the linking and callout steps do not apply.
- It does not decide what is worth keeping for you; the delete step needs your judgement about which notes still earn their place.
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 any payment.
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