Brief
alirezarezvani/claude-skills
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
Read before dispatching a node-smith (the brief and the review) and when an expert writes a node by hand: the node authoring manual, the test tiers, and the shapes half-done work takes.
$ npx skills add WeaveMindAI/weft --skill weft-node-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WeaveMindAI/weft weft-node-authoring --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-node-authoring .claude/skills/weft-node-authoring && 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-node-authoring" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-node-authoring into .claude/skills/weft-node-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-node-authoring", 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-node-authoringType 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-node-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WeaveMindAI/weft weft-node-authoring --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-node-authoring .agents/skills/weft-node-authoring && 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-node-authoring" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-node-authoring into .agents/skills/weft-node-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-node-authoring", 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-node-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WeaveMindAI/weft weft-node-authoring --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-node-authoring .cursor/skills/weft-node-authoring && 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-node-authoring" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-node-authoring into .cursor/skills/weft-node-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-node-authoring", 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-node-authoring--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-node-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WeaveMindAI/weft weft-node-authoring --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-node-authoring .gemini/skills/weft-node-authoring && 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-node-authoring" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-node-authoring into .gemini/skills/weft-node-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-node-authoring", 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-node-authoringInstalls 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-node-authoring -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-node-authoring .github/skills/weft-node-authoring && 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-node-authoring" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-node-authoring into .github/skills/weft-node-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-node-authoring", 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-node-authoring -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-node-authoring --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-node-authoring .opencode/skills/weft-node-authoring && 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-node-authoring" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/weft-node-authoring into .opencode/skills/weft-node-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weft-node-authoring", 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-node-authoringRead before dispatching a node-smith (the brief and the review) and when an expert writes a node by hand: the node authoring manual, the test tiers, and the shapes half-done work takes.
Weft Node Authoring is an agent skill from WeaveMindAI/weft. Read before dispatching a node-smith (the brief and the review) and when an expert writes a node by hand: the node authoring manual, the test tiers, and the shapes half-done work takes. The node-smith reads this same file as its manual.
Its SKILL.md is about 16k 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.
4 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 (its code samples are rust, json, javascript and toml).
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 Node Authoring loads about 16k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 8,957 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 8,957 words (~16,191 tokens).
“Tangle reads the dispatch protocol and [the review] checklist. The node-smith subagent, and an expert taking the hand, read the manual that follows them.”
Just SKILL.md in tangle/cline/.cline/skills/weft-node-authoring of WeaveMindAI/weft.
Open the folder on GitHubat commit 6e28f31
Weft Node Authoring 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 Node Authoring this skillWeaveMindAI/weft | 2k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Briefalirezarezvani/claude-skills | 28k | — | ~967 | Automated safety check: Pass | MIT | |
| Dispatchsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Configuring Oauth2 Authorization Flowmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Content Brief Authoringrampstackco/claude-skills | 935 | — | ~5.6k | Automated safety check: Pass | MIT |
alirezarezvani/claude-skills
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
sickn33/agentic-awesome-skills
Delegate tasks to OpenAI Codex CLI and Google Antigravity CLI from Claude Code with topic-aware sessions
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
mukul975/Anthropic-Cybersecurity-Skills
Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token…
rampstackco/claude-skills
How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both.
mukul975/Anthropic-Cybersecurity-Skills
Implements GCP Binary Authorization end to end, including creating KMS-backed attestors, Container Analysis notes, deploy-time policies, and signing image attestations, so that only trusted…
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…
Read before dispatching a node-smith (the brief and the review) and when an expert writes a node by hand: the node authoring manual, the test tiers, and the shapes half-done work takes. Weft Node Authoring is an agent skill from WeaveMindAI/weft. Read before dispatching a node-smith (the brief and the review) and when an expert writes a node by hand: the node authoring manual, the test tiers, and the shapes half-done work takes.
Run `npx skills add WeaveMindAI/weft --skill weft-node-authoring -a claude-code`. Or copy the skill folder (tangle/cline/.cline/skills/weft-node-authoring in WeaveMindAI/weft) into .claude/skills/weft-node-authoring in your project. Claude Code loads it when a task matches its description.
Run `npx skills add WeaveMindAI/weft --skill weft-node-authoring -a codex`. Or copy the skill folder (tangle/cline/.cline/skills/weft-node-authoring in WeaveMindAI/weft) into .agents/skills/weft-node-authoring 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-node-authoring -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-node-authoring, .gemini/skills/weft-node-authoring, .github/skills/weft-node-authoring and .opencode/skills/weft-node-authoring in your project.
SKILL.md names no scripts, command-line tools or credentials: Weft Node Authoring 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 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.
Weft Node Authoring has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 16k tokens (SKILL.md is roughly 65k 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 Node Authoring: Brief (alirezarezvani/claude-skills, 28k stars), Dispatch (sickn33/agentic-awesome-skills, 47k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars) and Configuring Oauth2 Authorization Flow (mukul975/Anthropic-Cybersecurity-Skills, 34k 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,994 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.