$ loading_
Automate Hystruct tasks via Rube MCP using current tool schemas first.
The material appears to be a prompt/instruction wrapper for using Rube MCP/Composio rather than executable local code, with no embedded secrets or obvious malicious content. The main caution is that actions and related data may be routed through external Rube/Composio services and rely on the permissions of the connected Hystruct account.
The material says there are no API keys, but it requires creating a `hystruct` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link when the connection is inactive; in practice this likely involves Hystruct/Rube OAuth or session-based authorization. No hardcoded secrets or direct requests for plaintext credentials are shown, and the main exposure is the permission scope of the connected account.
The README explicitly instructs adding the remote MCP endpoint `https://rube.app/mcp` and using Composio's Hystruct toolkit for search, connection management, and tool execution; task content, tool arguments, session IDs, and memory fields may therefore be sent to Rube/Composio and onward to the Hystruct service they integrate with. The endpoint and purpose are disclosed, so this is expected egress, but it is still external data transmission.
Based on the provided material, this is a prompt-only skill description with no instructions to spawn local processes, run scripts, or request system-level privileges on the host. The mentioned `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH` are remote orchestration capabilities, not evidence of local code execution.
The skill does not itself declare local file access or direct host resource access, but it can operate on data in the connected Hystruct account and requires passing session/memory plus schema-compliant arguments through the workflow. The effective data-access scope depends on what the Hystruct toolkit exposes and what permissions the user grants to Rube/Composio, so broad or sensitive connections should be avoided.
Positive factors: the system marks it as prompt-only and open-source, and it comes from a GitHub repository with strong community adoption (64.7k stars), which materially lowers supply-chain concern. Still, the repository appears to be a skills collection rather than a standalone codebase for this skill, the license is undeclared, maintenance status is unknown, and real execution depends on third-party remote services (Rube/Composio/Hystruct), so the full implementation is not completely auditable from this material alone.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "hystruct-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/hystruct-automation/SKILL.md 2. Save it as ~/.claude/skills/hystruct-automation/SKILL.md 3. Reload skills and tell me it's ready
Automate Hystruct operations through Composio's Hystruct toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/hystruct
RUBE_MANAGE_CONNECTIONS with toolkit hystructRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit hystructAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Hystruct operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Hystruct task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["hystruct"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Hystruct-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit hystruct |
| 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 Diffbot tasks via Rube MCP using current tool schemas.
Automate DigiCert certificate tasks via Rube MCP with schema-first tool discovery.
Automate Discord bot tasks and workflow actions through Rube MCP.
Automate DNSFilter administration and security operations through Rube MCP.
Automate Dock certificate tasks through Rube MCP for faster security operations.
Automate Front inbox conversations, contacts, and team workflows via Rube MCP.
Automate Autom workflows via Rube MCP while checking current tool schemas first.
Automate Hyperbrowser workflows via Rube MCP using current tool schemas first.
Automate Composio tasks via Rube MCP with tool schema lookup first.
Automate Honeyhive tasks via Rube MCP using current tool schemas.
Automate Habitica task creation, updates, and lookups through Rube MCP.
Automate Hyperise personalization and creative workflow tasks through Rube MCP.