chmeetings-automation

Overview of chmeetings-automation skill

What chmeetings-automation is for

chmeetings-automation is a Claude skill for running Chmeetings workflows through Composio’s Rube MCP server. It is not a standalone Chmeetings client; it teaches the agent to discover the current Chmeetings tool schemas with RUBE_SEARCH_TOOLS, verify the Chmeetings connection, and then execute the right Rube tools instead of guessing API parameters.

Use this skill when your goal is Workflow Automation around Chmeetings records, events, people, groups, attendance, or other operations exposed by the Composio Chmeetings toolkit.

Best-fit users and workflows

The chmeetings-automation skill is best for users who already work in a Claude or MCP-capable environment and want the agent to perform repeatable Chmeetings tasks with less manual navigation. It fits operational prompts such as “find upcoming meetings,” “update a member-related record,” or “create a report from Chmeetings data,” as long as the required operation is available in the live Rube toolkit.

It is especially useful when tool schemas may change, because the skill explicitly instructs the agent to search tools first rather than relying on stale examples.

Key adoption requirement

Before installing, check whether you can use Rube MCP. The skill requires:

• MCP support in your client
• Rube MCP configured at https://rube.app/mcp
• RUBE_SEARCH_TOOLS available
• An active Chmeetings connection created through RUBE_MANAGE_CONNECTIONS
• Willingness to authenticate Chmeetings if Rube returns an auth link

If your environment cannot call MCP tools, this skill will not execute real Chmeetings actions.

How to Use chmeetings-automation skill

chmeetings-automation install and setup path

Install the skill from the Composio skills repository:

npx skills add ComposioHQ/awesome-claude-skills --skill chmeetings-automation

Then add Rube MCP to your client configuration using:

https://rube.app/mcp

After Rube is available, ask the agent to verify that RUBE_SEARCH_TOOLS responds. Next, use RUBE_MANAGE_CONNECTIONS with toolkit chmeetings. If the connection is not ACTIVE, complete the returned authentication flow before asking the agent to modify or retrieve Chmeetings data.

Inputs the skill needs from you

For reliable chmeetings-automation usage, give the agent the task goal, the relevant Chmeetings object, any known identifiers, date ranges, filters, and whether the action should be read-only or write-capable. A weak prompt is:

“Update Chmeetings.”

A stronger prompt is:

“Use chmeetings-automation to find Chmeetings tools first, confirm the connection is ACTIVE, then list meetings scheduled for the next 14 days. Do not create or update anything. Return meeting name, date, group, and any missing fields.”

For write actions, add confirmation rules:

“Search the Chmeetings tool schema first. Prepare the update plan and show the exact fields before executing. Only run the write tool after I confirm.”

Practical workflow for agents

A good chmeetings-automation guide follows this sequence:

1. Call RUBE_SEARCH_TOOLS with the exact Chmeetings use case.
2. Reuse the returned session ID for related discovery.
3. Check the Chmeetings connection with RUBE_MANAGE_CONNECTIONS.
4. Inspect the returned tool slug, schema, required fields, and warnings.
5. Ask the user for missing required values instead of inventing them.
6. Execute the chosen Rube tool.
7. Summarize what changed, what failed, and what still needs user action.

This matters because the upstream skill’s central rule is schema discovery. Skipping tool discovery is the main way to get bad calls, wrong fields, or unsupported Chmeetings operations.

Repository files to inspect first

This skill is compact: the meaningful implementation is in composio-skills/chmeetings-automation/SKILL.md. There are no visible helper scripts, reference folders, or README files in the provided tree. Read SKILL.md before use, especially the sections on prerequisites, setup, tool discovery, and the core workflow pattern.

For toolkit-level behavior, the skill points to Composio’s Chmeetings toolkit documentation at composio.dev/toolkits/chmeetings, but live RUBE_SEARCH_TOOLS output should be treated as the authority for current schemas.

chmeetings-automation skill FAQ

Is chmeetings-automation enough without Rube MCP?

No. The chmeetings-automation skill depends on Rube MCP tools. It can guide the agent’s behavior, but it cannot connect to Chmeetings or perform operations unless RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS are available in your client.

How is this better than an ordinary prompt?

An ordinary prompt may ask the model to “use Chmeetings,” but it may guess tool names or fields. This skill adds a specific operating discipline: discover tools first, check the active connection, follow the returned schema, and only then execute. That reduces schema drift problems and makes the workflow safer for live Chmeetings data.

Is the chmeetings-automation skill beginner friendly?

It is beginner friendly if your MCP client is already configured. The skill’s workflow is simple, but first-time users may need help adding the Rube MCP server and completing the Chmeetings authentication flow. Beginners should start with read-only tasks before allowing create, update, or delete operations.

When should I not use this skill?

Do not use it when you only need a written Chmeetings process document, when your client cannot run MCP tools, or when you need guaranteed support for an operation not exposed by the Composio Chmeetings toolkit. Also avoid open-ended write prompts such as “clean up all meetings” unless you define filters, review steps, and confirmation boundaries.

How to Improve chmeetings-automation skill

Improve chmeetings-automation prompts with constraints

The biggest quality improvement is adding operational constraints. Include date ranges, record types, exact output columns, whether writes are allowed, and what to do when required fields are missing. For example:

“Use chmeetings-automation for Workflow Automation. Search tools for Chmeetings meeting lookup, list meetings from 2026-01-01 to 2026-01-31, return only active meetings, and do not call any write tools.”

This gives the agent enough structure to select the right Rube tool and avoid unnecessary actions.

Prevent common failure modes

Common failures include skipping RUBE_SEARCH_TOOLS, assuming old schemas, running before the connection is ACTIVE, and treating partial user instructions as permission to write. To prevent these, require the agent to state the discovered tool slug, required fields, and planned action before execution for any sensitive workflow.

For batch changes, ask for a dry run first. The first output should identify candidate records and missing information; the second step should perform the approved operation.

Iterate after the first tool result

After the first Rube result, refine based on actual returned fields. If the tool returns unexpected field names, empty data, pagination, or permission errors, update the prompt with those details instead of restarting from scratch. Good follow-up prompts include:

• “Use the same Rube session and include archived records if the schema supports it.”
• “The result has group_id; search for a Chmeetings group detail tool before summarizing.”
• “Retry only failed records and show the error for each one.”

What would make the skill stronger

The upstream skill would be stronger with example prompts for common Chmeetings tasks, explicit read-only versus write workflows, sample RUBE_MANAGE_CONNECTIONS calls, and safety guidance for destructive operations. Until then, users should treat SKILL.md as the execution pattern and rely on live Rube discovery for current Chmeetings capabilities.