Best use case
aura-openclaw is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using aura-openclaw should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/aura-openclaw/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How aura-openclaw Compares
| Feature / Agent | aura-openclaw | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Aura for OpenClaw
Persistent memory and instant knowledge retrieval for your OpenClaw agent. Compile 60+ file formats into queryable `.aura` archives and give your agent a 3-tier memory that survives sessions, compaction, and restarts.
## Setup
```bash
pip install auralith-aura
```
For full document support (PDFs, DOCX, etc.):
```bash
pip install 'aura-core[all]'
```
## What It Looks Like
### Learn an entire codebase
```
You: Learn my project in ~/repos/api-service
Agent: 🔥 Compiling ~/repos/api-service...
✅ Compiled 847 files → api-service.aura
Indexed: Python (312), TypeScript (201), YAML (44), Markdown (73), JSON (217)
You: How does the auth middleware handle token refresh?
Agent: Based on src/middleware/auth.ts (lines 45-89), the auth middleware
intercepts expired JWTs by checking the `exp` claim. When expired,
it calls `refreshTokenService.rotate()` which issues a new access
token and sets it via the `X-Refreshed-Token` response header.
The original request is then replayed with the new token.
```
### Compile legal docs with PII masking
```
You: Learn everything in ~/legal but mask any personal info
Agent: 🔥 Compiling with PII masking enabled...
✅ Compiled → legal.aura
Masked: 23 emails, 8 phone numbers, 4 SSNs
You: What are the termination conditions in the Series A agreement?
Agent: Per series_a_term_sheet.pdf, Section 7.2 — the agreement may be
terminated by either party with 30 days written notice if:
(a) material breach remains uncured after 15 business days,
(b) insolvency or bankruptcy filing, or
(c) failure to meet the minimum revenue threshold in Schedule B...
```
### Remember facts across sessions
```
You: Remember that our production database is on us-east-1, the staging
API key rotates every 30 days, and I prefer verbose error logs.
Agent: ✅ Written to /fact:
• Production DB region: us-east-1
• Staging API key rotation: 30-day cycle
• Preference: verbose error logging
--- next day, new session ---
You: Set up the deployment config for staging
Agent: I remember your staging API key rotates every 30 days — I'll add
a reminder comment in the config. Also setting error logging to
verbose per your preference. Targeting us-east-1 since that's
where your production DB lives...
```
### Track decisions across a long project
```
You: We decided to use PostgreSQL over MongoDB for the user service,
and the team agreed on GraphQL for the public API.
Agent: ✅ Written to /episodic:
• Architecture decision: PostgreSQL for user service (over MongoDB)
• API decision: GraphQL for public-facing API
--- two weeks later ---
You: Wait, should we use MongoDB for the new analytics service?
Agent: Based on your earlier decision log — you chose PostgreSQL over
MongoDB for the user service citing ACID compliance needs. The
analytics service has different requirements (write-heavy, schema
flexibility), so MongoDB could make sense here. Want me to draft
a comparison?
```
## Commands
### Compile a Knowledge Base
When the user asks you to "learn", "compile", "index", or "remember" files from a directory:
```bash
python {SKILL_DIR}/scripts/compile.py <input_directory> <output_file>
```
Options:
```bash
# Mask PII before compilation
python {SKILL_DIR}/scripts/compile.py ./data knowledge.aura --pii-mask
# Filter low-quality content
python {SKILL_DIR}/scripts/compile.py ./data knowledge.aura --min-quality 0.3
```
### Query the Knowledge Base
```bash
python {SKILL_DIR}/scripts/query.py knowledge.aura "search query here"
```
### Agent Memory
Write to memory tiers:
```bash
python {SKILL_DIR}/scripts/memory.py write pad "scratch note"
python {SKILL_DIR}/scripts/memory.py write fact "verified information"
python {SKILL_DIR}/scripts/memory.py write episodic "session event"
```
Search and manage memory:
```bash
python {SKILL_DIR}/scripts/memory.py query "search query"
python {SKILL_DIR}/scripts/memory.py list
python {SKILL_DIR}/scripts/memory.py usage
python {SKILL_DIR}/scripts/memory.py prune --before 2026-01-01
python {SKILL_DIR}/scripts/memory.py end-session
```
## Memory Tiers
| Tier | What It Stores | Lifecycle |
|------|---------------|-----------|
| **`/pad`** | Working notes, scratch space, in-progress thinking | Transient — cleared between sessions |
| **`/episodic`** | Session transcripts, decisions, conversation history | Auto-archived — retained for reference |
| **`/fact`** | Verified facts, user preferences, learned rules | Persistent — survives indefinitely |
## Supported File Types
Documents: PDF, DOCX, DOC, RTF, ODT, EPUB, TXT, HTML, PPTX, EML
Data: CSV, TSV, XLSX, XLS, Parquet, JSON, JSONL, YAML, TOML
Code: Python, JavaScript, TypeScript, Rust, Go, Java, C/C++, and 20+ more
Markup: Markdown (.md), reStructuredText, LaTeX
## External Endpoints
| URL | Data Sent |
|-----|-----------|
| None | None |
This skill makes **zero network requests**. All processing is local.
## Security & Privacy
- **No data leaves your machine.** All compilation and memory operations run locally.
- The `.aura` format uses `safetensors` (no pickle) — no arbitrary code execution risk.
- Memory files are stored locally at `~/.aura/memory/`.
- No environment variables or API keys are required.
- No telemetry, analytics, or usage reporting.
## Model Invocation Note
This skill is autonomously invoked by the agent as part of its normal operation. The agent decides when to compile documents and manage memory based on user requests. You can disable autonomous invocation in your OpenClaw settings.
## Trust Statement
By using this skill, **no data is sent to any external service**. All processing happens on your local machine. Only install this skill if you trust [Auralith Inc.](https://auralith.org) and have reviewed the source code at [GitHub](https://github.com/Auralith-Inc/aura-openclaw).
## Notes
- Memory uses a Two-Speed WAL: instant writes (~0.001s), background compilation to durable shards.
- For emphasis weighting and training features, see [OMNI Platform](https://omni.auralith.org).Related Skills
openclaw-tescmd
Installation and setup guide for Tesla vehicle control and telemetry via the tescmd node.
openclaw-starter-kit
Replace 100+ API keys with one. Instant access to LLMs, Twitter, YouTube, LinkedIn, Finance, Tavily & Scholar data. Enterprise stability for your local agent.
moltbot, openclaw-best-practices
Best practices for AI agents to avoid common mistakes. Learn from real failures - confirms before executing, shows drafts before publishing. Works with Claude, Cursor, GPT, Copilot.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
mcp-create-declarative-agent
Skill converted from mcp-create-declarative-agent.prompt.md
MCP Architecture Expert
Design and implement Model Context Protocol servers for standardized AI-to-data integration with resources, tools, prompts, and security best practices
mathem-shopping
Automatiserar att logga in på Mathem.se, söka och lägga till varor från en lista eller recept, hantera ersättningar enligt policy och reservera leveranstid, men lämnar varukorgen redo för manuell checkout.
math-modeling
本技能应在用户要求"数学建模"、"建模比赛"、"数模论文"、"数学建模竞赛"、"建模分析"、"建模求解"或提及数学建模相关任务时使用。适用于全国大学生数学建模竞赛(CUMCM)、美国大学生数学建模竞赛(MCM/ICM)等各类数学建模比赛。
matchms
Mass spectrometry analysis. Process mzML/MGF/MSP, spectral similarity (cosine, modified cosine), metadata harmonization, compound ID, for metabolomics and MS data processing.
managing-traefik
Manages Traefik reverse proxy for local development. Use when routing domains to local services, configuring CORS, checking service health, or debugging connectivity issues.
managing-skills
Install, find, update, and manage agent skills. Use when the user wants to add a new skill, search for skills that do something, check if skills are up to date, or update existing skills. Triggers on: install skill, add skill, get skill, find skill, search skill, update skill, check skills, list skills.
manage-agents
Create, modify, and manage Claude Code subagents with specialized expertise. Use when you need to "work with agents", "create an agent", "modify an agent", "set up a specialist", "I need an agent for [task]", or "agent to handle [domain]". Covers agent file format, YAML frontmatter, system prompts, tool restrictions, MCP integration, model selection, and testing.