Agent skill

Add Acceptance Test

Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022).

MITAuto-check passedTesting & QA

Install Add Acceptance Test

skills CLI

$ npx skills add talkincode/toughradius --skill add-acceptance-test -a claude-code

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

GitHub CLI

$ gh skill install talkincode/toughradius add-acceptance-test --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/talkincode/toughradius.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-acceptance-test .claude/skills/add-acceptance-test && 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 "add-acceptance-test" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/add-acceptance-test into .claude/skills/add-acceptance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-acceptance-test", 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/talkincode/toughradius/tree/main/.agents/skills/add-acceptance-test

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 talkincode/toughradius --skill add-acceptance-test -a codex

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

GitHub CLI

$ gh skill install talkincode/toughradius add-acceptance-test --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/talkincode/toughradius.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/add-acceptance-test .agents/skills/add-acceptance-test && 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 "add-acceptance-test" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/add-acceptance-test into .agents/skills/add-acceptance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-acceptance-test", 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 talkincode/toughradius --skill add-acceptance-test -a cursor

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

GitHub CLI

$ gh skill install talkincode/toughradius add-acceptance-test --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/talkincode/toughradius.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/add-acceptance-test .cursor/skills/add-acceptance-test && 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 "add-acceptance-test" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/add-acceptance-test into .cursor/skills/add-acceptance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-acceptance-test", 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/talkincode/toughradius.git --path .agents/skills/add-acceptance-test

--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 talkincode/toughradius --skill add-acceptance-test -a gemini-cli

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

GitHub CLI

$ gh skill install talkincode/toughradius add-acceptance-test --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/talkincode/toughradius.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/add-acceptance-test .gemini/skills/add-acceptance-test && 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 "add-acceptance-test" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/add-acceptance-test into .gemini/skills/add-acceptance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-acceptance-test", 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 talkincode/toughradius add-acceptance-test

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 talkincode/toughradius --skill add-acceptance-test -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/talkincode/toughradius.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/add-acceptance-test .github/skills/add-acceptance-test && 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 "add-acceptance-test" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/add-acceptance-test into .github/skills/add-acceptance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-acceptance-test", 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 talkincode/toughradius --skill add-acceptance-test -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 talkincode/toughradius add-acceptance-test --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/talkincode/toughradius.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/add-acceptance-test .opencode/skills/add-acceptance-test && 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 "add-acceptance-test" agent skill from https://github.com/talkincode/toughradius/tree/main/.agents/skills/add-acceptance-test into .opencode/skills/add-acceptance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-acceptance-test", 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: add-acceptance-test
GitHub stars: 691
Token cost: ~827 tokens
SKILL.md length: 289 words
Files: 1
Skills in repo: 15
Repo updated: Oct 3, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022).

Works in 2 steps: Unit / logic acceptance - *_test.go → End-to-end / protocol acceptance -…
A milestone subtask needs CI-backed acceptance
SKILL.md covers Goal, Two test types, Pre-research and Local run, plus 3 more sections
Calls go and make

What it does

Add Acceptance Test is an agent skill from talkincode/toughradius. Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022). Use whenever a milestone subtask needs CI-backed acceptance, covering test/integration integration tests and unit tests.

