$ ~/registry/skill/composiohq-composio-skills-front-automation

SKILL

front-automation

Name: front-automation
Author: Composio

Automate Front inbox conversations, contacts, and team workflows via Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill appears to be prompt-only open-source content, but it explicitly relies on remote Rube MCP and Composio/Front connections to discover and execute tools, so the overall posture is caution rather than high risk. The materials do not claim local code execution or local file access, and no direct API key is requested, but it does involve external services interacting with a Front account.

CredentialsCaution

The materials state that no API keys are needed, but they require an active `front` toolkit connection via `RUBE_MANAGE_CONNECTIONS` and an auth link, which implies use of Front account authorization tokens. There is no sign of asking users to paste secrets directly; the main concern is the third-party connection being granted access to Front, which is a normal integration caution.

Network egressCaution

The README explicitly instructs adding the remote MCP endpoint `https://rube.app/mcp` and performing actions through Composio's Front toolkit; therefore, user instructions and relevant Front operation data are handled by external services. Although the system metadata lists no host, the documentation clearly names the remote endpoint and service ownership, making this a declared, ordinary egress pattern rather than a standalone high-risk red flag.

Code executionLow risk

Based on the provided materials, this is a prompt-only skill description with no local script installation, shell execution, or steps requiring processes to be started on the user's machine. The referenced execution occurs at the MCP tool layer (such as `RUBE_MULTI_EXECUTE_TOOL` / `RUBE_REMOTE_WORKBENCH`), not as direct local code execution granted by this skill itself.

Data accessCaution

The skill is intended to automate Front operations, which means it can access whatever conversations, messages, or related business data the user authorizes within Front; however, the materials do not claim access to local files, system directories, or unrelated resources. Data access appears primarily bounded by Front authorization scopes and the third-party connection, which is a standard SaaS integration caution.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (about 64.9k stars), both of which are meaningful risk-reducing signals; the audited item also looks like README/skill prompt content rather than an executable binary. The missing license declaration and unknown maintenance status add some uncertainty, but without further red flags they do not justify a high-risk rating.

Recommendations

Grant only the minimum Front permissions needed for the task, and regularly review/revoke Composio or Rube connections.
Before using it on production data, test with a sandbox workspace or low-sensitivity account to verify what Front resources it reads or modifies.
Confirm that your client really connects to `https://rube.app/mcp`, and review its privacy, logging retention, and data handling policies.
If you later install the actual Rube MCP or related tooling, audit that software separately for code, dependencies, and runtime privileges.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "front-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/front-automation/SKILL.md
2. Save it as ~/.claude/skills/front-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Front Automation via Rube MCP

Automate Front operations through Composio's Front toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/front

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Front connection via RUBE_MANAGE_CONNECTIONS with toolkit front
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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit front
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: "Front operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Front task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["front"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Front-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `front`
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`

Powered by Composio

Automate MailerSend sending and management tasks through Rube MCP workflows.

ComposioGet→

$ loading_