Agent skill

Neolata Mem

by LeoYeAI in LeoYeAI/openclaw-master-skills

Graph-native memory engine for AI agents — hybrid vector+keyword search, biological decay, Zettelkasten linking, trust-gated conflict resolution, explainability, episodes, compression & consolidation.

MITAuto-check passedKnowledge Management

Install Neolata Mem

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill neolata-mem -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills neolata-mem --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/neolata-mem .claude/skills/neolata-mem && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
neolata-mem
GitHub stars
2.2k
Token cost
~4.1k tokens
SKILL.md length
1,026 words
Files
5 (incl. references)
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Graph-native memory engine for AI agents — hybrid vector+keyword search, biological decay, Zettelkasten linking, trust-gated conflict resolution, explainability, episodes, compression & consolidation.

  • Tasks that involve Note-taking
  • SKILL.md covers When to Use This Skill, Install, Security & Data Flow and Quick Start (Zero Config), plus 7 more sections
  • Calls npx and npm; needs OPENAI_API_KEY and OPENCLAW_GATEWAY_TOKEN

What it does

Neolata Mem is an agent skill from LeoYeAI/openclaw-master-skills. Graph-native memory engine for AI agents — hybrid vector+keyword search, biological decay, Zettelkasten linking, trust-gated conflict resolution, explainability, episodes, compression & consolidation. Zero dependencies. npm install and go.

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `_meta.json`, `references/guide.md` and `references/implementation-notes.md`).

It sits in Knowledge Management, covering Note-taking. It works with npm and Ollama. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Tasks that involve Note-taking

Example prompts

  • “/neolata-mem”

Requirements

  • Node.js
  • Docker
  • A credential in OPENAI_API_KEY
  • A credential in OPENCLAW_GATEWAY_TOKEN

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • npmjs.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENAI_API_KEY
    • OPENCLAW_GATEWAY_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Neolata Mem loads about 4.1k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 1,026 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~21k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,026 words, ~4,135 tokens.

Download SKILL.mdSave it as .claude/skills/neolata-mem/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
neolata-mem
description
Graph-native memory engine for AI agents — hybrid vector+keyword search, biological decay, Zettelkasten linking, trust-gated conflict resolution, explainability, episodes, compression & consolidation. Zero dependencies. npm install and go.
version
0.8.4

neolata-mem — Agent Memory Engine

Graph-native memory for AI agents with hybrid search, biological decay, and zero infrastructure.

npm package: @jeremiaheth/neolata-mem Repository: github.com/Jeremiaheth/neolata-mem License: Elastic-2.0 | Tests: 367/367 passing (34 files) | Node: ≥18

When to Use This Skill

Use neolata-mem when you need:

  • Persistent memory across sessions that survives context compaction
  • Semantic search over stored facts, decisions, and findings
  • Memory decay so stale information naturally fades
  • Multi-agent memory with cross-agent search and graph linking
  • Conflict resolution — detect and evolve contradictory memories

Do NOT use if:

  • You only need OpenClaw's built-in memorySearch (keyword + vector on workspace files)
  • You want cloud-hosted memory (use Mem0 instead)
  • You need a full knowledge graph database (use Graphiti + Neo4j)

Install

bash
npm install @jeremiaheth/neolata-mem

No Docker. No Python. No Neo4j. No cloud API required.

Supply-chain verification: This package has zero runtime dependencies and no install scripts. Verify before installing:

bash
# Check for install scripts (should show only "test"):
npm view @jeremiaheth/neolata-mem scripts
# Check for runtime deps (should be empty):
npm view @jeremiaheth/neolata-mem dependencies
# Audit the tarball contents (15 files, ~40 kB):
npm pack @jeremiaheth/neolata-mem --dry-run

Source is fully auditable at github.com/Jeremiaheth/neolata-mem.

Security & Data Flow

Default configuration is fully local — JSON files on disk, no network calls, no embeddings, no external services.

Data only leaves the host if you explicitly configure one of these:

