Want to access all premium content?
Become a paying subscriber to get access to all courses, guides like this, prompts and skills library, and $500+ worth of AI tools.
Jev is TypeSafe's decision model. Give it text and a set of options, and it returns a decision with probabilities. In this setup, Jev labels your notes while Opus 5.5 reads them and answers your questions.
We'll create a folder where notes are organized by type, project, and priority. You'll need Claude Code with Opus 5.5, a TypeSafe API key, and Terminal. Start with made-up notes until you've checked the filing rules.
Step 1: Set up the vault. Install the skill and connect your key.
Step 2: Define your labels. Choose the categories Jev can use.
Step 3: File your notes. Build the filer and check its decisions.
Step 4: Ask your notes. Get answers with source filenames.
Step 5: Review each week. Update priorities and check what needs attention.
Step 1: Set up the vault
Open Terminal and add TypeSafe's official marketplace:
claude plugin marketplace add typesafe-ai/skillsInstall the skill:
claude plugin install typesafe@typesafe-ai
Create an API key at console.typesafe.ai/keys. Enter it in Terminal, replacing the placeholder:
echo 'export TYPESAFE_API_KEY="your-api-key"' >> ~/.zshrcThis saves the key in your shell configuration. Keep it out of chat.
Open a new Terminal window, then create the folders:
mkdir -p ~/second-brain/inbox ~/second-brain/notesStart Claude Code inside the vault:
cd ~/second-brain && claudeRun /model and select Opus 5.5.
Check the connection:
Read the TypeSafe skill and confirm which environment variable it expects. Check that it's set without printing the value.
Then send one Jev test call using:
State: "Buy basil and tomatoes for Friday's pasta."
Noul question: "This note is about cooking."
Show the result without exposing my API key.
Expect a high value for this example. If authentication fails, check the variable name and whether the new Terminal session loaded the key.
Step 2: Define your labels
The labels tell Jev where each note belongs. Use categories you can explain clearly, including somewhere for notes that don't match a project.
Create labels.md with editable definitions for:
Types: idea, task, reference, meeting, journal.
Projects: [MY PROJECTS], plus none or unclear.
Priority: five ordered levels, from archive candidate to act this week.
Define each priority level in plain language. Keep the displayed priority labels separate from any zero-based score returned by the API.
Start with three to eight projects so the list is easy to review. Add more when you need them.Each note gets several questions:
Question | Primitive | Result |
What kind of note is it? | Choice | A type and its probabilities |
Which project does it concern? | Choice | A project and its probabilities |
How soon does it need attention? | Score | A position on your defined scale |
Is it useful long-term? | Noul | A value from 0 to 1 |
A note can be useful without being urgent. Keep the priority and long-term usefulness questions separate.
Step 3: File your notes
Ask Opus 5.5 to build the filer:
Read the TypeSafe skill and current API documentation, then build a filer for this vault.
For each Markdown or text file in inbox/:
1. Send its contents to the current documented Jev model.
2. Ask for type, project, priority, and long-term usefulness using labels.md.
3. Save the labels and returned probabilities in a metadata block.
4. Propose a destination under notes/[type]/.
5. Leave uncertain classifications in inbox/ for review.
Start with 0.6 as the review threshold for choice probabilities. Don't assume every question returns a separate confidence field.
If long-term usefulness is below 0.3, mark the note as an archive candidate rather than moving it automatically.
Preserve the original text, never overwrite a file, and keep an action log. Read the API key from the environment without printing it.
Show a dry run first and give me the command to apply approved moves.
The thresholds are starting points. Review the decisions before adjusting them.
Copy a few non-sensitive notes into ~/second-brain/inbox, or ask:
Save this as a new file in inbox/ without changing the wording:
[NOTE]
Run the dry run, inspect the proposed labels, then approve the moves you want.
Open a filed note. Check its type, project, priority, usefulness value, and recorded probabilities against the original text.
Step 4: Ask your notes
Have Opus 5.5 use the labels to narrow its search, then read the relevant files before answering:
Using only notes/ as your source, list the open tasks for [PROJECT], sorted by priority.
Read the relevant files and cite a filename for each task. Don't assume a task is open unless its contents or status support that. Flag anything unclear.
Open two cited files and compare them with the answer. Labels help find information, but they don't replace reading it.
If a cited file doesn't exist, ask Opus to list the actual paths and answer again from those files.
Step 5: Review each week
Priorities change. Give Jev the current date and review context rather than assuming an old task no longer matters.
Run a dry run of the inbox filer.
Then reassess priority for task notes older than seven days. Include today's date and any recorded deadlines or status. Don't treat age alone as a reason to archive.
Show proposed priority changes and archive candidates for my approval.
Write weekly.md with:
- New notes by project
- The five highest-priority open tasks
- Notes still waiting in inbox/
- Proposed changes needing review
Don't move archive candidates until I approve.
Read the summary and resolve the inbox items. A note left behind may need a better definition, more context, or a manual label.
Once the process works, you can set up a Monday cleanup in the Claude Code desktop app. Confirm the schedule and what it is allowed to change.
Use cases
Once the filer works, try these four jobs.
Use case #1: Sort an old folder
Bring loose notes into the vault while preserving the originals.
Copy the .md and .txt files from [FOLDER] into inbox/. Preserve the originals and avoid filename collisions.
Run the filer in dry-run mode and show the proposed destinations.
Review uncertain notes before importing another folder.
Use case #2: Prepare for a meeting
Gather recent project context before a call.
Read notes for [PROJECT] from the last 30 days.
Summarize confirmed decisions, open issues, and three questions worth asking. Cite a filename for each factual point and separate your suggested questions from recorded facts.
Check the decisions against their sources.
Use case #3: Revisit old ideas
Find ideas that might fit your current work.
Find idea notes older than 30 days with a recorded priority of 3 or higher.
Read them and suggest three that fit my current projects. Cite the files and explain the connection. Don't change their labels.
Choose which ideas deserve a new task.
Use case #4: Spot duplicates
Compare new notes with likely matches.
For each note filed this week, find five candidates with similar titles.
Use Jev to assess whether each pair contains substantially the same information. List pairs above 0.8 with both file paths.
Don't merge or delete anything.
Read both files before merging. Similar titles can hide different details, and different titles can hide duplicates.
Confirmed limitations
Jev requires a TypeSafe account and API key. Launch coverage reported $0.042 per million input tokens with free output; check the console for current pricing.
Categories and thresholds need testing. A high probability doesn't guarantee a correct label, and a low priority doesn't mean a note should be archived.
The filer sends note contents to TypeSafe's API. Start with fictional or non-sensitive material and follow your data-sharing requirements.
Starting Claude Code inside the vault doesn't technically restrict it to that folder. Give explicit source instructions and check permissions separately.
Opus 5.5 can misread notes or cite the wrong file. Check important answers against their sources.
Closing
Start with a small batch of notes and review the labels before applying any moves. Adjust the definitions where Jev gets the categories wrong.
Then ask a few questions whose answers you already know. Once filing and retrieval hold up, add more notes and use the weekly review to keep priorities current.
See you in the next one :)