Habitica Automation

What This Skill Does

• The Habitica Automation skill allows users to automate tasks within the Habitica gamified task management platform.
• It leverages the Composio Habitica toolkit via Rube MCP. This skill is designed for users who want to programmatically interact with Habitica to manage tasks, habits, and rewards.

When to Use

• Automate task creation in Habitica.
• Manage daily habits programmatically. Retrieve and update task details. Automate reward distribution. Integrate Habitica with other tools. Create custom Habitica workflows.

Key Features

• Requires Rube MCP and active Habitica connection.
• Uses RUBE_SEARCH_TOOLS for tool discovery. Employs RUBE_MANAGE_CONNECTIONS for connection management. Executes tools via RUBE_MULTI_EXECUTE_TOOL. Tool schemas are dynamically retrieved. Connection status is checked before execution.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedHabitica Automation via Rube MCP

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

• Toolkit docs: composio.
• dev/toolkits/habitica.

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["habitica"] 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