New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Testerarmy CLI

by novuhq in novuhq/novu

Use TesterArmy CLI to create, organize, and run dashboard-managed QA tests.

MITAuto-check passed

Install Testerarmy CLI

skills CLI
$ npx skills add novuhq/novu --skill testerarmy-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install novuhq/novu testerarmy-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/novuhq/novu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testerarmy-cli .claude/skills/testerarmy-cli && rm -rf skills-src

Use ~/.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/

Facts

Skill name
testerarmy-cli
GitHub stars
40k
Token cost
~1.6k tokens
SKILL.md length
375 words
Files
3 (incl. references)
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Use TesterArmy CLI to create, organize, and run dashboard-managed QA tests.

  • Defining regression coverage
  • SKILL.md covers When to Use, Setup, Project Context and Tests, plus 6 more sections
  • Needs TESTERARMY_API_KEY
  • Adding QA flows

What it does

Testerarmy CLI is an agent skill from novuhq/novu. Use TesterArmy CLI to create, organize, and run dashboard-managed QA tests. Prefer saved tests, groups, project context, credentials, and remote runs over one-off local prompts. Trigger when defining regression coverage, adding QA flows, or wiring CI checks.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/reporting-template.md`).

The repository describes itself as: The open-source communication infrastructure for agents and products. The licence is MIT.

When your agent uses it

  • Defining regression coverage
  • Adding QA flows
  • Wiring CI checks

Example prompts

  • “/testerarmy-cli”

Requirements

  • A credential in TESTERARMY_API_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit 8a05b88. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • TESTERARMY_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Testerarmy CLI loads about 1.6k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 375 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

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

The full file from novuhq/novu at commit 8a05b88, republished under its MIT licence (© novuhq). 375 words, ~1,637 tokens.

Download SKILL.mdSave it as .claude/skills/testerarmy-cli/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
testerarmy-cli
description
Use TesterArmy CLI to create, organize, and run dashboard-managed QA tests. Prefer saved tests, groups, project context, credentials, and remote runs over one-off local prompts. Trigger when defining regression coverage, adding QA flows, or wiring CI checks.
license
MIT
metadata.author
TesterArmy
metadata.tags
testerarmy, qa, cli, dashboard-tests, regression, ci

TesterArmy CLI

Create dashboard-managed QA coverage with ta / testerarmy.

Default to saved dashboard tests, groups, project context, credentials, and remote runs. Use local ta run "..." only for quick exploration.

When to Use

  • Create persistent QA coverage for a feature or product area.
  • Convert acceptance criteria into dashboard tests.
  • Add or update smoke, regression, auth, billing, onboarding, or mobile flows.
  • Prepare CI-visible groups for PRs or releases.

Setup

Check auth:

bash
ta status --json

If needed:

bash
ta auth
TESTERARMY_API_KEY=<key> ta status --json

Discover scope:

bash
ta projects list --json
ta groups list --project <projectId> --json
ta tests list --project <projectId> --json

Use IDs exactly as returned.

Project Context

Create a project:

bash
echo '{"name":"Example","url":"https://example.com","projectType":"web"}' | ta projects create --json

Store app knowledge:

bash
echo '{"category":"site_structure","title":"Auth route","content":"Login is at /login","importance":"high"}' | ta memories create --project <projectId> --json

Memory categories: site_structure, test_insights, user_preferences.

Create credentials for login or inbox flows:

bash
echo '{"kind":"login","label":"Admin","username":"admin@example.com","password":"secret"}' | ta projects credentials-create <projectId> --json
echo '{"kind":"inbox","label":"Signup inbox"}' | ta projects credentials-create <projectId> --json

Never print real secrets in final messages.

Tests

Create:

bash
echo '{"title":"Login flow","description":"User can sign in and reach the dashboard","steps":[{"title":"Navigate to /login","type":"act"},{"title":"Sign in with the saved admin credentials","type":"login","credentialId":"<credentialId>"},{"title":"Dashboard loads and shows the project list","type":"assert"}]}' | ta tests create --project <projectId> --json

Create in a group:

bash
echo '{"title":"Pricing CTA","steps":[{"title":"Open /pricing","type":"act"},{"title":"Click the primary CTA","type":"act"},{"title":"Signup or dashboard flow starts","type":"assert"}]}' | ta tests create --project <projectId> --group <groupId> --json

Payload:

json
{
  "title": "string, required",
  "description": "string, optional",
  "platform": "web or mobile, optional",
  "steps": [
    { "title": "User action", "type": "act" },
    { "title": "Expected result", "type": "assert" },
    { "title": "Login instruction", "type": "login", "credentialId": "uuid" },
    { "title": "Use temporary email", "type": "login", "temporaryEmail": true },
    { "title": "Screenshot label", "type": "screenshot" }
  ]
}

Rules:

  • Cover one user journey.
  • Prefer 3-8 meaningful steps.
  • Use act for navigation, clicks, typing, upload, and other user actions.
  • Use assert for visible outcomes, persisted state, email delivery, or URL changes.
  • Use login with credentialId or temporaryEmail; do not put passwords in step titles.
  • Use screenshot only for important visual checkpoints.
  • Maximum 50 steps per test.

Inspect before changing:

bash
ta tests get <testId> --json

Update title, description, or steps:

bash
echo '{"title":"Updated login smoke"}' | ta tests update <testId> --json
echo '{"steps":[{"title":"Open /login","type":"act"},{"title":"Sign in","type":"login","credentialId":"<credentialId>"},{"title":"Dashboard is visible","type":"assert"}]}' | ta tests update <testId> --json

Replacing steps requires the complete array.

Groups

Create suites:

bash
echo '{"projectId":"<projectId>","name":"Smoke"}' | ta groups create --json
ta groups add-test <groupId> <testId> --json
ta groups remove-test <groupId> <testId> --json

Common groups: Smoke, Auth, Core journeys, Mobile smoke.

Show full SKILL.md (181 more words)Show less

Runs

Modes:

  • Default/local: fetches a saved test, then runs it on this machine.
  • --remote: queues the saved test in TesterArmy cloud.

Local debugging:

bash
ta tests run <testId> --url http://localhost:3000 --json
ta tests run --group <groupId> --project <projectId> --url http://localhost:3000 --parallel 3 --json

Remote validation:

bash
ta tests run <testId> --remote --wait --json
ta tests run --group <groupId> --project <projectId> --remote --wait --json

Defaults:

  • No --remote: local browser execution.
  • --remote: cloud execution.
  • --wait: wait for remote results.
  • Local-only flags such as --headed, --browser, --timeout, and --system-prompt-file are ignored with --remote.
  • Remote group runs can use --environment production|preview.
  • Remote single-test runs can use --mode fast|deep.

CI:

bash
ta ci --group <groupId> --project <projectId> --target-url https://staging.example.com --json

Runs:

bash
ta runs list --project <projectId> --json
ta runs get <runId> --json
ta runs wait <runId> --timeout 600000 --json
ta runs cancel <runId> --json

Mobile App Coverage

Upload an iOS Simulator app before cloud runs:

bash
ta upload-app --app-path ios/build/Build/Products/Release-iphonesimulator/MyApp.app --project <projectId> --json
ta ci --group <groupId> --project <projectId> --app-id <appId> --delete-app-after-run --json

Supported uploads: .app, .app.zip, .zip, .app.tar.gz, .tar.gz, .tgz. .ipa and Android artifacts are not supported yet.

Local Prompt

ta run <prompt> runs an ad hoc local browser test:

bash
ta run "check pricing CTA" --url https://example.com --json

Use only to explore before creating or updating dashboard tests. Use ta tests create and ta tests run --group for durable workflows.

Reporting

Report:

  • Project ID/name
  • Test IDs and titles created or updated
  • Group IDs/names touched
  • Remote validation command and result, if run
  • Run ID or artifact/output path, if available

Do not claim durable coverage unless ta tests create or ta tests update ran.

References

FileDescription
reporting-template.mdDashboard coverage report template

© novuhq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/testerarmy-cli of novuhq/novu.

  • SKILL.md
  • agents/openai.yaml
  • references/reporting-template.md

Open the folder on GitHubat commit 8a05b88

Compare with similar skills

Testerarmy CLI 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.

Testerarmy CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testerarmy CLI this skillnovuhq/novu40k—~1.6kAutomated safety check: PassMIT
Managing DashboardsPostHog/posthog40k—~2.7kAutomated safety check: PassCustom licence
Manage Dashboard WidgetsPostHog/posthog40k—~2.3kAutomated safety check: PassCustom licence
DashboardInsForge/InsForge13k—~2.3kAutomated safety check: PassApache-2.0
Secrets Managementdavila7/claude-code-templates32k12 repos~2kAutomated safety check: PassMIT
Organizationthedaviddias/Front-End-Checklist74k—~609Automated safety check: PassMIT

Similar skills

  • Managing Dashboards

    PostHog/posthog

    Official

    Guides PostHog engineers through dashboard platform and scene changes.

    40k GitHub stars~2.7k tokensUpdated today
    Backend & APIsAuto-check passed

  • Manage Dashboard Widgets

    PostHog/posthog

    Official

    Guides PostHog engineers through dashboard widget platform work — ship a new widgettype (WIDGETREGISTRY, catalog, runwidgets, WidgetCard) or update a shipped type (config, query, layout, RBAC, tile…

    40k GitHub stars~2.3k tokensUpdated today
    Backend & APIsAuto-check passed

  • Dashboard

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's shared dashboard package.

    13k GitHub stars~2.3k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

  • Secrets Management

    davila7/claude-code-templates

    Secure secrets management practices for CI/CD pipelines using Vault, AWS Secrets Manager, and other tools.

    32k GitHub starsUsed in 12 repos~2k tokens
    DevOps & CloudAuto-check passed

  • Organization

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing structured data on a business or brand website homepage.

    74k GitHub stars~609 tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

  • Project Manager

    RightNow-AI/openfang

    Project management expert for Agile, estimation, risk management, and stakeholder communication

    18k GitHub stars~960 tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed

More from novuhq/novu

All 28 skills in this repo

  • Ink Tui Wizard

    novuhq/novu

    Build terminal user interfaces (TUIs) using Ink (React for CLIs) and @inkjs/ui with a reactive, session-driven wizard pattern.

    40k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Novu Design Workflow

    novuhq/novu

    Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state.

    40k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Novu Inbox Integration

    novuhq/novu

    Integrate Novu's in-app notification inbox into web applications.

    40k GitHub stars~5.2k tokensUpdated today
    Auto-check passed

  • Novu Manage Preferences

    novuhq/novu

    Configure notification preferences in Novu at the workflow and subscriber level.

    40k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Novu Manage Subscribers

    novuhq/novu

    Create, update, search, and delete subscribers in Novu. An agent skill from novuhq/novu.

    40k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Novu Trigger Notification

    novuhq/novu

    Trigger Novu notification workflows to send messages across email, SMS, push, chat, and in-app channels.

    40k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Testerarmy CLI

What does Testerarmy CLI do?

Use TesterArmy CLI to create, organize, and run dashboard-managed QA tests. Testerarmy CLI is an agent skill from novuhq/novu. Use TesterArmy CLI to create, organize, and run dashboard-managed QA tests.

When should I use Testerarmy CLI?

Testerarmy CLI fits situations like: defining regression coverage; adding QA flows; wiring CI checks.

How do I install Testerarmy CLI in Claude Code?

Run `npx skills add novuhq/novu --skill testerarmy-cli -a claude-code`. Or copy the skill folder (.agents/skills/testerarmy-cli in novuhq/novu) into .claude/skills/testerarmy-cli in your project. Claude Code loads it when a task matches its description.

How do I install Testerarmy CLI in Codex?

Run `npx skills add novuhq/novu --skill testerarmy-cli -a codex`. Or copy the skill folder (.agents/skills/testerarmy-cli in novuhq/novu) into .agents/skills/testerarmy-cli in your project. Codex loads it when a task matches its description.

Can I use Testerarmy CLI 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 novuhq/novu --skill testerarmy-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testerarmy-cli, .gemini/skills/testerarmy-cli, .github/skills/testerarmy-cli and .opencode/skills/testerarmy-cli in your project.

What does Testerarmy CLI need to run?

Going by SKILL.md and its folder, Testerarmy CLI needs credentials named TESTERARMY_API_KEY. Our summary lists: A credential in TESTERARMY_API_KEY.

Does Testerarmy CLI access the network?

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.

Is Testerarmy CLI 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 Testerarmy CLI use?

Testerarmy CLI is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testerarmy CLI use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 155 tokens, read only when the agent opens those files.

What are the alternatives to Testerarmy CLI?

Skills that share tags, products or a category with Testerarmy CLI: Managing Dashboards (PostHog/posthog, 40k stars), Manage Dashboard Widgets (PostHog/posthog, 40k stars), Dashboard (InsForge/InsForge, 13k stars) and Secrets Management (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testerarmy CLI?

novuhq (a GitHub organization) maintains it in novuhq/novu, which has 40,134 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 2026.

Source: novuhq/novu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.