SkillAgentSearch skills...

custom-connector

Gets the plugin talking to a manufacturing system that has no vendor MCP, working down a seven-tier access ladder in order — vendor MCP, community MCP, a scoped API wrapper, a read-only database view, a Zapier bridge, screen automation as a last resort, or a scheduled export contract — and stopping…

Install / Use

npx skills add anthropics/claude-plugins-official --skill custom-connector

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

96/100

Category

Automation

Supported Platforms

Universal

Our assessment of custom-connector

custom-connector scores 96/100 on our quality scale, 176th of 2,790 Automation skills we index (top 7%).

Its SKILL.md is 22 KB long, well organised into 20 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 47,209 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
17/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so custom-connector is actively maintained.
  • Our last check on 2026-11-14 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-14. Automated pattern scan on 2026-11-14. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

custom-connector compared with similar skills

All 4 of these similar skills score higher than custom-connector; compare them before choosing.

SkillScoreStarsUpdatedFormat
custom-connector (this skill)by anthropics9647.2k3d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install custom-connector?
Run npx skills add anthropics/claude-plugins-official --skill custom-connector. The install tabs above show the steps for each supported agent.
Which AI agents does custom-connector work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is custom-connector safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is custom-connector still maintained?
The repository was last updated 3 days ago, so custom-connector is actively maintained.

name: custom-connector description: "Gets the plugin talking to a manufacturing system that has no vendor MCP, working down a seven-tier access ladder in order — vendor MCP, community MCP, a scoped API wrapper, a read-only database view, a Zapier bridge, screen automation as a last resort, or a scheduled export contract — and stopping at the highest rung that actually works. States plainly at every rung what the customer gets, what it costs, and how it will eventually break. Most often the answer is that a vendor MCP already exists and nothing needs building — just an admin turning it on. Maps whatever it reaches onto the consolidated dataset schema, so no downstream skill changes. Credentials never enter the conversation. Use when someone says "connect our ERP," "we use SAP," "can you reach our MES," "set up a connector for this system," or "our system isn't supported."" compatibility: "Requires none of its own. Reads whatever the target system exposes — an existing MCP, a documented API, a database view, a Zapier connector, or a scheduled export — and produces setup instructions, a wrapper, a view definition, a Zap specification, or an export specification depending on which tier the system actually supports. Never accepts a credential in conversation."

Custom Connector

SAP and Infor have the largest installed base in manufacturing, and neither has an official MCP for business data. Neither does most of what actually runs a mid-market plant — a large share of it is on-prem, a decade old, and has a SQL database but no API at all. That is not a failure case. It is the normal case, and this skill is what turns "your system isn't supported" from a dead end into scoped, buildable work with a known ceiling.

A Claude skill produces artifacts. It does not stand up and host infrastructure. That boundary decides what "as far as it can go" means at every rung of the ladder below — this is not a deployment tool, and scoping it as one is the most common way to get it wrong.

The most common good outcome is the one most likely to be missed. A vendor has often already shipped an MCP server, quietly, without announcing it anywhere the customer would see. Recognizing that and walking an admin through turning it on is worth more than a week of wrapper code, and it is the first thing this skill checks, not an afterthought.

Quick start

→ Identify the system precisely: vendor, product, version, on-prem or cloud
→ Scope the need. "Connect our ERP" is unbuildable; one data flow is
→ Work the ladder in order. Don't build before checking what already exists
→ Report the finding and its tier before building anything
→ Pick the tier, record why, and what was ruled out
→ Handle credentials narrowly. They never enter the conversation
→ Build only what Step 2 scoped, then map it onto the consolidated schema
→ Test against real data, show it back, ask what's still missing
→ Say how it will break, while the customer is still listening

Inputs

First, find the plant setup: from the task's own folder (never cd into the plugin), run python3 -I <this skill's folder>/../../shared/scripts/plant_setup.py find, do its setup_page_first step, then read the profile at profile_path and any rate at rates_path, per ../../shared/replies.md.

| Input | Source | Form | |---|---|---| | System identity | User, in conversation | Vendor, product, version, cloud or on-prem, who administers it | | The specific need | User, and the skill being unblocked | What data out or action in, how often, which skill it serves | | Consolidated dataset schema | data-consolidate | ../../shared/contracts/consolidated-dataset.md — the mapping target | | MCP registries and vendor docs | Web research | — | | Credentials | Customer IT, through a secure path | Never in a skill file, a prompt, or the chat |


Workflow

Step 1 — Identify the system precisely

Vendor, product, version, deployment model, and who administers it inside the customer's organization. "We use SAP" is not enough — S/4HANA cloud and ECC on-prem are different problems on different tiers. Where the name is ambiguous, ask the system's administrator for product, version and hosting. Never infer them from a login URL. Version and hosting narrow the search; they do not by themselves prove any rung works. Read reference/known-systems.md.

Step 2 — Scope the need before looking at access

"Connect our ERP" is unbounded and unbuildable. "Pull closed work orders with actual cost, so quote-build has real cost history" is buildable today. (How fresh it is depends on the tier: live at Tiers 1 to 3, where nothing is scheduled; a stated cadence only at Tiers 4 to 7. Never promise a nightly sync a live connector does not do.) Scope is what keeps this an afternoon instead of an engagement.

Step 3 — Work the ladder, in order

Vendor MCP, community MCP, documented API, database access, Zapier, export. Do not build before checking what already exists — most of the time something does. Read reference/access-ladder.md.

