Manage Settings
asgeirtj/system_prompts_leaks
Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool…
COMMAND, not reference: Walk the user through setting up and running a node's live test.
$ npx skills add WeaveMindAI/weft --skill weft-live-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WeaveMindAI/weft weft-live-test --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/WeaveMindAI/weft.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-live-test .claude/skills/weft-live-test && 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 "weft-live-test" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-live-test into .claude/skills/weft-live-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-live-test", 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/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-live-testType 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 WeaveMindAI/weft --skill weft-live-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WeaveMindAI/weft weft-live-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-live-test .agents/skills/weft-live-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "weft-live-test" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-live-test into .agents/skills/weft-live-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-live-test", 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 WeaveMindAI/weft --skill weft-live-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WeaveMindAI/weft weft-live-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-live-test .cursor/skills/weft-live-test && 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 "weft-live-test" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-live-test into .cursor/skills/weft-live-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-live-test", 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/WeaveMindAI/weft.git --path tangle/cline/.cline/skills/weft-live-test--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 WeaveMindAI/weft --skill weft-live-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WeaveMindAI/weft weft-live-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-live-test .gemini/skills/weft-live-test && 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 "weft-live-test" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-live-test into .gemini/skills/weft-live-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-live-test", 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 WeaveMindAI/weft weft-live-testInstalls 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 WeaveMindAI/weft --skill weft-live-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .github/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-live-test .github/skills/weft-live-test && 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 "weft-live-test" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-live-test into .github/skills/weft-live-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-live-test", 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 WeaveMindAI/weft --skill weft-live-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WeaveMindAI/weft weft-live-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-live-test .opencode/skills/weft-live-test && 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 "weft-live-test" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-live-test into .opencode/skills/weft-live-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-live-test", 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.
weft-live-testCOMMAND, not reference: Walk the user through setting up and running a node's live test.
Weft Live Test is an agent skill from WeaveMindAI/weft. COMMAND, not reference: Walk the user through setting up and running a node's live test. Run this when the user asks for this step by name, optionally naming the node type or package name. The weft- reference skills beside it are things you read; this is a procedure you carry out.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A programming language for AI orchestrations.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 6e28f31. 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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
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.
Weft Live Test loads about 666 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 384 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.
CE>_<FIELD>=...` lines in the project's `.env` (auto-loaded) or their shell themselves. Never ask them to paste a secretAutomated 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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 384 words (~666 tokens).
“Run the live tier of a node's self-tests, with the user's informed consent. The node type or package is the one the user named when they asked. The local tiers (basic, fake) already passed when the node was built; the…”
Just SKILL.md in tangle/cline/.cline/skills/weft-live-test of WeaveMindAI/weft.
Open the folder on GitHubat commit 6e28f31
Weft Live Test 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 |
|---|---|---|---|---|---|---|
| Weft Live Test this skillWeaveMindAI/weft | 2k | — | ~666 | Automated safety check: Notes | Custom licence | |
| Manage Settingsasgeirtj/system_prompts_leaks | 69k | — | ~3.1k | Automated safety check: Pass | CC0-1.0 | |
| Warp Settings Editorwarpdotdev/warp | 65k | 1 repos | ~675 | Automated safety check: Pass | AGPL-3.0 | |
| Warp Settings Page Builderwarpdotdev/warp | 65k | 1 repos | ~4.5k | Automated safety check: Pass | AGPL-3.0 | |
| Add Server Env Var for User Settinglobehub/lobehub | 83k | — | ~644 | Automated safety check: Pass | Custom licence | |
| Add Settings Pagesimstudioai/sim | 30k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
asgeirtj/system_prompts_leaks
Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool…
warpdotdev/warp
Finds and changes Warp application settings by searching a bundled JSON schema and editing the matching TOML settings file at the right nesting depth.
warpdotdev/warp
How to build a settings page in the Warp desktop client so widgets, page titles and settings search behave correctly, and which common mistakes to avoid.
lobehub/lobehub
Adds a server-side environment variable that sets the default for a user setting in LobeHub, wired from the env schema through server config to the user store and docs.
simstudioai/sim
Add a new Sim settings page, or audit existing settings pages for design-system compliance with the shared SettingsPanel layout.
anthropics/claude-plugins-official
Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.
WeaveMindAI/weft
Read when the user wants weft itself on their Google Cloud for the first time, or to upgrade or resize the weft already there: getting the user's GitHub and Google Cloud accounts and CLIs ready, the…
WeaveMindAI/weft
Read when the user wants their own website, app, bot or extension to list, show, answer, skip or cancel what a program is waiting on, fetch a file it carries, or show what one of its nodes is…
WeaveMindAI/weft
Read when the user wants weft or a program live for real people on their cloud, asks about prod, a target, --on, a domain or GCP, or a deploy failed: targets and logging in, domains, the deploy…
WeaveMindAI/weft
Read when the user asks what a run costs, or when a node is wired to a paid API weft does not already price: the three pieces of a custom paid service, a meter to copy, and the rules that keep a…
WeaveMindAI/weft
Read when growing a program stage by stage: carving a run, supplying starting values, baking a trigger and firing it without activating, reusing completed work with a seed, freezing an accepted…
WeaveMindAI/weft
Read when the user wants a page, app or site for the program, and before dispatching the frontend-builder: the verified scaffold commands, the default stack (pnpm, SvelteKit, PostgreSQL, BetterAuth…
COMMAND, not reference: Walk the user through setting up and running a node's live test. Weft Live Test is an agent skill from WeaveMindAI/weft. COMMAND, not reference: Walk the user through setting up and running a node's live test.
Weft Live Test fits situations like: asks for this step by name; optionally naming the node type.
Run `npx skills add WeaveMindAI/weft --skill weft-live-test -a claude-code`. Or copy the skill folder (tangle/cline/.cline/skills/weft-live-test in WeaveMindAI/weft) into .claude/skills/weft-live-test in your project. Claude Code loads it when a task matches its description.
Run `npx skills add WeaveMindAI/weft --skill weft-live-test -a codex`. Or copy the skill folder (tangle/cline/.cline/skills/weft-live-test in WeaveMindAI/weft) into .agents/skills/weft-live-test 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 WeaveMindAI/weft --skill weft-live-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weft-live-test, .gemini/skills/weft-live-test, .github/skills/weft-live-test and .opencode/skills/weft-live-test in your project.
SKILL.md names no scripts, command-line tools or credentials: Weft Live Test is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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.
Weft Live Test has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 666 tokens (SKILL.md is roughly 2.7k 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 Weft Live Test: Manage Settings (asgeirtj/system_prompts_leaks, 69k stars), Warp Settings Editor (warpdotdev/warp, 65k stars), Warp Settings Page Builder (warpdotdev/warp, 65k stars) and Add Server Env Var for User Setting (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
WeaveMindAI (a GitHub organization) maintains it in WeaveMindAI/weft, which has 1,995 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 6, 2026.
Source: WeaveMindAI/weft on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.