agentleFS
Sign inStart free
diegopachecodiegopacheco/agent-skills/container-skill/SKILL.md

container-skill

Skill0 starsChanged 3 months agoUnlicenseView on GitHub

When need to create a containerized solution, use this skill to create a Containerfile and podman-compose files. IF user mentiond docker, docker-compose, use this skill.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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. Distinctive:

    Prefer name the file as Containerfile

    line 8
  2. Distinctive:

    Never use Docker, always use podman and podman-compose

    line 9
  3. Distinctive:

    Make sure you are using the latest versions

    line 10
  4. Distinctive:

    Do not write comments, never comment.

    line 11
  5. Distinctive:

    Make sure you dont do ENTER between commands make it compact

    line 12
  6. Distinctive:

    Never use docker-compose always use podman-compose

    line 15
  7. Very specific:

    always have a start.sh where you start docker-compose.

    line 18
  8. Very specific:

    always have a stop.sh to stop docker-compose.

    line 19
  9. Very specific:

    always have a test.sh where you show the feature is working.

    line 20
  10. Distinctive:

    dont use timeouts more than 1 min

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Containerfile

  • Prefer name the file as Containerfile
  • Never use Docker, always use podman and podman-compose
  • Make sure you are using the latest versions
  • Do not write comments, never comment.
  • Make sure you dont do ENTER between commands make it compact

podman-compose

  • Never use docker-compose always use podman-compose
  • This section only apply if you have podman-compose requirements otherwise ignore it.
  • docker-compose it's alias to podman, keep that in mind.
  • always have a start.sh where you start docker-compose.
  • always have a stop.sh to stop docker-compose.
  • always have a test.sh where you show the feature is working.
  • dont use timeouts more than 1 min

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