Agent skill

Testing

by trieb-work in trieb-work/nextjs-turbo-redis-cache

Run tests and add Next.js version coverage for the cache handler.

MITAuto-check passedTesting & QA

Install Testing

skills CLI

$ npx skills add trieb-work/nextjs-turbo-redis-cache --skill testing -a claude-code

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

GitHub CLI

$ gh skill install trieb-work/nextjs-turbo-redis-cache testing --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/trieb-work/nextjs-turbo-redis-cache.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/testing .claude/skills/testing && 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/

Paste into Claude Code

Install the "testing" agent skill from https://github.com/trieb-work/nextjs-turbo-redis-cache/tree/main/.cursor/skills/testing into .claude/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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

$skill-installer install https://github.com/trieb-work/nextjs-turbo-redis-cache/tree/main/.cursor/skills/testing

Type 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.

skills CLI

$ npx skills add trieb-work/nextjs-turbo-redis-cache --skill testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install trieb-work/nextjs-turbo-redis-cache testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trieb-work/nextjs-turbo-redis-cache.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/testing .agents/skills/testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "testing" agent skill from https://github.com/trieb-work/nextjs-turbo-redis-cache/tree/main/.cursor/skills/testing into .agents/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.

skills CLI

$ npx skills add trieb-work/nextjs-turbo-redis-cache --skill testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install trieb-work/nextjs-turbo-redis-cache testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trieb-work/nextjs-turbo-redis-cache.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/testing .cursor/skills/testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "testing" agent skill from https://github.com/trieb-work/nextjs-turbo-redis-cache/tree/main/.cursor/skills/testing into .cursor/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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

$ gemini skills install https://github.com/trieb-work/nextjs-turbo-redis-cache.git --path .cursor/skills/testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add trieb-work/nextjs-turbo-redis-cache --skill testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install trieb-work/nextjs-turbo-redis-cache testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trieb-work/nextjs-turbo-redis-cache.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/testing .gemini/skills/testing && rm -rf skills-src

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

Paste into Gemini CLI

Install the "testing" agent skill from https://github.com/trieb-work/nextjs-turbo-redis-cache/tree/main/.cursor/skills/testing into .gemini/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.

GitHub CLI

$ gh skill install trieb-work/nextjs-turbo-redis-cache testing

Installs 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).

skills CLI

$ npx skills add trieb-work/nextjs-turbo-redis-cache --skill testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/trieb-work/nextjs-turbo-redis-cache.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/testing .github/skills/testing && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "testing" agent skill from https://github.com/trieb-work/nextjs-turbo-redis-cache/tree/main/.cursor/skills/testing into .github/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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.

skills CLI

$ npx skills add trieb-work/nextjs-turbo-redis-cache --skill testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install trieb-work/nextjs-turbo-redis-cache testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/trieb-work/nextjs-turbo-redis-cache.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/testing .opencode/skills/testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "testing" agent skill from https://github.com/trieb-work/nextjs-turbo-redis-cache/tree/main/.cursor/skills/testing into .opencode/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", 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: testing
GitHub stars: 151
Token cost: ~1.1k tokens
SKILL.md length: 262 words
Files: 1
Skills in repo: 1
Repo updated: Sep 24, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run tests and add Next.js version coverage for the cache handler.

