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

Compiling

by gkeyllorg in gkeyllorg/gkeyll

How to compile Gkeyll libraries, executables, and specific unit or regression test targets on CPU or CUDA.

MITAuto-check passedTesting & QA

Install Compiling

skills CLI
$ npx skills add gkeyllorg/gkeyll --skill compiling -a claude-code

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

GitHub CLI
$ gh skill install gkeyllorg/gkeyll compiling --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/gkeyllorg/gkeyll.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/compiling .claude/skills/compiling && 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
compiling
GitHub stars
112
Token cost
~759 tokens
SKILL.md length
355 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

How to compile Gkeyll libraries, executables, and specific unit or regression test targets on CPU or CUDA.

  • Tasks that involve Unit testing
  • SKILL.md covers Compiling the Gkeyll library, Compiling a C unit or… and Compiling C input files
  • Calls make and git

What it does

Compiling is an agent skill from gkeyllorg/gkeyll. How to compile Gkeyll libraries, executables, and specific unit or regression test targets on CPU or CUDA.

Its SKILL.md is about 760 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. It works with CUDA. The repository describes itself as: The Gkeyll Computational Plasma Physics Package. The licence is MIT.

When your agent uses it

  • Tasks that involve Unit testing

Example prompts

  • “/compiling”

What it can do on your machine

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

    • make
    • git

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

  • Network

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

Compiling loads about 759 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 355 words of instructions outside code blocks.

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

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 gkeyllorg/gkeyll at commit e6b37b0, republished under its MIT licence (© gkeyllorg). 355 words, ~759 tokens.

