Cloud backup, restore, and local vector search for agent .md memory files.
Works with
Push/pull markdown memory files to ATXP cloud servers for disaster recovery and workspace bootstrapping; only .md files are transmitted, never credentials or configs
Index local memories into a zvec vector database and search by natural language query using locality-sensitive hashing embeddings, entirely offline with no authentication required
Chunk memories by heading boundaries and return ranked results with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionatxp-memoryExecute the skills CLI command in your project's root directory to begin installation:
Fetches atxp-memory from atxp-dev/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate atxp-memory. Access via /atxp-memory in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
4
total installs
4
this week
9
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
9
stars
Manage your agent's .md memory files: back up and restore to/from ATXP cloud servers, and search your local memories using zvec vector similarity search.
| Capability | Description |
|---|---|
| Cloud Backup | Push/pull .md files to ATXP servers for disaster recovery |
| Local Search | Index .md files into a local zvec vector database, then search by natural language query |
| Status | View cloud backup info and local index statistics |
.md files are collected and transmitted (push/pull). No credentials, JSON configs, binaries, or other file types are ever sent.push replaces the server snapshot entirely (latest snapshot only, no history).pull is non-destructive — it writes server files to the local directory but does not delete local files absent from the server..atxp-memory-index/ subdirectory inside --path. It never leaves the local machine.--path directory (push/index), writes to --path directory (pull) and --path/.atxp-memory-index/ (index). No other directories are touched.| Situation | Command |
|---|---|
| After meaningful changes to SOUL.md, MEMORY.md, or at end of session | push |
| Bootstrapping a fresh workspace or recovering from environment loss | pull |
| After updating memory files and before starting a task that requires recall | index |
| Looking for relevant context in past memories | search |
| Verify backup exists before risky operations | status |
| Command | Description |
|---|---|
npx atxp@latest memory push --path <dir> |
Recursively collect all *.md files from <dir> and upload to server |
npx atxp@latest memory pull --path <dir> |
Download backup from server and write files to <dir> |
npx atxp@latest memory index --path <dir> |
Chunk .md files by heading and build a local zvec search index |
npx atxp@latest memory search <query> --path <dir> |
Search indexed memories by similarity |
npx atxp@latest memory status [--path <dir>] |
Show cloud backup info and/or local index stats |
| Option | Required | Description |
|---|---|---|
--path <dir> |
Yes (push/pull/index/search) | Directory to operate on |
--topk <n> |
No (search only) | Number of results to return (default: 10) |
Indexing (memory index):
.md files recursively from --path<path>/.atxp-memory-index/Searching (memory search):
The search is purely local — no network requests, no API keys, no cost. Re-index after modifying memory files.
Typical OpenClaw workspace paths:
~/.openclaw/workspace-<id>/
~/.openclaw/workspace-<id>/SOUL.md
~/.openclaw/workspace-<id>/MEMORY.md
~/.openclaw/workspace-<id>/memory/
~/.openclaw/workspace-<id>/AGENTS.md
~/.openclaw/workspace-<id>/USER.md
The backup command is still accepted as an alias for memory:
npx atxp@latest backup push --path <dir> # works, same as memory push
npx atxp@latest backup pull --path <dir> # works, same as memory pull
npx atxp@latest backup status # works, same as memory status
.md files only — all other file types are ignored during push/index and not present in pull.npx atxp@latest login or npx atxp@latest agent register first.--path is required — there is no auto-detection of workspace location.npm install @zvec/zvec before using index/search.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
We added atxp-memory from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
atxp-memory reduced setup friction for our internal harness; good balance of opinion and flexibility.
atxp-memory fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in atxp-memory — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added atxp-memory from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in atxp-memory — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
atxp-memory has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: atxp-memory is focused, and the summary matches what you get after install.
atxp-memory fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for atxp-memory matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 62