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

SKILL

peopledatalabs-automation

Name: peopledatalabs-automation
Author: Composio

Automate People Data Labs lookups and data workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source prompt template with strong community trust and no clear red flags for local execution or local file access. The main concern is that actual use depends on external Rube MCP/Composio and a Peopledatalabs connection, so task inputs may be sent to third-party services; overall this is cautionary rather than high risk.

CredentialsCaution

The material says the skill itself needs no API key or environment variable, but it requires creating a `peopledatalabs` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link if the connection is not active. This suggests credentials are likely handled through Rube/Composio or OAuth; the skill does not directly expose secrets, but there is still third-party authorization and account-misuse surface.

Network egressCaution

The README explicitly requires connecting to the remote MCP endpoint `https://rube.app/mcp` and using remote capabilities such as `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and `RUBE_MULTI_EXECUTE_TOOL`; execution arguments, session data, and Peopledatalabs operation requests will be sent to the Rube/Composio side. The egress target and purpose are broadly declared, which is consistent with normal tool behavior, but users should assume relevant business data leaves the client.

Code executionLow risk

Based on the provided material, this is a prompt/workflow description and does not declare launching local processes, executing scripts, installing binaries, or invoking privileged system capabilities. Its core function is to direct use of remote MCP tools rather than local code execution.

Data accessCaution

There is no indication of local filesystem access or local data read/write; however, it performs automation within the context of a connected Peopledatalabs account, so the effective data scope depends on permissions granted to that external connection. The main concern is not local overreach, but ensuring least-privilege access for remote business data queries and operations.

Supply chainCaution

Positive signals include that the skill comes from a GitHub open-source repository with very high community stars, which improves visibility and external scrutiny. Points to watch are that the license is not stated, maintenance status is unknown, and actual functionality depends on off-repository Rube/Composio services whose implementation and changes are not fully covered by the current open-source material, so supply-chain auditability is not end-to-end.

Recommendations

Only connect to `rube.app` when needed, and use a least-privilege account when authorizing Peopledatalabs access.
Avoid submitting unnecessary sensitive personal data, customer data, or internal identifiers in tool arguments.
Review the data retention, logging, and subprocess/third-party handling policies of Rube/Composio and Peopledatalabs before production use.
Prefer pinned versions or snapshots and re-validate external tool schema changes to avoid overreach or unintended actions caused by remote capability changes.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Peopledatalabs Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/peopledatalabs

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["peopledatalabs"]
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 Peopledatalabs-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `peopledatalabs`
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 API Labz tasks via Rube MCP using current tool schemas.

ComposioGet→

$ loading_