logo-dev-automation

by ComposioHQ

logo-dev-automation helps Claude run Logo Dev operations through Composio Rube MCP by discovering current tool schemas, checking the logo_dev connection, and executing workflows safely.

Stars67.5k

Favorites0

Comments0

AddedJul 12, 2026

CategoryWorkflow Automation

Install Command

npx skills add ComposioHQ/awesome-claude-skills --skill logo-dev-automation

Curation Score

This skill scores 66/100, which means it is acceptable for listing but should be presented as a lightweight connector/workflow prompt rather than a deeply packaged automation skill. Directory users get enough information to know it is for Logo Dev operations through Composio/Rube MCP and how an agent should start, authenticate, and discover tools, but the repository evidence shows limited Logo Dev-specific workflow substance and no supporting files beyond SKILL.md.

66/100

Strengths

Frontmatter is valid and clearly declares the trigger intent: automating Logo Dev tasks via Rube MCP, with `requires: mcp: [rube]`.
Prerequisites and setup steps are explicit, including adding `https://rube.app/mcp`, checking `RUBE_SEARCH_TOOLS`, and managing an active `logo_dev` connection.
The skill repeatedly instructs agents to search tools first for current schemas, reducing risk from stale or guessed Logo Dev tool parameters.

Cautions

No support files, scripts, resources, README, or metadata are present beyond SKILL.md, so adoption depends entirely on a short text guide.
Operational guidance is mostly discovery-oriented rather than Logo Dev-specific; users must rely on RUBE_SEARCH_TOOLS and external toolkit schemas for exact actions and parameters.

MCP Rube Composio Tool Integration API Branding

Overview

Overview of logo-dev-automation skill

What logo-dev-automation is for

logo-dev-automation is a Claude skill for running Logo Dev operations through Composio’s Rube MCP server. Instead of hard-coding one API shape, the skill instructs the agent to discover the current Logo Dev tool schemas first, verify the connection, and then execute the requested workflow through the available Rube tools.

Best-fit users and jobs

This skill is best for teams that already use Claude with MCP and want repeatable Logo Dev actions inside a broader agent workflow. Typical use cases include retrieving brand/logo data, automating Logo Dev toolkit calls, and embedding logo-related operations into research, enrichment, or internal workflow automation tasks. It is especially relevant if you want logo-dev-automation for Workflow Automation rather than one-off manual API calls.

Main differentiator

The most important behavior is the “search tools first” pattern. The Logo Dev toolkit schema can change, so logo-dev-automation tells the agent to call RUBE_SEARCH_TOOLS before execution. That reduces brittle prompts, stale field names, and failed calls caused by assuming an old schema.

Adoption requirements

Before installing, confirm your client supports MCP and can connect to Rube. The skill requires Rube MCP with RUBE_SEARCH_TOOLS available and an active Logo Dev connection through RUBE_MANAGE_CONNECTIONS using toolkit logo_dev. If you cannot use MCP tools, this skill will not provide much value beyond general prompting guidance.

How to Use logo-dev-automation skill

logo-dev-automation install and setup path

Install the skill from the repository with:

npx skills add ComposioHQ/awesome-claude-skills --skill logo-dev-automation

Then add Rube as an MCP server in your client configuration:

https://rube.app/mcp

After restarting or refreshing your MCP client, verify that RUBE_SEARCH_TOOLS responds. Next, call RUBE_MANAGE_CONNECTIONS for toolkit logo_dev. If the returned status is not ACTIVE, complete the authentication link and re-check before asking the agent to run Logo Dev actions.

What to read before using it

Start with composio-skills/logo-dev-automation/SKILL.md. This repository path contains the operating contract for the skill: prerequisites, setup, tool discovery, connection checks, and the core execution pattern. There are no extra scripts, reference folders, rules, or metadata files in the skill directory, so the SKILL.md is the source of truth.

For external tool behavior, use the linked toolkit documentation at composio.dev/toolkits/logo_dev, but still let the agent discover live schemas through Rube before execution.

Turning a rough goal into a usable prompt

A weak prompt is: “Use Logo Dev to get logos.”

A stronger logo-dev-automation usage prompt is:

“Use the logo-dev-automation skill. First call RUBE_SEARCH_TOOLS for the specific Logo Dev task: find the official logo and brand metadata for these domains: example.com, stripe.com, and github.com. Check the logo_dev connection with RUBE_MANAGE_CONNECTIONS before execution. Use only fields confirmed by the discovered schema. Return a table with domain, logo URL or asset reference, brand name, confidence/notes if available, and any failures.”

