Sglang Prod Incident Triage
sgl-project/sglang
Replay-first debug flow for SGLang serving problems. An agent skill from sgl-project/sglang.
Apply Gkeyll naming conventions when creating, editing, or reviewing C, CUDA, or Lua files and code elements.
Install Naming Conventions
$ npx skills add gkeyllorg/gkeyll --skill naming-conventions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gkeyllorg/gkeyll naming-conventions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gkeyllorg/gkeyll.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/naming-conventions .claude/skills/naming-conventions && rm -rf skills-srcUse ~/.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/
Install the "naming-conventions" agent skill from https://github.com/gkeyllorg/gkeyll/tree/main/.agents/skills/naming-conventions into .claude/skills/naming-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming-conventions", 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 install https://github.com/gkeyllorg/gkeyll/tree/main/.agents/skills/naming-conventionsType 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.
$ npx skills add gkeyllorg/gkeyll --skill naming-conventions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gkeyllorg/gkeyll naming-conventions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gkeyllorg/gkeyll.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/naming-conventions .agents/skills/naming-conventions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "naming-conventions" agent skill from https://github.com/gkeyllorg/gkeyll/tree/main/.agents/skills/naming-conventions into .agents/skills/naming-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming-conventions", 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.
$ npx skills add gkeyllorg/gkeyll --skill naming-conventions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gkeyllorg/gkeyll naming-conventions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gkeyllorg/gkeyll.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/naming-conventions .cursor/skills/naming-conventions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "naming-conventions" agent skill from https://github.com/gkeyllorg/gkeyll/tree/main/.agents/skills/naming-conventions into .cursor/skills/naming-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming-conventions", 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 https://github.com/gkeyllorg/gkeyll.git --path .agents/skills/naming-conventions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gkeyllorg/gkeyll --skill naming-conventions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gkeyllorg/gkeyll naming-conventions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gkeyllorg/gkeyll.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/naming-conventions .gemini/skills/naming-conventions && rm -rf skills-srcUse ~/.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/
Install the "naming-conventions" agent skill from https://github.com/gkeyllorg/gkeyll/tree/main/.agents/skills/naming-conventions into .gemini/skills/naming-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming-conventions", 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.
$ gh skill install gkeyllorg/gkeyll naming-conventionsInstalls 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).
$ npx skills add gkeyllorg/gkeyll --skill naming-conventions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gkeyllorg/gkeyll.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/naming-conventions .github/skills/naming-conventions && rm -rf skills-srcUse ~/.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/
Install the "naming-conventions" agent skill from https://github.com/gkeyllorg/gkeyll/tree/main/.agents/skills/naming-conventions into .github/skills/naming-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming-conventions", 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.
$ npx skills add gkeyllorg/gkeyll --skill naming-conventions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gkeyllorg/gkeyll naming-conventions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gkeyllorg/gkeyll.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/naming-conventions .opencode/skills/naming-conventions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "naming-conventions" agent skill from https://github.com/gkeyllorg/gkeyll/tree/main/.agents/skills/naming-conventions into .opencode/skills/naming-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming-conventions", 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
naming-conventions- GitHub stars
- 112
- Token cost
- ~301 tokens
- SKILL.md length
- 167 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Apply Gkeyll naming conventions when creating, editing, or reviewing C, CUDA, or Lua files and code elements.
- AI & LLM Engineering work in your project
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Naming Conventions is an agent skill from gkeyllorg/gkeyll. Apply Gkeyll naming conventions when creating, editing, or reviewing C, CUDA, or Lua files and code elements.
Its SKILL.md is about 300 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 AI & LLM Engineering. It works with Lua and CUDA. The repository describes itself as: The Gkeyll Computational Plasma Physics Package. The licence is MIT.
When your agent uses it
- AI & LLM Engineering work in your project
Example prompts
- “/naming-conventions”
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
No scripts in the folder and no shell commands in SKILL.md.
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
Naming Conventions loads about 301 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 167 words of instructions outside code blocks.
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). 167 words, ~301 tokens.
Download SKILL.mdSave it as
.claude/skills/naming-conventions/SKILL.md (or your agent's skills folder).- name
- naming-conventions
- description
- Apply Gkeyll naming conventions when creating, editing, or reviewing C, CUDA, or Lua files and code elements.
Instructions
- Apply these naming conventions when creating, editing, or reviewing C, CUDA, and Lua code.
Naming conventions
Files.
- Public header files have names starting with gkyl_ and ending in .h.
- Private header files have names starting with gkyl_ and ending in _priv.h.
- CUDA files have names ending in _cu.cu.
- luareg/ folders have Lua input files whose names end with .lua. The Lua wrappers are in the apps/ folders and have names ending in _lw.c
Functions
- Public functions (defined in public header files) should have a name that starts with gkyl_.
- Public functions in files in zero/ folders should have a name that starts with the name of the file that contains it.
- Private functions (defined in private header files) or static (and not defined in private headers) in files in zero/ folders should have a name that starts with an abbreviated version of the name of the file that contains it.
Variables
- Do not use single letter names for variables whose scope spans more than 15 lines.
© 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/naming-conventions of gkeyllorg/gkeyll.
Open the folder on GitHubat commit e6b37b0
Compare with similar skills
Naming Conventions 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Naming Conventions this skillgkeyllorg/gkeyll | 112 | — | ~301 | Automated safety check: Pass | MIT | |
| Sglang Prod Incident Triagesgl-project/sglang | 37k | 3 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Paddle BuildPaddlePaddle/Paddle | 24k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Paddle Design CompilerPaddlePaddle/Paddle | 24k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Fastllm Triton Opsztxz16/fastllm | 5.1k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Cuda Index Widthpytorch/pytorch | 104k | — | ~1.6k | Automated safety check: Pass | Custom licence |
Similar skills
Paddle Build
PaddlePaddle/Paddle
A skill your agent uses when needing to compile, rebuild, or install Paddle from source after code changes.
Paddle Design Compiler
PaddlePaddle/Paddle
A skill your agent uses when working with Paddle 3.0 compiler full pipeline: SOT (Symbolic Opcode Translator) for bytecode-level dy2st graph capture, PIR (Paddle IR) for SSA-based intermediate…
Fastllm Triton Ops
ztxz16/fastllm
Guide for adding Triton-backed CUDA operators to FastLLM. An agent skill from ztxz16/fastllm.
Cuda Index Width
pytorch/pytorch
Choose 32-bit vs 64-bit index math in PyTorch CUDA kernels. An agent skill from pytorch/pytorch.
Esmfold2
JimLiu/science-skills
Biohub ESMFold2 / ESMFold2-Fast all-atom co-folding (Candido et al.
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.
Compiling
gkeyllorg/gkeyll
How to compile Gkeyll libraries, executables, and specific unit or regression test targets on CPU or CUDA.
Gyrokinetic Details
gkeyllorg/gkeyll
Apply gyrokinetic solver conventions when working on gyrokinetic-related source code or input files.
Directory Structure
gkeyllorg/gkeyll
Locate Gkeyll code and understand solver dependencies when exploring the repository or deciding where new code belongs.
Software Design
gkeyllorg/gkeyll
Some design practices in Gkeyll code to consider when implementing new modules (apps, updaters) or modifying existing ones.
Related
Categories
Questions about Naming Conventions
What does Naming Conventions do?
Apply Gkeyll naming conventions when creating, editing, or reviewing C, CUDA, or Lua files and code elements. Naming Conventions is an agent skill from gkeyllorg/gkeyll. Apply Gkeyll naming conventions when creating, editing, or reviewing C, CUDA, or Lua files and code elements.
When should I use Naming Conventions?
Naming Conventions fits situations like: AI & LLM Engineering work in your project.
How do I install Naming Conventions in Claude Code?
Run `npx skills add gkeyllorg/gkeyll --skill naming-conventions -a claude-code`. Or copy the skill folder (.agents/skills/naming-conventions in gkeyllorg/gkeyll) into .claude/skills/naming-conventions in your project. Claude Code loads it when a task matches its description.
How do I install Naming Conventions in Codex?
Run `npx skills add gkeyllorg/gkeyll --skill naming-conventions -a codex`. Or copy the skill folder (.agents/skills/naming-conventions in gkeyllorg/gkeyll) into .agents/skills/naming-conventions in your project. Codex loads it when a task matches its description.
Can I use Naming Conventions 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 naming-conventions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/naming-conventions, .gemini/skills/naming-conventions, .github/skills/naming-conventions and .opencode/skills/naming-conventions in your project.
What does Naming Conventions need to run?
SKILL.md names no scripts, command-line tools or credentials: Naming Conventions is instructions for the agent only.
Does Naming Conventions 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 Naming Conventions 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 Naming Conventions use?
Naming Conventions 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 Naming Conventions use?
About 301 tokens (SKILL.md is roughly 1.2k 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 Naming Conventions?
Skills that share tags, products or a category with Naming Conventions: Sglang Prod Incident Triage (sgl-project/sglang, 37k stars), Paddle Build (PaddlePaddle/Paddle, 24k stars), Paddle Design Compiler (PaddlePaddle/Paddle, 24k stars) and Fastllm Triton Ops (ztxz16/fastllm, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Naming Conventions?
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 8, 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.