Dockerhub Automation

When to use this skill

Use Dockerhub Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Docker Hub tasks via Rube MCP (Composio): repositories, images, tags, and container registry management. Always search tools first for current schemas.

When not to use it

Skip Dockerhub Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

1. Personal install: create ~/.claude/skills/dockerhub-automation/SKILL.md (and any bundled scripts) so Claude Code, Claude Desktop, and compatible agents can load it in every project.
2. Project install: commit the same folder at .claude/skills/dockerhub-automation/ so teammates get the skill with the repo.
3. Restart the agent session after copying files so it re-scans the skills directory, then ask for the task in words that match the skill description.

Full install guide for Claude, Cursor, and Codex

What this skill does

# Docker Hub Automation via Rube MCP

Automate Docker Hub operations through Composio's Docker Hub toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/docker_hub](https://composio.dev/toolkits/docker_hub)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Docker Hub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

## Setup

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` 3. If connection is not ACTIVE, follow the returned auth link to complete setup 4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

``` RUBE_SEARCH_TOOLS: queries=[{"use_case": "repositories, images, tags, and container registry management", "known_fields": ""}] ```

This returns: - Available tool slugs for Docker Hub - Recommended execution plan steps - Known pitfalls and edge cases - Input schemas for each tool

## Core Workflows

### 1. Discover Available Docker Hub Tools

``` RUBE_SEARCH_TOOLS: queries: - use_case: "list all available Docker Hub tools and capabilities" ```

Review the returned tools, their descriptions, and input schemas before proceeding.

### 2. Execute Docker Hub Operations

After discovering tools, execute them via:

``` RUBE_MULTI_EXECUTE_TOOL: tools: - tool_slug: "<discovered_tool_slug>" arguments: {<schema-compliant arguments>} memory: {} sync_response_to_workbench: false ```

### 3. Multi-Step Workflows

For complex workflows involving multiple Docker Hub operations:

1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case 2. Execute prerequisite steps first (e.g., fetch before update) 3. Pass data between steps using tool responses 4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing

## Common Patterns

### Search Before Action Always search for existing resources before creating new ones to avoid duplicates.

### Pagination Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted.

### Error Handling - Check tool responses for errors before proceeding - If a tool fails, verify the connection is still ACTIVE - Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired

### Batch Operations For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution.

## Known Pitfalls

- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. - **Check connection status**: Ensure the Docker Hub connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. - **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. - **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`.

## Quick Reference

| Operation | Approach | |-----------|----------| | Find tools | `RUBE_SEARCH_TOOLS` with Docker Hub-specific use case | | Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` | | Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | | Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | | Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` |

> **Toolkit docs**: [composio.dev/toolkits/docker_hub](https://composio.dev/toolkits/docker_hub)

Intended uses

• Use Dockerhub Automation when this documented workflow matches the task.