Alexandrie

What This Skill Does

The Alexandrie skill serves as an interface between the OpenClaw AI agent and the Alexandrie note-taking application. It enables seamless integration with a private knowledge base, allowing users to programmatically manage notes, documents, and category structures hosted at notes.eth3rnit3.org. By leveraging this skill, the AI can perform CRUD operations on your digital workspace, effectively transforming your note-taking app into an interactive, AI-driven second brain. It automates the retrieval, categorization, and creation of documentation, ensuring your research and personal notes remain organized and accessible through natural language commands.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/eth3rnit3/alexandrie Ensure you have configured your environmental variables correctly in /home/eth3rnit3/clawd/.env by setting the ALEXANDRIE_PASSWORD variable, as the skill relies on this for local authentication management.

Use Cases

This skill is perfect for users who want to bridge the gap between their AI assistant and their personal documentation. You can use it to archive important AI-generated research, draft project documentation, or maintain a running log of tasks across multiple workspaces. For instance, an developer might use it to log snippets of code as they work, while a researcher might use it to query existing notes to synthesize information from previous sessions.

Example Prompts

1. "Alexandrie, list all the notes in my Perso workspace so I can see what I have been working on lately."
2. "Create a new note titled 'Project Plan' inside the Test category with the content 'Implement authentication module using JWT.'"
3. "Search my notes for 'test' and summarize the content of the document you find."

Tips & Limitations

When using Alexandrie, note that the skill uses a local cookie file /tmp/alexandrie_cookies.txt to maintain your session. Always ensure that the user IDs provided match your specific account structure, as identified in the configuration. The system differentiates between roles: role 1 for containers/workspaces and role 3 for content-based documents. Be mindful when using the delete command, as it is permanent and cannot be undone through the CLI directly. Always verify the nodeId before executing destructive actions to prevent accidental data loss.