Docker Hub Automation
Automate Docker Hub operations -- manage organizations, repositories, teams, members, and webhooks via the Composio MCP integration.
What this skill does
# Docker Hub Automation Automate your Docker Hub workflows -- create and manage organizations, repositories, teams, add members, set up image push webhooks, and list container images. **Toolkit docs:** [composio.dev/toolkits/docker_hub](https://composio.dev/toolkits/docker_hub) --- ## Setup 1. Add the Composio MCP server to your client: `https://rube.app/mcp` 2. Connect your Docker Hub account when prompted (JWT/token authentication) 3. Start using the workflows below --- ## Core Workflows ### 1. List Organizations Use `DOCKER_HUB_LIST_ORGANIZATIONS` to discover which organizations the authenticated user belongs to. ``` Tool: DOCKER_HUB_LIST_ORGANIZATIONS Inputs: - page: integer (1-indexed, default 1) - page_size: integer (1-100, default 25) ``` ### 2. Create an Organization Use `DOCKER_HUB_CREATE_ORGANIZATION` to programmatically create a new Docker Hub organization. ``` Tool: DOCKER_HUB_CREATE_ORGANIZATION Inputs: - orgname: string (required) -- lowercase, letters/numbers/._- only, min 2 chars - company: string (optional) -- company name associated with the org ``` **Note:** Requires JWT authentication obtained via `/v2/users/login` and may have restricted access. ### 3. Get Organization Details and Repositories Use `DOCKER_HUB_GET_ORGANIZATION` to retrieve namespace info and its repositories. Works with any public namespace. ``` Tool: DOCKER_HUB_GET_ORGANIZATION Inputs: - organization: string (required) -- e.g., "docker", "bitnami", "library" ``` ### 4. Create a Repository Use `DOCKER_HUB_CREATE_REPOSITORY` to create public or private repositories under a namespace. ``` Tool: DOCKER_HUB_CREATE_REPOSITORY Inputs: - namespace: string (required) -- Docker Hub username or org name - name: string (required) -- lowercase; letters, numbers, ._- allowed - description: string (optional) -- max 100 characters - full_description: string (optional) -- Markdown README content - is_private: boolean (default false) -- private repos require paid plan ``` ### 5. List Repositories with Filtering Use `DOCKER_HUB_LIST_REPOSITORIES` to enumerate repos within a namespace with sorting and content-type filtering. ``` Tool: DOCKER_HUB_LIST_REPOSITORIES Inputs: - namespace: string (required) -- e.g., "library", "myorg" - ordering: "name" | "last_updated" | "pull_count" (prefix with - for descending) - page: integer (default 1) - page_size: integer (1-100, default 25) - content_types: string (comma-separated, e.g., "image,artifact") ``` ### 6. Manage Teams, Members, and Webhooks Use `DOCKER_HUB_LIST_TEAMS` to list teams within an org, `DOCKER_HUB_ADD_ORG_MEMBER` to invite users, and `DOCKER_HUB_CREATE_WEBHOOK` for push notifications. ``` Tool: DOCKER_HUB_LIST_TEAMS - Lists all teams/groups within a Docker Hub organization Tool: DOCKER_HUB_ADD_ORG_MEMBER - Invite a user to join an organization by Docker ID or email - Requires owner or admin permissions Tool: DOCKER_HUB_CREATE_WEBHOOK - Create a webhook on a repository for image push notifications - Two-step process: create webhook, then add hook URL - Requires admin permissions on the repository ``` --- ## Known Pitfalls | Pitfall | Detail | |---------|--------| | JWT authentication | `DOCKER_HUB_CREATE_ORGANIZATION` requires JWT auth from `/v2/users/login` -- standard API tokens may not suffice. | | Private repo limits | Creating private repos (`is_private: true`) requires a paid Docker Hub plan. | | Org name constraints | Organization names must be lowercase, at least 2 characters, containing only letters, numbers, `.`, `_`, or `-`. | | Webhook two-step | `DOCKER_HUB_CREATE_WEBHOOK` is a two-step process: first create the webhook with a name, then add a hook URL to it. | | Pagination | All list endpoints use page-based pagination -- iterate pages until results are exhausted. | --- ## Quick Reference | Tool Slug | Description | |-----------|-------------| | `DOCKER_HUB_LIST_ORGANIZATIONS` | List orgs the user belongs to | | `DOCKER_HUB_CREATE_ORGANIZATION` | Create a new Docker Hub organization | | `DOCKER_HUB_GET_ORGANIZATION` | Get org details and repository list | | `DOCKER_HUB_CREATE_REPOSITORY` | Create a repository under a namespace | | `DOCKER_HUB_LIST_REPOSITORIES` | List repos with filtering and sorting | | `DOCKER_HUB_LIST_TEAMS` | List teams/groups within an org | | `DOCKER_HUB_ADD_ORG_MEMBER` | Invite a user to an organization | | `DOCKER_HUB_CREATE_WEBHOOK` | Create push-notification webhook on a repo | --- *Powered by [Composio](https://composio.dev)*
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.