Its SKILL.md is about 830 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 End-to-end testing, Integration testing and Task breakdown. The repository describes itself as: A powerful, open-source RADIUS server designed for ISPs, enterprise networks, and carriers. Supports standard RADIUS protocols, a full EAP / 802.1X authentication suite (EAP-TLS… The licence is MIT.

When your agent uses it

A milestone subtask needs CI-backed acceptance
Covering test/integration integration tests and unit tests

Example prompts

“/add-acceptance-test”

Requirements

Docker

Workflow steps

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

Unit / logic acceptance - *_test.go
End-to-end / protocol acceptance - test/integration/

What it can do on your machine

Read from SKILL.md and the folder at commit 50907c9. 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:
- go
- make
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Add Acceptance Test loads about 827 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 289 words of instructions outside code blocks.

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

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 talkincode/toughradius at commit 50907c9, republished under its MIT licence (© talkincode). 289 words, ~827 tokens.

Download SKILL.mdSave it as .claude/skills/add-acceptance-test/SKILL.md (or your agent's skills folder).

name: add-acceptance-test
description: Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022). Use whenever a milestone subtask needs CI-backed acceptance, covering test/integration integration tests and unit tests.

Skill: Write CI Automated Acceptance Tests

Feature ID: TR-F022 | Scope: all protocol / end-to-end acceptance

Goal

Every milestone subtask's acceptance criteria must be backed by a CI-executable test. This skill explains where the two test types live and how to write them.

Two test types

1. Unit / logic acceptance - `*_test.go`

Same package as the code under test; the CI test job runs go test -short ./....
For: pure logic, attribute encode/decode, validators, config parsing, etc.
How-to: see ../write-go-tests/SKILL.md.

2. End-to-end / protocol acceptance - `test/integration/`

First line //go:build integration, package integration.
Backed by a real PostgreSQL (the production default database), driving live RADIUS / Admin services with real packets.

The CI integration job runs it automatically:

go test -tags=integration -count=1 -v ./test/integration/...
INTEGRATION_REQUIRED=1   # CI hard-fails when the environment is missing, preventing false green

Existing templates:
- test/integration/main_test.go - shared harness (DB setup, service startup)
- test/integration/radius_test.go - real PAP Access-Request end-to-end
- test/integration/adminapi_test.go - Admin API end-to-end
- test/integration/migration_test.go - migration
- test/integration/client_test.go

Pre-research

text

view test/integration/main_test.go          # harness usage
view test/integration/radius_test.go         # RADIUS end-to-end template
grep_search "INTEGRATION_REQUIRED" --include test/**
view Makefile                                # test / test-integration-pg targets

Local run

bash

# unit
go test ./...
# integration (auto-starts the Postgres in docker-compose.test.yml, cleans up afterwards)
make test-integration-pg
# or, after manually providing TEST_DATABASE_*:
go test -tags=integration -count=1 -v ./test/integration/...

Steps to add an end-to-end acceptance case

Create or extend <feature>_test.go under test/integration/, with //go:build integration as the first line.
Reuse the main_test.go harness to create data and start services; drive real packets for the new feature (e.g. EAP-TLS / CoA) following the existing radius_test.go pattern.
Assert both success and failure paths (reject reasons, timeouts, NAS rejects, etc.).
Do not t.Parallel() for cases that serially depend on global state (see the comments in radius_test.go).
Confirm the CI integration job covers the path (it runs all of ./test/integration/... by default; no CI change needed).

Boundaries

Integration cases must not depend on external public services; provide dependencies via a service container / compose.
Do not weaken assertions or skip failure paths just to pass.

Acceptance

The new feature has a corresponding CI automated acceptance case (unit or integration)
Failure paths are asserted
make test-integration-pg passes locally
The CI test and integration jobs pass

Files

Just SKILL.md in .agents/skills/add-acceptance-test of talkincode/toughradius.

Open the folder on GitHubat commit 50907c9

Compare with similar skills

Add Acceptance Test 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.

Add Acceptance Test compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Add Acceptance Test this skilltalkincode/toughradius	691	—	~827	Automated safety check: Pass	MIT	5 days ago
Integration E2E Testingshinpr/claude-code-workflows	691	—	~3.5k	Automated safety check: Pass	MIT	7 days ago
Integration E2E Testingshinpr/ai-coding-project-boilerplate	232	—	~2.8k	Automated safety check: Pass	MIT	4 days ago
Migrate E2E To Integrationopenshift/oc-mirror	124	—	~1.5k	Automated safety check: Pass	Apache-2.0	yesterday
Om Integration Testsgo-musicfox/go-musicfox	2.6k	1 repos	~3.6k	Automated safety check: Notes	GPL-3.0	1 mo ago
Test Collaborationqshanx/docs-governance	132	—	~1.1k	Automated safety check: Pass	MIT	3 days ago

Similar skills

Integration E2E Testing
shinpr/claude-code-workflows
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.
691 GitHub stars~3.5k tokensUpdated 7 days ago
Testing & QAAuto-check passed
Integration E2E Testing
shinpr/ai-coding-project-boilerplate
Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary.
232 GitHub stars~2.8k tokensUpdated 4 days ago
Testing & QAAuto-check passed
Migrate E2E To Integration
openshift/oc-mirror
Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
124 GitHub stars~1.5k tokensUpdated yesterday
Testing & QAAuto-check passed
Om Integration Tests
go-musicfox/go-musicfox
Run and create integration/E2E tests by exploring the live app with the configured browser provider, preserving repository-native runners, reusing the shared test environment, and diagnosing…
2.6k GitHub starsUsed in 1 repo~3.6k tokens
Testing & QAAuto-check: notes
Test Collaboration
qshanx/docs-governance
盘点并维护项目测试资产，把需求、业务规则、风险、Bug 和跨端接口契约转成 TEST-ID 与可验证证据，生成或更新 TESTS.md。用于测试资产盘点、测试缺口分析、单元/集成/契约/E2E/冒烟分类、Bug 回归保护、前后端或多服务基于同一契约的消费者/提供者测试、测试必要性判断、测试清单维护与交付前测试证据审查。中文触发：测试盘点、测试清单、测试资产、测试缺口、测试必要性、Bug…
132 GitHub stars~1.1k tokensUpdated 3 days ago
Testing & QAAuto-check passed
Raytsystem Run Review
romarayt/raytsystem-public-os
Independently review an raytsystem run, diff, contract, test result, or milestone checkpoint and return structured findings.
150 GitHub stars~523 tokensUpdated yesterday
Testing & QAAuto-check passed

Questions about Add Acceptance Test

What does Add Acceptance Test do?

Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022). Add Acceptance Test is an agent skill from talkincode/toughradius. Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022).

When should I use Add Acceptance Test?

Add Acceptance Test fits situations like: A milestone subtask needs CI-backed acceptance; covering test/integration integration tests and unit tests.

How do I install Add Acceptance Test in Claude Code?

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

How do I install Add Acceptance Test in Codex?

Run `npx skills add talkincode/toughradius --skill add-acceptance-test -a codex`. Or copy the skill folder (.agents/skills/add-acceptance-test in talkincode/toughradius) into .agents/skills/add-acceptance-test in your project. Codex loads it when a task matches its description.

Can I use Add Acceptance Test 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 talkincode/toughradius --skill add-acceptance-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-acceptance-test, .gemini/skills/add-acceptance-test, .github/skills/add-acceptance-test and .opencode/skills/add-acceptance-test in your project.

What does Add Acceptance Test need to run?

Going by SKILL.md and its folder, Add Acceptance Test needs the command-line tools its instructions call (go and make). Our summary lists: Docker.

Does Add Acceptance Test 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 Add Acceptance Test 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 Add Acceptance Test use?

Add Acceptance Test 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 Add Acceptance Test use?

About 827 tokens (SKILL.md is roughly 3.3k 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 Add Acceptance Test?

Skills that share tags, products or a category with Add Acceptance Test: Integration E2E Testing (shinpr/claude-code-workflows, 691 stars), Integration E2E Testing (shinpr/ai-coding-project-boilerplate, 232 stars), Migrate E2E To Integration (openshift/oc-mirror, 124 stars) and Om Integration Tests (go-musicfox/go-musicfox, 2.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Acceptance Test?

talkincode (a GitHub organization) maintains it in talkincode/toughradius, which has 691 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 3, 2026.

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

Install Add Acceptance Test

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill: Write CI Automated Acceptance Tests

Goal

Two test types

1. Unit / logic acceptance - *_test.go

2. End-to-end / protocol acceptance - test/integration/

Pre-research

Local run

Steps to add an end-to-end acceptance case

Boundaries

Acceptance

Files

Compare with similar skills

Similar skills

More from talkincode/toughradius

Related

Questions about Add Acceptance Test

1. Unit / logic acceptance - `*_test.go`

2. End-to-end / protocol acceptance - `test/integration/`