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

Build Test

by atomisticnet in atomisticnet/aenet

Configure, build, and validate the aenet Fortran backend with CMake and CTest, including compiler, MPI, and BLAS variants relevant to the change.

MPL-2.0Auto-check passed

Install Build Test

skills CLI
$ npx skills add atomisticnet/aenet --skill build-test -a claude-code

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

GitHub CLI
$ gh skill install atomisticnet/aenet build-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/atomisticnet/aenet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/build-test .claude/skills/build-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/

Facts

Skill name
build-test
GitHub stars
129
Token cost
~1k tokens
SKILL.md length
494 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MPL-2.0

At a glance

Configure, build, and validate the aenet Fortran backend with CMake and CTest, including compiler, MPI, and BLAS variants relevant to the change.

  • SKILL.md covers Select a configuration and Validate according to the change
  • Calls cmake

What it does

Build Test is an agent skill from atomisticnet/aenet. Configure, build, and validate the aenet Fortran backend with CMake and CTest, including compiler, MPI, and BLAS variants relevant to the change.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with C++. The repository describes itself as: Atomic interaction potentials based on artificial neural networks. The licence is MPL-2.0.

Example prompts

  • “/build-test”

What it can do on your machine

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

    • cmake

    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

Build Test loads about 1k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 494 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~39
When it runs · the whole SKILL.md, loaded when a task matches
~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 atomisticnet/aenet at commit 9403bc5, republished under its MPL-2.0 licence (© atomisticnet). 494 words, ~1,028 tokens.

