Connect
ComposioHQ/awesome-claude-skills
Connect Claude to any app. An agent skill from ComposioHQ/awesome-claude-skills.
Fetch data from a RapidMiner graph mart or any SPARQL 1.1 HTTP endpoint (AnzoGraph and friends) and surface it as Mendix entities.
$ npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mendixlabs/mxcli connect-rapidminer-graph --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mendix/connect-rapidminer-graph .claude/skills/connect-rapidminer-graph && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "connect-rapidminer-graph" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/connect-rapidminer-graph into .claude/skills/connect-rapidminer-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connect-rapidminer-graph", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/connect-rapidminer-graphType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mendixlabs/mxcli connect-rapidminer-graph --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/mendix/connect-rapidminer-graph .agents/skills/connect-rapidminer-graph && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "connect-rapidminer-graph" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/connect-rapidminer-graph into .agents/skills/connect-rapidminer-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connect-rapidminer-graph", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mendixlabs/mxcli connect-rapidminer-graph --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/mendix/connect-rapidminer-graph .cursor/skills/connect-rapidminer-graph && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "connect-rapidminer-graph" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/connect-rapidminer-graph into .cursor/skills/connect-rapidminer-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connect-rapidminer-graph", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mendixlabs/mxcli.git --path .claude/skills/mendix/connect-rapidminer-graph--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mendixlabs/mxcli connect-rapidminer-graph --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/mendix/connect-rapidminer-graph .gemini/skills/connect-rapidminer-graph && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "connect-rapidminer-graph" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/connect-rapidminer-graph into .gemini/skills/connect-rapidminer-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connect-rapidminer-graph", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mendixlabs/mxcli connect-rapidminer-graphInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/mendix/connect-rapidminer-graph .github/skills/connect-rapidminer-graph && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "connect-rapidminer-graph" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/connect-rapidminer-graph into .github/skills/connect-rapidminer-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connect-rapidminer-graph", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mendixlabs/mxcli connect-rapidminer-graph --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mendixlabs/mxcli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/mendix/connect-rapidminer-graph .opencode/skills/connect-rapidminer-graph && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "connect-rapidminer-graph" agent skill from https://github.com/mendixlabs/mxcli/tree/main/.claude/skills/mendix/connect-rapidminer-graph into .opencode/skills/connect-rapidminer-graph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connect-rapidminer-graph", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
connect-rapidminer-graphFetch data from a RapidMiner graph mart or any SPARQL 1.1 HTTP endpoint (AnzoGraph and friends) and surface it as Mendix entities.
Connect Rapidminer Graph is an agent skill from mendixlabs/mxcli. Fetch data from a RapidMiner graph mart or any SPARQL 1.1 HTTP endpoint (AnzoGraph and friends) and surface it as Mendix entities. Use when a graph database with a SPARQL endpoint has to feed a Mendix app read-only.
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Mendix cli tool, a headless way to work with Mendix projects. Enables Mendix projects for use with 3rd party agentic coding tools like Claude Code and Copilot. Includes a… The licence is Apache-2.0.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 20a6c89. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
graphstudio.mendixdemo.comcambridgesemantics.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Connect Rapidminer Graph loads about 3.2k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 886 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mendixlabs/mxcli at commit 20a6c89, republished under its Apache-2.0 licence (© mendixlabs). 886 words, ~3,168 tokens.
.claude/skills/connect-rapidminer-graph/SKILL.md (or your agent's skills folder).Use this skill when you need to fetch data from a RapidMiner graph mart (or any SPARQL 1.1 HTTP endpoint like AnzoGraph) and surface it in a Mendix app.
A RapidMiner / AnzoGraph graphmart endpoint looks like:
https://<host>/sparql/graphmart/<url-encoded-graphmart-uri>Example:
https://graphstudio.mendixdemo.com/sparql/graphmart/http%3A%2F%2Fcambridgesemantics.com%2FGraphmart%2F3617250aca6a40d88972c1c0de38f86aTwo things to note:
%3A / %2F).content-type: application/sparql-query, and the response is JSON when Accept: application/sparql-results+json.Verify with curl first:
curl -u 'user@example.com:password' \
-H 'Accept: application/sparql-results+json' \
-H 'Content-Type: application/sparql-query' \
--data-binary 'SELECT ?s WHERE { ?s a <http://example.com/Foo> } LIMIT 10' \
'https://host/sparql/graphmart/<encoded-uri>'If curl returns 200 and a JSON results.bindings array, you're ready to wire it into Mendix.
Every SPARQL HTTP result looks like this:
{
"head": { "vars": ["customer", "customerId", "customerName"] },
"results": {
"bindings": [
{
"customer": {"type": "uri", "value": "http://.../Customer/0000000"},
"customerId": {"type": "literal", "value": "CUST001"},
"customerName": {"type": "literal", "value": "Global Tech Solutions Inc."}
}
]
}
}Each row in bindings is an object of {var: {type, value}}. A JSLT transformer flattens this to something directly mappable into Mendix entities.
┌────────────────────┐ ┌────────────────────┐ ┌────────────────────┐ ┌────────────────┐
│ Inline rest call │─▶│ data transformer │─▶│ import mapping │─▶│ Mendix entity │
│ post + basic auth │ │ jslt: flatten │ │ json → entities │ │ (persistent) │
│ SPARQL as body │ │ results.bindings │ │ │ │ │
└────────────────────┘ └────────────────────┘ └────────────────────┘ └────────────────┘Why inline call rest service rather than create consumed rest service + send rest request?
authentication: basic (username: '...', password: '...') silently fails to attach the Authorization header when the password contains special characters (e.g. !). Result: 401 Unauthorized.call rest service ... (Authentication: basic (Username: '<user>', Password: '<pass>')) handles the same credentials correctly.Why persistent entities for the final list?
ReferenceSet children can't be extracted as a list in MDL microflows (no documented retrieve ... by association syntax), and loop $c in $Parent/Assoc fails at build time.datasource: database on a DataGrid — the standard happy path.mdl 1;
@position(100, 100)
create persistent entity MyModule.Customer (
CustomerUri: string(500),
CustomerId: string(50),
CustomerName: string(200)
);Import mappings need a single root entity. A tiny non-persistent wrapper with one dummy attribute is enough:
mdl 1;
@position(400, 100)
create non-persistent entity MyModule.CustomerImport (
DummyAttr: string(10)
);
create association MyModule.CustomerImport_Customer
from MyModule.CustomerImport
to MyModule.Customer
type ReferenceSet;Take the nested results.bindings[].*.value shape and emit a flat customers[] array:
mdl 1;
create data transformer MyModule.SimplifyCustomers
source json '{"head":{"vars":["customer","customerId","customerName"]},"results":{"bindings":[{"customer":{"type":"uri","value":"http://.../Customer/0"},"customerId":{"type":"literal","value":"CUST001"},"customerName":{"type":"literal","value":"Global Tech Solutions Inc."}}]}}'
{
jslt $$
{
"customers": [for (.results.bindings)
{
"customerUri": .customer.value,
"customerId": .customerId.value,
"customerName": .customerName.value
}
]
}
$$;
};JSLT notes for this runtime:
[for (.path.to.array) <expr>] works for iteration..field.subfield path access works.[N] array indexing works.$var[start : end] slice works for strings — do not use substring(...) (it silently drops the field from the output).let variables and if/else expressions work.def fn(arg) ... helper functions work.The JSON structure represents the transformed shape (after JSLT), not the raw SPARQL response:
mdl 1;
create json structure MyModule.JSON_Customers
sample '{"customers":[{"customerUri":"http://example.com/Customer/0","customerId":"CUST001","customerName":"Global Tech Solutions Inc."}]}';
create import mapping MyModule.IMM_Customers
with json structure MyModule.JSON_Customers
{
create MyModule.CustomerImport {
create MyModule.CustomerImport_Customer/MyModule.Customer = customers {
CustomerUri = customerUri,
CustomerId = customerId,
CustomerName = customerName
}
}
};mdl 1;
create microflow MyModule.ACT_RefreshCustomers ()
returns boolean as $success
begin
log info node 'MyModule' '=== Refresh start ===';
-- Clear existing persistent records (full replace)
retrieve $Existing from MyModule.Customer;
loop $C in $Existing begin
delete $C;
end loop;
-- Inline REST CALL — NOT the REST Client (see notes)
$RawJson = call rest service post 'https://graphstudio.mendixdemo.com/sparql/graphmart/http%3A%2F%2Fcambridgesemantics.com%2FGraphmart%2F3617250aca6a40d88972c1c0de38f86a' (
Headers: ('Accept': 'application/sparql-results+json', 'Content-Type': 'application/sparql-query'),
Authentication: basic (Username: '<username>', Password: '<password>'),
Body: template 'PREFIX model: <http://cambridgesemantics.com/SourceLayer/c4ce0eca2e7241f2aee13b46fbdca3f8/Model#> SELECT ?customer ?customerId ?customerName FROM <http://cambridgesemantics.com/SourceLayer/c4ce0eca2e7241f2aee13b46fbdca3f8/Model> WHERE {1} ?customer a model:ExamplePlmBom.Customer; model:ExamplePlmBom.Customer.id ?customerId; model:ExamplePlmBom.Customer.name ?customerName; {2}'
with ({1} = '{', {2} = '}'),
Timeout: 60,
) returns string
on error continue;
log info node 'MyModule' '{1}' with ({1} = 'HTTP status: ' + toString($latestHttpResponse/StatusCode));
if $latestHttpResponse/StatusCode = 200 then
$SimplifiedJson = transform $RawJson with MyModule.SimplifyCustomers;
$ImportResult = import from mapping MyModule.IMM_Customers($SimplifiedJson);
log info node 'MyModule' '=== Done ===';
end if;
return true;
end;mdl 1;
create page MyModule.Customer_Overview (
title: 'Customers (from Graph Mart)',
layout: Atlas_Core.Atlas_Default
) {
dynamictext heading (content: 'Customers', rendermode: H2)
actionbutton btnRefresh (caption: 'Refresh', action: call microflow MyModule.ACT_RefreshCustomers, buttonstyle: primary)
datagrid gridCustomers (datasource: database MyModule.Customer sort by CustomerId asc) {
column (attribute: CustomerId, caption: 'ID')
column (attribute: CustomerName, caption: 'Name')
column (attribute: CustomerUri, caption: 'URI')
}
};! in Basic Auth password → 401REST Client authentication: basic (...) with a literal password containing ! sends no auth header at runtime. Workaround: use inline call rest service ... (Authentication: basic (Username: '<user>', Password: '<pass>')). The inline form works with the same literal credentials.
{ braces in Body: template are consumed as placeholder escapesIn call rest service ... (Body: template '...'), the body is a template string where {1}, {2} are placeholders. A literal { must be escaped as {{, but in this runtime {{ is sent literally rather than being converted to { → server returns 400 Bad request.
Solution: pass literal braces as placeholder values:
Body: template '... WHERE {1} ... {2}'
with ({1} = '{', {2} = '}')If your JSLT emits ISO 8601 timestamps ("2026-04-13T14:00") and the target Mendix attribute is string, create json structure ... sample '...' will infer datetime from the sample and mxbuild fails with CE5015 ("schema type DateTime doesn't match attribute type String").
Solutions:
"2026-04-13 14:00 CET").$rawTime[11 : 16] for HH:MM).datetime.The import mapping happily populates CustomerImport with a ReferenceSet of Customer children, but:
return $Root/MyModule.CustomerImport_Customer → "Error(s) in expression" at builddeclare $C list of MyModule.Customer = $Root/... → "Error(s) in expression"loop $c in $Root/MyModule.CustomerImport_Customer → "The 'Iterate over' property is required"datasource: $currentObject/MyModule.CustomerImport_Customer → BSON serializer drops the datasourceSolution: Make the target entity persistent. The import mapping commits them automatically, and the page uses the standard datasource: database MyModule.Customer for the grid. A full replace on each refresh (delete-all-then-import) keeps data consistent with the graph.
If you drop entity X then create entity X repeatedly while associations referencing X exist, the associations may hold the old entity GUID → mxbuild fails with KeyNotFoundException. Fix by dropping/recreating the broken association after the entity change.
Before building the pipeline, explore the graph to understand what's there. Useful SPARQL queries (send via curl):
List all classes with counts:
select distinct ?class (count(?s) as ?count)
from <http://.../model>
where { ?s a ?class }
GROUP by ?class
ORDER by desc(?count)List properties used by a given class:
PREFIX model: <http://.../model#>
select distinct ?property
from <http://.../model>
where {
?s a model:ExamplePlmBom.Customer ;
?property ?o .
}
ORDER by ?propertyFilter to a single namespace (skip rdf/owl noise):
select distinct ?class ?property
from <http://.../model>
where {
?s a ?class ;
?property ?o .
filter(STRSTARTS(STR(?class), "http://.../model#MyPrefix"))
}For demos, literal credentials inline in the microflow are the simplest and most reliable. For anything else, put them in a project constant and reference it as @Module.ConstantName — the one way MDL refers to a constant, in a microflow expression and in create consumed rest service ... authentication: basic (username: @Module.User, password: @Module.Password) alike. The older $ConstantName spelling in a REST credential still parses and warns MDL-DEPR083.
© mendixlabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/mendix/connect-rapidminer-graph of mendixlabs/mxcli.
Open the folder on GitHubat commit 20a6c89
Connect Rapidminer Graph next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Connect Rapidminer Graph this skillmendixlabs/mxcli | 128 | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| ConnectComposioHQ/awesome-claude-skills | 77k | 3 repos | ~987 | Automated safety check: Pass | None | |
| Graphagenticnotetaking/arscontexta | 3.5k | 1 repos | ~4.9k | Automated safety check: Notes | MIT | |
| Node Connectopenclaw/openclaw | 392k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Bigquery Graphgoogle/adk-python | 22k | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Connectnimbalyst/nimbalyst | 1.9k | — | ~1.8k | Automated safety check: Pass | MIT |
ComposioHQ/awesome-claude-skills
Connect Claude to any app. An agent skill from ComposioHQ/awesome-claude-skills.
agenticnotetaking/arscontexta
Interactive knowledge graph analysis. An agent skill from agenticnotetaking/arscontexta.
openclaw/openclaw
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.
google/adk-python
Skill for Graph Query Language (GQL) or SQL/PGQ queries against a property graph.
nimbalyst/nimbalyst
Connect this repository to its Nimbalyst team project so the session can read and write the team's pages.
tirth8205/code-review-graph
Builds or incrementally updates the code-review knowledge graph for a repository and reports whether the build succeeded, partly or failed.
mendixlabs/mxcli
Push OData query options into the SQL of a Mendix resource served by a read microflow, so $filter, $orderby, $top, $skip, $count and the key lookup reach the database instead of being silently…
mendixlabs/mxcli
Chart a Mendix app with Vega-Lite through a pluggable widget that takes the specification and the data as separate properties, so the model emits rows and never assembles a chart payload.
mendixlabs/mxcli
Author Mendix AI agent documents in MDL — Model, Knowledge Base, Consumed MCP Service and Agent, with variables, tools and multi-line prompts.
mendixlabs/mxcli
Run set-based INSERT, UPDATE and DELETE against Mendix entities through OQL statements, which the runtime supports and Studio Pro cannot author.
mendixlabs/mxcli
Define event-driven APIs over Kafka with Mendix business event services — publish and subscribe contracts, CREATE/DROP/DESCRIBE.
mendixlabs/mxcli
Search the Mendix Catalog platform service registry (catalog.mendix.com) from the CLI to find services published across an organisation.
Fetch data from a RapidMiner graph mart or any SPARQL 1.1 HTTP endpoint (AnzoGraph and friends) and surface it as Mendix entities. Connect Rapidminer Graph is an agent skill from mendixlabs/mxcli.1 HTTP endpoint (AnzoGraph and friends) and surface it as Mendix entities.
Connect Rapidminer Graph fits situations like: A graph database with a SPARQL endpoint has to feed a Mendix app read-only.
Run `npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a claude-code`. Or copy the skill folder (.claude/skills/mendix/connect-rapidminer-graph in mendixlabs/mxcli) into .claude/skills/connect-rapidminer-graph in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a codex`. Or copy the skill folder (.claude/skills/mendix/connect-rapidminer-graph in mendixlabs/mxcli) into .agents/skills/connect-rapidminer-graph in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mendixlabs/mxcli --skill connect-rapidminer-graph -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/connect-rapidminer-graph, .gemini/skills/connect-rapidminer-graph, .github/skills/connect-rapidminer-graph and .opencode/skills/connect-rapidminer-graph in your project.
Going by SKILL.md and its folder, Connect Rapidminer Graph needs the command-line tools its instructions call (curl).
SKILL.md names 2 domains. In commands or code: graphstudio.mendixdemo.com and cambridgesemantics.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Connect Rapidminer Graph is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Connect Rapidminer Graph: Connect (ComposioHQ/awesome-claude-skills, 77k stars), Graph (agenticnotetaking/arscontexta, 3.5k stars), Node Connect (openclaw/openclaw, 392k stars) and Bigquery Graph (google/adk-python, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mendixlabs (a GitHub organization) maintains it in mendixlabs/mxcli, which has 128 GitHub stars. The repository holds 72 skills in this directory. The repository was last updated on October 7, 2026.
Source: mendixlabs/mxcli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.