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

SKILL

pushover-automation

Name: pushover-automation
Author: Composio

Automate Pushover notification tasks and message workflows 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 is itself open-source prompt/documentation material, but its intended use depends on external Rube MCP and Composio for remote tool discovery, connection management, and tool execution; based on the provided material, it does not directly require local secrets or local code execution, so the overall posture is caution rather than high risk. The high-star open-source source materially lowers supply-chain risk, while actual data egress and permission scope depend on the connected Rube/Composio service and the granted Pushover account access.

CredentialsCaution

The material says the skill itself needs 'no API keys,' but it explicitly requires creating a `pushover` connection via `RUBE_MANAGE_CONNECTIONS` and completing an external auth flow, implying credentials are actually managed or proxied by Rube/Composio. No local plaintext secret handling is shown, but normal third-party connection authorization exposure remains.

Network egressCaution

The README requires adding `https://rube.app/mcp` as an MCP server and using Composio/Rube remote capabilities for tool search, connection management, and execution. This means task descriptions, session data, and possibly operation arguments are sent to the declared external service. No suspicious extra endpoints are disclosed beyond the Rube/Composio and Pushover-related flow.

Code executionLow risk

System checks classify this project as `prompt-only`; the provided material only describes workflow guidance and MCP call patterns, with no local script execution, process spawning, or requests for system command privileges.

Data accessCaution

The skill itself does not claim local file reads or local resource access, but the remote tools it relies on can act on an authorized Pushover account and will pass `session_id`, `memory`, and task arguments in the workflow. The effective data-access scope mainly depends on the external service and the granted Pushover permissions.

Supply chainLow risk

The source is an open-source GitHub repository with very high community adoption (about 64.9k stars). The audited object is also a prompt-style skill rather than an executable package, giving it good auditability. Although the license is unspecified and maintenance status is unknown, that alone is not enough to raise it to high risk.

Recommendations

Only add `https://rube.app/mcp` after you trust the Rube/Composio service, and review its privacy and data-handling terms.
Use the minimum necessary authorization when connecting Pushover, and regularly review/revoke third-party connections you no longer need.
Inspect the tool schemas returned by `RUBE_SEARCH_TOOLS` before execution, and avoid placing sensitive content into unnecessary arguments or memory.
Validate the workflow in an isolated test environment before using it with real notifications or production accounts.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Pushover Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pushover

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["pushover"]
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 Pushover-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `pushover`
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 Uptimerobot monitoring tasks and status checks through Rube MCP.

ComposioGet→

$ loading_