agentleFS
AbilityaiAbilityai/cornelius/.claude/skills/recall/SKILL.md

recall

Skill109 starsChanged 39 days agoMITView on GitHub

Retrieve relevant knowledge from Obsidian vault using 3-layer semantic search based on conversation context

146 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware 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.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 133 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Local Brain Search for all semantic search operations.

    line 15
  2. Distinctive:

    Use spreading activation for better context:

    line 40
  3. Very specific:

    Use Read tool to read the full content of the top 2 results

    line 44
  4. Very specific:

    Use Read tool to read the full content of the top 2 connected notes

    line 51
  5. Very specific:

    Use --mode spreading for synthesis and connection-finding queries

    line 89
  6. Distinctive:

    Use static mode for exact factual lookups

    line 90
  7. Distinctive:

    If search returns no results, try broader terms or related concepts

    line 94

“Common” is measured: kept by at least 6 in 10 of the 133 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Semantic Knowledge Retrieval

You are tasked with retrieving relevant knowledge from the Obsidian vault using multi-layer semantic search.

Local Brain Search

Use Local Brain Search for all semantic search operations. Spreading activation mode recommended for synthesis queries.

Scripts:

# Static search (fast, exact matches)
BRAIN_READ_SCOPE=core,Books,document-insights resources/local-brain-search/run_search.sh "query" --limit 10 --json

# Spreading activation search (follows graph connections)
BRAIN_READ_SCOPE=core,Books,document-insights resources/local-brain-search/run_search.sh "query" --mode spreading --limit 10 --json

# Find connections
BRAIN_READ_SCOPE=core,Books,document-insights resources/local-brain-search/run_connections.sh "Note Name" --json

# Find hubs
resources/local-brain-search/run_connections.sh --hubs --json

Search Query

$ARGUMENTS

Instructions

Read role: lookup (contract: scope-mount, decided 2026-09-04): every search and neighbourhood call runs at the reasoning mount core,Books,document-insights, so recall answers "what do I know about X", and the output is grouped by scope so "what do I think about X" stays legible (the core group). Run the scope-mount trigger check on the query first; a hit appends ,company / ,thinkers / ,Books/<slug> for this run. --scope core (or "only my notes") pins the read to core; --hubs stays core always (fingerprint).

  1. First Layer - Initial Search:
    • Use spreading activation for better context:
      BRAIN_READ_SCOPE=core,Books,document-insights resources/local-brain-search/run_search.sh "$ARGUMENTS" --mode spreading --limit 5 --json
    • Use Read tool to read the full content of the top 2 results
  2. Second Layer - Direct Associations:
    • For the top result from layer 1, get connections:
      BRAIN_READ_SCOPE=core,Books,document-insights resources/local-brain-search/run_connections.sh "Top Result Note" --json
    • Use Read tool to read the full content of the top 2 connected notes
  3. Third Layer - Extended Network:
    • For additional context, check hub notes and bridges:
      resources/local-brain-search/run_connections.sh --hubs --json
    • This reveals deeper conceptual connections

Output Format

Present the findings in this structured format:

# Knowledge Recall: [Query Topic]

## Layer 1: Direct Matches
### Your thinking (core: 02-Permanent · 03-MOCs · AI Extracted Notes · 01-Sources)
[notes found, with key excerpts]
### What you have read (Books · Document Insights) - encountered, not endorsed
[notes found, with key excerpts - never presented as "your view"]
### Records (Company · Canon · Thinkers) - only when a trigger mounted them
[facts, `provenance: reference`]

## Layer 2: First-Degree Associations
[List connected notes with their relationships and excerpts]

## Layer 3: Extended Network
[Show hub notes and bridge connections]

## Key Insights
[Synthesize the main themes and connections discovered]

## Relevant Content
[Include the most pertinent excerpts from the retrieved notes]

Important Notes

  • Use --mode spreading for synthesis and connection-finding queries
  • Use static mode for exact factual lookups
  • Focus on quality over quantity
  • Highlight unexpected connections
  • Provide enough context for the user to understand the relevance
  • If search returns no results, try broader terms or related concepts
  • Learning active: Searches are tracked and rankings improve over time based on usage

State Dependencies

SourceLocationReadWriteDescription
Brain notesBrain/**/*.mdXSearch permanent notes, sources, MOCs
Local Brain Search indexresources/local-brain-search/XVector index for semantic search
Memory configresources/local-brain-search/memory_config.pyXTunable memory parameters

Completion Checklist

  • Layer 1 search executed (spreading mode for synthesis queries)
  • Layer 2 connections retrieved for top result
  • Layer 3 hub notes checked for context
  • Key insights synthesized from findings
  • Relevant excerpts included in output

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.