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

SKILL

storeganise-automation

Name: storeganise-automation
Author: Composio

Automate Storeganise tasks and connect them into streamlined workflows.

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 an open-source prompt/instruction wrapper with no declared local execution or built-in secrets, so overall risk is relatively low. The main caution is that it relies on external Rube MCP and Storeganise connections, so actual data egress and account scope depend on those external authorizations.

CredentialsCaution

The material says the skill itself needs no API key or environment variables, but it requires a Storeganise connection via RUBE_MANAGE_CONNECTIONS and an external auth flow. This means credentials are likely handled by Rube/Composio rather than locally, creating the usual third-party token scope and over-authorization considerations.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint https://rube.app/mcp and performing actions through Composio's Storeganise toolkit; task descriptions, session IDs, tool arguments, and Storeganise business data may be sent to those external services. No unrelated or covert egress endpoint is shown, but this is a clear external network dependency.

Code executionLow risk

The system flags it as prompt-only, and the material only describes how to call existing MCP tools; there is no indication of installing executables locally, spawning local processes, or granting shell/system-level execution rights. Any execution capability resides primarily in the external MCP/tool side, not in the skill itself.

Data accessCaution

The skill is intended to 'Automate Storeganise operations' and supports tool discovery, bulk execution, and remote workbench calls; once the external connection is authorized, it may access or modify resources in the linked Storeganise account. The material does not show direct local file access, but the scope over remote business data depends on the connected account permissions and should be minimized.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), both of which are meaningful risk-reducing signals; the visible content also looks like a public README/skill description that is easy to review. The missing license declaration and unknown maintenance status are caveats, but not enough on the current facts to raise it to high risk.

Recommendations

Enable it only after confirming trust in rube.app, Composio, and the related Storeganise integration, and review their privacy/data-handling terms.
Grant the Storeganise connection the minimum necessary scope, ideally using a restricted test account first to validate visible data and allowed actions.
Avoid placing unnecessary sensitive business data into tool discovery queries, session memory, or execution arguments.
Before production use, document the MCP service, authorized account, and allowed tool scope, and regularly review connection status and granted permissions.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Storeganise Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/storeganise

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["storeganise"]
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 Storeganise-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `storeganise`
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 AI/ML API workflows via Rube MCP, checking latest tool schemas first.

ComposioGet→

$ loading_