Report each rung by the call that checked it, in the connection plan (step 4), not rung by rung in the reply. "I searched the public MCP registry for SAP and found nothing official" — if a registry search is what ran. Never "I checked your connector directory" or "three connectors are installed on this account" unless the account's own connector listing was queried in this run; which tools happen to be loaded in the session is not that listing. A rung that could not be checked is reported as not checked, with the reason. Per ../../shared/command-center.md.

Tier 2 is searched, not handed back. "A community MCP might exist, worth ten minutes of your time" is the rung skipped. Search for one with the tools available and report what came back, marked community and unverified; where no search tool exists in the session, say the rung was not checked and why. Then land on a tier in the same turn, with reasons — Tier 2 found and reviewed, or Tier 3 because nothing at Tier 2 was found or fit. Deferring the Tier-2-versus-3 call to the user is not a landing.

Step 4 — Report the finding before building anything

The reply leads with the decision, and the ladder research goes in the connection plan. For a plan or "can you connect X" request, the reply is, in this order:

  1. The recommendation: the path for each system in plain words (vendor MCP, API, database view, scheduled export), why, and that it is conditional on what is still open.
  2. Connection status, honestly: nothing is connected; what this run confirmed, and each condition still open.
  3. Three first questions, each labelled with who answers it: for example the ERP administrator (version, hosting, whether the licence includes API access), the MES developer (where the data lives, whether hours are measured or backflushed), and the person asking (what the data is for and how fresh it must be). Three, not a questionnaire.
  4. A short comparison of manual, export and API: what each gives, what it needs, how it breaks, and a provisional effort.
  5. Where the connection plan is. Save it as connector-output/connection-plan.html (house style, internal), one file saved over the last run's: per system, the tier decision record with each rung and the call that checked it (or not checked, and why), what was ruled out, the sources, and the proposed field mapping. Name the path. With no way to write a file, print it in the reply below the comparison.

No tier-by-tier walk in the reply, and about 250 words before the comparison table; the reply never claims a check the plan does not show. This layout is for a plan or "how do we connect" request only. A request to set up, build, map files, test a connection, register or verify one, or a question about one system is answered in the reply in full, as before: the field mapping onto the dataset's own column names, its transforms and the test results are always in the reply when the person asked for any of those, even when the reply also leads with a recommendation. The plan file still holds the ladder. Setup steps for a Tier 1 or 2 system are an exception: the admin acts on them, so they stay in the reply, quoted as below.

State the tier and its consequences, in the customer's own terms, before a line of anything gets built:

"Limble already publishes a hosted MCP — Tier 1, nothing to build. It isn't one of the plugin's four supported connectors, so it's added for your plant. A Limble Super User generates an API key at Settings → Configuration → API Keys. The secret is shown once. The client ID and secret are sent as the Limble-Client-ID and Limble-Client-Secret headers, set as LIMBLE_CLIENT_ID and LIMBLE_CLIENT_SECRET in the environment the connector runs in. That gives assets, work orders and maintenance history in real time. The one limit: write scope for closing out work orders isn't confirmed publicly, so plan on breakdown-diagnosis drafting an update the technician applies rather than updating the ticket itself. Want me to walk through it?"

Setup steps are quoted word for word from reference/known-systems.md — the four supported connectors from its setup-steps table, and a vendor-published MCP (Limble, Onshape) from its Vendor-published MCP table; the Limble steps above are that row. Never paraphrase a row and never add a step it does not contain: not "install it from the connector directory," not "sign in and authorise." For Onshape that means opt in to Onshape Labs and Subscribe to the FeatureScript MCP Server app, with the cost stated as not public and unconfirmed. No admin step: none is documented. How the plant registers the vendor's MCP address with Claude is not written in the table, so do not invent it — no menu path, no "ask your admin to enable it." Give the address and what it needs, and say that registering it as a custom connector in Claude is done by whoever manages connectors for their Claude account.

Readiness is conditional until this run has evidence for it. Never write "works today", "available now" or "nothing needed from IT" unless this run saw it: a licence or permission the customer confirmed, an export or report they showed exists, records shown back. Otherwise name each condition still open: whether the licence includes API access, whether the integration user can be granted the scope, whether the deployment is reachable, whether the export or report exists and who may schedule it. Every proposed field mapping stays proposed, unverified until instance evidence exists.

Sources: the vendor's and publisher's own documentation first. A technical specific (auth method, paging, endpoint names, rate limits) that no official source in this run states stays unknown, and a community README that contradicts the vendor is reported as a contradiction, not resolved. Never give a link this run did not open; a file this run wrote is named by its path. Every effort estimate is labelled provisional with what it assumes.

Once connected, record the system's ### Systems line in the plant profile as live (custom), through onboarding's reconfigure, so every skill that reads "CMMS connector live" or "CAD connector live" takes its live path.

Step 5 — Pick the tier, and record why

Which tier, why, and what was ruled out and on what evidence. The decision record matters more than the code — it's what the next engineer reads, and it's what stops the same question being re-litigated in three months.

Step 6 — Handle credentials properly

Narrowest scope that does the job. Read-only unless a write is genuinely required and approved. A dedicated integration user, never someone's personal login, so access can be revoked without locking a person out. Tokens and OAuth only, never a password. Read `r

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars47.2k
CategoryAutomation
Updated3d ago
Forks4.9k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions