Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
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…
Install Warpnet Testnet Verify
$ npx skills add Warp-net/warpnet --skill warpnet-testnet-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Warp-net/warpnet warpnet-testnet-verify --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-testnet-verify .claude/skills/warpnet-testnet-verify && 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-testnet-verify" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-testnet-verify into .claude/skills/warpnet-testnet-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-testnet-verify", 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-testnet-verifyType 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-testnet-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Warp-net/warpnet warpnet-testnet-verify --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-testnet-verify .agents/skills/warpnet-testnet-verify && 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-testnet-verify" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-testnet-verify into .agents/skills/warpnet-testnet-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-testnet-verify", 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-testnet-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Warp-net/warpnet warpnet-testnet-verify --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-testnet-verify .cursor/skills/warpnet-testnet-verify && 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-testnet-verify" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-testnet-verify into .cursor/skills/warpnet-testnet-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-testnet-verify", 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-testnet-verify--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-testnet-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Warp-net/warpnet warpnet-testnet-verify --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-testnet-verify .gemini/skills/warpnet-testnet-verify && 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-testnet-verify" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-testnet-verify into .gemini/skills/warpnet-testnet-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-testnet-verify", 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-testnet-verifyInstalls 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-testnet-verify -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-testnet-verify .github/skills/warpnet-testnet-verify && 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-testnet-verify" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-testnet-verify into .github/skills/warpnet-testnet-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-testnet-verify", 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-testnet-verify -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-testnet-verify --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-testnet-verify .opencode/skills/warpnet-testnet-verify && 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-testnet-verify" agent skill from https://github.com/Warp-net/warpnet/tree/main/.claude/skills/warpnet-testnet-verify into .opencode/skills/warpnet-testnet-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warpnet-testnet-verify", 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.
Facts
- Skill name
warpnet-testnet-verify- GitHub stars
- 157
- Token cost
- ~4.1k tokens
- SKILL.md length
- 1,610 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
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…
- Works in 5 steps: build from the working tree → 3 — run on testnet → liveness vs readiness → …
- A Warpnet change needs to be verified by actually running it in the testnet network — any task phrased as test this in testnet
- SKILL.md covers The mandatory verification loop, Step 1 — build from the…, Step 2/3 — run on testnet and Step 4 — liveness vs readiness, plus 5 more sections
- Calls go, node and git
What it does
Warpnet Testnet Verify is an agent skill from Warp-net/warpnet. Use this skill 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 it end-to-end", "does the handler actually respond", "prove the route works on a real node", "smoke-test before pushing", or when you've just added/changed a handler, DTO, or protocol path and want runtime confirmation rather than just go test. This skill MANDATES bringing up a real remote node…
Its SKILL.md is about 4.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 Testing & QA, covering QA and bug reports. 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…
When your agent uses it
- 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 it end-to-end
- Does the handler actually respond
Example prompts
- “test this in testnet”
- “verify the feature works”
- “check it end-to-end”
- “/warpnet-testnet-verify”
Requirements
- Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- build from the working tree
- 3 — run on testnet
- liveness vs readiness
- drive the /ws bridge
- teardown & clean state
What it can do on your machine
Read from SKILL.md and the folder at commit da3b67b. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
gonodegit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Warpnet Testnet Verify loads about 4.1k tokens when it runs. Until then it costs about 228 tokens; SKILL.md has 1,610 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.
Safety
Auto-check passed
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.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,610 words (~4,149 tokens).
“go test proves the pieces compile and the unit logic holds. It does not prove that a route is registered, that the libp2p self-stream reaches the handler, that the auth-signed envelope decodes, or that the wire payload is what the…”
- name
- warpnet-testnet-verify
Files
Just SKILL.md in .claude/skills/warpnet-testnet-verify of Warp-net/warpnet.
Open the folder on GitHubat commit da3b67b
Compare with similar skills
Warpnet Testnet Verify 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 Testnet Verify this skillWarp-net/warpnet | 157 | — | ~4.1k | Automated safety check: Pass | Custom licence | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Moav E2EMotherofallVPNs/MoaV | 448 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Creating A Coral TaskHuman-Agent-Society/CORAL | 1.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Launch Rlmarin-community/marin | 3.9k | — | ~894 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Creating A Coral Task
Human-Agent-Society/CORAL
Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…
Launch Rl
marin-community/marin
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.
Actionbook Web Test
actionbook/actionbook
Run browser-based web tests against websites using Actionbook CLI.
More from Warp-net/warpnet
Semantic Compression
Warp-net/warpnet
Apply semantic logic compression (Ovchinnikov method) when crafting prompts for LLMs or describing complex conditional logic.
Warpdroid UI Test
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…
Warpnet Claude Node
Warp-net/warpnet
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 Debug Backend
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.
Warpnet Add Handler
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…
Related
Categories
Questions about Warpnet Testnet Verify
What does Warpnet Testnet Verify do?
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…. Warpnet Testnet Verify is an agent skill from Warp-net/warpnet. Use this skill 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 it end-to-end", "does the handler actually respond", "prove the route works on a real node", "smoke-test before pushing", or when you've just added/changed a handler, DTO, or protocol path and want runtime confirmation rather than just go test.
When should I use Warpnet Testnet Verify?
Warpnet Testnet Verify fits situations like: 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 it end-to-end; does the handler actually respond.
How do I install Warpnet Testnet Verify in Claude Code?
Run `npx skills add Warp-net/warpnet --skill warpnet-testnet-verify -a claude-code`. Or copy the skill folder (.claude/skills/warpnet-testnet-verify in Warp-net/warpnet) into .claude/skills/warpnet-testnet-verify in your project. Claude Code loads it when a task matches its description.
How do I install Warpnet Testnet Verify in Codex?
Run `npx skills add Warp-net/warpnet --skill warpnet-testnet-verify -a codex`. Or copy the skill folder (.claude/skills/warpnet-testnet-verify in Warp-net/warpnet) into .agents/skills/warpnet-testnet-verify in your project. Codex loads it when a task matches its description.
Can I use Warpnet Testnet Verify in Cursor, Gemini CLI or GitHub Copilot?
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-testnet-verify -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-testnet-verify, .gemini/skills/warpnet-testnet-verify, .github/skills/warpnet-testnet-verify and .opencode/skills/warpnet-testnet-verify in your project.
What does Warpnet Testnet Verify need to run?
Going by SKILL.md and its folder, Warpnet Testnet Verify needs the command-line tools its instructions call (go, node and git). Our summary lists: Docker.
Does Warpnet Testnet Verify access the network?
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.
Is Warpnet Testnet Verify safe to install?
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.
What licence does Warpnet Testnet Verify use?
Warpnet Testnet Verify has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Warpnet Testnet Verify use?
About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Warpnet Testnet Verify?
Skills that share tags, products or a category with Warpnet Testnet Verify: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 448 stars) and Creating A Coral Task (Human-Agent-Society/CORAL, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Warpnet Testnet Verify?
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.