FeatureWhat leavesWhere it goesHow to avoid
Embeddings (OpenAI/NVIDIA/Azure)Memory textEmbedding API endpointUse noop embeddings or Ollama (local)
LLM (OpenAI/OpenClaw/Ollama)Memory text for extraction/compressionLLM API endpointDon't configure llm option, or use Ollama
Supabase storageAll memory dataYour Supabase projectUse json or memory storage (default)
Webhook writethroughStore/decay event payloadsYour webhook URLDon't configure webhookWritethrough

Key security properties:

  • Only 2 env vars are read directly by code: OPENAI_API_KEY and OPENCLAW_GATEWAY_TOKEN. All others (Supabase, NVIDIA, Azure) are passed via explicit config objects.
  • All provider URLs are validated against SSRF (private IPs blocked, cloud metadata blocked).
  • Supabase: prefer anon key + RLS over service key. Service key bypasses row-level security.
  • JSON storage uses atomic writes (temp file + rename) to prevent corruption.
  • All user content sent to LLMs is XML-fenced with injection guards.
  • Test safely with storage: { type: 'memory' } — nothing touches disk or network.

See docs/guide.md § Security for the full security model.

Quick Start (Zero Config)

javascript
import { createMemory } from '@jeremiaheth/neolata-mem';

const mem = createMemory();
await mem.store('agent-1', 'User prefers dark mode');
const results = await mem.search('agent-1', 'UI preferences');

Works immediately with local JSON storage and keyword search. No API keys needed.

javascript
const mem = createMemory({
  embeddings: {
    type: 'openai',
    apiKey: process.env.OPENAI_API_KEY,
    model: 'text-embedding-3-small',
  },
});

// Agent IDs like 'kuro' and 'maki' are just examples — use any string.
await mem.store('kuro', 'Found XSS in login form', { category: 'finding', importance: 0.9 });
const results = await mem.search('kuro', 'security vulnerabilities');

Supports 5+ embedding providers: OpenAI, NVIDIA NIM, Ollama, Azure, Together, or any OpenAI-compatible endpoint.

Key Features

Hybrid Search (Vector + Keyword Fallback)

Uses semantic similarity when embeddings are configured; falls back to tokenized keyword matching when they're not:

javascript
// With embeddings → vector cosine similarity search
// Without embeddings → normalized keyword matching (stop word removal, lowercase, dedup)
const results = await mem.search('agent', 'security vulnerabilities');

Keyword search uses an inverted token index for O(1) lookups. When >500 memories exist, vector search pre-filters candidates using token overlap before cosine similarity (candidate narrowing).

Biological Decay

Memories fade over time unless reinforced. Old, unaccessed memories naturally lose relevance:

javascript
await mem.decay();        // Run maintenance — archive/delete stale memories
await mem.reinforce(id);  // Boost a memory to resist decay
Memory Graph (Zettelkasten Linking)

Every memory is automatically linked to related memories by semantic similarity:

javascript
const links = await mem.links(memoryId);     // Direct connections
const path = await mem.path(idA, idB);       // Shortest path between memories
const clusters = await mem.clusters();        // Detect topic clusters
Conflict Resolution & Quarantine

Detect contradictions before storing — with claim-based structural detection or LLM-based semantic detection:

javascript
// Structural (no LLM needed): claim-based conflict detection
await mem.store('agent', 'Server uses port 443', {
  claim: { subject: 'server', predicate: 'port', value: '443' },
  provenance: { source: 'user_explicit', trust: 1.0 },
  onConflict: 'quarantine',  // low-trust conflicts quarantined for review
});

// Semantic (requires LLM): LLM classifies as conflict/update/novel
await mem.evolve('agent', 'Server now uses port 8080');

// Review quarantined memories
const quarantined = await mem.listQuarantined();
await mem.reviewQuarantine(quarantined[0].id, { action: 'activate' });
Predicate Schema Registry

Define per-predicate rules for conflict handling, normalization, and deduplication:

javascript
const mem = createMemory({
  predicateSchemas: {
    'preferred_language': { cardinality: 'single', conflictPolicy: 'supersede', normalize: 'lowercase_trim' },
    'spoken_languages':   { cardinality: 'multi', dedupPolicy: 'corroborate' },
    'salary':             { cardinality: 'single', conflictPolicy: 'require_review', normalize: 'currency' },
  },
});

