Awesome-claude-skills docker_hub-automation
Automate Docker Hub tasks via Rube MCP (Composio): repositories, images, tags, and container registry management. Always search tools first for current schemas.
git clone https://github.com/ComposioHQ/awesome-claude-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComposioHQ/awesome-claude-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/composio-skills/docker_hub-automation" ~/.claude/skills/composiohq-awesome-claude-skills-docker-hub-automation-6ff1a7 && rm -rf "$T"
composio-skills/docker_hub-automation/SKILL.mdDocker 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
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Docker Hub connection via
with toolkitRUBE_MANAGE_CONNECTIONSdocker_hub - Always call
first to get current tool schemasRUBE_SEARCH_TOOLS
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.
- Verify Rube MCP is available by confirming
respondsRUBE_SEARCH_TOOLS - Call
with toolkitRUBE_MANAGE_CONNECTIONSdocker_hub - If connection is not ACTIVE, follow the returned auth link to complete setup
- 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:
- Search for all relevant tools:
with specific use caseRUBE_SEARCH_TOOLS - Execute prerequisite steps first (e.g., fetch before update)
- Pass data between steps using tool responses
- Use
for bulk operations or data processingRUBE_REMOTE_WORKBENCH
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
if connection expiredRUBE_MANAGE_CONNECTIONS
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
to load full input schemas whenRUBE_GET_TOOL_SCHEMAS
is returned instead ofschemaRef
.input_schema
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | with Docker Hub-specific use case |
| Connect | with toolkit |
| Execute | with discovered tool slugs |
| Bulk ops | with |
| Full schema | for tools with |
Toolkit docs: composio.dev/toolkits/docker_hub