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

SKILL

apiflash-automation

Name: apiflash-automation
Author: Composio

Automate Apiflash tasks like webpage screenshots and workflow integrations 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 itself is a prompt-style open-source entry, but its functionality depends on external Rube MCP and an Apiflash connection. Based on the materials, the main concern is the use of third-party services for remote tool discovery and execution, rather than any malicious local behavior in the skill itself; given the open-source source and strong community adoption, it is better classified as caution rather than high risk.

CredentialsCaution

The material says the skill itself needs no API key, but it does require establishing an Apiflash connection via RUBE_MANAGE_CONNECTIONS and completing authentication, which implies credentials are involved in the external connection flow. There is no evidence that the skill text directly asks users to expose local secrets, but tokens would be handled by the Rube/Apiflash side.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint https://rube.app/mcp and using Composio/Rube to search tools, check connections, and execute workflows. This means task inputs, session IDs, and tool arguments may be sent to a third-party service. The egress target is related to the declared function, but the material does not detail data minimization, retention, or onward transfer scope.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no bundled executable scripts, install commands, or local process launch steps. While downstream MCP tooling may perform remote tool operations, the skill itself does not request local code execution or elevated system capabilities.

Data accessCaution

The skill itself does not claim to read or write local files or directly access local resources, but it does send task content and parameters to external services via RUBE_SEARCH_TOOLS, RUBE_MULTI_EXECUTE_TOOL, and RUBE_REMOTE_WORKBENCH. Because the exact Apiflash tools are discovered dynamically, the ultimate data-access boundary is not fully transparent in the material, so sensitive input should be limited.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (about 64.9k stars), which is a meaningful risk-reducing factor. The visible content is mainly documentation/skill text rather than a closed-source binary; although the license is unspecified and maintenance status is unknown, that alone is not enough to raise it to high risk.

Recommendations

Only connect it after confirming you trust the rube.app / Composio / Apiflash services, terms, and data-handling practices.
Avoid submitting unnecessary sensitive business data or personal information in tool searches, execution arguments, or sessions.
Use least-privilege Apiflash accounts for the connection, and regularly review or revoke unused authorizations.
Before production use, manually inspect the concrete tool schemas and operation scope returned by RUBE_SEARCH_TOOLS.

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 "apiflash-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/apiflash-automation/SKILL.md
2. Save it as ~/.claude/skills/apiflash-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Apiflash Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/apiflash

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Apiflash connection via RUBE_MANAGE_CONNECTIONS with toolkit apiflash
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 apiflash
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: "Apiflash 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 Apiflash task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["apiflash"]
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 Apiflash-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `apiflash`
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 AppsFlyer queries, reports, and attribution tasks through Rube MCP.

ComposioGet→

$ loading_