Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
One-time setup wizard for the memmy upgrade skill. An agent skill from MemTensor/memmy-agent.
$ npx skills add MemTensor/memmy-agent --skill update-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MemTensor/memmy-agent update-setup --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/MemTensor/memmy-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/App/memmy-agent/src/skills/update-setup .claude/skills/update-setup && 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 "update-setup" agent skill from https://github.com/MemTensor/memmy-agent/tree/main/App/memmy-agent/src/skills/update-setup into .claude/skills/update-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-setup", 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/MemTensor/memmy-agent/tree/main/App/memmy-agent/src/skills/update-setupType 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 MemTensor/memmy-agent --skill update-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MemTensor/memmy-agent update-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MemTensor/memmy-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/App/memmy-agent/src/skills/update-setup .agents/skills/update-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-setup" agent skill from https://github.com/MemTensor/memmy-agent/tree/main/App/memmy-agent/src/skills/update-setup into .agents/skills/update-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-setup", 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 MemTensor/memmy-agent --skill update-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MemTensor/memmy-agent update-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MemTensor/memmy-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/App/memmy-agent/src/skills/update-setup .cursor/skills/update-setup && 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 "update-setup" agent skill from https://github.com/MemTensor/memmy-agent/tree/main/App/memmy-agent/src/skills/update-setup into .cursor/skills/update-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-setup", 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/MemTensor/memmy-agent.git --path App/memmy-agent/src/skills/update-setup--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 MemTensor/memmy-agent --skill update-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MemTensor/memmy-agent update-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MemTensor/memmy-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/App/memmy-agent/src/skills/update-setup .gemini/skills/update-setup && 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 "update-setup" agent skill from https://github.com/MemTensor/memmy-agent/tree/main/App/memmy-agent/src/skills/update-setup into .gemini/skills/update-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-setup", 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 MemTensor/memmy-agent update-setupInstalls 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 MemTensor/memmy-agent --skill update-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MemTensor/memmy-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/App/memmy-agent/src/skills/update-setup .github/skills/update-setup && 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 "update-setup" agent skill from https://github.com/MemTensor/memmy-agent/tree/main/App/memmy-agent/src/skills/update-setup into .github/skills/update-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-setup", 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 MemTensor/memmy-agent --skill update-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MemTensor/memmy-agent update-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MemTensor/memmy-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/App/memmy-agent/src/skills/update-setup .opencode/skills/update-setup && 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 "update-setup" agent skill from https://github.com/MemTensor/memmy-agent/tree/main/App/memmy-agent/src/skills/update-setup into .opencode/skills/update-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-setup", 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.
update-setupOne-time setup wizard for the memmy upgrade skill. An agent skill from MemTensor/memmy-agent.
Update Setup is an agent skill from MemTensor/memmy-agent. One-time setup wizard for the memmy upgrade skill. Triggers: setup update, configure update, 切设置更新, 初始化更新.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with OpenAI. The repository describes itself as: 🍙 A personal AI agent & local memory hub for all AI agents, gives every AI one shared, fully controlled memory and persistent context — all AI remember the same you. Now… The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit ee0ed02. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmnodepnpmyarngitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, pnpm, yarn and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Update Setup loads about 1.3k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 563 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.
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.
The full file from MemTensor/memmy-agent at commit ee0ed02, republished under its MIT licence (© MemTensor). 563 words, ~1,278 tokens.
.claude/skills/update-setup/SKILL.md (or your agent's skills folder).Generate a personalized upgrade skill for this workspace.
Use read_file to check if skills/update/SKILL.md already exists in the workspace.
If it exists, ask the user: "An upgrade skill already exists. Reconfigure?" Wait for the user's reply. If no, stop here.
Use exec to run memmy --version. Tell the user the current version.
Then collect install clues with exec. These commands are best-effort; if one fails,
keep going and show the useful output:
command -v memmy || true
npm list -g memmy-agent --depth=0 || true
pnpm list -g memmy-agent --depth=0 || true
yarn global list --pattern memmy-agent || trueSummarize what you found in one short paragraph. Use the clues only to suggest a likely install method. Do not treat them as confirmation.
CRITICAL: Do not write skills/update/SKILL.md until the install method is
explicitly confirmed by the user. The install method must come from a user
answer or confirmation, not from inference alone. If you cannot get a clear
answer, stop and ask the user to rerun this setup when they know how memmy was
installed.
Treat a request like "generate upgrade config", "set up updates", or "use
update-setup" as the goal, not as confirmation of the install method. Install
clues are only hints for the question summary; never choose npm, pnpm,
yarn, or source from clues alone. In the initial setup turn, write
skills/update/SKILL.md only if the user message already contains an explicit
install method and proxy answer. Otherwise, ask Question 1 and stop.
Hard stop rule: after collecting install clues without an explicit install
method from the user, do not call write_file for any path ending in
skills/update/SKILL.md in that same assistant turn. This remains true when
update-setup is part of a larger task that also creates other skills or runs
external installers. Finish the safe parts, ask Question 1, and wait for a later user
message before continuing.
Ask the user the questions below, one at a time, in your response text. Wait for the user's reply before proceeding to the next question. If you cannot get a clear answer, stop without writing the skill.
Question 1 — Install method:
question: "I found these install clues: <SUMMARY>. Which update method should this workspace use?"
options: ["npm", "pnpm", "yarn", "source (git clone)", "not sure"]If the user selected not sure, explain the difference between the options and
stop. Do not generate the upgrade skill.
If the user selected source (git clone), ask for the local checkout path:
question: "Where is your memmy source checkout? Enter an absolute path or a path relative to this workspace:".
Question 2 — Proxy:
question: "Do you need an HTTP proxy to reach the npm registry or GitHub?"
options: ["no", "yes"]If yes, ask one more time for the proxy URL: question: "Enter proxy URL (e.g. http://127.0.0.1:7890):".
Determine the upgrade command from the install method:
| Method | Command |
|---|---|
| npm | npm install -g memmy-agent@latest |
| pnpm | pnpm add -g memmy-agent@latest |
| yarn | yarn global add memmy-agent@latest |
| source | cd <SOURCE_CHECKOUT> && git pull && npm install && npm run build |
For source installs, quote the source checkout path if it contains spaces.
Determine the preflight check from the install method:
| Method | Preflight check |
|---|---|
| npm | command -v npm && node --version |
| pnpm | command -v pnpm && node --version |
| yarn | command -v yarn && node --version |
| source | test -d <SOURCE_CHECKOUT> && test -d <SOURCE_CHECKOUT>/.git && test -f <SOURCE_CHECKOUT>/package.json |
For source installs, quote the source checkout path in the preflight check if it contains spaces.
Build the skill content. If proxy is configured, add export http_proxy=URL and export https_proxy=URL lines before the upgrade command.
Use write_file to write skills/update/SKILL.md with this content:
---
name: update
description: "Upgrade memmy to the latest version. Triggers: upgrade memmy, update memmy, 升级memmy, 更新memmy."
---
# Update Memmy
1. (If proxy configured) Set proxy: `export http_proxy=URL && export https_proxy=URL`
2. Use `exec` to run the preflight check: <PREFLIGHT_CHECK>. If it fails, stop and tell the user to rerun `update-setup` because the saved install method no longer matches this environment.
3. Use `exec` to run the upgrade command: <UPGRADE_COMMAND>
4. Use `exec` to verify: `memmy --version`
5. Tell the user the new version. Say: "Run `/restart` to restart memmy and apply the update. If `/restart` is unavailable in this channel, restart the memmy process manually."Tell the user: "Upgrade skill created. Say 'upgrade memmy' when you want to update."
© MemTensor, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in App/memmy-agent/src/skills/update-setup of MemTensor/memmy-agent.
Open the folder on GitHubat commit ee0ed02
Update Setup 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Update Setup this skillMemTensor/memmy-agent | 2.1k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Geo Fundamentalswasp-lang/wasp | 19k | 8 repos | ~861 | Automated safety check: Pass | MIT | |
| AI SDKvercel-labs/ai-facts | 168 | 21 repos | ~1.2k | Automated safety check: Pass | None | |
| AI Image Generation and Editingzhayujie/CowAgent | 47k | — | ~1.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| SEO GeoReScienceLab/opc-skills | 1.8k | 4 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 |
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
vercel-labs/ai-facts
Answer questions about the AI SDK and help build AI-powered features.
zhayujie/CowAgent
Generates or edits images from text prompts through a Python script that picks an image backend based on which API keys are configured.
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
andrewyng/context-hub
Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.
MemTensor/memmy-agent
Create, read, edit, review, redline, comment on, merge, audit, render, and verify .docx Word documents, including layout-sensitive and OOXML-level work.
MemTensor/memmy-agent
Create, edit, improve, tidy, review, audit, or restructure memmy-agent skills and SKILL.md files.
MemTensor/memmy-agent
On-demand provisioning guide for a Memmy GUI task that fully connects an explicitly named local Agent: discover its active history store, install or remove its rendered Memmy Skill, bootstrap a scan…
MemTensor/memmy-agent
Create, inspect, edit, validate, render, and deliver PowerPoint presentations and templates while preserving OOXML structure and user metadata.
MemTensor/memmy-agent
Answer questions about what the user recently did on their computer — who contacted them, what they were working on, where they left off — by reading the local Computer History summaries and raw…
MemTensor/memmy-agent
Generate images and iteratively edit saved image artifacts. An agent skill from MemTensor/memmy-agent.
Works with
One-time setup wizard for the memmy upgrade skill. An agent skill from MemTensor/memmy-agent. Update Setup is an agent skill from MemTensor/memmy-agent. One-time setup wizard for the memmy upgrade skill.
Run `npx skills add MemTensor/memmy-agent --skill update-setup -a claude-code`. Or copy the skill folder (App/memmy-agent/src/skills/update-setup in MemTensor/memmy-agent) into .claude/skills/update-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add MemTensor/memmy-agent --skill update-setup -a codex`. Or copy the skill folder (App/memmy-agent/src/skills/update-setup in MemTensor/memmy-agent) into .agents/skills/update-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MemTensor/memmy-agent --skill update-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-setup, .gemini/skills/update-setup, .github/skills/update-setup and .opencode/skills/update-setup in your project.
Going by SKILL.md and its folder, Update Setup needs the command-line tools its instructions call (npm, node, pnpm, yarn and git). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Update Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Update Setup: Geo Fundamentals (wasp-lang/wasp, 19k stars), AI SDK (vercel-labs/ai-facts, 168 stars), AI Image Generation and Editing (zhayujie/CowAgent, 47k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
MemTensor (a GitHub organization) maintains it in MemTensor/memmy-agent, which has 2,064 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 30, 2026.
Source: MemTensor/memmy-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.