agentleFS
Sign inStart free
enunoenuno/unifi-mcp-server/.agents/skills/source-command-build-docker/SKILL.md

source-command-build-docker

Skill294 starsChanged 18 days agoApache-2.0View on GitHub

Build and test Docker image locally

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Use this skill when the user asks to run the migrated source command build-docker.

    line 8
  2. Distinctive:

    Check if Dockerfile exists.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

source-command-build-docker

Use this skill when the user asks to run the migrated source command build-docker.

Command Template

Build the Docker image locally and verify it works.

Execute the following steps:

  1. Check if Dockerfile exists; if not, offer to create one
  2. Build the Docker image: docker build -t unifi-mcp-server:local .
  3. Display the build output and any warnings
  4. List the image size and layers
  5. Optionally run the container with test environment variables

Report back with:

  • Build success/failure status
  • Image size
  • Any build warnings or errors
  • Suggestions for optimization if needed

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