Workthreads
specstoryai/getspecstory
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more).
Shipping weft: merging into main through a PR, what the release workflow publishes, the record tags that decide which stores publish, and the store rules that have actually bitten us.
$ npx skills add WeaveMindAI/weft --skill releasing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WeaveMindAI/weft releasing --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/.kilo/skills/releasing .claude/skills/releasing && 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 "releasing" agent skill from https://github.com/WeaveMindAI/weft/tree/main/.kilo/skills/releasing into .claude/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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/.kilo/skills/releasingType 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 releasing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WeaveMindAI/weft releasing --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/.kilo/skills/releasing .agents/skills/releasing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "releasing" agent skill from https://github.com/WeaveMindAI/weft/tree/main/.kilo/skills/releasing into .agents/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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 releasing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WeaveMindAI/weft releasing --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/.kilo/skills/releasing .cursor/skills/releasing && 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 "releasing" agent skill from https://github.com/WeaveMindAI/weft/tree/main/.kilo/skills/releasing into .cursor/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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 .kilo/skills/releasing--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 releasing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WeaveMindAI/weft releasing --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/.kilo/skills/releasing .gemini/skills/releasing && 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 "releasing" agent skill from https://github.com/WeaveMindAI/weft/tree/main/.kilo/skills/releasing into .gemini/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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 releasingInstalls 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 releasing -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/.kilo/skills/releasing .github/skills/releasing && 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 "releasing" agent skill from https://github.com/WeaveMindAI/weft/tree/main/.kilo/skills/releasing into .github/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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 releasing -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 releasing --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/.kilo/skills/releasing .opencode/skills/releasing && 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 "releasing" agent skill from https://github.com/WeaveMindAI/weft/tree/main/.kilo/skills/releasing into .opencode/skills/releasing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing", 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.
releasingShipping weft: merging into main through a PR, what the release workflow publishes, the record tags that decide which stores publish, and the store rules that have actually bitten us.
Releasing is an agent skill from WeaveMindAI/weft. Shipping weft: merging into main through a PR, what the release workflow publishes, the record tags that decide which stores publish, and the store rules that have actually bitten us. Load before merging to main, bumping an extension version, or debugging a red publish job.
Its SKILL.md is about 2.9k 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 Development. It works with Visual Studio Code. The repository describes itself as: A programming language for AI orchestrations.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 350a891. 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:
pnpmcargogitghterraformcurldockernodeFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
marketplace.visualstudio.comFrom 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.
Releasing loads about 2.9k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 1,640 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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,640 words (~2,902 tokens).
“How a change gets from the working tree to the stores, and the traps that cost a round trip the last time each one was hit.”
Just SKILL.md in .kilo/skills/releasing of WeaveMindAI/weft.
Open the folder on GitHubat commit 350a891
Releasing 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 |
|---|---|---|---|---|---|---|
| Releasing this skillWeaveMindAI/weft | 2k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Workthreadsspecstoryai/getspecstory | 1.3k | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Excalidraw Diagram Studiotech-leads-club/agent-skills | 7k | — | ~3.6k | Automated safety check: Pass | CC-BY-4.0 | |
| Git Worktree Managermicrosoft/WindowsAppSDK | 4.7k | — | ~2k | Automated safety check: Pass | MIT | |
| Roo Conflict Resolutionzgsm-ai/costrict | 4.4k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Interactive Extension TestingPowerShell/vscode-powershell | 1.9k | — | ~824 | Automated safety check: Pass | MIT |
specstoryai/getspecstory
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more).
tech-leads-club/agent-skills
Generates Excalidraw diagram files from plain descriptions, choosing among flowcharts, mind maps, architecture, swimlane, class, sequence and ER diagrams.
microsoft/WindowsAppSDK
Creates and manages Git worktrees with PowerShell scripts so separate issues and Copilot sessions each get an isolated branch, build and test environment.
zgsm-ai/costrict
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context.
PowerShell/vscode-powershell
Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace.
PowerShell/vscode-powershell
Guide for preparing a release of the PowerShell VS Code extension.
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…
Works with
Categories
Shipping weft: merging into main through a PR, what the release workflow publishes, the record tags that decide which stores publish, and the store rules that have actually bitten us. Releasing is an agent skill from WeaveMindAI/weft. Shipping weft: merging into main through a PR, what the release workflow publishes, the record tags that decide which stores publish, and the store rules that have actually bitten us.
Releasing fits situations like: development work in your project.
Run `npx skills add WeaveMindAI/weft --skill releasing -a claude-code`. Or copy the skill folder (.kilo/skills/releasing in WeaveMindAI/weft) into .claude/skills/releasing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add WeaveMindAI/weft --skill releasing -a codex`. Or copy the skill folder (.kilo/skills/releasing in WeaveMindAI/weft) into .agents/skills/releasing 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 releasing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/releasing, .gemini/skills/releasing, .github/skills/releasing and .opencode/skills/releasing in your project.
Going by SKILL.md and its folder, Releasing needs the command-line tools its instructions call (pnpm, cargo, git, gh, terraform and curl). Our summary lists: Docker.
SKILL.md names 1 domain. In commands or code: marketplace.visualstudio.com; the agent is likely to contact it when it follows the instructions. 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.
Releasing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 2.9k tokens (SKILL.md is roughly 12k 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 Releasing: Workthreads (specstoryai/getspecstory, 1.3k stars), Excalidraw Diagram Studio (tech-leads-club/agent-skills, 7k stars), Git Worktree Manager (microsoft/WindowsAppSDK, 4.7k stars) and Roo Conflict Resolution (zgsm-ai/costrict, 4.4k 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,996 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 8, 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.