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

Directory Structure

by gkeyllorg in gkeyllorg/gkeyll

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

MITAuto-check passed

Install Directory Structure

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

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

GitHub CLI
$ gh skill install gkeyllorg/gkeyll directory-structure --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/directory-structure .claude/skills/directory-structure && 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
directory-structure
GitHub stars
112
Token cost
~695 tokens
SKILL.md length
384 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

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

  • SKILL.md covers Library dependencies, CPU - GPU organization and Search hierarchy
  • Calls git

What it does

Directory Structure is an agent skill from gkeyllorg/gkeyll. Locate Gkeyll code and understand solver dependencies when exploring the repository or deciding where new code belongs.

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

The repository describes itself as: The Gkeyll Computational Plasma Physics Package. The licence is MIT.

Example prompts

  • “/directory-structure”

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:

    • 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

Directory Structure loads about 695 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 384 words of instructions outside code blocks.

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

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). 384 words, ~695 tokens.

Download SKILL.mdSave it as .claude/skills/directory-structure/SKILL.md (or your agent's skills folder).
name
directory-structure
description
Locate Gkeyll code and understand solver dependencies when exploring the repository or deciding where new code belongs.

Instructions

  • Use when exploring the repository, trying to find something, or deciding where new code belongs.
  • Operate relative to the repository root (git rev-parse --show-toplevel).

Gkeyll file structure

Gkeyll has four PDE solvers:

  • Moments or fluid solver.
  • Vlasov solver.
  • Gyrokinetic solver.
  • PKPM solver.

Correspondingly, these solvers are organized into four separate folders, and they share some common functionality in a fifth folder. Gkeyll is mostly organized in:

  • core/: functionality common to all solvers.
  • moments/: files for the moments solver.
  • vlasov/: files for the Vlasov solver.
  • gyrokinetic/: files for the gyrokinetic solver.
  • pkpm/: files for the PKPM solver.

Note that the four solvers are not independent. They have the following dependencies:

  • moments depends on core.
  • vlasov depends on moments.
  • gyrokinetic depends on vlasov.
  • pkpm depends on gyrokinetic.

Keep lower layers independent of higher layers.

Each of the solvers' folders have the sub-folders:

  • ker/: C kernels generated with Maxima stored in the gkylcas repository. Do not hand-edit generated kernels; modify their source templates instead.
  • zero/: C and CUDA functions or modules (sometimes we call them updaters), some of which call kernels in ker/.
  • data/: data needed for some simulations.
  • unit/: unit tests of specific components in zero/.
  • apps/: apps are called by input files or regression tests, and they organize solver workflow or simulations and call modules in zero/. Communication happens in the app level.
  • creg/: C regression tests or short simulations to ensure solvers work (these are also examples of C input files).
  • luareg/: Lua regression tests or short simulations to ensure solvers work (these are also examples of Lua input files).
Show full SKILL.md (123 more words)Show less

Library dependencies

The Gkeyll source code in gkeyll/ depends on other libraries installed in gkylsoft/. Most of the time you shouldn't need to read files in gkylsoft/ unless prompted.

CPU - GPU organization

Gkeyll runs on both CPUs and GPUs, the latter using CUDA.

  • CPU-only implementations live in .c files.
  • C files call host-side wrappers of CUDA kernels, both of which live in _cu.cu files.

Search hierarchy

Rather than looking into the entire codebase without prior knowledge, look into folders in the following order:

  • Look into a folder (ending in /) the user referenced.
  • If the user referenced a specific solver (e.g. gyrokinetic), look into its folder.
  • Look into folders for solvers that the specified solver depends on, following the dependency chain up through core/.

© 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/directory-structure of gkeyllorg/gkeyll.

Open the folder on GitHubat commit e6b37b0

Compare with similar skills

Directory Structure 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.

Directory Structure compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Directory Structure this skillgkeyllorg/gkeyll112—~695Automated safety check: PassMIT
Dependency Scanningsickn33/agentic-awesome-skills47k1 repos~2.4kAutomated safety check: PassMIT
Dependency Checkruvnet/ruflo74k—~258Automated safety check: PassMIT
Dependency Updatecodewhale-hq/Codewhale41k—~142Automated safety check: PassMIT
Solveratopile/atopile4k—~2.3kAutomated safety check: PassMIT
Bump Sentry Dependencygetsentry/sentry45k—~815Automated safety check: PassCustom licence

Similar skills

  • Dependency Scanning

    sickn33/agentic-awesome-skills

    Scan package dependencies for known vulnerabilities using Snyk, Dependabot, and OWASP Dependency-Check.

    47k GitHub starsUsed in 1 repo~2.4k tokens
    SecurityAuto-check passed

  • Dependency Check

    ruvnet/ruflo

    Scan project dependencies for known vulnerabilities and CVEs.

    74k GitHub stars~258 tokensUpdated today
    SecurityAuto-check passed

  • Dependency Update

    codewhale-hq/Codewhale

    Read release notes/changelogs, update a defined dependency scope, handle breaking changes, and verify.

    41k GitHub stars~142 tokensUpdated today
    DevelopmentAuto-check passed

  • Solver

    atopile/atopile

    How the Faebryk parameter solver works (Sets/Literals, Parameters, Expressions), the core invariants enforced during mutation, and practical workflows for debugging and extending the solver.

    4k GitHub stars~2.3k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Bump Sentry Dependency

    getsentry/sentry

    Official

    Bumps an existing Python dependency in getsentry/sentry through the repository's self-serve GitHub Actions workflow.

    45k GitHub stars~815 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Logseq Dependency Upgrade

    logseq/logseq

    Audit, plan, and refresh dependency upgrades for the Logseq repository by scanning every non-gitignored package.json, deps.edn, bb.edn and nbb.edn manifest, checking latest upstream versions…

    45k GitHub stars~1.1k tokensUpdated today
    Knowledge ManagementAuto-check passed

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

  • Compiling

    gkeyllorg/gkeyll

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

    112 GitHub stars~759 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

  • 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

Questions about Directory Structure

What does Directory Structure do?

Locate Gkeyll code and understand solver dependencies when exploring the repository or deciding where new code belongs. Directory Structure is an agent skill from gkeyllorg/gkeyll. Locate Gkeyll code and understand solver dependencies when exploring the repository or deciding where new code belongs.

How do I install Directory Structure in Claude Code?

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

How do I install Directory Structure in Codex?

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

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

What does Directory Structure need to run?

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

Does Directory Structure 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 Directory Structure 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 Directory Structure use?

Directory Structure 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 Directory Structure use?

About 695 tokens (SKILL.md is roughly 2.8k 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 Directory Structure?

Skills that share tags, products or a category with Directory Structure: Dependency Scanning (sickn33/agentic-awesome-skills, 47k stars), Dependency Check (ruvnet/ruflo, 74k stars), Dependency Update (codewhale-hq/Codewhale, 41k stars) and Solver (atopile/atopile, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Directory Structure?

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.