This works better because it gives the agent the task, entities, output format, required discovery step, and failure-handling expectations.

Practical workflow to follow

Use a three-step loop: discover, verify, execute. First, call RUBE_SEARCH_TOOLS with the exact use case, not a generic “Logo Dev operations” query. Second, verify the logo_dev connection is active. Third, run the selected tool using the discovered schema. If a call fails, do not guess field names; search again with the failed action and error context.

logo-dev-automation skill FAQ

Is logo-dev-automation only for Composio users?

It is for users who can access Logo Dev through Composio’s Rube MCP. The skill depends on Rube tools such as RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS. If your environment does not expose those tools, use the Logo Dev API or toolkit documentation directly instead.

How is this better than an ordinary prompt?

A normal prompt may invent tool names or rely on stale API assumptions. The logo-dev-automation skill adds a safer execution pattern: discover current tools, inspect schemas, confirm authentication, then act. That is the main reason to install it if you run Logo Dev tasks repeatedly.

Is it beginner-friendly?

It is beginner-friendly for MCP users, but not for users who have never configured an MCP server. The skill itself is short and direct, but successful use depends on connecting Rube, activating the logo_dev toolkit connection, and understanding that the agent must call tools rather than just describe what to do.

When should I not use this skill?

Do not use it if you only need a static explanation of Logo Dev, if your client cannot run MCP tools, or if your workflow requires fully offline logo processing. Also avoid it when you need a heavily customized multi-step business process; this skill provides the Logo Dev automation pattern, not a full application-specific workflow.

How to Improve logo-dev-automation skill

Improve logo-dev-automation prompts with task context

The fastest way to improve results is to include the exact Logo Dev job, input list, desired fields, and output format. For example, specify whether you need logo URLs, brand metadata, company identity checks, enrichment for a CSV, or validation of existing assets. The more precise the use case, the better RUBE_SEARCH_TOOLS can return relevant tool slugs and schemas.

Common failure modes to prevent

The most common adoption blocker is skipping connection verification. If the logo_dev connection is inactive, execution will fail even if tool discovery works. Another failure mode is letting the agent reuse an old schema. Tell it explicitly: “Do not call Logo Dev tools until you have searched current schemas and selected fields from the result.”

Iterate after the first output

After the first run, ask the agent to summarize which Rube tool was used, which required fields were supplied, which records failed, and whether the failures were caused by missing input, auth, schema mismatch, or no Logo Dev result. This makes the next run more reliable and turns the skill from a one-shot call into a repeatable workflow automation asset.

Repository-level improvements worth considering

The skill would be stronger with a short README.md, example prompts for common Logo Dev tasks, and one or two sample RUBE_SEARCH_TOOLS queries showing expected input patterns. A troubleshooting section for inactive connections, schema mismatches, and partial results would also make the logo-dev-automation guide easier to adopt without reading the whole MCP flow carefully.

Ratings & Reviews

No ratings yet

Share your review

0/10000

Latest reviews

Saving...

more skill

playwright-interactive

by openai

playwright-interactive is a browser automation skill for persistent Playwright sessions in local web and Electron apps. Use it to inspect UI state, retry interactions, and run functional or visual QA without restarting the toolchain. Ideal when you need a practical playwright-interactive guide for iterative debugging.

Browser Automation

Favorites 0GitHub 0

huggingface-datasets

by huggingface

Use the huggingface-datasets skill for Hugging Face Dataset Viewer API workflows to validate datasets, resolve splits, preview and paginate rows, search text, apply filters, and fetch parquet links or statistics. It is a practical huggingface-datasets guide for read-only dataset exploration.

Web Scraping

Favorites 0GitHub 10.4k

iterative-retrieval

by affaan-m

iterative-retrieval is a workflow pattern for progressively refining context retrieval in agentic work. It helps subagents avoid too much or too little context, making it useful for iterative-retrieval usage, install decisions, and iterative-retrieval for Workflow Automation.

Workflow Automation

Favorites 0GitHub 156.2k

data-scraper-agent

by affaan-m

data-scraper-agent helps build a repeatable public-data pipeline for web scraping, enrichment, and storage. It is designed for monitoring jobs, prices, news, repos, sports, and listings on a schedule using GitHub Actions, with outputs to Notion, Sheets, or Supabase. Best for ongoing tracking, not one-off extractions.

Web Scraping

Favorites 0GitHub 156.1k

