New: 97,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

Testing

by owent in owent/libatbus

A skill your agent uses when: designing, writing, reviewing, or running libatbus unit tests, filtering private-framework cases, testing topology/channel behavior, or diagnosing Windows test…

MITAuto-check passedTesting & QA

Install Testing

skills CLI
$ npx skills add owent/libatbus --skill testing -a claude-code

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

GitHub CLI
$ gh skill install owent/libatbus 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/owent/libatbus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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/

Facts

Skill name
testing
GitHub stars
234
Token cost
~1k tokens
SKILL.md length
504 words
Files
2 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when: designing, writing, reviewing, or running libatbus unit tests, filtering private-framework cases, testing topology/channel behavior, or diagnosing Windows test…

  • Running libatbus unit tests
  • SKILL.md covers Choose the narrowest real path, Drive time and I/O…, Run tests and Windows startup
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Filtering private-framework cases

What it does

Testing is an agent skill from owent/libatbus. Use when: designing, writing, reviewing, or running libatbus unit tests, filtering private-framework cases, testing topology/channel behavior, or diagnosing Windows test startup/PATH.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/test-design-and-acceptance.md`).

It sits in Testing & QA, covering Unit testing. The repository describes itself as: 用于搭建高性能、全异步、树形结构的BUS消息系统的跨平台框架库. The licence is MIT.

When your agent uses it

  • Running libatbus unit tests
  • Filtering private-framework cases
  • Testing topology/channel behavior
  • Diagnosing Windows test startup/PATH

Example prompts

  • “/testing”

What it can do on your machine

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

    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

Testing loads about 1k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 504 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
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.9k

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 owent/libatbus at commit d46c04d, republished under its MIT licence (© owent). 504 words, ~1,037 tokens.

Download SKILL.mdSave it as .claude/skills/testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
testing
description
Use when: designing, writing, reviewing, or running libatbus unit tests, filtering private-framework cases, testing topology/channel behavior, or diagnosing Windows test startup/PATH.

Unit testing (libatbus)

The test executable is atbus_unit_test; cases and their real helpers live under test/case/.

Read test design and acceptance when planning, writing, or reviewing cases. It is not needed merely to run a known test command. Also load libatbus-protocol-crypto when protocol compatibility, framing, authentication, encryption, compression, or cross-language vectors are in scope.

Choose the narrowest real path

  • For buffers, message packing, connection contexts, crypto primitives, topology registries, and other in-process logic, construct real public objects and assert public results/state. Do not start TCP/Unix/SHM merely to reach an internal branch that has an in-memory production path.
  • Use real TCP, Unix sockets, pipes, or shared memory only when that transport's connect/read/write/close behavior is the subject. Treat address availability, OS permissions, and cross-process support as integration prerequisites; do not copy a fixed port/address or invent an allocation API because a nearby test happens to use one.
  • Build protocol/auth/crypto cases from the current .proto, public APIs, and verified vectors. Assert stable round-trip, validation, compatibility, and error semantics; never assert exact random key/nonce output.
  • Reuse the nearest actual fixture/helper and its cleanup order. Keep libuv, crypto, protobuf, shared-memory, and global callback state isolated so case order does not affect results.

Drive time and I/O deterministically

  • UNITTEST_WAIT_UNTIL in test/case/atbus_test_utils.h pumps libuv with a wall-clock safety limit. Its timeout does not make the case fail by itself. Always assert the awaited predicate and business result after the loop.
  • Use unit_test_make_timepoint(...) and explicit node::proc(...) calls for logical timeout/heartbeat/state-machine behavior. Do not use real elapsed time, a fixed sleep, CPU scheduling, or a precise pump/tick count as the oracle.
  • When actual asynchronous I/O is the subject, wait for an observable predicate with a bounded safety timeout. The timeout prevents a hang; connection/message/callback state proves correctness.
  • Prefer memory/in-process channels for routing and lifecycle logic that does not require kernel transport. If a real transport is unavoidable, use current platform guards and verify cleanup even after a failed precondition.

CASE_EXPECT_* is non-fatal. Guard dependent operations after setup failures. Cross-language vector cases may return early when required generated files are absent; inspect output/case counts and report that path as skipped, not green compatibility coverage.

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

Run tests

Resolve <BUILD_DIR> as required by AGENTS.md, then prefer the registered CTest:

bash
ctest --test-dir <BUILD_DIR> -R "^libatbus\.unit_test$" --output-on-failure

Add -C <CONFIG> for a verified multi-config generator.

The executable supports:

  • List: atbus_unit_test -l / --list-tests
  • Run a group/case: atbus_unit_test -r <group> or -r <group>.<case>
  • Filter: atbus_unit_test -f "pattern*" / --filter "pattern*"
  • Help/version: -h, -v

Run the exact case first and confirm it was selected, then the registered CTest and broader matrix in proportion to protocol/platform risk. Do not maintain hand-counted case inventories in this Skill; discover current groups with -l and source search.

Windows startup

Prefer the registered CTest command so the target and working directory match current CMake configuration. If CTest or a direct run reports missing DLLs, locate the actual executable/DLL outputs in the current build tree and prepend only those verified directories to the current process PATH. Windows private shared memory and public shared-memory permissions differ; preserve current platform guards and report unsupported/skipped coverage explicitly.

© owent, 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 1 other file (references) in .agents/skills/testing of owent/libatbus.

  • SKILL.md
  • references/test-design-and-acceptance.md

Open the folder on GitHubat commit d46c04d

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
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing this skillowent/libatbus234—~1kAutomated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
Testing OpenLogi UIAprilNEA/OpenLogi23k—~1.1kAutomated safety check: PassApache-2.0
Go Testingcxuu/golang-skills1701 repos~1.3kAutomated safety check: PassApache-2.0
Contractssamchon/nestia2.2k—~1.3kAutomated safety check: PassMIT
Cohesion Over TestabilityEpicenterHQ/epicenter4.8k—~2kAutomated safety check: PassCustom licence

Similar skills

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • Testing OpenLogi UI

    AprilNEA/OpenLogi

    Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.

    23k GitHub stars~1.1k tokensUpdated 4 days ago
    Testing & QAAuto-check passed

  • Go Testing

    cxuu/golang-skills

    A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.

    170 GitHub starsUsed in 1 repo~1.3k tokens
    Testing & QAAuto-check passed

  • Contracts

    samchon/nestia

    Defines self-acknowledgments for production declarations and tests.

    2.2k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Cohesion Over Testability

    EpicenterHQ/epicenter

    Collapse test-shaped production boundaries while preserving behavior and coverage.

    4.8k GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed

  • JS-in-HTML Testing

    liaohch3/claude-tap

    Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.

    3.3k GitHub stars~924 tokensUpdated 15 days ago
    Testing & QAAuto-check passed

More from owent/libatbus

  • Libatbus Protocol Crypto

    owent/libatbus

    A skill your agent uses when: working on libatbus protocol transport, ECDH handshakes, cipher/compression negotiation, message framing, access token auth, connectioncontext, or crypto-related tests.

    234 GitHub stars~4.3k tokensUpdated 26 days ago
    Auto-check passed

  • AI Agent Maintenance

    owent/libatbus

    A skill your agent uses when: initializing, auditing, or optimizing repository AI guidance, including AGENTS.md/CLAUDE.md bridges, Agent Skills, trigger descriptions, progressive disclosure, source…

    234 GitHub stars~1.4k tokensUpdated 26 days ago
    Auto-check passed

  • Change Workflow

    owent/libatbus

    A skill your agent uses when: diagnosing or fixing a defect, test/build/runtime failure, or planning and implementing a nontrivial feature, behavior change, cross-module refactor, public API/ABI…

    234 GitHub stars~1.2k tokensUpdated 26 days ago
    Auto-check passed

  • Shell Tooling

    owent/libatbus

    A skill your agent uses when: running terminal commands, writing or debugging shell/PowerShell scripts, choosing or installing CLI tools, or diagnosing command failures, quoting/escaping errors, or…

    234 GitHub stars~1.4k tokensUpdated 26 days ago
    Auto-check passed

  • Engineering Guidelines

    owent/libatbus

    A skill your agent uses when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFWUTILSYMBOLVISIBLE, or ATFWUTILFORCEINLINE.

    234 GitHub stars~386 tokensUpdated 26 days ago
    Auto-check passed

Categories

Questions about Testing

What does Testing do?

A skill your agent uses when: designing, writing, reviewing, or running libatbus unit tests, filtering private-framework cases, testing topology/channel behavior, or diagnosing Windows test…. Testing is an agent skill from owent/libatbus. Use when: designing, writing, reviewing, or running libatbus unit tests, filtering private-framework cases, testing topology/channel behavior, or diagnosing Windows test startup/PATH.

When should I use Testing?

Testing fits situations like: running libatbus unit tests; filtering private-framework cases; testing topology/channel behavior; diagnosing Windows test startup/PATH.

How do I install Testing in Claude Code?

Run `npx skills add owent/libatbus --skill testing -a claude-code`. Or copy the skill folder (.agents/skills/testing in owent/libatbus) 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 owent/libatbus --skill testing -a codex`. Or copy the skill folder (.agents/skills/testing in owent/libatbus) 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 owent/libatbus --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?

SKILL.md names no scripts, command-line tools or credentials: Testing is instructions for the agent only.

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 1k tokens (SKILL.md is roughly 4.1k 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 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Testing?

Skills that share tags, products or a category with Testing: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars), Go Testing (cxuu/golang-skills, 170 stars) and Contracts (samchon/nestia, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing?

owent (a GitHub user) maintains it in owent/libatbus, which has 234 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 11, 2026.

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