read_memory

Retrieve an org-roam memory node by UUID and return its title, content, and file path as JSON.

Updated Mar 29, 2024
One-click install
npx skills add https://github.com/addisonbeck/nix --skill read-memory-addisonbeck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: read_memory
Source: https://github.com/addisonbeck/nix/tree/main/bobert/skills/read_memory
Command: npx skills add https://github.com/addisonbeck/nix --skill read-memory-addisonbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Retrieving a memory node from org-roam by UUID can be time-consuming when you need its core details quickly. This skill streamlines the process by returning the node's title, full content, and exact file path in a structured format.

Core Features & Use Cases

  • Read a memory node by UUID and receive a JSON payload with id, title, content, and file.
  • Gracefully report errors when a node cannot be found and avoid breaking the workflow.
  • Integrate with memory-centric workflows to quickly access knowledge by ID during research or note-taking sessions.

Quick Start

Provide a UUID and I will return the memory node's title, content, and file path.

Frequently Asked Questions about read_memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve an org-roam memory node by UUID?

To retrieve an org-roam memory node by UUID, provide the UUID to the skill and it returns a structured JSON payload containing the node's title, full content, and absolute file path.

What is the best way to fetch org-roam knowledge by ID during research?

Fetching org-roam knowledge by ID is best handled by passing the node's UUID to retrieve its core details instantly, avoiding manual searches and streamlining your research workflow.

Do I need jq installed to read org-roam memory nodes by ID?

Yes, you need the jq dependency installed to read org-roam memory nodes by ID, as the underlying bash script relies on it to parse and emit the structured JSON output.

How does the system handle a missing org-roam node when fetching by UUID?

When handling a missing org-roam node during a UUID fetch, the system gracefully reports the error in the JSON response, ensuring your knowledge-management workflow does not break.

What data format is returned when reading a memory node from org-roam?

Reading a memory node from org-roam returns a structured JSON format that includes four specific fields: id, title, content, and file, providing the exact file path and full text.