Agent skill

Running Tests

by NangoHQ in NangoHQ/nango

A skill your agent uses when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns

Custom licenceAuto-check passedTesting & QA

Install Running Tests

skills CLI
$ npx skills add NangoHQ/nango --skill running-tests -a claude-code

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

GitHub CLI
$ gh skill install NangoHQ/nango running-tests --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/NangoHQ/nango.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/running-tests .claude/skills/running-tests && 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
running-tests
GitHub stars
13k
Token cost
~876 tokens
SKILL.md length
251 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Custom licence

At a glance

A skill your agent uses when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns

  • Running tests in the Nango monorepo - knows unit vs integration configs
  • SKILL.md covers Overview, Quick Reference, Running Specific Tests and Before Running Tests, plus 4 more sections
  • Calls npm
  • Vitest commands

What it does

Running Tests is an agent skill from NangoHQ/nango. Use when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns

Its SKILL.md is about 880 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 Unit testing, Integration testing and Monorepo tooling. It works with Docker, Vitest and npm. The repository describes itself as: Connect your agents & product to 1,000 APIs.

When your agent uses it

  • Running tests in the Nango monorepo - knows unit vs integration configs
  • Vitest commands
  • Common test patterns

Example prompts

  • “/running-tests”

Requirements

  • Node.js
  • Docker

What it can do on your machine

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

    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npm, 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

Running Tests loads about 876 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 251 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~876

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 251 words (~876 tokens).

“Nango uses Vitest with three separate configs for unit, integration, and CLI tests. Getting the config wrong silently runs zero tests.”

— opening of SKILL.md by NangoHQ, Custom licence
name
running-tests

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/running-tests of NangoHQ/nango.

Open the folder on GitHubat commit b07eb10

Compare with similar skills

Running Tests 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.

Running Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Running Tests this skillNangoHQ/nango13k—~876Automated safety check: PassCustom licence
Flowfile Testing And ValidationEdwardvaneechoud/Flowfile375—~8.3kAutomated safety check: NotesMIT
Create Saleor Packagesaleor/apps162—~608Automated safety check: PassCustom licence
Test Writing WorkflowiOfficeAI/AionUi33k1 repos~1.2kAutomated safety check: PassApache-2.0
Go Redis Client Test Runnerredis/go-redis22k—~786Automated safety check: PassBSD-2-Clause
Ckeditor5 TestingTriliumNext/Trilium38k—~3.3kAutomated safety check: PassAGPL-3.0

Similar skills

  • Flowfile Testing And Validation

    Edwardvaneechoud/Flowfile

    Exact per-package pytest/vitest/playwright commands, the registered pytest markers and which need Docker, the testutils Docker fixture matrix, the shared-test-DB isolation model and its failure…

    375 GitHub stars~8.3k tokensUpdated today
    Testing & QAAuto-check: notes
  • Scaffold a new shared package in the saleor-apps monorepo under ./packages/.

    162 GitHub stars~608 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Test Writing Workflow

    iOfficeAI/AionUi

    Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.

    33k GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed
  • Official

    Explains how to run go-redis tests: the Docker Compose stack, make targets, focusing a single Ginkgo spec, the e2e suite and the version environment variables.

    22k GitHub stars~786 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Ckeditor5 Testing

    TriliumNext/Trilium

    Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.

    38k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Scaffold a new workspace package in the c15t monorepo. An agent skill from c15t/c15t.

    1.9k GitHub stars~913 tokensUpdated today
    Testing & QAAuto-check passed

More from NangoHQ/nango

All 9 skills in this repo
  • Creating Skills

    NangoHQ/nango

    A skill your agent uses when creating new agent skills or improving existing ones - ensures skills are discoverable, scannable, and effective through proper structure, discovery optimization, and…

    13k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check passed
  • Adding Audit Events

    NangoHQ/nango

    A skill your agent uses when adding or changing an audited Nango endpoint, or deciding one shouldn't be audited - covers the vocabulary table, metadata typing, spec placement, mount ordering, and…

    13k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • A skill your agent uses when building the Nango monorepo or verifying TypeScript compilation - covers build commands, project references, common tsc errors, and package dependency order

    13k GitHub stars~902 tokensUpdated today
    Auto-check passed
  • A skill your agent uses when adding or editing Nango database migrations - covers migration directory selection, timestamped .cjs naming, matching recent migration style, down migration decisions…

    13k GitHub stars~449 tokensUpdated today
    Auto-check passed
  • A skill your agent uses when adding or editing Nango integration documentation - creates and maintains integration pages, setup guides, connect guides, navigation, and provider metadata following…

    13k GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • A skill your agent uses when running the Nango application locally for development and browser testing - covers Docker services, dev commands, service URLs, and troubleshooting startup issues

    13k GitHub stars~3.8k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Running Tests

What does Running Tests do?

A skill your agent uses when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns. Running Tests is an agent skill from NangoHQ/nango.

When should I use Running Tests?

Running Tests fits situations like: running tests in the Nango monorepo - knows unit vs integration configs; vitest commands; common test patterns.

How do I install Running Tests in Claude Code?

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

How do I install Running Tests in Codex?

Run `npx skills add NangoHQ/nango --skill running-tests -a codex`. Or copy the skill folder (.agents/skills/running-tests in NangoHQ/nango) into .agents/skills/running-tests in your project. Codex loads it when a task matches its description.

Can I use Running Tests 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 NangoHQ/nango --skill running-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/running-tests, .gemini/skills/running-tests, .github/skills/running-tests and .opencode/skills/running-tests in your project.

What does Running Tests need to run?

Going by SKILL.md and its folder, Running Tests needs the command-line tools its instructions call (npm). Our summary lists: Node.js; Docker.

Does Running Tests access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Running Tests 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 Running Tests use?

Running Tests 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 Running Tests use?

About 876 tokens (SKILL.md is roughly 3.5k 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 Running Tests?

Skills that share tags, products or a category with Running Tests: Flowfile Testing And Validation (Edwardvaneechoud/Flowfile, 375 stars), Create Saleor Package (saleor/apps, 162 stars), Test Writing Workflow (iOfficeAI/AionUi, 33k stars) and Go Redis Client Test Runner (redis/go-redis, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Running Tests?

NangoHQ (a GitHub organization) maintains it in NangoHQ/nango, which has 12,575 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

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