Download SKILL.mdSave it as .claude/skills/compiling/SKILL.md (or your agent's skills folder).
name
compiling
description
How to compile Gkeyll libraries, executables, and specific unit or regression test targets on CPU or CUDA.

Instructions

Use this skill whenever you need to compile

  • Any of the Gkeyll libraries.
  • A C unit or regression test.
  • A C input file.

Compiling in Gkeyll

We assume the dependencies have already been installed (e.g. via a machines/mkdeps file) and configured (e.g. via a machines/configure file).

Operate relative to the repository root (git rev-parse --show-toplevel). Dependencies are typically already installed in the sibling gkylsoft/ directory. Check the existing configuration before building. If configuration is missing or needs changing, consult machines/configure.<machine>.sh for required modules and library paths, or use ./configure with the intended installation prefix and solver.

Compiling the Gkeyll library

We compile using a Makefile. The make command allows you to specify the number of cores to use via -j. We will use no more than half the available processors for parallel builds. So before invoking make, set the NPROC environment variable on a Mac using

export NPROC=$(sysctl -n hw.physicalcpu)
NPROC=$((NPROC > 1 ? NPROC / 2 : 1))

or on Linux using

sh
NPROC=$(nproc)
NPROC=$((NPROC > 1 ? NPROC / 2 : 1))

Then, you can build the Gkeyll library with

sh
make -j"$NPROC" install

Compiling a C unit or regression test

Unit tests are located in the unit/ directory of each solver (core/moments/vlasov/gyrokinetic/pkpm), while C regression tests are located in creg/ folders and have names beginning with rt_.

Compile a specific test by giving make its executable target:

sh
make -j"$NPROC" build/core/unit/ctest_array
make -j"$NPROC" build/gyrokinetic/creg/rt_gk_sheath_2x2v_p1

CPU targets are located in build/, and GPU targets are in cuda-build/. Match test targets to the configured build directory.

For executing the resulting tests, see testing-and-verification.

Show full SKILL.md (125 more words)Show less
Compiling all or groups of C unit tests

The Makefile supports compiling groups of unit tests all at once. For example, to compile all the unit tests at once run

sh
make -j"$NPROC" unit

Alternatively, you can compile all the unit tests for a specific solver. For example, to compile all the unit tests for the gyrokinetic solver use

sh
make -j"$NPROC" gyrokinetic-unit

Compiling C input files

Input files written in C work just like C regression tests. They can be compiled similarly if they are located in the creg/ folder. For example, if my_sim.c is a gyrokinetic input file, and located in gyrokinetic/creg/, it can be compiled with

sh
make -j"$NPROC" build/gyrokinetic/creg/my_sim

If the input file is outside of the repository, use the shared makefile in <gkeyll_install_prefix>/share/. Run it from the directory containing the input file:

sh
cd <input_file_directory>
cp <gkeyll_install_prefix>/share/Makefile ./
make

© gkeyllorg, MIT. 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 .agents/skills/compiling of gkeyllorg/gkeyll.

Open the folder on GitHubat commit e6b37b0

Compare with similar skills

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

Compiling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Compiling this skillgkeyllorg/gkeyll112—~759Automated safety check: PassMIT
ONNX Runtime GPU Transformers Testsmicrosoft/onnxruntime22k—~2.9kAutomated safety check: PassMIT
Test Changeceleritas-project/celeritas105—~640Automated safety check: PassCustom licence
Debug Failing GPUfacebookexperimental/triton201—~709Automated safety check: PassMIT
Ut Refactor Reviewintel/torch-xpu-ops115—~917Automated safety check: PassApache-2.0
Jest Testing PatternsChrisWiles/claude-code-showcase6.1k7 repos~1.5kAutomated safety check: PassNone

Similar skills

  • ONNX Runtime GPU Transformers Tests

    microsoft/onnxruntime

    Official

    Runs the ONNX Runtime transformers Python tests against a GPU wheel and proves the cuDNN flash attention path was used rather than a silent fallback.

    22k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed

  • Test Change

    celeritas-project/celeritas

    Build and run the unit tests covering changed Celeritas source files.

    105 GitHub stars~640 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Debug Failing GPU

    facebookexperimental/triton

    Official

    Recover from GPU-busy / GPU-unavailable failures. An agent skill from facebookexperimental/triton.

    201 GitHub stars~709 tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Ut Refactor Review

    intel/torch-xpu-ops

    Official

    Review PyTorch upstream unit-test (UT) PRs that enable Intel GPU (XPU) on existing tests.

    115 GitHub stars~917 tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

  • Jest Testing Patterns

    ChrisWiles/claude-code-showcase

    Jest patterns for React Native style tests: TDD discipline, mock factory functions, module and GraphQL hook mocking, custom render helpers and anti-patterns to avoid.

    6.1k GitHub starsUsed in 7 repos~1.5k tokens
    Testing & QAAuto-check passed

  • Rust TDD Workflow

    rtk-ai/rtk

    Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated yesterday
    Testing & QAAuto-check: notes

More from gkeyllorg/gkeyll

  • Testing And Verification

    gkeyllorg/gkeyll

    How to run and write Gkeyll unit and regression tests, as well as performing memory checks.

    112 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Gyrokinetic Details

    gkeyllorg/gkeyll

    Apply gyrokinetic solver conventions when working on gyrokinetic-related source code or input files.

    112 GitHub stars~272 tokensUpdated today
    Auto-check passed

  • Directory Structure

    gkeyllorg/gkeyll

    Locate Gkeyll code and understand solver dependencies when exploring the repository or deciding where new code belongs.

    112 GitHub stars~695 tokensUpdated today
    Auto-check passed

  • Naming Conventions

    gkeyllorg/gkeyll

    Apply Gkeyll naming conventions when creating, editing, or reviewing C, CUDA, or Lua files and code elements.

    112 GitHub stars~301 tokensUpdated today
    Auto-check passed

  • Software Design

    gkeyllorg/gkeyll

    Some design practices in Gkeyll code to consider when implementing new modules (apps, updaters) or modifying existing ones.

    112 GitHub stars~398 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Compiling

What does Compiling do?

How to compile Gkeyll libraries, executables, and specific unit or regression test targets on CPU or CUDA. Compiling is an agent skill from gkeyllorg/gkeyll. How to compile Gkeyll libraries, executables, and specific unit or regression test targets on CPU or CUDA.

When should I use Compiling?

Compiling fits situations like: tasks that involve Unit testing.

How do I install Compiling in Claude Code?

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

How do I install Compiling in Codex?

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

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

What does Compiling need to run?

Going by SKILL.md and its folder, Compiling needs the command-line tools its instructions call (make and git).

Does Compiling access the network?

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

Is Compiling 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 Compiling use?

Compiling 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 Compiling use?

About 759 tokens (SKILL.md is roughly 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 Compiling?

Skills that share tags, products or a category with Compiling: ONNX Runtime GPU Transformers Tests (microsoft/onnxruntime, 22k stars), Test Change (celeritas-project/celeritas, 105 stars), Debug Failing GPU (facebookexperimental/triton, 201 stars) and Ut Refactor Review (intel/torch-xpu-ops, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Compiling?

gkeyllorg (a GitHub organization) maintains it in gkeyllorg/gkeyll, which has 112 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

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