Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →memtensor/update-setup
One-time setup wizard for the memmy upgrade skill. Triggers: setup update, configure update, 切设置更新, 初始化更新.
3 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 4 comparable cases; this report requires 8.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
After successfully writing `skills/update/SKILL.md` for a confirmed setup, what message should be displayed to the user?
| Checked | Without skill | With skill |
|---|---|---|
| Informs the user that the upgrade skill has been created. | Missed | Passed |
| Mentions 'upgrade memmy' as the trigger phrase. | Missed | Passed |
The instructions your model reads when the skill loads.
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 || true
Summarize 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
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.