agentleFS
projectbluefinprojectbluefin/finpilot/.agents/skills/customize/SKILL.md

customize

Skill131 starsChanged 18 days agoApache-2.0View on GitHub

Decide where a package, app, or command belongs — dnf5 at build time, Homebrew, Flatpak, or ujust — and how each is validated. Use when adding or removing something from the image.

40 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-discord, add-slack and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • +10 more from microsoft

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Prefer a package the base already ships.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “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
SKILL.md

Customize

Where does it go?

The thing is…Put it inInstalled
A system package the image needs to boot or runbuild/20-packages-and-services.shat build time
A CLI tool a user chooses to havecustom/brew/*.Brewfileon demand, by the user
A GUI applicationcustom/flatpaks/*.preinstallon first boot
A command that configures the systemcustom/ujust/*.justavailable from first login
A system file: unit, preset, tmpfiles.dcustom/files/at build time
Per-user config for new accountscustom/config/at build time, into /etc/skel

The dividing line is who decides and when: build time for what the image must have, runtime for what the user chooses.

By destination

Build-time packages

build/20-packages-and-services.sh. Use dnf5, always with -y, and disable any repository you enable. build/README.md has the phase map.

Prefer a package the base already ships. When a COPR is unavoidable, copr_install_isolated enables and disables it for you.

Homebrew

Brewfiles in custom/brew/, plus a ujust recipe so users install it by name. custom/brew/README.md has the format.

Flatpak

Preinstall declarations in custom/flatpaks/. The app must exist on Flathub; just validate-flatpaks checks. custom/flatpaks/README.md has the format and the first-boot behaviour.

ujust

Recipes in custom/ujust/. No dnf5 or rpm — the image is immutable. custom/ujust/README.md has the recipe shape.

System files and user config

custom/files/ mirrors /; custom/config/ seeds /etc/skel/.config/. Each directory's README has the semantics.

Removing something

The reverse of adding: delete the line or the file, then check nothing still references it. A package removed from the package phase may still arrive as a dependency or from an overlay; bootc container lint and the image build catch the obvious cases.

Validate

just validate-brewfiles
just validate-flatpaks
just check
just build

CI runs validate-brewfiles, validate-flatpaks, and validate-justfiles on every pull request.

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.