Works in 4 steps: Standard Integration Test App → Cache Components Test App (Next.js 16+… → Checklist After Adding → …
Adding a new Next.js version to the test matrix
SKILL.md covers Running Tests, Test Structure, Adding a New Next.js Version and Environment Variables, plus 1 more section
Calls pnpm

What it does

Testing is an agent skill from trieb-work/nextjs-turbo-redis-cache. Run tests and add Next.js version coverage for the cache handler. Use when running tests, adding a new Next.js version to the test matrix, creating test apps, or debugging CI failures.

Its SKILL.md is about 1.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 Caching and Failing and flaky tests. It works with Next.js, Redis, Playwright and pnpm. The repository describes itself as: Designed for speed, scalability, and optimized performance, nextjs-turbo-redis-cache is your go-to solution Next.js cache handler for demanding production environments. If you…. The licence is MIT.

When your agent uses it

Adding a new Next.js version to the test matrix
Creating test apps
Debugging CI failures

Example prompts

“/testing”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Standard Integration Test App
Cache Components Test App (Next.js 16+ only)
Checklist After Adding
Removing a Version

What it can do on your machine

Read from SKILL.md and the folder at commit c895dce. 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:
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, 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

Testing loads about 1.1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 262 words of instructions outside code blocks.

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

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 trieb-work/nextjs-turbo-redis-cache at commit c895dce, republished under its MIT licence (© trieb-work). 262 words, ~1,117 tokens.

Download SKILL.mdSave it as .claude/skills/testing/SKILL.md (or your agent's skills folder).

name: testing
description: Run tests and add Next.js version coverage for the cache handler. Use when running tests, adding a new Next.js version to the test matrix, creating test apps, or debugging CI failures.

Testing

Running Tests

bash

# Unit tests (fast, no Redis needed)
pnpm test:unit
pnpm test:unit:watch          # watch mode
pnpm test:unit:coverage       # with coverage

# Integration tests (needs Redis + pre-built Next.js app)
pnpm test:integration
pnpm test:integration:build-id-prefix
pnpm test:integration:cache-components

# E2E / Playwright for cached components (needs Redis, auto-starts Next.js app)
pnpm test:e2e

Test Structure

test/
├── playwright/              # E2E (Playwright browser tests)
├── vitest/
│   ├── unit/                # Unit tests (no external deps)
│   └── integration/         # Integration tests (Redis + Next.js)
│       └── cache-components/
└── nextjs-test-projects/    # Shared Next.js app fixtures

For details on each layer, see test/README.md.

Adding a New Next.js Version

1. Standard Integration Test App

For testing the core cache handler against a new Next.js version (e.g. 16.5.0):

bash

cp -r test/nextjs-test-projects/next-app-16-2-6 test/nextjs-test-projects/next-app-16-5-0
rm -rf test/nextjs-test-projects/next-app-16-5-0/{node_modules,.next,pnpm-lock.yaml}

Edit test/nextjs-test-projects/next-app-16-5-0/package.json:

Change "name" to "next-app-16-5-0"
Change "next" version to "16.5.0"
Change "eslint-config-next" version to "16.5.0"

Then add the app to the CI integration matrix in .github/workflows/ci.yml:

yaml

# In the `integration` job → strategy.matrix.next-test-app
- next-app-16-5-0

2. Cache Components Test App (Next.js 16+ only)

If the new version supports use cache / cacheTag / cacheLife:

bash

cp -r test/nextjs-test-projects/next-app-16-2-6-cache-components test/nextjs-test-projects/next-app-16-5-0-cache-components
rm -rf test/nextjs-test-projects/next-app-16-5-0-cache-components/{node_modules,.next,pnpm-lock.yaml}

Edit the package.json:

Change "name" to "next-app-16-5-0-cache-components"
Change "next" to "16.5.0"
Change "eslint-config-next" to "16.5.0"

Then add it to both CI matrix jobs in .github/workflows/ci.yml:

yaml

# In `integration-cache-components` → strategy.matrix.cache-components-app
- next-app-16-5-0-cache-components

# In `e2e` → strategy.matrix.cache-components-app
- next-app-16-5-0-cache-components

3. Checklist After Adding

package.json has correct Next.js version + matching eslint-config-next
"@trieb.work/nextjs-turbo-redis-cache": "file:../../../" path is correct
No leftover node_modules/, .next/, or pnpm-lock.yaml from the copy
CI matrix updated (integration and/or cache-components + e2e)
test/README.md → "Next.js Test Projects" table updated
Run cd test/nextjs-test-projects/next-app-16-5-0 && pnpm install && pnpm build to verify it builds

4. Removing a Version

Remove the folder, remove it from the CI matrix entries, and update test/README.md.

Environment Variables

Variable	Default	Purpose
`NEXT_TEST_APP`	`next-app-15-4-11`	Which app for `pnpm test:integration`
`CACHE_COMPONENTS_APP`	`next-app-16-2-6-cache-components`	Which app for cache-components tests
`PLAYWRIGHT_TEST_APP`	`next-app-16-2-6-cache-components`	Which app Playwright starts
`PLAYWRIGHT_BASE_URL`	`http://localhost:3101`	Override to use an already-running server
`SKIP_BUILD`	—	Skip Next.js build in integration tests
`DEBUG_INTEGRATION`	—	Print child process output

Writing New Tests

Unit tests: Add *.test.ts in test/vitest/unit/. No Redis, no Next.js. Use mocks.
Integration tests: Add *.test.ts in test/vitest/integration/. Spawn Next.js, use fetch(), check Redis.
E2E tests: Add *.spec.ts in test/playwright/. Use Playwright browser automation.

Unit tests use .test.ts extension. Playwright tests use .spec.ts extension.

Files

Just SKILL.md in .cursor/skills/testing of trieb-work/nextjs-turbo-redis-cache.

Open the folder on GitHubat commit c895dce

Compare with similar skills

Testing 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.

Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Testing this skilltrieb-work/nextjs-turbo-redis-cache	151	—	~1.1k	Automated safety check: Pass	MIT	13 days ago
Debuggingidavidov13/agentic-playwright	223	—	~6.2k	Automated safety check: Notes	MIT	6 days ago
Ckeditor5 TestingTriliumNext/Trilium	38k	—	~3.3k	Automated safety check: Pass	AGPL-3.0	today
UI Previewtingly-dev/tingly-box	351	—	~2k	Automated safety check: Notes	MPL-2.0	today
Proxy Setupasmyshlyaev177/test-proxy-recorder	112	—	~4.3k	Automated safety check: Pass	MIT	3 days ago
NodeHsienW/chat-gun	143	—	~1.6k	Automated safety check: Pass	Custom licence	3 days ago

Similar skills

Debugging
idavidov13/agentic-playwright
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema…
223 GitHub stars~6.2k tokensUpdated 6 days ago
Testing & QAAuto-check: notes
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
UI Preview
tingly-dev/tingly-box
Capture headless-Chrome screenshots of the tingly-box frontend (running locally in mock mode) so frontend changes can be visually verified in environments without a real browser.
351 GitHub stars~2k tokensUpdated today
Testing & QAAuto-check: notes
Proxy Setup
asmyshlyaev177/test-proxy-recorder
Set up test-proxy-recorder for any Playwright project. An agent skill from asmyshlyaev177/test-proxy-recorder.
112 GitHub stars~4.3k tokensUpdated 3 days ago
Testing & QAAuto-check passed
Node
HsienW/chat-gun
Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging…
143 GitHub stars~1.6k tokensUpdated 3 days ago
Testing & QAAuto-check passed
Playwright Pnpm Workspace
mizchi/luna.mbt
A skill your agent uses when running Playwright tests in this repo (luna.mbt) and either the test fails to discover specs ("did not expect test.describe()" / "two different versions of…
173 GitHub stars~1.2k tokensUpdated 21 days ago
Testing & QAAuto-check passed

Works with

Questions about Testing

What does Testing do?

Run tests and add Next.js version coverage for the cache handler. Testing is an agent skill from trieb-work/nextjs-turbo-redis-cache.js version coverage for the cache handler.

When should I use Testing?

Testing fits situations like: adding a new Next.js version to the test matrix; creating test apps; debugging CI failures.

How do I install Testing in Claude Code?

Run `npx skills add trieb-work/nextjs-turbo-redis-cache --skill testing -a claude-code`. Or copy the skill folder (.cursor/skills/testing in trieb-work/nextjs-turbo-redis-cache) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.

How do I install Testing in Codex?

Run `npx skills add trieb-work/nextjs-turbo-redis-cache --skill testing -a codex`. Or copy the skill folder (.cursor/skills/testing in trieb-work/nextjs-turbo-redis-cache) into .agents/skills/testing in your project. Codex loads it when a task matches its description.

Can I use Testing 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 trieb-work/nextjs-turbo-redis-cache --skill testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.

What does Testing need to run?

Going by SKILL.md and its folder, Testing needs the command-line tools its instructions call (pnpm).

Does Testing 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 Testing 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 Testing use?

Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing use?

About 1.1k tokens (SKILL.md is roughly 4.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 Testing?

Skills that share tags, products or a category with Testing: Debugging (idavidov13/agentic-playwright, 223 stars), Ckeditor5 Testing (TriliumNext/Trilium, 38k stars), UI Preview (tingly-dev/tingly-box, 351 stars) and Proxy Setup (asmyshlyaev177/test-proxy-recorder, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing?

trieb-work (a GitHub organization) maintains it in trieb-work/nextjs-turbo-redis-cache, which has 151 GitHub stars. The repository was last updated on September 24, 2026.

Source: trieb-work/nextjs-turbo-redis-cache on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Testing

Running Tests

Test Structure

Adding a New Next.js Version

1. Standard Integration Test App

2. Cache Components Test App (Next.js 16+ only)

3. Checklist After Adding

4. Removing a Version

Environment Variables

Writing New Tests

Files

Compare with similar skills

Similar skills

Debugging

Ckeditor5 Testing

UI Preview

Proxy Setup

Node

Playwright Pnpm Workspace

Related

Questions about Testing