@majiayu000/nocrm-io-automation
BAutomate Nocrm IO tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install
agr install @majiayu000/nocrm-io-automation --target claudeWrites 2 files into .claude/skills/, pinned to git-dcd4927e.
- .claude/skills/nocrm-io-automation/SKILL.md
- .claude/skills/nocrm-io-automation/metadata.json
Document
name: nocrm-io-automation description: "Automate Nocrm IO tasks via Rube MCP (Composio). Always search tools first for current schemas." requires: mcp: [rube]
Nocrm IO Automation via Rube MCP
Automate Nocrm IO operations through Composio's Nocrm IO toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/nocrm_io
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Nocrm IO connection via
RUBE_MANAGE_CONNECTIONSwith toolkitnocrm_io - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitnocrm_io - 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: "Nocrm IO 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 Nocrm IO task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["nocrm_io"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Nocrm IO-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit nocrm_io |
| 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
Repository README
Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.
Claude Skill Registry (Data)
This repo contains the archived skill contents (the heavy, browsable skill files).
Canonical layout
- Category folders at repo root (e.g.
development/,documents/,data/, ...) - Each skill lives under a category:
<category>/<skill>/SKILL.md+<category>/<skill>/metadata.json - Case conflicts are resolved with
{name}-{owner}-{repo}suffixes (fallback:-{short-hash}).
Archive status
- Live badges above are sourced from
claude-skill-registry-corestats.json. - Counts in this README are intentionally dynamic, not hardcoded.
- If the badges look stale, refresh the
corebuild/index pipeline rather than editing numbers here.
Where the index + site live
- Core repo: https://github.com/majiayu000/claude-skill-registry-core
- Main repo (merged publish artifact): https://github.com/majiayu000/claude-skill-registry
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-dcd4927e18ea2026-07-31