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

SKILL

hashnode-automation

Name: hashnode-automation
Author: Composio

Automate Hashnode content and site management tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

The material is an open-source prompt/usage document with no embedded executable code and no local API key requirement, so overall risk is low. The main caveat is that actual use depends on external Rube MCP and a Hashnode connection, which introduces network interaction and third-party account authorization.

CredentialsCaution

The material states 'No API keys needed', but the workflow requires an active `hashnode` connection via `RUBE_MANAGE_CONNECTIONS` and completing setup through a returned auth link; this implies third-party account authorization/tokens, even if not exposed as local environment variables.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and performing Hashnode operations through Composio/Rube; therefore user requests, tool arguments, and potentially content data would be sent to declared third-party endpoints. There is no evidence of exfiltration to unrelated or hidden endpoints.

Code executionLow risk

For the material under review, this is a prompt/instruction document and does not contain local scripts, install commands, or executable payloads; it does not show direct local process spawning or arbitrary code execution. The referenced tool calls occur within the external MCP/tooling system.

Data accessCaution

The skill is intended to 'Automate Hashnode operations' and executes publish/query-style actions through external tools; this means it may access or modify content and metadata within the user's Hashnode account. The material does not show excessive access to the local filesystem or unrelated resources.

Supply chainLow risk

The source is a GitHub open-source repository with very high community adoption (64.7k stars); the current material itself is a reviewable README/skill description, giving good supply-chain visibility. Although the license and maintenance status are not clearly stated, there are no signs of closed-source distribution, obfuscation, or obvious injection/deception red flags.

Recommendations

Only connect `https://rube.app/mcp` from a trusted client, and review its privacy and data-handling terms.
Apply least-privilege when authorizing the Hashnode connection; avoid granting unnecessary site or publishing permissions.
Before execution, inspect the tool scope returned by `RUBE_SEARCH_TOOLS` to avoid invoking actions beyond expectation.
If used for production content, validate the automation behavior and write results in a test account or draft environment first.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Hashnode Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hashnode

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["hashnode"]
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 Hashnode-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `hashnode`
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 Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_