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

SKILL

timekit-automation

Name: timekit-automation
Author: Composio

Automate Timekit tasks via Rube MCP with schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be prompt/documentation-only, with an open-source source and strong community adoption, so overall risk is low. Caution is still warranted because actual network access, authorization scope, and data handling depend on the external Rube MCP and Timekit connection it instructs users to use.

CredentialsCaution

The material claims 'no API keys,' but it explicitly requires establishing an ACTIVE Timekit connection via `RUBE_MANAGE_CONNECTIONS` and completing an external auth link. This implies third-party account authorization/tokens are involved; the skill does not directly request secrets, but credentials are handled by the external MCP/integration, so scope and token management should be reviewed.

Network egressCaution

The README instructs users to add the remote MCP endpoint `https://rube.app/mcp` and perform actions through Composio/Timekit tools. Therefore, user requests and related business data may transit through Rube/Composio to Timekit. The material does not provide a more detailed data-flow description, retention policy, or full endpoint list.

Code executionLow risk

Based on the provided material, this skill only supplies workflow instructions and call ordering. It does not include local scripts, install commands, or require arbitrary code execution on the host, and it does not request system execution privileges beyond normal MCP usage.

Data accessCaution

The skill is intended to 'Automate Timekit operations' and supports tool discovery, connection management, bulk execution, and a remote workbench. This means it may access and modify data/resources within the linked Timekit account. No local file read/write needs are shown, but least-privilege boundaries for the external connection are not described.

Supply chainLow risk

The source is an open GitHub repository from `ComposioHQ/awesome-claude-skills` with high community adoption (64.9k stars), which are strong risk-reducing signals. The skill content itself is auditable; gaps are that the license is unspecified, maintenance status is unknown, and the actual server-side behavior of Rube/Composio is outside this material.

Recommendations

Before linking Timekit, verify that the OAuth/authorization scopes requested by Rube/Composio follow least-privilege principles.
Do not submit unnecessary sensitive business data in tool arguments, and review Rube/Composio privacy and data-retention policies.
Validate available tools and bulk operations in a test account or restricted environment before using production data.
Review the MCP endpoint and pinned repository/version over time, as schema or server-side behavior may change and expand effective privileges.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Timekit Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/timekit

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["timekit"]
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 Timekit-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `timekit`
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 Timely task workflows through Rube MCP for faster time operations.

ComposioGet→

$ loading_