A skill your agent uses to stand up, log into, or tear down your own Warpnet node — the Claude account on the NODESEED=claude node, running from Dockerfile.remote on testnet.
$ npx skills add Warp-net/warpnet --skill warpnet-claude-node -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Warp-net/warpnet warpnet-claude-node --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/Warp-net/warpnet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/warpnet-claude-node .claude/skills/warpnet-claude-node && 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 "warpnet-claude-node" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-claude-node into .claude/skills/warpnet-claude-node/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-claude-node", 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/Warp-net/warpnet/tree/main/.claude/skills/warpnet-claude-nodeType 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 Warp-net/warpnet --skill warpnet-claude-node -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Warp-net/warpnet warpnet-claude-node --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Warp-net/warpnet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/warpnet-claude-node .agents/skills/warpnet-claude-node && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "warpnet-claude-node" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-claude-node into .agents/skills/warpnet-claude-node/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-claude-node", 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 Warp-net/warpnet --skill warpnet-claude-node -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Warp-net/warpnet warpnet-claude-node --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Warp-net/warpnet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/warpnet-claude-node .cursor/skills/warpnet-claude-node && 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 "warpnet-claude-node" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-claude-node into .cursor/skills/warpnet-claude-node/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-claude-node", 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/Warp-net/warpnet.git --path .claude/skills/warpnet-claude-node--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 Warp-net/warpnet --skill warpnet-claude-node -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Warp-net/warpnet warpnet-claude-node --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Warp-net/warpnet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/warpnet-claude-node .gemini/skills/warpnet-claude-node && 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 "warpnet-claude-node" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-claude-node into .gemini/skills/warpnet-claude-node/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-claude-node", 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 Warp-net/warpnet warpnet-claude-nodeInstalls 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 Warp-net/warpnet --skill warpnet-claude-node -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Warp-net/warpnet.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/warpnet-claude-node .github/skills/warpnet-claude-node && 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 "warpnet-claude-node" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-claude-node into .github/skills/warpnet-claude-node/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-claude-node", 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 Warp-net/warpnet --skill warpnet-claude-node -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Warp-net/warpnet warpnet-claude-node --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Warp-net/warpnet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/warpnet-claude-node .opencode/skills/warpnet-claude-node && 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 "warpnet-claude-node" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-claude-node into .opencode/skills/warpnet-claude-node/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-claude-node", 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.
warpnet-claude-nodeA skill your agent uses to stand up, log into, or tear down your own Warpnet node — the Claude account on the NODESEED=claude node, running from Dockerfile.remote on testnet.
Warpnet Claude Node is an agent skill from Warp-net/warpnet. Use this skill to stand up, log into, or tear down your own Warpnet node — the Claude account on the NODESEED=claude node, running from Dockerfile.remote on testnet. Triggers include "spin up a node", "start your own node", "log into the node", "I need a live node to reproduce this", "rebuild the container", "the node is gone / recreate it", "set up the Claude account", "the dashboard says logged out after a restart", "reset the node's data", or any task that begins with "log into the fat node first" and you…
Its SKILL.md is about 3k 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 DevOps & Cloud, covering Containers and Meeting notes and agendas. It works with Docker. The repository describes itself as: Warpnet is a decentralized, peer-to-peer social network/media inspired by Twitter, built with Go. It runs without central servers, using Noise protocol for inter-node…
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit da3b67b. 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:
dockergogitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use docker 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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Warpnet Claude Node loads about 3k tokens when it runs. Until then it costs about 258 tokens; SKILL.md has 1,029 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,029 words (~2,992 tokens).
“Most debugging dances start with "log into the fat node first." When you don't have the user's desktop node in front of you, stand up your own headless remote node (cmd/node/member/remote-member.go — the same binary warpnet-testnet-verify uses) in a Docker…”
Just SKILL.md in .claude/skills/warpnet-claude-node of Warp-net/warpnet.
Open the folder on GitHubat commit da3b67b
Warpnet Claude Node 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 |
|---|---|---|---|---|---|---|
| Warpnet Claude Node this skillWarp-net/warpnet | 157 | — | ~3k | Automated safety check: Pass | Custom licence | |
| Metro AI App Recipeopen-edge-platform/edge-ai-suites | 140 | — | ~4.4k | Automated safety check: Notes | Apache-2.0 | |
| Local Platform E2Ecomputesdk/benchmarks | 126 | — | ~3k | Automated safety check: Notes | MIT | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence |
open-edge-platform/edge-ai-suites
Stand up a complete, ready-to-run computer-vision analytics stack on Intel hardware with one Docker Compose command — point it at your video sources and an OpenVINO/ONNX model to get live annotated…
computesdk/benchmarks
Stand up benchmarks-platform locally (Postgres + MinIO + ClickHouse in docker) and run a real @benchsdk/runner benchmark against it, with no cloud or provider credentials.
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
Warp-net/warpnet
Apply semantic logic compression (Ovchinnikov method) when crafting prompts for LLMs or describing complex conditional logic.
Warp-net/warpnet
A skill your agent uses whenever a warpdroid (Android client) change or bug needs to be verified by actually driving the app's visual UI — any task phrased as "test the warpdroid UI", "click through…
Warp-net/warpnet
A skill your agent uses when a Warpnet bug lives in the Go node/backend — the fat/member/remote node, its handlers, storage, or libp2p layer.
Warp-net/warpnet
A skill your agent uses whenever a Warpnet change needs to be verified by actually running it in the testnet network — any task phrased as "test this in testnet", "verify the feature works", "check…
Warp-net/warpnet
A skill your agent uses whenever the task is to add a new feature to Warpnet that crosses layers — anything described as a "new endpoint", "new route", "new RPC", "new event", "new path", or any…
Works with
Categories
A skill your agent uses to stand up, log into, or tear down your own Warpnet node — the Claude account on the NODESEED=claude node, running from Dockerfile.remote on testnet. Warpnet Claude Node is an agent skill from Warp-net/warpnet.remote on testnet.
Warpnet Claude Node fits situations like: tear down your own Warpnet node — the Claude account on the NODESEED=claude node; running from Dockerfile.remote on testnet; include spin up a node; start your own node.
Run `npx skills add Warp-net/warpnet --skill warpnet-claude-node -a claude-code`. Or copy the skill folder (.claude/skills/warpnet-claude-node in Warp-net/warpnet) into .claude/skills/warpnet-claude-node in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Warp-net/warpnet --skill warpnet-claude-node -a codex`. Or copy the skill folder (.claude/skills/warpnet-claude-node in Warp-net/warpnet) into .agents/skills/warpnet-claude-node 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 Warp-net/warpnet --skill warpnet-claude-node -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/warpnet-claude-node, .gemini/skills/warpnet-claude-node, .github/skills/warpnet-claude-node and .opencode/skills/warpnet-claude-node in your project.
Going by SKILL.md and its folder, Warpnet Claude Node needs the command-line tools its instructions call (docker, go and git). Our summary lists: Docker.
SKILL.md contains no URLs. Its commands use docker and 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 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.
Warpnet Claude Node has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 3k 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 Warpnet Claude Node: Metro AI App Recipe (open-edge-platform/edge-ai-suites, 140 stars), Local Platform E2E (computesdk/benchmarks, 126 stars), Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars) and GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Warp-net (a GitHub organization) maintains it in Warp-net/warpnet, which has 157 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.
Source: Warp-net/warpnet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
