Agent Recall
Goldentrii/AgentRecall-X
Persistent compounding memory for AI agents. An agent skill from Goldentrii/AgentRecall-X.
Lay out a Vue app on the local Supabase stack, served as static files by wrangler, with tests that run against the local stack.
$ npx skills add receptron/mulmoterminal --skill blueprint-supabase-scaffold -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install receptron/mulmoterminal blueprint-supabase-scaffold --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/receptron/mulmoterminal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/blueprints/supabase/skills/scaffold .claude/skills/blueprint-supabase-scaffold && 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 "blueprint-supabase-scaffold" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/supabase/skills/scaffold into .claude/skills/blueprint-supabase-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-supabase-scaffold", 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/receptron/mulmoterminal/tree/main/blueprints/supabase/skills/scaffoldType 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 receptron/mulmoterminal --skill blueprint-supabase-scaffold -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install receptron/mulmoterminal blueprint-supabase-scaffold --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .agents/skills && cp -r skills-src/blueprints/supabase/skills/scaffold .agents/skills/blueprint-supabase-scaffold && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blueprint-supabase-scaffold" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/supabase/skills/scaffold into .agents/skills/blueprint-supabase-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-supabase-scaffold", 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 receptron/mulmoterminal --skill blueprint-supabase-scaffold -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install receptron/mulmoterminal blueprint-supabase-scaffold --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/blueprints/supabase/skills/scaffold .cursor/skills/blueprint-supabase-scaffold && 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 "blueprint-supabase-scaffold" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/supabase/skills/scaffold into .cursor/skills/blueprint-supabase-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-supabase-scaffold", 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/receptron/mulmoterminal.git --path blueprints/supabase/skills/scaffold--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 receptron/mulmoterminal --skill blueprint-supabase-scaffold -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install receptron/mulmoterminal blueprint-supabase-scaffold --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/blueprints/supabase/skills/scaffold .gemini/skills/blueprint-supabase-scaffold && 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 "blueprint-supabase-scaffold" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/supabase/skills/scaffold into .gemini/skills/blueprint-supabase-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-supabase-scaffold", 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 receptron/mulmoterminal blueprint-supabase-scaffoldInstalls 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 receptron/mulmoterminal --skill blueprint-supabase-scaffold -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .github/skills && cp -r skills-src/blueprints/supabase/skills/scaffold .github/skills/blueprint-supabase-scaffold && 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 "blueprint-supabase-scaffold" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/supabase/skills/scaffold into .github/skills/blueprint-supabase-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-supabase-scaffold", 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 receptron/mulmoterminal --skill blueprint-supabase-scaffold -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install receptron/mulmoterminal blueprint-supabase-scaffold --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/receptron/mulmoterminal.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/blueprints/supabase/skills/scaffold .opencode/skills/blueprint-supabase-scaffold && 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 "blueprint-supabase-scaffold" agent skill from https://github.com/receptron/mulmoterminal/tree/main/blueprints/supabase/skills/scaffold into .opencode/skills/blueprint-supabase-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blueprint-supabase-scaffold", 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.
blueprint-supabase-scaffoldLay out a Vue app on the local Supabase stack, served as static files by wrangler, with tests that run against the local stack.
Blueprint Supabase Scaffold is an agent skill from receptron/mulmoterminal. Lay out a Vue app on the local Supabase stack, served as static files by wrangler, with tests that run against the local stack.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. It works with Supabase, Cloudflare Workers, Vue.js and TypeScript. The repository describes itself as: Run multiple Claude Code and Codex sessions in parallel — a browser terminal grid that shows which agent needs you. Local, tmux-backed, MIT. The licence is MIT.
Read from SKILL.md and the folder at commit b3f6ff0. 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:
yarnwranglersupabasenodevitestgitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use yarn, wrangler, supabase 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 these keys or tokens, usually read from environment variables:
PUBLISHABLE_KEYVITE_SUPABASE_PUBLISHABLE_KEYSECRET_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Blueprint Supabase Scaffold loads about 1.1k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 460 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 noted patterns worth knowing about, such as sudo or a known installer.
scripts/local-env.mjs writes .env.development.local from the running local stack`.env.development.local` as those two variables.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 receptron/mulmoterminal at commit b3f6ff0, republished under its MIT licence (© receptron). 460 words, ~1,096 tokens.
.claude/skills/blueprint-supabase-scaffold/SKILL.md (or your agent's skills folder).One folder, one package.json, TypeScript throughout, yarn. The later checks rely on this layout exactly:
supabase/config.toml yarn supabase init; project_id is the app's name
supabase/migrations/ the schema, one timestamped .sql per change (yarn supabase migration new <name>)
supabase/seed.sql rows for trying the app locally; the security check needs one in every table
index.html the Vue entry (<div id="app">)
src/client/ Vue 3 + Vite; src/client/supabase.ts creates the one Supabase client
vite.config.ts writes _headers into the build (see below)
wrangler.jsonc serves the build as static files; there is no Worker code
scripts/local-env.mjs writes .env.development.local from the running local stack
test/ vitest against the local stack; one file per area: data, ui, authsupabase, @supabase/supabase-js, vite, @vitejs/plugin-vue, vue, typescript@^6 (not 7:
a later check reads test files through TypeScript's compiler API, which TypeScript 7 does not ship), vitest,
wrangler.VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY (the
publishable key, sb_publishable_…). The secret key never goes into src/ or any VITE_ variable.scripts/local-env.mjs runs yarn -s supabase status -o json and writes API_URL and PUBLISHABLE_KEY to
.env.development.local as those two variables.vite.config.ts: on vite build only, read VITE_SUPABASE_URL with loadEnv (throw if it is missing) and emit a
_headers asset for every path: Content-Security-Policy: default-src 'self'; connect-src 'self' <that URL>; frame-ancestors 'none'; object-src 'none'; base-uri 'self', X-Content-Type-Options: nosniff,
Referrer-Policy: same-origin. The CSP has to name the Supabase URL of the build it is in, or the browser blocks
every call; a fixed public/_headers cannot, because the local and the production URL differ.wrangler.jsonc: name, compatibility_date (a date the installed wrangler supports — about a month before
today), "assets": { "directory": "./dist", "not_found_handling": "single-page-application" }. No main.db:start: supabase start -x studio,imgproxy,logflare,vector,edge-runtime,realtime,mailpit,supavisor,postgres-meta && node scripts/local-env.mjs
(leave out mailpit from -x if the spec signs people in by email link)build: vite build --mode development — the local build, talking to the local stackstart: yarn -s db:start >/dev/null && yarn -s build && wrangler dev --local --ip 127.0.0.1. The checks run
yarn start --port <n>, so extra arguments must reach wrangler dev.test: vitest rundeploy: vite build --mode production && wrangler deploy.gitignore: node_modules, dist, .wrangler, *.local.test/local-stack.ts: reads yarn -s supabase status -o json; exports an admin client made with SECRET_KEY
(tests only, never the app), a signed-out client made with PUBLISHABLE_KEY, and signedIn(), which creates a
fresh user with auth.admin.createUser({ email, password, email_confirm: true }) and returns a client signed in as
them. Tests never reach a hosted project.test/ that reaches the local stack, so the harness is proven.The checks start the local stack themselves and reset its database to the migrations and the seed before testing, so a test may not rely on rows another test left behind.
Done when the check passes: the layout exists, yarn db:start starts the stack, yarn build and yarn test succeed.
.blueprint/spec.md first. It is the agreed specification; do not widen it.git init: a new repository loses the folder's trust and the next unattended step stops at Claude
Code's trust prompt. The user adds git themselves after the build if they want it.© receptron, 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 blueprints/supabase/skills/scaffold of receptron/mulmoterminal.
Open the folder on GitHubat commit b3f6ff0
Blueprint Supabase Scaffold 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 |
|---|---|---|---|---|---|---|
| Blueprint Supabase Scaffold this skillreceptron/mulmoterminal | 237 | — | ~1.1k | Automated safety check: Notes | MIT | |
| Agent RecallGoldentrii/AgentRecall-X | 371 | — | ~5.2k | Automated safety check: Notes | MIT | |
| Init Ruleslifedever/claude-rules | 191 | — | ~652 | Automated safety check: Pass | MIT | |
| Uniapp App Generate Skilljiushiwon/wg-skills | 114 | — | ~5k | Automated safety check: Notes | Apache-2.0 | |
| Architecturepikax/verter | 113 | — | ~5.6k | Automated safety check: Pass | MIT | |
| Vue Generate Skilljiushiwon/wg-skills | 114 | — | ~3.1k | Automated safety check: Pass | Apache-2.0 |
Goldentrii/AgentRecall-X
Persistent compounding memory for AI agents. An agent skill from Goldentrii/AgentRecall-X.
lifedever/claude-rules
Initialize or update CLAUDE.md coding standards for any project by auto-detecting tech stack and assembling rules from the claude-rules template library.
jiushiwon/wg-skills
This skill should be used when the user wants to create a standardized uni-app project for WeChat mini-program, H5, and App from scratch.
pikax/verter
Verter codebase architecture: high-level module map, TypeScript packages, plugin system, CSS analysis, MCP server, static analysis types
jiushiwon/wg-skills
This skill should be used when the user wants to create a standardized Vue 3 + TypeScript + Vite + Pinia project from scratch.
teambit/bit
Generate comprehensive release notes for Bit from git commits and pull requests.
receptron/mulmoterminal
Help desk for "MulmoTerminal is broken". An agent skill from receptron/mulmoterminal.
receptron/mulmoterminal
Check what this project's humans have already been asked, and how they answered, before asking them something similar.
receptron/mulmoterminal
Help desk for questions about MulmoTerminal itself — what it can do, how a feature or a part of the screen works, how to set something up, what is new in this version or in the latest one.
receptron/mulmoterminal
Decide which moments MulmoTerminal beeps or pushes for, and what each one plays — soundKinds, sounds and pushKinds in ~/.mulmoterminal/config.json, plus a per-project sound / sounds in…
receptron/mulmoterminal
Build a colour scheme of your own for MulmoTerminal — one that joins Midnight, Nord, Daylight and Solarized in Settings' theme picker and can then be pinned per project.
receptron/mulmoterminal
Answer each question from the named documents only, quoting where the answer is written, or saying plainly that the documents do not say — changing nothing yet.
Categories
Lay out a Vue app on the local Supabase stack, served as static files by wrangler, with tests that run against the local stack. Blueprint Supabase Scaffold is an agent skill from receptron/mulmoterminal. Lay out a Vue app on the local Supabase stack, served as static files by wrangler, with tests that run against the local stack.
Blueprint Supabase Scaffold fits situations like: agent Workflows work in your project.
Run `npx skills add receptron/mulmoterminal --skill blueprint-supabase-scaffold -a claude-code`. Or copy the skill folder (blueprints/supabase/skills/scaffold in receptron/mulmoterminal) into .claude/skills/blueprint-supabase-scaffold in your project. Claude Code loads it when a task matches its description.
Run `npx skills add receptron/mulmoterminal --skill blueprint-supabase-scaffold -a codex`. Or copy the skill folder (blueprints/supabase/skills/scaffold in receptron/mulmoterminal) into .agents/skills/blueprint-supabase-scaffold 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 receptron/mulmoterminal --skill blueprint-supabase-scaffold -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blueprint-supabase-scaffold, .gemini/skills/blueprint-supabase-scaffold, .github/skills/blueprint-supabase-scaffold and .opencode/skills/blueprint-supabase-scaffold in your project.
Going by SKILL.md and its folder, Blueprint Supabase Scaffold needs the command-line tools its instructions call (yarn, wrangler, supabase, node, vitest and git) and credentials named PUBLISHABLE_KEY, VITE_SUPABASE_PUBLISHABLE_KEY and SECRET_KEY. Our summary lists: A credential in VITE_SUPABASE_PUBLISHABLE_KEY; A credential in PUBLISHABLE_KEY.
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.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Blueprint Supabase Scaffold 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.1k tokens (SKILL.md is roughly 4.4k 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 Blueprint Supabase Scaffold: Agent Recall (Goldentrii/AgentRecall-X, 371 stars), Init Rules (lifedever/claude-rules, 191 stars), Uniapp App Generate Skill (jiushiwon/wg-skills, 114 stars) and Architecture (pikax/verter, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
receptron (a GitHub organization) maintains it in receptron/mulmoterminal, which has 237 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 10, 2026.
Source: receptron/mulmoterminal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.