Meridian Budget Optimization
google/meridian
Reopens a fitted Meridian MMM from a saved file and runs budget allocation scenarios, producing an HTML report and a Python script that repeats the run.
TestSprite verification loop — after finishing a feature or fix in a TestSprite-tested repo, use the testsprite CLI to run the relevant TestSprite tests against the change and inspect any failure…
Install Testsprite Verify
$ npx skills add Gingiris-1031/Competitor-analysis-tool --skill testsprite-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Gingiris-1031/Competitor-analysis-tool testsprite-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/Gingiris-1031/Competitor-analysis-tool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/testsprite-verify .claude/skills/testsprite-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 "testsprite-verify" agent skill from https://github.com/Gingiris-1031/Competitor-analysis-tool/tree/main/.claude/skills/testsprite-verify into .claude/skills/testsprite-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testsprite-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/Gingiris-1031/Competitor-analysis-tool/tree/main/.claude/skills/testsprite-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 Gingiris-1031/Competitor-analysis-tool --skill testsprite-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Gingiris-1031/Competitor-analysis-tool testsprite-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gingiris-1031/Competitor-analysis-tool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/testsprite-verify .agents/skills/testsprite-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 "testsprite-verify" agent skill from https://github.com/Gingiris-1031/Competitor-analysis-tool/tree/main/.claude/skills/testsprite-verify into .agents/skills/testsprite-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testsprite-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 Gingiris-1031/Competitor-analysis-tool --skill testsprite-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Gingiris-1031/Competitor-analysis-tool testsprite-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gingiris-1031/Competitor-analysis-tool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/testsprite-verify .cursor/skills/testsprite-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 "testsprite-verify" agent skill from https://github.com/Gingiris-1031/Competitor-analysis-tool/tree/main/.claude/skills/testsprite-verify into .cursor/skills/testsprite-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testsprite-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/Gingiris-1031/Competitor-analysis-tool.git --path .claude/skills/testsprite-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 Gingiris-1031/Competitor-analysis-tool --skill testsprite-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Gingiris-1031/Competitor-analysis-tool testsprite-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gingiris-1031/Competitor-analysis-tool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/testsprite-verify .gemini/skills/testsprite-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 "testsprite-verify" agent skill from https://github.com/Gingiris-1031/Competitor-analysis-tool/tree/main/.claude/skills/testsprite-verify into .gemini/skills/testsprite-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testsprite-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 Gingiris-1031/Competitor-analysis-tool testsprite-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 Gingiris-1031/Competitor-analysis-tool --skill testsprite-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Gingiris-1031/Competitor-analysis-tool.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/testsprite-verify .github/skills/testsprite-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 "testsprite-verify" agent skill from https://github.com/Gingiris-1031/Competitor-analysis-tool/tree/main/.claude/skills/testsprite-verify into .github/skills/testsprite-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testsprite-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 Gingiris-1031/Competitor-analysis-tool --skill testsprite-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 Gingiris-1031/Competitor-analysis-tool testsprite-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gingiris-1031/Competitor-analysis-tool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/testsprite-verify .opencode/skills/testsprite-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 "testsprite-verify" agent skill from https://github.com/Gingiris-1031/Competitor-analysis-tool/tree/main/.claude/skills/testsprite-verify into .opencode/skills/testsprite-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testsprite-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
testsprite-verify- GitHub stars
- 110
- Token cost
- ~5.5k tokens
- SKILL.md length
- 2,337 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- None found
At a glance
TestSprite verification loop — after finishing a feature or fix in a TestSprite-tested repo, use the testsprite CLI to run the relevant TestSprite tests against the change and inspect any failure…
- Works in 6 steps: Preflight → Find the project → Decide what to test → …
- Code has changed outside docs/config and is about to be reported complete — by running an existing test that covers the change
- SKILL.md covers When to run, When to skip, The one-test minimum and 1. Preflight, plus 6 more sections
- Calls git
What it does
Testsprite Verify is an agent skill from Gingiris-1031/Competitor-analysis-tool. TestSprite verification loop — after finishing a feature or fix in a TestSprite-tested repo, use the testsprite CLI to run the relevant TestSprite tests against the change and inspect any failure artifacts before reporting the work as done. Use whenever code has changed outside docs/config and is about to be reported complete — by running an existing test that covers the change, or by creating a new TestSprite test (a frontend plan, or a backend Python assertion) and running it to a terminal verdict.
Its SKILL.md is about 5.5k 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 Marketing & SEO. It works with Python. The repository describes itself as: AI competitor analysis backend powering analook.com. Generates competitor teardowns from any URL via FastAPI + Supabase.
When your agent uses it
- Code has changed outside docs/config and is about to be reported complete — by running an existing test that covers the change
- By creating a new TestSprite test (a frontend plan
- A backend Python assertion) and running it to a terminal verdict
Example prompts
- “/testsprite-verify”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Preflight
- Find the project
- Decide what to test
- Run
- On failure → download the artifact
- Report
What it can do on your machine
Read from SKILL.md and the folder at commit 92d6b12. 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:
git
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
Testsprite Verify loads about 5.5k tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 2,337 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 2,337 words (~5,508 tokens).
“The verification loop that flies your just-shipped feature through the TestSprite CLI and reports back.”
- name
- testsprite-verify
Files
Just SKILL.md in .claude/skills/testsprite-verify of Gingiris-1031/Competitor-analysis-tool.
Open the folder on GitHubat commit 92d6b12
Compare with similar skills
Testsprite 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 |
|---|---|---|---|---|---|---|
| Testsprite Verify this skillGingiris-1031/Competitor-analysis-tool | 110 | — | ~5.5k | Automated safety check: Pass | None | |
| Meridian Budget Optimizationgoogle/meridian | 1.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Dev Localsuperdesigndev/treg | 4.5k | — | ~623 | Automated safety check: Pass | Custom licence | |
| Last 30 Days Trend Researchnexu-io/open-design | 100k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Beyondseobeyondtahir/beyondseo | 155 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Meta Ad Builderkrusemediallc/arcads-claude-code | 1.6k | — | ~1.7k | Automated safety check: Notes | MIT |
Similar skills
- Official
Dev Local
superdesigndev/treg
One-command local dev stack for tools-registry. An agent skill from superdesigndev/treg.
Last 30 Days Trend Research
nexu-io/open-design
Produces a cited Markdown briefing on recent community sentiment and social reaction to a topic, labeling every source it could not actually check.
Beyondseo
beyondtahir/beyondseo
Audit websites, apply authorised SEO improvements and plan content, competitors and backlinks with evidence, design checks and optional project monitoring.
Meta Ad Builder
krusemediallc/arcads-claude-code
Publish finished creatives as live Meta (Facebook/Instagram) ads via the Meta Marketing API, plus research and ad-copy support.
Market Research Reports
K-Dense-AI/claude-scientific-writer
Builds market research reports and market sizing or forecast scenarios in which every claim, source, assumption and uncertainty can be traced and audited.
More from Gingiris-1031/Competitor-analysis-tool
All 9 skills in this repoGingiris B2b Growth
Gingiris-1031/Competitor-analysis-tool
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF.
Gingiris GitHub Star Growth
Gingiris-1031/Competitor-analysis-tool
🇺🇸 GitHub Star Sustained Growth Playbook — Monthly 300+ star growth SOP.
Gingiris Ugc Matrix
Gingiris-1031/Competitor-analysis-tool
🇺🇸 UGC Matrix Growth Playbook — Scale user-generated content with AI + real creators.
Gingiris User Interview
Gingiris-1031/Competitor-analysis-tool
🇺🇸 User Interview & Cold-Start Operations Playbook — Battle-tested framework from HeyGen's 937 interviews to PMF.
Gingiris Aso Growth
Gingiris-1031/Competitor-analysis-tool
🇺🇸 ASO & Mobile App Growth Playbook 2026 — Complete App Store Optimization guide.
Gingiris Go Global
Gingiris-1031/Competitor-analysis-tool
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization.
Related
Works with
Categories
Questions about Testsprite Verify
What does Testsprite Verify do?
TestSprite verification loop — after finishing a feature or fix in a TestSprite-tested repo, use the testsprite CLI to run the relevant TestSprite tests against the change and inspect any failure…. Testsprite Verify is an agent skill from Gingiris-1031/Competitor-analysis-tool. TestSprite verification loop — after finishing a feature or fix in a TestSprite-tested repo, use the testsprite CLI to run the relevant TestSprite tests against the change and inspect any failure artifacts before reporting the work as done.
When should I use Testsprite Verify?
Testsprite Verify fits situations like: code has changed outside docs/config and is about to be reported complete — by running an existing test that covers the change; by creating a new TestSprite test (a frontend plan; A backend Python assertion) and running it to a terminal verdict.
How do I install Testsprite Verify in Claude Code?
Run `npx skills add Gingiris-1031/Competitor-analysis-tool --skill testsprite-verify -a claude-code`. Or copy the skill folder (.claude/skills/testsprite-verify in Gingiris-1031/Competitor-analysis-tool) into .claude/skills/testsprite-verify in your project. Claude Code loads it when a task matches its description.
How do I install Testsprite Verify in Codex?
Run `npx skills add Gingiris-1031/Competitor-analysis-tool --skill testsprite-verify -a codex`. Or copy the skill folder (.claude/skills/testsprite-verify in Gingiris-1031/Competitor-analysis-tool) into .agents/skills/testsprite-verify in your project. Codex loads it when a task matches its description.
Can I use Testsprite 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 Gingiris-1031/Competitor-analysis-tool --skill testsprite-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/testsprite-verify, .gemini/skills/testsprite-verify, .github/skills/testsprite-verify and .opencode/skills/testsprite-verify in your project.
What does Testsprite Verify need to run?
Going by SKILL.md and its folder, Testsprite Verify needs the command-line tools its instructions call (git). Our summary lists: Python 3.
Does Testsprite 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 Testsprite 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 Testsprite Verify use?
No licence was found for Testsprite Verify or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Testsprite Verify use?
About 5.5k tokens (SKILL.md is roughly 22k 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 Testsprite Verify?
Skills that share tags, products or a category with Testsprite Verify: Meridian Budget Optimization (google/meridian, 1.6k stars), Dev Local (superdesigndev/treg, 4.5k stars), Last 30 Days Trend Research (nexu-io/open-design, 100k stars) and Beyondseo (beyondtahir/beyondseo, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Testsprite Verify?
Gingiris-1031 (a GitHub user) maintains it in Gingiris-1031/Competitor-analysis-tool, which has 110 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 5, 2026.
Source: Gingiris-1031/Competitor-analysis-tool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.