Download SKILL.mdSave it as .claude/skills/build-test/SKILL.md (or your agent's skills folder).
name
build-test
description
Configure, build, and validate the aenet Fortran backend with CMake and CTest, including compiler, MPI, and BLAS variants relevant to the change.

Build and Test

Read root and src/CMakeLists.txt and any config/local.toml before choosing commands. CMake is authoritative for options and targets. Local TOML records tool locations for the agent; CMake does not read it. Do not eval local configuration as shell code; construct commands with properly quoted arguments.

Select a configuration

Use an out-of-source directory per compiler, build type, MPI, and BLAS combination. Do not reuse an unrelated existing build cache or change its compiler. Preserve source-tree artifacts and other work already present.

For a GNU serial Debug baseline, with tools available on PATH:

sh
cmake -S . -B build-gnu-debug -DBUILD_AENET=ON \
  -DCMAKE_Fortran_COMPILER=gfortran -DCMAKE_BUILD_TYPE=Debug \
  -DUSE_MPI=OFF -DUSE_MKL=OFF -DUSE_OPENBLAS=OFF
cmake --build build-gnu-debug --target build_tests
ctest --test-dir build-gnu-debug -N
ctest --test-dir build-gnu-debug --output-on-failure

Choose a new directory if this example name already belongs to other work. Use ctest -R '<pattern>' for focused tests after checking registration with -N; ensure the pattern actually selects the intended cases. The registered build_test_binaries fixture can also build tests automatically. CTest's --test-dir needs CTest 3.20 or newer; with older supported CMake versions, run CTest from inside the chosen build directory instead.

The default build excludes the main artifacts. Use explicit targets: main, lib, tools, build_tests, or build_all. New Fortran tests belong under src/tests/ and must be registered in src/CMakeLists.txt, including the existing test-build target and fixture dependencies as appropriate.

For a test-first change, add or extend a focused case using src/ext/unittest.f90 and the existing test-driver pattern. Build it and confirm CTest reports the intended failure before implementing the fix. Ensure assertion failures reach a nonzero process exit status (see tst_exit_nonzero_if_failed); printed failure messages alone are not sufficient. Then implement, rebuild, rerun the focused case, and broaden validation according to risk. CTest runs the test programs; it does not require a different development cycle or a new test framework.

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

Validate according to the change

  • Numerical changes: focused module tests, then the broader suite for shared routines. Debug checks help detect bounds and initialization errors; test Release too when optimization or floating-point behavior is relevant.
  • Compiler/build changes: configure and build the affected GNU/Intel variants when available, using CMAKE_Fortran_COMPILER and separate directories.
  • MPI changes: build with USE_MPI=ON and run relevant serial/multi-rank comparisons with bounded execution. Current CTest registrations do not launch mpiexec; an MPI build alone is not multi-rank validation.
  • BLAS changes: exercise the affected system/OpenBLAS/MKL configuration; choose only one vendor option and verify actual resolved linkage.
  • CLI/library/install changes: build the affected artifacts, exercise their public boundary, and test installation into a temporary prefix when needed. Inspect actual output names; build configuration currently adds suffixes.
  • Policy-only changes: validate links, examples against configuration, and skill structure. A full Fortran rebuild is not required for prose alone.

Start with serial test execution. Enable CTest parallelism only when selected cases have independent output paths. Do not change tests or numerical thresholds merely to obtain a pass. Report baseline failures separately from failures caused by the change.

Record exact commands, compiler/version, configuration, results, and unrun required checks. An unavailable Intel compiler, MPI runtime, or vendor library limits coverage; it does not demonstrate portability. Resolve or record the gap according to the task's acceptance criteria before closure.

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

Files

Just SKILL.md in skills/build-test of atomisticnet/aenet.

Open the folder on GitHubat commit 9403bc5

Compare with similar skills

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

Build Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Build Test this skillatomisticnet/aenet129—~1kAutomated safety check: PassMPL-2.0
Paddle BuildPaddlePaddle/Paddle24k—~1kAutomated safety check: PassApache-2.0
Fory Releaseapache/fory4.6k—~2.9kAutomated safety check: PassApache-2.0
ONNX Runtime Shape Inference Safety Auditmicrosoft/onnxruntime22k—~3.3kAutomated safety check: PassMIT
Code Audit3stoneBrother/code-audit8921 repos~2.7kAutomated safety check: PassNone
Qt C++ Code Reviewx-tools-author/x-tools1.1k2 repos~4.3kAutomated safety check: PassBSD-3-Clause

Similar skills

  • Paddle Build

    PaddlePaddle/Paddle

    A skill your agent uses when needing to compile, rebuild, or install Paddle from source after code changes.

    24k GitHub stars~1k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Fory Release

    apache/fory

    Prepare an Apache Fory release candidate from a clean release branch, including the version bump, RC tag, JVM staging, ASF source artifacts, SVN upload, and vote email.

    4.6k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

  • ONNX Runtime Shape Inference Safety Audit

    microsoft/onnxruntime

    Official

    Finds and fixes out-of-range output writes in ONNX Runtime operator shape-inference functions where a getNumOutputs guard admits too few outputs.

    22k GitHub stars~3.3k tokensUpdated today
    SecurityAuto-check passed

  • Code Audit

    3stoneBrother/code-audit

    Professional code security audit skill covering 55+ vulnerability types.

    892 GitHub starsUsed in 1 repo~2.7k tokens
    SecurityAuto-check passed

  • Qt C++ Code Review

    x-tools-author/x-tools

    Read-only review of Qt6 C++ code that combines a deterministic lint script with six parallel analysis agents and reports only high-confidence issues.

    1.1k GitHub starsUsed in 2 repos~4.3k tokens
    DevelopmentAuto-check passed

  • Translation

    doxygen/doxygen

    Keeps all Doxygen and Doxywizard translations up to date across three mechanisms: translator C++ classes (src/translatorxx.h), Qt .ts locale files for the Doxywizard GUI (addon/doxywizard/i18n/)…

    6.6k GitHub stars~5.2k tokensUpdated 8 days ago
    Writing & ContentAuto-check passed

More from atomisticnet/aenet

  • Issue Workflow

    atomisticnet/aenet

    Plan, implement, review, validate, and close aenet work tracked by shared or local issues, or explicitly linked GitHub issues.

    129 GitHub stars~980 tokensUpdated 13 days ago
    Auto-check passed

  • Code Review

    atomisticnet/aenet

    Review aenet commits, branches, diffs, or working-tree changes for correctness, numerical validity, compatibility, maintainability, and test quality.

    129 GitHub stars~537 tokensUpdated 13 days ago
    Auto-check passed

  • Documentation

    atomisticnet/aenet

    Create or substantially revise aenet maintained documentation, Fortran or C interface comments, CLI help, and runnable examples using the repository's current documentation sources.

    129 GitHub stars~654 tokensUpdated 13 days ago
    Auto-check passed

Works with

Questions about Build Test

What does Build Test do?

Configure, build, and validate the aenet Fortran backend with CMake and CTest, including compiler, MPI, and BLAS variants relevant to the change. Build Test is an agent skill from atomisticnet/aenet. Configure, build, and validate the aenet Fortran backend with CMake and CTest, including compiler, MPI, and BLAS variants relevant to the change.

How do I install Build Test in Claude Code?

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

How do I install Build Test in Codex?

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

Can I use Build 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 atomisticnet/aenet --skill build-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/build-test, .gemini/skills/build-test, .github/skills/build-test and .opencode/skills/build-test in your project.

What does Build Test need to run?

Going by SKILL.md and its folder, Build Test needs the command-line tools its instructions call (cmake).

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

Build Test is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Build Test 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.

What are the alternatives to Build Test?

Skills that share tags, products or a category with Build Test: Paddle Build (PaddlePaddle/Paddle, 24k stars), Fory Release (apache/fory, 4.6k stars), ONNX Runtime Shape Inference Safety Audit (microsoft/onnxruntime, 22k stars) and Code Audit (3stoneBrother/code-audit, 892 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build Test?

atomisticnet (a GitHub organization) maintains it in atomisticnet/aenet, which has 129 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 25, 2026.

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