agentleFS
ecosyste-msecosyste-ms/claude-plugin/skills/docker/SKILL.md

docker

Skill3 starsChanged 6 months agoMITView on GitHub

Query docker.ecosyste.ms for Docker Hub image metadata and the system/language packages installed inside images (via Syft SBOMs). Use when checking what's inside a Docker image, finding which images ship a given OS or language package, or browsing Linux distro variants.

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ml-training-recipe, replication 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.
  • getcompanion-aiSkill

    ml-training-recipe

    Find implementable ML training recipes from papers, datasets, docs, and code. Use when the user wants to fine-tune, train, reproduce, or choose a practical ML method, dataset, hyperparameter setup, or benchmark recipe.

    Also in 3 projects that use this

  • getcompanion-aiSkill

    replication

    Plan a replication of a paper, claim, or benchmark, and execute only after an explicit environment choice. Use when the user asks to replicate results, reproduce an experiment, verify a claim empirically, or build a replication package.

    Also in 3 projects that use this

  • Sorcha-PlatformSkill

    scalar

    Generates and configures Scalar OpenAPI UI for API documentation. Use when: Adding API documentation to services, configuring OpenAPI endpoints, customizing documentation themes

    Also in 3 projects that use this

  • brainbytes-devSkill

    alpha-research

    Also in 3 projects that use this

  • JaimeParkerSkill

    paper-code-audit

    Perform three-way cross-validation of a research paper by comparing the original paper text (via Zotero), official code implementation (via Git), and personal Obsidian notes. Use this skill whenever the user wants to "audit a paper", "verify paper claims against code", "cross-check notes with implementation", "triangulate paper + code + notes", "find discrepancies between paper and code", or mentions wanting a deep, structured comparison of a paper's claims against its implementation and their own notes. Also trigger when the user asks to "analyze this paper thoroughly" with code available, or when they want to systematically reconcile what the paper says, what the code does, and what their notes claim.

    Also in 3 projects that use this

  • Sorcha-PlatformSkill

    redis

    Implements Redis caching, session management, and distributed coordination for the Sorcha platform. Use when: Adding caching layers, token revocation, rate limiting, SignalR backplane, or distributed state.

    Also in 5 projects that use this

  • +1 more from getcompanion-ai

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 46 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:

    All responses are JSON. No auth required.

    line 11

“Common” is measured: kept by at least 6 in 10 of the 46 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

ecosyste.ms Docker API

Base URL: https://docker.ecosyste.ms/api/v1

All responses are JSON. No auth required. Set a User-Agent header.

Full OpenAPI spec: https://docker.ecosyste.ms/docs/api/v1/openapi.yaml

Docker images

Image names containing / must be URL-encoded (%2F). Official images live under the library/ namespace.

curl -s 'https://docker.ecosyste.ms/api/v1/packages/library%2Fnginx'
curl -s 'https://docker.ecosyste.ms/api/v1/packages/grafana%2Fgrafana'

Returns: name, description, downloads, versions_count, latest_release_number, latest_release_published_at, dependencies_count, has_sbom, repository_url.

Image versions (tags) and their contents

curl -s 'https://docker.ecosyste.ms/api/v1/packages/library%2Fnginx/versions'
curl -s 'https://docker.ecosyste.ms/api/v1/packages/library%2Fnginx/versions/1.27.0'

The version response includes a dependencies array listing every OS and language package found in the image SBOM (ecosystem, name, version).

Reverse lookup: which images contain a package

Ecosystem names here come from Syft: deb, rpm, apk, npm, pypi, gem, golang, maven, cargo, nuget, composer, binary. Package names with / must be URL-encoded.

# how many images ship this package, total downloads of those images
curl -s 'https://docker.ecosyste.ms/api/v1/usage/npm/lodash'
curl -s 'https://docker.ecosyste.ms/api/v1/usage/deb/openssl'
curl -s 'https://docker.ecosyste.ms/api/v1/usage/golang/github.com%2Fstretchr%2Ftestify'

# list all ecosystems with counts
curl -s 'https://docker.ecosyste.ms/api/v1/usage'

# packages in an ecosystem ranked by image count
curl -s 'https://docker.ecosyste.ms/api/v1/usage/apk?per_page=20'

Linux distros

Distros and versions detected from /etc/os-release across indexed images:

curl -s 'https://docker.ecosyste.ms/api/v1/distros'
curl -s 'https://docker.ecosyste.ms/api/v1/distros/alpine-3-19'
curl -s 'https://docker.ecosyste.ms/api/v1/distros/alpine-3-19/versions'

Pagination

List endpoints accept ?page=N&per_page=N.

When to use

  • Inspecting what packages are bundled inside a Docker image without pulling it
  • Finding which popular images include a vulnerable system library
  • Estimating the Docker-side blast radius of a package
  • Comparing base image distro choices

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.