inbox-triage

by alirezarezvani

inbox-triage runs recurring or on-demand email triage from an inbox-setup knowledge base. It classifies recent mail, researches senders, recommends actions, drafts replies without sending, logs results, and updates `${WORKSPACE}/Email/` using helper scripts for KB validation, search windows, and draft safety.

Workflow Automation

Favorites 0GitHub 22.2k

changelog-generator

by alirezarezvani

changelog-generator turns Conventional Commit history into auditable Keep a Changelog release notes. Use this changelog-generator skill to lint commits, infer semver bumps, generate CHANGELOG.md entries, and support CI, monorepo, hotfix, and Technical Writing workflows.

Technical Writing

Favorites 0GitHub 22.2k

notion-meeting-intelligence

by openai

notion-meeting-intelligence helps turn Notion context into meeting-ready agendas and pre-reads, with Codex research for decisions, status, planning, retros, and 1:1 prep. Best for the notion-meeting-intelligence for Meeting Prep workflow when you need grounded materials, clear timeboxes, and attendee-specific outputs.

Meeting Prep

Favorites 0GitHub 18.6k

multi-agent-patterns

by muratcankoylan

The multi-agent-patterns skill helps you design and implement agent systems with Agent Orchestration, context isolation, parallel work, and structured handoffs. Use it when choosing between a single agent and a multi-agent setup, or when you need supervisor routing, peer handoffs, consensus, or fault handling. It is best for orchestration-heavy tasks where clear coordination matters more than adding agents.

Agent Orchestration

Favorites 0GitHub 15.6k

building-incident-response-playbook

by mukul975

building-incident-response-playbook helps security teams create reusable incident response playbooks with step-by-step phases, decision trees, escalation criteria, RACI ownership, and SOAR-ready structure. It is designed for incident response procedure documentation, incident triage workflows, and audit-friendly operational response plans.

Incident Triage

Favorites 0GitHub 6.1k

building-patch-tuesday-response-process

by mukul975

building-patch-tuesday-response-process helps teams build a repeatable Microsoft Patch Tuesday process to triage advisories, rank risk, test patches, approve rollout, and track compliance. Useful for security operations, vulnerability management, and building-patch-tuesday-response-process for Project Management.

Project Management

Favorites 0GitHub 6.1k

read

by tw93

The read skill fetches URLs and PDFs as clean Markdown for reading, quoting, citation, and downstream work. It is built for read usage on paywalled pages, JS-heavy sites, X/Twitter, GitHub files, Chinese platforms, and Workflow Automation flows that need reliable source text before analysis. Use the read guide when you want source capture, not commentary.

Workflow Automation

Favorites 0GitHub 5.1k

secure-workflow-guide

by trailofbits

secure-workflow-guide guides a 5-step Solidity security workflow: Slither triage, feature-specific checks, visual inspection, security-property notes, and manual review. It is built for smart contract teams, auditors, and builders who want a repeatable secure-workflow-guide guide before deployment or release.

Security Audit

Favorites 0GitHub 4.9k

twitter-cli

by public-clis

twitter-cli is a terminal-first Twitter/X skill for reading timelines, bookmarks, search results, profiles, and tweet details, with posting and other write actions when authenticated. Use it for Social Media research, account monitoring, and lightweight publishing from the command line.

Social Media

Favorites 0GitHub 2.3k

azure-ai-contentunderstanding-py

by microsoft

azure-ai-contentunderstanding-py is the Python skill for Azure AI Content Understanding. It extracts structured content from documents, images, audio, and video for RAG workflows and automation. Use it when you need reliable multimodal extraction, Azure authentication, and repeatable pipeline-ready output.

RAG Workflows

Favorites 0GitHub 2.2k

wp-performance

by WordPress

Use wp-performance to investigate and improve WordPress performance from the backend, without a browser UI. It supports measurement-first diagnosis for slow frontend requests, admin pages, REST routes, and WP-Cron, with guidance on WP-CLI profile/doctor, Query Monitor via REST headers, Server-Timing, database queries, autoloaded options, object caching, cron, and remote HTTP calls.

Performance Optimization

Favorites 0GitHub 1.4k

wp-wpcli-and-ops

by WordPress

The wp-wpcli-and-ops skill helps with WordPress operations in WP-CLI: safe search-replace, db export/import, plugin and theme actions, cron, cache flushing, multisite targeting, and repeatable automation for backend development.

Backend Development

Favorites 0GitHub 1.4k