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

SKILL

ngrok-automation

Name: ngrok-automation
Author: Composio

Automate Ngrok tunnels, endpoints, and operations through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be primarily an open-source prompt/instruction layer with strong community trust signals, and it shows no direct red flags such as local code execution or hardcoded secrets. The main caution is that it relies on external Rube MCP and Ngrok/Composio connections, so real data egress and account access boundaries depend on those remote services and granted scopes.

CredentialsCaution

The material says the skill itself needs 'no API keys,' but real usage requires activating an `ngrok` connection via `RUBE_MANAGE_CONNECTIONS` and completing auth through a returned link, implying credentials/tokens are likely brokered by Rube/Composio or established through OAuth. There is no sign of hardcoded secrets or obvious credential theft, but external account authorization still requires attention to granted scopes and token storage.

Network egressCaution

The README explicitly requires adding `https://rube.app/mcp` as an MCP server and performing remote actions through Composio's Ngrok toolkit; tool discovery, connection management, execution arguments, and session data will be sent to external services. The egress targets appear consistent with the stated functionality, with no unrelated or hidden endpoints shown, but using this skill does mean data leaves the local environment for Rube/Composio/Ngrok-related services.

Code executionLow risk

Based on the provided material, this is a prompt-only skill that mainly instructs how to call existing MCP tools; it does not describe itself running scripts locally, spawning processes, or requesting extra system privileges. Remote tool invocation exists, but there is no red flag indicating the skill itself performs local code execution.

Data accessCaution

The material does not show direct read/write access to local files or system data, but it can automate actions against external Ngrok resources through an authorized connection and pass context through session and `memory` parameters in remote workflows. The access surface is mainly the external account/tunnel resources rather than the local filesystem, so account permissions and the sensitivity of submitted content should be controlled.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption signals (64.7k stars), which materially lowers risk; the material is also classified as prompt-only and open-source. While the license is unspecified and maintenance status is unknown, those governance gaps alone do not amount to a high-risk supply-chain red flag here.

Recommendations

Only add `https://rube.app/mcp` in trusted clients, and verify the actual domain, certificate, and MCP permission boundaries.
Use least-privilege authorization for the Ngrok connection, and avoid high-privilege production accounts for automation testing.
Before sending arguments to `RUBE_MULTI_EXECUTE_TOOL`, avoid submitting unnecessary sensitive data and review whether `memory` or session state contains secrets.
Before deployment, review Rube/Composio privacy practices, token handling, audit logging, and connection revocation mechanisms.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Ngrok Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ngrok

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ngrok"]
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 Ngrok-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ngrok`
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 OpenRouter workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_