Options: cardinality (single/multi), conflictPolicy (supersede/require_review/keep_both), normalize (none/trim/lowercase/lowercase_trim/currency), dedupPolicy (corroborate/store).

Explainability API

Understand why search returned or filtered specific memories:

javascript
const results = await mem.search('agent', 'query', { explain: true });
console.log(results.meta);        // query options, result count
console.log(results[0].explain);  // retrieved, rerank, statusFilter details

const detail = await mem.explainMemory(memoryId);
// { id, status, trust, confidence, provenance, claimSummary }
Multi-Agent Support
javascript
await mem.store('kuro', 'Vuln found in API gateway');
await mem.store('maki', 'API gateway deployed to prod');
const all = await mem.searchAll('API gateway');  // Cross-agent search
Episodes (Temporal Grouping)

Group related memories into named episodes:

javascript
const ep = await mem.createEpisode('Deploy v2.0', [id1, id2, id3], { tags: ['deploy'] });
const ep2 = await mem.captureEpisode('kuro', 'Standup', { start: '...', end: '...' });
const results = await mem.searchEpisode(ep.id, 'database migration');
const { summary } = await mem.summarizeEpisode(ep.id);  // requires LLM
Memory Compression & Consolidation

Consolidate redundant memories into digests:

javascript
await mem.compress([id1, id2, id3], { method: 'llm', archiveOriginals: true });
await mem.compressEpisode(episodeId);
await mem.autoCompress({ minClusterSize: 3, maxDigests: 5 });

// Full maintenance: dedup → contradictions → corroborate → compress → prune
await mem.consolidate({ dedupThreshold: 0.95, compressAge: 30, pruneAge: 90 });
Labeled Clusters

Persistent named groups:

javascript
await mem.createCluster('Security findings', [id1, id2]);
await mem.autoLabelClusters();  // LLM labels unlabeled clusters
Event Emitter

Hook into the memory lifecycle:

javascript
mem.on('store', ({ agent, content, id }) => { /* ... */ });
mem.on('search', ({ agent, query, results }) => { /* ... */ });
mem.on('decay', ({ archived, deleted, dryRun }) => { /* counts, not arrays */ });
Batch APIs

Amortize embedding calls and I/O with bulk operations:

javascript
// Store many memories in one call (single embed batch + single persist)
const result = await mem.storeMany('agent', [
  { text: 'Fact one', category: 'fact', importance: 0.8 },
  { text: 'Fact two', tags: ['infra'] },
  'Plain string also works',
]);
// { total: 3, stored: 3, results: [{ id, links }, ...] }

// Search multiple queries in one call (single embed batch)
const results = await mem.searchMany('agent', ['query one', 'query two']);
// [{ query: 'query one', results: [...] }, { query: 'query two', results: [...] }]

Batch operations include:

  • Atomic rollback on persist failure (memories, indexes, backlinks all reverted)
  • Cross-linking within the same batch
  • Configurable caps: maxBatchSize (default 1000), maxQueryBatchSize (default 100)
Bulk Ingestion with Fact Extraction

Extract atomic facts from text using an LLM, then store each with A-MEM linking:

javascript
const mem = createMemory({
  embeddings: { type: 'openai', apiKey: process.env.OPENAI_API_KEY },
  extraction: { type: 'llm', apiKey: process.env.OPENAI_API_KEY },
});

const result = await mem.ingest('agent', longText);
// { total: 12, stored: 10, results: [...] }

CLI

bash
npx neolata-mem store myagent "Important fact here"
npx neolata-mem search myagent "query"
npx neolata-mem decay --dry-run
npx neolata-mem health
npx neolata-mem clusters
Show full SKILL.md (414 more words)Show less

OpenClaw Integration

neolata-mem complements OpenClaw's built-in memorySearch:

  • memorySearch = searches your workspace .md files (BM25 + vector)
  • neolata-mem = structured memory store with graph, decay, evolution, multi-agent

