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

SKILL

helpwise-automation

Name: helpwise-automation
Author: Composio

Automate Helpwise support and collaboration tasks to streamline team workflows.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is an open-source prompt-only instruction asset from a highly trusted GitHub repository, with no clear red flags for local execution or local file access. The main security consideration is that it relies on remote Rube MCP and a connected Helpwise account, which may access and operate on Helpwise data on the user's behalf, so the overall posture is low to moderate caution.

CredentialsCaution

The material says the skill itself does not require local API keys or environment variables, but it does require an active Helpwise connection via `RUBE_MANAGE_CONNECTIONS` and an external auth-link flow. This means third-party managed account tokens/authorizations are still involved; there is no explicit sign of credential abuse, but the authorization scope and session handling should be reviewed.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing operations through the Composio/Helpwise toolchain; user requests and Helpwise-related data may therefore be transmitted to or processed by that remote service. The egress target and purpose are disclosed, which is typical for this kind of integration, but it still means business data may leave the local client environment.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no executable install script, shell command, or instruction to start local processes. It directs the user to call remote MCP tool interfaces rather than execute arbitrary local code, so no local code-execution red flag is evident.

Data accessCaution

The skill is intended to 'Automate Helpwise operations' and executes actions through a connected Helpwise toolkit, so its effective data access scope is the user's authorized Helpwise account data and objects. The material does not indicate access to the local filesystem, system directories, or unrelated resources, but the remote business-data access should still be reviewed under least-privilege principles.

Supply chainLow risk

The source is an open-source GitHub repository with very strong community adoption (64.7k stars), both of which materially reduce risk; the material is also a skill document rather than a closed-source binary. Although the license is not stated and maintenance status is unknown, that alone is not enough to create a high supply-chain risk signal, and overall auditability is reasonably good.

Recommendations

Before connecting Helpwise, verify the scopes requested by Composio/Rube and grant only the minimum permissions needed for the automation.
Avoid processing unnecessary sensitive tickets, customer PII, or highly confidential data through this flow, and confirm whether data is relayed via `rube.app`.
Validate behavior first in a test account or low-privilege Helpwise workspace before using it in production.
Continuously review the MCP endpoint, repository version, and updates to catch schema or behavior changes that could expand effective access.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Helpwise Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/helpwise

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["helpwise"]
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 Helpwise-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `helpwise`
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 Yousearch tasks through Rube MCP and chain follow-up workflows.

ComposioGet→

$ loading_