agentleFS
Sign inStart free
ekala-projectekala-project/ekala-claude-skills/AGENTS.md

ekala-claude-skills

AGENTS.md1 starsChanged 9 months agoMITView on GitHub

Centralized AI skills for ekapkgs and the broader Ekala ecosystem. Consumed as a Claude Code plugin. Read the guide matching the package's build system or language. 1. Create skills/<skill-name>/SKILL.md with YAML frontmatter (name, description) followed by the skill prompt. 2. Follow the naming and structure conventions enforced by scripts/. 3. Update README.md with a short entry for the new skill. Skills should target concrete Ekala/Nix workflows: building, evaluation, packaging patterns, toolchain integration, etc. Keep each skill focused on a single…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository14 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not: add AI attribution (e.g., Co-Authored-By) to commit messages

    line 8
  2. Distinctive:

    Read the guide matching the package's build system or language.

    line 12
  3. Very specific:

    Create skills/<skill-name>/SKILL.md with YAML frontmatter (name, description) followed by the skill prompt.

    line 52
  4. Very specific:

    Follow the naming and structure conventions enforced by scripts/.

    line 54
  5. Distinctive:

    Update README.md with a short entry for the new skill.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Ekala AI Skills

Centralized AI skills for ekapkgs and the broader Ekala ecosystem. Consumed as a Claude Code plugin.

Commit Conventions

  • Do not add AI attribution (e.g., Co-Authored-By) to commit messages

Writing Packages

Read the guide matching the package's build system or language.

TaskGuide
Nix expression basics (mkDerivation, finalAttrs, meta, deps, fetchers, patches, outputs, passthru)packaging
Python (buildPythonPackage, pyproject, build-system, testPaths, disabledTests, pythonImportsCheck)python
Rust (buildRustPackage, cargoHash, cargoBuildFlags, checkFlags)rust
Go (buildGoModule, vendorHash, ldflags, subPackages)go
CMake project (cmake.configurePhaseHook, cmakeEntries)cmake
CMake+Nix troubleshooting (attributes, flags, cross-compilation)ekala-cmake-nix
Meson project (meson.configurePhaseHook, mesonEntries, mesonFeatures)meson
Multi-version package (mkManyVariants, variants.nix)mk-many-variants
Porting from nixpkgs (copy, strip maintainers/updateScript, TODO missing deps)porting
Bash phases under structured attrs (array iteration, env attrset, substituteAll)structured-attrs

Repository Scaffolding

TaskGuide
Create a new ekapkgs-style repo (flake, pins, CI, GitHub Actions)ekapkgs-repo

Fixing Build Failures

SymptomGuide
Eval or build error — validation workflow, nix-instantiate, nix-build, nix fmtvalidation
General Nix build failures and troubleshootingnix-build
Nix evaluation, inspecting expressionsnix-eval

Repository Layout

skills/
  <skill-name>/
    SKILL.md          # Skill definition (frontmatter + prompt)
scripts/              # CI validation scripts

Adding a Skill

  1. Create skills/<skill-name>/SKILL.md with YAML frontmatter (name, description) followed by the skill prompt.
  2. Follow the naming and structure conventions enforced by scripts/.
  3. Update README.md with a short entry for the new skill.

Skills should target concrete Ekala/Nix workflows: building, evaluation, packaging patterns, toolchain integration, etc. Keep each skill focused on a single responsibility.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free