Use both together: memorySearch for workspace file recall, neolata-mem for agent-managed knowledge.

In your agent's daily cron or heartbeat:

javascript
// Store important facts from today's session
await mem.store(agentId, 'Key decision: migrated to Postgres', {
  category: 'decision',
  importance: 0.8,
  tags: ['infrastructure'],
});

// Run decay maintenance
await mem.decay();

Comparison

Featureneolata-memMem0OpenClaw memorySearch
Local-first (data stays on machine)✅ (default)❌✅
Hybrid search (vector + keyword)✅❌✅
Memory decay✅❌❌
Memory graph / linking✅❌❌
Conflict resolution✅Partial❌
Quarantine lane✅❌❌
Predicate schemas✅❌❌
Explainability API✅❌❌
Episodes & compression✅❌❌
Labeled clusters✅❌❌
Multi-agent✅✅Per-agent
Zero infrastructure✅❌✅
Event emitter✅❌❌
Batch APIs (storeMany/searchMany)✅❌❌
npm package✅✅Built-in

Security

neolata-mem includes hardening against common agent memory attack vectors:

  • Prompt injection mitigation: XML-fenced user content in all LLM prompts + structural output validation
  • Input validation: Agent names (alphanumeric, max 64), text length caps (10KB), bounded memory count (50K), batch size caps (1000 store / 100 query)
  • Batch atomicity: storeMany rolls back all memories, indexes, and backlinks on persist failure
  • SSRF protection: All provider URLs validated via validateBaseUrl() — blocks cloud metadata endpoints (169.254.169.254), private IP ranges, non-HTTP protocols
  • Supabase hardening: UUID validation on query params, error text sanitized (strips tokens/keys), upsert-based save (crash-safe), 429 retry with backoff
  • Atomic writes: Write-to-temp + rename prevents file corruption
  • Path traversal guards: Storage directories and write-through paths validated with resolve() + prefix checks
  • Cryptographic IDs: crypto.randomUUID() — no predictable memory references
  • Retry bounds: Exponential backoff with max 3 retries on 429s
  • Error surfacing: Failed conflict detection returns { error } instead of silent fallthrough

Supabase key guidance: Prefer the anon key with Row Level Security (RLS) policies over the service role key. The service key bypasses RLS and grants full access to all stored memories. Only use it for admin/migration tasks.

See the full security section for details.

Data Residency & External API Usage

Local-only mode (default): Memories are stored as JSON at ./neolata-mem-data/graph.json (relative to CWD). No data leaves your machine. Keyword search works without any API keys.

With embeddings/extraction/LLM: When you configure an external provider (OpenAI, NIM, Ollama, etc.), your memory text is sent to that provider's API for embedding or extraction. This is opt-in — you must explicitly provide an API key and base URL.

ModeData sent externally?Storage location
Default (no config)❌ No./neolata-mem-data/graph.json
Ollama embeddings❌ No (local)./neolata-mem-data/graph.json
OpenAI/NIM embeddings⚠️ Memory text → provider./neolata-mem-data/graph.json
Supabase storage⚠️ All data → SupabaseSupabase PostgreSQL
LLM conflict resolution⚠️ Memory text → providerStorage unchanged

To keep all data local: Use Ollama for embeddings and JSON storage. No API keys needed for keyword-only search.

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/neolata-mem of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json
  • references/guide.md
  • references/implementation-notes.md
  • references/runtime-helpers.md

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Neolata Mem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Neolata Mem compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Neolata Mem this skillLeoYeAI/openclaw-master-skills2.2k—~4.1kAutomated safety check: PassMIT
Openclone CLIteam-attention/openclone130—~712Automated safety check: PassCustom licence
Dev BumpNetis/heron102—~983Automated safety check: PassApache-2.0
Page AgentTommy-yw/RunbookHermes5463 repos~2.3kAutomated safety check: NotesMIT
Knap Markdown Templateskepano/obsidian-skills49k2 repos~986Automated safety check: PassMIT
Check Deps SyncHyk260/PureChat546—~594Automated safety check: PassMIT

