Engine E2E
wix/react-native-navigation
Run Wix Engine (mobile-apps-engine) iOS E2E tests locally to validate RNN changes.
Use before any Tabox store release — before merging a release branch to main, when asked "are we good to ship / good to go / release-ready", or before publishing to the Chrome Web Store or Edge…
Custom licenceAuto-check: warnings
Install Verifying Store Release
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add gilgold/tabox --skill verifying-store-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gilgold/tabox verifying-store-release --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/gilgold/tabox.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/verifying-store-release .claude/skills/verifying-store-release && 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 "verifying-store-release" agent skill from https://github.com/gilgold/tabox/tree/main/.claude/skills/verifying-store-release into .claude/skills/verifying-store-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-store-release", 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/gilgold/tabox/tree/main/.claude/skills/verifying-store-releaseType 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 gilgold/tabox --skill verifying-store-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gilgold/tabox verifying-store-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gilgold/tabox.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/verifying-store-release .agents/skills/verifying-store-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verifying-store-release" agent skill from https://github.com/gilgold/tabox/tree/main/.claude/skills/verifying-store-release into .agents/skills/verifying-store-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-store-release", 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 gilgold/tabox --skill verifying-store-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gilgold/tabox verifying-store-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gilgold/tabox.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/verifying-store-release .cursor/skills/verifying-store-release && 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 "verifying-store-release" agent skill from https://github.com/gilgold/tabox/tree/main/.claude/skills/verifying-store-release into .cursor/skills/verifying-store-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-store-release", 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/gilgold/tabox.git --path .claude/skills/verifying-store-release--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 gilgold/tabox --skill verifying-store-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gilgold/tabox verifying-store-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gilgold/tabox.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/verifying-store-release .gemini/skills/verifying-store-release && 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 "verifying-store-release" agent skill from https://github.com/gilgold/tabox/tree/main/.claude/skills/verifying-store-release into .gemini/skills/verifying-store-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-store-release", 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 gilgold/tabox verifying-store-releaseInstalls 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 gilgold/tabox --skill verifying-store-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gilgold/tabox.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/verifying-store-release .github/skills/verifying-store-release && 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 "verifying-store-release" agent skill from https://github.com/gilgold/tabox/tree/main/.claude/skills/verifying-store-release into .github/skills/verifying-store-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-store-release", 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 gilgold/tabox --skill verifying-store-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gilgold/tabox verifying-store-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gilgold/tabox.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/verifying-store-release .opencode/skills/verifying-store-release && 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 "verifying-store-release" agent skill from https://github.com/gilgold/tabox/tree/main/.claude/skills/verifying-store-release into .opencode/skills/verifying-store-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verifying-store-release", 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
verifying-store-release- GitHub stars
- 116
- Token cost
- ~1.8k tokens
- SKILL.md length
- 614 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Use before any Tabox store release — before merging a release branch to main, when asked "are we good to ship / good to go / release-ready", or before publishing to the Chrome Web Store or Edge…
- Works in 5 steps: Production, not sandbox → Git identity — gilgold, never gil-wix → No Wix npm registry URLs → …
- SKILL.md covers Overview, Checklist and Verdict rules
- Calls yarn, git and gh; reaches clients2.google.com; needs PADDLE_CLIENT_TOKEN and PADDLE_WEBHOOK_SECRET
What it does
Verifying Store Release is an agent skill from gilgold/tabox. Use before any Tabox store release — before merging a release branch to main, when asked "are we good to ship / good to go / release-ready", or before publishing to the Chrome Web Store or Edge Add-ons.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Wix. The repository describes itself as: Tabox is a browser extension for Chrome and Chromium based browsers. It lets you save all your open tabs and groups into a collection that you can later click to reopen.
Example prompts
- “are we good to ship / good to go / release-ready”
- “/verifying-store-release”
Requirements
- A credential in PADDLE_CLIENT_TOKEN
- A credential in PADDLE_WEBHOOK_SECRET
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Production, not sandbox
- Git identity — gilgold, never gil-wix
- No Wix npm registry URLs
- No secrets in the bundle
- Release mechanics
What it can do on your machine
Read from SKILL.md and the folder at commit 4161ada. 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:
yarngitghcurl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
clients2.google.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
PADDLE_CLIENT_TOKENPADDLE_WEBHOOK_SECRETJWT_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verifying Store Release loads about 1.8k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 614 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: warnings
The automated check found patterns that need a careful read before installing.
- WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:70
arn.lock .yarnrc.yml server/.yarnrc.yml .npmrc server/.npmrc 2>/dev/null - NoteMentions a .env fileSKILL.md:93
dled. Local `chrome/api-keys*.json` and `.env*` files are gitignored and not copied (CopyPlugin glob is `chrome/*.js`);
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 614 words (~1,840 tokens).
“Merging to main IS publishing: .github/workflows/release.yml builds and pushes to both stores on every push to main. This checklist is the last gate before that. Run every section; report a verdict only after all commands have actually run.”
- name
- verifying-store-release
Files
Just SKILL.md in .claude/skills/verifying-store-release of gilgold/tabox.
Open the folder on GitHubat commit 4161ada
Compare with similar skills
Verifying Store Release 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 |
|---|---|---|---|---|---|---|
| Verifying Store Release this skillgilgold/tabox | 116 | — | ~1.8k | Automated safety check: Warn | Custom licence | |
| Engine E2Ewix/react-native-navigation | 13k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Linkyee Plugin BuilderZhgChgLi/linkyee | 180 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Linkyee Style DesignerZhgChgLi/linkyee | 180 | — | ~4.4k | Automated safety check: Notes | MIT | |
| Mergeremotion-dev/remotion | 63k | — | ~508 | Automated safety check: Pass | Custom licence | |
| Merge Upsymfony/symfony | 31k | — | ~4k | Automated safety check: Pass | MIT |
Similar skills
- Official
Linkyee Plugin Builder
ZhgChgLi/linkyee
A skill your agent uses when the user wants to add dynamic data (GitHub stars, latest blog posts, weather, follower counts, repo activity, anything fetched from a URL) to their linkyee site by…
Linkyee Style Designer
ZhgChgLi/linkyee
A skill your agent uses when the user wants to design, customize, or generate a custom visual theme for their linkyee site (a Hexo-like LinkTree-style static site).
- Official
Merge
remotion-dev/remotion
Wait for a Remotion pull request to become mergeable, handle merge conflicts, distinguish genuine CI failures from flakes, rerun flaky checks through the flake skill, and merge the PR.
Merge Up
symfony/symfony
Cascade-merge maintained Symfony branches from oldest to newest (e.g.
Merge
alirezarezvani/claude-skills
Merge the winning agent's branch into base, archive losers, and clean up worktrees.
Related
Works with
Questions about Verifying Store Release
What does Verifying Store Release do?
Use before any Tabox store release — before merging a release branch to main, when asked "are we good to ship / good to go / release-ready", or before publishing to the Chrome Web Store or Edge…. Verifying Store Release is an agent skill from gilgold/tabox. Use before any Tabox store release — before merging a release branch to main, when asked "are we good to ship / good to go / release-ready", or before publishing to the Chrome Web Store or Edge Add-ons.
How do I install Verifying Store Release in Claude Code?
Run `npx skills add gilgold/tabox --skill verifying-store-release -a claude-code`. Or copy the skill folder (.claude/skills/verifying-store-release in gilgold/tabox) into .claude/skills/verifying-store-release in your project. Claude Code loads it when a task matches its description.
How do I install Verifying Store Release in Codex?
Run `npx skills add gilgold/tabox --skill verifying-store-release -a codex`. Or copy the skill folder (.claude/skills/verifying-store-release in gilgold/tabox) into .agents/skills/verifying-store-release in your project. Codex loads it when a task matches its description.
Can I use Verifying Store Release 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 gilgold/tabox --skill verifying-store-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verifying-store-release, .gemini/skills/verifying-store-release, .github/skills/verifying-store-release and .opencode/skills/verifying-store-release in your project.
What does Verifying Store Release need to run?
Going by SKILL.md and its folder, Verifying Store Release needs the command-line tools its instructions call (yarn, git, gh and curl) and credentials named PADDLE_CLIENT_TOKEN, PADDLE_WEBHOOK_SECRET and JWT_SECRET. Our summary lists: A credential in PADDLE_CLIENT_TOKEN; A credential in PADDLE_WEBHOOK_SECRET.
Does Verifying Store Release access the network?
SKILL.md names 1 domain. In commands or code: clients2.google.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Verifying Store Release safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Verifying Store Release use?
Verifying Store Release 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 Verifying Store Release use?
About 1.8k tokens (SKILL.md is roughly 7.4k 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 Verifying Store Release?
Skills that share tags, products or a category with Verifying Store Release: Engine E2E (wix/react-native-navigation, 13k stars), Linkyee Plugin Builder (ZhgChgLi/linkyee, 180 stars), Linkyee Style Designer (ZhgChgLi/linkyee, 180 stars) and Merge (remotion-dev/remotion, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verifying Store Release?
gilgold (a GitHub user) maintains it in gilgold/tabox, which has 116 GitHub stars. The repository was last updated on September 29, 2026.
Source: gilgold/tabox on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.