Align
ambient-code/platform
Run a convention alignment check across the codebase to measure adherence to documented standards.
Manage the auto-memory system for this project. An agent skill from ambient-code/platform.
MITAuto-check passed
Install Memory
$ npx skills add ambient-code/platform --skill memory -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ambient-code/platform memory --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ambient-code/platform.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/memory .claude/skills/memory && rm -rf skills-srcUse ~/.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/
Install the "memory" agent skill from https://github.com/ambient-code/platform/tree/main/skills/memory into .claude/skills/memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ambient-code/platform/tree/main/skills/memoryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ambient-code/platform --skill memory -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ambient-code/platform memory --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ambient-code/platform.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/memory .agents/skills/memory && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memory" agent skill from https://github.com/ambient-code/platform/tree/main/skills/memory into .agents/skills/memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ambient-code/platform --skill memory -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ambient-code/platform memory --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ambient-code/platform.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/memory .cursor/skills/memory && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "memory" agent skill from https://github.com/ambient-code/platform/tree/main/skills/memory into .cursor/skills/memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ambient-code/platform.git --path skills/memory--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ambient-code/platform --skill memory -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ambient-code/platform memory --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ambient-code/platform.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/memory .gemini/skills/memory && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "memory" agent skill from https://github.com/ambient-code/platform/tree/main/skills/memory into .gemini/skills/memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ambient-code/platform memoryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ambient-code/platform --skill memory -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ambient-code/platform.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/memory .github/skills/memory && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "memory" agent skill from https://github.com/ambient-code/platform/tree/main/skills/memory into .github/skills/memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ambient-code/platform --skill memory -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ambient-code/platform memory --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ambient-code/platform.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/memory .opencode/skills/memory && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "memory" agent skill from https://github.com/ambient-code/platform/tree/main/skills/memory into .opencode/skills/memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memory", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
memory- GitHub stars
- 131
- Token cost
- ~1k tokens
- SKILL.md length
- 409 words
- Files
- 2
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Manage the auto-memory system for this project. An agent skill from ambient-code/platform.
- Works in 4 steps: Read MEMORY.md to get the index → Count total memories by type (user,… → List the most recently modified files → …
- You need to find a past decision
- SKILL.md covers Usage, User Input, Memory Location and Subcommands, plus 3 more sections
- Calls git
What it does
Memory is an agent skill from ambient-code/platform. Manage the auto-memory system for this project. Search, audit, prune, and create memories with proper frontmatter. Use when you need to find a past decision, check if memories are stale, clean up duplicates, add a new memory, or understand what context is available. Triggers on: "check memory", "what do we remember about", "find the memory about", "clean up memories", "audit memories", "add to memory", "is there a memory for".
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).
The repository describes itself as: Vision/Mission https://ambient-code.ai : Virtual team management and collaboration platform. User guides: https://ambient-code.github.io/platform/. The licence is MIT.
When your agent uses it
- You need to find a past decision
- Check if memories are stale
- Clean up duplicates
- Add a new memory
Example prompts
- “check memory”
- “what do we remember about”
- “find the memory about”
- “/memory”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read MEMORY.md to get the index
- Count total memories by type (user, feedback, project, reference)
- List the most recently modified files
- Report: total count, breakdown by type, last modified dates
What it can do on your machine
Read from SKILL.md and the folder at commit e15afd3. 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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Memory loads about 1k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 409 words of instructions outside code blocks.
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 ambient-code/platform at commit e15afd3, republished under its MIT licence (© ambient-code). 409 words, ~1,015 tokens.
Download SKILL.mdSave it as
.claude/skills/memory/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- memory
- description
- Manage the auto-memory system for this project. Search, audit, prune, and create memories with proper frontmatter. Use when you need to find a past decision, check if memories are stale, clean up duplicates, add a new memory, or understand what context is available. Triggers on: "check memory", "what do we remember about", "find the memory about", "clean up memories", "audit memories", "add to memory", "is there a memory for".
Memory Management
Manage the auto-memory system for the Ambient Code Platform project.
Usage
/memory # Show summary of all memories
/memory search <query> # Search for a topic
/memory audit # Check for stale/duplicate memories
/memory prune # Remove stale memories (with confirmation)
/memory add <topic> # Create a new memoryUser Input
$ARGUMENTSParse the subcommand from $ARGUMENTS. Default to summary if empty.
Memory Location
All memory files live at:
$HOME/.claude/projects/<project-slug>/memory/Use the active project's slug (the repo path with / replaced by -).
The index file is MEMORY.md in that directory.
Subcommands
/memory — Summary
- Read
MEMORY.mdto get the index - Count total memories by type (user, feedback, project, reference)
- List the most recently modified files
- Report: total count, breakdown by type, last modified dates
/memory search <query>
- Read
MEMORY.mdfor the index - Grep through all memory files for the query term
- Read matching files and show relevant excerpts
- Report: matching files with frontmatter (name, type, description)
/memory audit
Check for quality issues:
- Stale memories — project/reference memories older than 3 months may be outdated
- Duplicate memories — similar names or descriptions across files
- Missing frontmatter — files without proper
name,description,typefields - Orphaned files — memory files not referenced in
MEMORY.md - Broken links —
MEMORY.mdentries pointing to nonexistent files - Oversized index —
MEMORY.mdapproaching the 200-line truncation limit
Report each issue with the file path and suggested action.
/memory prune
- Run the audit checks
- Present findings to the user
- For each stale/duplicate/orphaned memory, ask: keep, update, or delete?
- Execute confirmed deletions
- Update
MEMORY.mdindex accordingly
Never delete without explicit confirmation.
Show full SKILL.md (174 more words)Show less
/memory add <topic>
- Ask the user what they want to remember (if not clear from context)
- Determine the memory type (user, feedback, project, reference)
- Create a new file with proper frontmatter:
---
name: <descriptive name>
description: <one-line description for relevance matching>
type: <user|feedback|project|reference>
---
<memory content>- Add an entry to
MEMORY.md - Verify the entry was added correctly
Memory Types
| Type | What to store | When to save |
|---|---|---|
| user | Role, preferences, knowledge | Learning about the user |
| feedback | Corrections, validated approaches | User corrects or confirms approach |
| project | Decisions, initiatives, deadlines | Learning project context |
| reference | Pointers to external systems | Discovering external resources |
What NOT to Store
- Code patterns derivable from reading current code
- Git history (use
git log) - Debugging solutions (the fix is in the code)
- Anything in CLAUDE.md
- Ephemeral task details
- Secrets or credentials (API keys, tokens, passwords, private keys, OAuth secrets)
- Sensitive personal data unless explicitly required
Quality Guidelines
- Keep
MEMORY.mdunder 200 lines (truncation risk) - Each entry: one line, under 150 characters
- Update existing memories rather than creating duplicates
- Include absolute dates (not "next Thursday")
- For feedback/project types: include Why: and How to apply: lines
© ambient-code, 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 1 other file in skills/memory of ambient-code/platform.
- SKILL.md
- evals/evals.json
Open the folder on GitHubat commit e15afd3
More from ambient-code/platform
All 18 skills in this repoAmber Review
ambient-code/platform
Perform a comprehensive code review using repository-specific standards.
Cypress Demo
ambient-code/platform
Create a Cypress-based video demo for a feature branch with cursor, click effects, and captions.
Deploy
ambient-code/platform
Deploy, update manifests, and troubleshoot the ambient-ui component.
Discover
ambient-code/platform
Discover domain-specific skills and context before starting any coding or spec work.
Frontend Development
ambient-code/platform
Required context for all frontend work. An agent skill from ambient-code/platform.
Questions about Memory
What does Memory do?
Manage the auto-memory system for this project. An agent skill from ambient-code/platform. Memory is an agent skill from ambient-code/platform. Manage the auto-memory system for this project.
When should I use Memory?
Memory fits situations like: you need to find a past decision; check if memories are stale; clean up duplicates; add a new memory.
How do I install Memory in Claude Code?
Run `npx skills add ambient-code/platform --skill memory -a claude-code`. Or copy the skill folder (skills/memory in ambient-code/platform) into .claude/skills/memory in your project. Claude Code loads it when a task matches its description.
How do I install Memory in Codex?
Run `npx skills add ambient-code/platform --skill memory -a codex`. Or copy the skill folder (skills/memory in ambient-code/platform) into .agents/skills/memory in your project. Codex loads it when a task matches its description.
Can I use Memory 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 ambient-code/platform --skill memory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memory, .gemini/skills/memory, .github/skills/memory and .opencode/skills/memory in your project.
What does Memory need to run?
Going by SKILL.md and its folder, Memory needs the command-line tools its instructions call (git).
Does Memory access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Memory 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 Memory use?
Memory 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 Memory use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Who maintains Memory?
ambient-code (a GitHub organization) maintains it in ambient-code/platform, which has 131 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 6, 2026.
Source: ambient-code/platform on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.