Similar skills

  • Openclone CLI

    team-attention/openclone

    A skill your agent uses when the user wants to consult an AI persona "clone" for advice, strategy, analysis, or domain expertise—especially in startup, VC, tech, growth, HR, or business contexts.

    130 GitHub stars~712 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Dev Bump

    Netis/heron

    Bump Heron version via the VERSION-file SSOT. An agent skill from Netis/heron.

    102 GitHub stars~983 tokensUpdated 6 days ago
    AI & LLM EngineeringAuto-check passed
  • Page Agent

    Tommy-yw/RunbookHermes

    Embed alibaba/page-agent into your own web application — a pure-JavaScript in-page GUI agent that ships as a single <script tag or npm package and lets end-users of your site drive the UI with…

    546 GitHub starsUsed in 3 repos~2.3k tokens
    Productivity & AutomationAuto-check: notes
  • Knap Markdown Templates

    kepano/obsidian-skills

    Renders Markdown notes from Knap templates and JSON data on the command line, including notes built from Defuddle web page output.

    49k GitHub starsUsed in 2 repos~986 tokens
    Documents & OfficeAuto-check passed
  • Check Deps Sync

    Hyk260/PureChat

    Check if package.json files are in sync with pnpm-lock.yaml.

    546 GitHub stars~594 tokensUpdated 24 days ago
    DevOps & CloudAuto-check passed
  • Cortexdb Memory Openclaw

    liliang-cn/cortexdb

    Give a Node.js agent (such as OpenClaw) durable, local-first memory plus a queryable SPARQL knowledge graph, backed by CortexDB through its gRPC sidecar and the cortexdb-client npm package.

    274 GitHub stars~1.6k tokensUpdated 3 days ago
    Knowledge ManagementAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,200 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about Neolata Mem

What does Neolata Mem do?

Graph-native memory engine for AI agents — hybrid vector+keyword search, biological decay, Zettelkasten linking, trust-gated conflict resolution, explainability, episodes, compression & consolidation. Neolata Mem is an agent skill from LeoYeAI/openclaw-master-skills. Graph-native memory engine for AI agents — hybrid vector+keyword search, biological decay, Zettelkasten linking, trust-gated conflict resolution, explainability, episodes, compression & consolidation.

When should I use Neolata Mem?

Neolata Mem fits situations like: tasks that involve Note-taking.

How do I install Neolata Mem in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill neolata-mem -a claude-code`. Or copy the skill folder (skills/neolata-mem in LeoYeAI/openclaw-master-skills) into .claude/skills/neolata-mem in your project. Claude Code loads it when a task matches its description.

How do I install Neolata Mem in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill neolata-mem -a codex`. Or copy the skill folder (skills/neolata-mem in LeoYeAI/openclaw-master-skills) into .agents/skills/neolata-mem in your project. Codex loads it when a task matches its description.

Can I use Neolata Mem in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill neolata-mem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/neolata-mem, .gemini/skills/neolata-mem, .github/skills/neolata-mem and .opencode/skills/neolata-mem in your project.

What does Neolata Mem need to run?

Going by SKILL.md and its folder, Neolata Mem needs the command-line tools its instructions call (npx and npm) and credentials named OPENAI_API_KEY and OPENCLAW_GATEWAY_TOKEN. Our summary lists: Node.js; Docker; A credential in OPENAI_API_KEY; A credential in OPENCLAW_GATEWAY_TOKEN.

Does Neolata Mem access the network?

SKILL.md names 2 domains. As links in the text: github.com and npmjs.com. This is read from the text; nothing was executed.

Is Neolata Mem safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Neolata Mem use?

Neolata Mem is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Neolata Mem use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.

What are the alternatives to Neolata Mem?

Skills that share tags, products or a category with Neolata Mem: Openclone CLI (team-attention/openclone, 130 stars), Dev Bump (Netis/heron, 102 stars), Page Agent (Tommy-yw/RunbookHermes, 546 stars) and Knap Markdown Templates (kepano/obsidian-skills, 49k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Neolata Mem?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.