Agent skill

Connector Assistant

by DemonDamon in DemonDamon/AgenticX

连接器助手(Connector Assistant)。当用户想在对话里新建 / 接入 / 更新一个「连接器」(把外部系统、MCP Server、API 接到 Near)时使用:先列模板与已有实例去重,匹配模板则复用,否则用一张结构化表单问清系统类型、认证方式与上游地址,再创建连接器、用掩码卡片收凭证、做连通性检查。连接器不是分身(Avatar)。

Apache-2.0Auto-check passedAgent Workflows

Install Connector Assistant

skills CLI
$ npx skills add DemonDamon/AgenticX --skill connector-assistant -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install DemonDamon/AgenticX connector-assistant --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/DemonDamon/AgenticX.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agenticx/skills/connector-assistant .claude/skills/connector-assistant && rm -rf skills-src

Use ~/.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/

Facts

Skill name
connector-assistant
GitHub stars
315
Token cost
~2.1k tokens
SKILL.md length
529 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
Apache-2.0

At a glance

连接器助手(Connector Assistant)。当用户想在对话里新建 / 接入 / 更新一个「连接器」(把外部系统、MCP Server、API 接到 Near)时使用:先列模板与已有实例去重,匹配模板则复用,否则用一张结构化表单问清系统类型、认证方式与上游地址,再创建连接器、用掩码卡片收凭证、做连通性检查。连接器不是分身(Avatar)。

  • Works in 4 steps: 概念:连接器 ≠ 分身 → 工具 → 流程(严格按序) → …
  • Tasks that involve MCP servers
  • SKILL.md covers 0. 概念:连接器 ≠ 分身, 1. 工具, 2. 流程(严格按序) and 3. 红线
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Connector Assistant is an agent skill from DemonDamon/AgenticX. 连接器助手(Connector Assistant)。当用户想在对话里新建 / 接入 / 更新一个「连接器」(把外部系统、MCP Server、API 接到 Near)时使用:先列模板与已有实例去重,匹配模板则复用,否则用一张结构化表单问清系统类型、认证方式与上游地址,再创建连接器、用掩码卡片收凭证、做连通性检查。连接器不是分身(Avatar)。

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: AgenticX is a unified, production-ready multi-agent platform — Python SDK + CLI (agx) + Studio server + Machi desktop app. Features Meta-Agent orchestration, 15+ LLM providers… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve MCP servers

Example prompts

  • “/connector-assistant”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. 概念:连接器 ≠ 分身
  2. 工具
  3. 流程(严格按序)
  4. 红线

What it can do on your machine

Read from SKILL.md and the folder at commit ce32aff. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Connector Assistant loads about 2.1k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 529 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from DemonDamon/AgenticX at commit ce32aff, republished under its Apache-2.0 licence (© DemonDamon). 529 words, ~2,055 tokens.

Download SKILL.mdSave it as .claude/skills/connector-assistant/SKILL.md (or your agent's skills folder).
name
connector-assistant
description
连接器助手(Connector Assistant)。当用户想在对话里新建 / 接入 / 更新一个「连接器」(把外部系统、MCP Server、API 接到 Near)时使用:先列模板与已有实例去重,匹配模板则复用,否则用一张结构化表单问清系统类型、认证方式与上游地址,再创建连接器、用掩码卡片收凭证、做连通性检查。连接器不是分身(Avatar)。
metadata.author
AgenticX
metadata.version
1.1.0
metadata.display_name
连接器助手

连接器助手

0. 概念:连接器 ≠ 分身

  • 连接器(Connector)=一个「模板实例」:把外部系统接进 Near,在「设置 → 连接器 → 我的连接」、市场卡片、对话框连接器选择器里只出现一次。三种形态:
    • mcp:远程 MCP Server(存于 ~/.agenticx/mcp.json);
    • rest:HTTP API,登记到本机连接器网关(connector-runtime,~/.agenticx/connector-runtime/connectors/<id>.json),对话里通过网关 MCP 工具 search_actions → get_action_guide → execute_action 调用,实例 id 形如 rest:<id>;
    • database:SQLite / MySQL / PostgreSQL,内置只读 MCP(list_tables / describe_table / query),存于 mcp.json。
  • 分身(Avatar)=另一个智能体人格,与连接器无关。
  • 通用 MCP Server ≠ 连接器:手动添加 / 导入 / 市场安装的 MCP 只在「插件市场 → MCP」里展示与管理,不进「我的连接」。用户只是想加一个 MCP Server(不要求作为连接器)时,不走本助手,引导到「插件市场 → MCP → + 新建 MCP」(远程 URL / 导入 JSON);「新建连接器」菜单里没有「新建自定义 MCP」。只有用户明确要把它作为连接器接入时,才用 connector_manage create 建(会打连接器标,出现在「我的连接」)。
  • 用户说「创建一个连接器 叫 abc」→ abc 是连接器名。禁止 create_avatar、禁止追问「abc 是不是分身」、禁止说「无法创建原生连接器」然后结束。

1. 工具

只用 connector_manage(不要手写 / file_edit mcp.json,不要 mcp_import):

action用途
list_templates模板目录(create_via: mcp_url 可在对话里建;ui_native 需在 UI 握手;unavailable 未接线)
list_instances已有实例:instances(mcp / database)+ rest_instances(网关 REST),只返回 has_credential,不含密钥
create新建 / 更新 MCP 实例(mcp_oauth:true = 标准 MCP OAuth,verify 时浏览器授权)
create_rest登记 REST 连接器(OpenAPI/Swagger URL 或文件优先;否则简短接口清单)
create_database新建数据库连接器(默认只读 + 行数上限)
request_credential弹出掩码卡片按类型收凭证(多字段),你拿不到明文;OAuth 授权码模式会在填完后自动打开系统浏览器授权
authorize_oauth重新走 OAuth 授权码(PKCE)浏览器授权(REST)
verify探活:MCP 握手 / REST 执行一个无参 read 动作 / 数据库连接 + 列表
delete仅在用户明确要求删除时使用

2. 流程(严格按序)

第 1 步:先盘点,避免重复建设
  1. 并行调用 connector_manage {action:"list_templates"} 与 {action:"list_instances"}。
  2. 按名称 / 关键词匹配:
    • 已有同名或同系统实例 → 告诉用户已存在,用 request_clarification 问「直接使用 / 更新连接」(单题即可)。选「更新」时 create 带 overwrite:true。
    • 命中模板且 create_via=mcp_url → 走模板实例:template_id 用该模板 id。模板带 mcp_url(官方端点,已核实)时不要再问地址,url 可省略(自动用 mcp_url);否则只问上游地址(第 2 步只保留 Q3)。认证方式按模板 auth:
      • mcp_oauth(官方远程 MCP,OAuth 2.1 + 动态客户端注册,如腾讯文档 / Notion / Linear / Cloudflare / 天眼查 / 企查查)→ 只需名称,绝不索要 Token / Client ID / Secret;create 自动 mcp_oauth:true,随后 verify 打开系统浏览器授权,令牌只存本机 ~/.agenticx/connectors/oauth/(0600)。
      • 模板带 auth_query(如高德 key、百度地图 ak、腾讯地图 key、快递100 key)→ create 自动 auth_style:"query" + query_param,再 request_credential 用掩码卡片收 Key。
      • 模板带 auth_header(如盈米 x-api-key)→ create 自动 auth_style:"header" + header_name,同样用掩码卡片收 Key。
      • api_key/custom_credential → bearer(模板 create 未传 auth_style 时自动 bearer);none → none。
      • 模板带 credential_label / credential_help_url(如恒生聚源:Access Token + 飞书「如何获取凭证」文档)→ 收凭证前在回复里用一句话附上该链接(Markdown 链接,如「如何获取凭证」),request_credential 的 credential_label 用模板给的名称(不传也会自动取模板值)。
    • 命中 ui_native 模板(腾讯会议 / TAPD / GitHub / 飞书 / 企业微信 / Agent Mail)→ 不在对话里建,引导用户到「市场 / 设置 → 连接器」点「连接」完成授权;结束。
    • 命中 unavailable 模板(OAuth 类)→ 说明暂未接线,可改用该服务的 MCP Server URL 走自定义。
    • 都不匹配 → 第 2 步。
第 2 步:一张结构化表单问清楚(只调用一次 request_clarification)

不要拆成多次提问,不要写成正文问题。<名称> 换成用户给的连接器名:

json
{
  "prompt": "为了创建连接器「<名称>」,需要确认以下信息",
  "decisions": [
    {
      "id": "system_type",
      "question": "<名称> 要接入的是什么类型的系统?",
      "options": ["REST API(提供 HTTP 接口文档)", "MCP Server(提供 MCP 接入 URL)", "数据库直连(需手动配置)", "其他(自定义输入)"],
      "custom_option": "其他(自定义输入)"
    },
    {
      "id": "auth",
      "question": "该系统的认证方式是什么?",
      "options": ["无需认证", "Bearer Token", "自定义请求头", "Query 参数", "AK/SK 签名", "OAuth 2.0", "其他(自定义输入)"],
      "custom_option": "其他(自定义输入)"
    },
    {
      "id": "upstream_url",
      "question": "请提供上游服务地址(REST API 的 base_url,或 MCP Server 完整 URL,须含 path)",
      "input_type": "url",
      "label": "上游地址",
      "placeholder": "https://example.com/api 或 https://example.com/mcp"
    }
  ],
  "allow_free_text": false,
  "submit_label": "确认",
  "skip_label": "忽略"
}

用户点「忽略」(结果为「用户未提供具体内容」)→ 简短说明可随时从「+ 新建连接器」继续,结束。

第 3 步:按类型分支,只追问该类型缺的字段

已知字段不重复问;缺的字段合并成一次 request_clarification(input_type:"text"/"url"),绝不在表单里问密钥(密钥只走第 5 步掩码卡片)。

MCP Server → 第 4 步(create)。认证方式映射:

用户选择create 参数
无需认证auth_style:"none"
Bearer Tokenauth_style:"bearer"
自定义请求头auth_style:"header" + header_name(问名字,默认 X-API-Key)
Query 参数auth_style:"query" + query_param(默认 api_key)
OAuth 2.0auth_style:"none" + mcp_oauth:true(服务端支持标准 MCP OAuth 时;verify 打开浏览器授权)。模板 auth=mcp_oauth 时自动设置,无需再问
AK/SK 签名MCP 不支持签名认证;若该系统实际是 HTTP API → 按 REST 处理

REST API → create_rest。追问:

  1. 「是否有 OpenAPI / Swagger 文档?」→ 有:spec_source(URL 或本机文件路径,优先);没有:请用户给简短接口清单 endpoints(每行 METHOD /path 描述,如 GET /orders/{id} 查询订单)。
  2. base_url:表单 Q3 已给则直接用(OpenAPI 里有 servers 时可省略)。
  3. 认证(映射到 auth_type):
用户选择auth_type需追问(非密钥)卡片收集(密钥)
无需认证none——
Bearer Tokenbearer—Token
自定义请求头api_key_headerheader_nameAPI Key
Query 参数api_key_queryquery_paramAPI Key
AK/SK 签名hmacAK/签名/时间戳请求头名(默认 X-Access-Key/X-Signature/X-Timestamp),签名串模板(默认 {method}\n{path}\n{query}\n{timestamp}\n{body_sha256}),hex/base64AK(明文显示)+ SK
OAuth 2.0(服务间)oauth2_client_credentialstoken_url、scopesClient ID + Client Secret
OAuth 2.0(用户授权)oauth2_authorization_codeauthorize_url、token_url、scopes(通常含 offline_access)Client ID (+Secret),随后系统浏览器授权

未指定认证且有 OpenAPI 时可省略 auth_type,按文档的 securitySchemes 推断(结果 auth_from_spec:true,向用户确认)。 AK/SK 仅覆盖通用 HMAC-SHA256 请求头签名;AWS SigV4、阿里云/腾讯云官方签名不在支持范围,要如实说明。

数据库直连 → create_database。追问:db_type(SQLite / MySQL / PostgreSQL);SQLite 问文件路径 db_path;MySQL/PostgreSQL 问 db_host、db_port(默认 3306/5432)、db_name、db_user(不问密码,密码走第 5 步)。默认只读;只有用户明确要求写入时才 allow_writes:true,并提醒风险。

其他 → 依据描述判断能否归入以上三类;不能则说明并结束。

Show full SKILL.md (139 more words)Show less
第 4 步:创建
  • MCP:connector_manage {action:"create", name, url, auth_style, header_name?, query_param?, template_id?, mcp_oauth?}
  • REST:connector_manage {action:"create_rest", name, base_url?, spec_source? | endpoints?, auth_type?, header_name?/query_param?/hmac_*?/token_url?/authorize_url?/scopes?}
  • 数据库:connector_manage {action:"create_database", name, db_type, db_path? | db_host, db_port, db_name, db_user, allow_writes?}

通用结果处理:

  • error=exists → 已有实例(返回 existing),问「直接使用 / 更新」,不要换个名字再建一份;更新带 overwrite:true。
  • error=duplicate → 名称被占用,请用户换名。
  • error=invalid_form / spec_invalid / driver_missing → 指出原因并只重问该字段。
  • gateway_unavailable → 本机连接器网关未就绪(桌面端未打包网关时会出现),如实告知。
第 5 步:收凭证(仅当 needs_credential=true)
  • MCP:{action:"request_credential", server_name, credential_label:"API Key" 或 "Token"}(模板有 credential_label 时用模板值,如恒生聚源 Access Token;create 结果带 credential_help_url 时先把「如何获取凭证」链接发给用户,掩码卡片里也会显示该链接)
  • REST:{action:"request_credential", instance_id:"rest:<id>"}(按认证类型自动给出多字段卡片;OAuth 授权码会在提交后打开系统浏览器,用户在浏览器里同意即可)
  • 数据库:{action:"request_credential", server_name}(数据库密码;SQLite 无需)
  • 永远不要让用户把 Token / Key / 密码 / Secret 发在聊天里;如果用户主动贴了,提醒其已暴露、建议到服务端轮换,并仍通过掩码卡片重新填写。
  • 不要在回复里复述、拼接、猜测任何凭证内容。
  • 返回 skipped / no_answer → 提示可稍后再填;no_refresh_token → 说明需在 scopes 中加入 offline_access(或服务方等价设置)后重试 authorize_oauth。
第 6 步:探活

connector_manage {action:"verify", server_name | instance_id}:

  • MCP 成功 → 报告可用工具数;失败:401/403 多为凭证错误(可再走第 5 步),404 多为 URL path 错误,超时多为网络 / 内网地址。
  • REST → 执行首个无必填参数的 read 动作;no_probe_action 表示没有可直接探测的动作(不算失败,提示用户用 execute_action 实测)。
  • 数据库 → 返回表数量与前若干个表名。
第 7 步:汇报

简短列出:连接器名、类型(MCP / REST / 数据库)、地址(host 即可)、认证方式(不含密钥)、探活结果(REST 附动作数,数据库附只读与行数上限),并提示: 「可在 设置 → 连接器 → 我的连接 查看 / 更新凭证 / 删除;在对话框的连接器选择器里即可启用。」

3. 红线

  • 不重复建设:先 list,再决定复用 / 更新 / 新建;同一模板只保留一个实例。
  • 不泄露密钥:凭证只走 request_credential 掩码卡片;工具结果里也不会出现明文。
  • 不越权:不改其它 MCP 条目;delete 只在用户明确要求删除某个连接器时使用。
  • 数据库默认只读;写入需用户明确同意。

© DemonDamon, 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

Files

Just SKILL.md in agenticx/skills/connector-assistant of DemonDamon/AgenticX.

Open the folder on GitHubat commit ce32aff

Compare with similar skills

Connector Assistant 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.

Connector Assistant compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Connector Assistant this skillDemonDamon/AgenticX315—~2.1kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
MCP Server Builder with mcp-usemcp-use/mcp-use11k—~923Automated safety check: PassApache-2.0
Agents SDKcloudflare/skills3k2 repos~3kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Builds, modifies, debugs, migrates and verifies TypeScript MCP servers and MCP Apps with the mcp-use framework, treating the installed package's types as the source of truth.

    11k GitHub stars~923 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agents SDK

    cloudflare/skills

    Official

    Build, debug, or review Cloudflare Agents SDK applications using the agents package.

    3k GitHub starsUsed in 2 repos~3k tokens
    Agent WorkflowsAuto-check passed
  • Cao MCP Apps

    awslabs/cli-agent-orchestrator

    Official

    Enable, operate, and extend CAO's MCP Apps surface — the host-rendered fleet dashboard visible inside MCP App hosts (Claude Desktop, ChatGPT, VS Code Copilot, Goose, Postman).

    1.4k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from DemonDamon/AgenticX

All 17 skills in this repo
  • Code Module Summaries

    DemonDamon/AgenticX

    A skill your agent uses when scanning an arbitrary Git repository to create, refresh, or selectively update Markdown summaries of code modules, especially when changes must be traced from each…

    315 GitHub stars~3.7k tokensUpdated today
    Auto-check passed
  • Agenticx A2a Connector

    DemonDamon/AgenticX

    Guide for using the A2A (Agent-to-Agent) communication protocol in AgenticX including agent discovery, skill invocation, remote agent cards, and distributed agent systems.

    315 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Agenticx Agent Builder

    DemonDamon/AgenticX

    Guide for creating persistent Near desktop digital avatars (数字分身) via natural-language interview and the createavatar tool.

    315 GitHub stars~893 tokensUpdated today
    Auto-check passed
  • Agenticx Deployer

    DemonDamon/AgenticX

    Guide for deploying AgenticX agents to production including Docker containerization, Kubernetes orchestration, Volcengine AgentKit cloud deployment, and API server setup.

    315 GitHub stars~866 tokensUpdated today
    Auto-check passed
  • Agenticx Memory Architect

    DemonDamon/AgenticX

    Guide for setting up and using the AgenticX memory system including Mem0 integration, long-term memory, context management, and memory-enhanced agents.

    315 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agenticx Query Data Source

    DemonDamon/AgenticX

    A skill your agent uses when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come…

    315 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Questions about Connector Assistant

What does Connector Assistant do?

连接器助手(Connector Assistant)。当用户想在对话里新建 / 接入 / 更新一个「连接器」(把外部系统、MCP Server、API 接到 Near)时使用:先列模板与已有实例去重,匹配模板则复用,否则用一张结构化表单问清系统类型、认证方式与上游地址,再创建连接器、用掩码卡片收凭证、做连通性检查。连接器不是分身(Avatar)。. Connector Assistant is an agent skill from DemonDamon/AgenticX.

When should I use Connector Assistant?

Connector Assistant fits situations like: tasks that involve MCP servers.

How do I install Connector Assistant in Claude Code?

Run `npx skills add DemonDamon/AgenticX --skill connector-assistant -a claude-code`. Or copy the skill folder (agenticx/skills/connector-assistant in DemonDamon/AgenticX) into .claude/skills/connector-assistant in your project. Claude Code loads it when a task matches its description.

How do I install Connector Assistant in Codex?

Run `npx skills add DemonDamon/AgenticX --skill connector-assistant -a codex`. Or copy the skill folder (agenticx/skills/connector-assistant in DemonDamon/AgenticX) into .agents/skills/connector-assistant in your project. Codex loads it when a task matches its description.

Can I use Connector Assistant in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DemonDamon/AgenticX --skill connector-assistant -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/connector-assistant, .gemini/skills/connector-assistant, .github/skills/connector-assistant and .opencode/skills/connector-assistant in your project.

What does Connector Assistant need to run?

SKILL.md names no scripts, command-line tools or credentials: Connector Assistant is instructions for the agent only.

Does Connector Assistant access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Connector Assistant safe to install?

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.

What licence does Connector Assistant use?

Connector Assistant 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.

How many tokens does Connector Assistant use?

About 2.1k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Connector Assistant?

Skills that share tags, products or a category with Connector Assistant: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and MCP Server Builder with mcp-use (mcp-use/mcp-use, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Connector Assistant?

DemonDamon (a GitHub user) maintains it in DemonDamon/AgenticX, which has 315 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 9, 2026.

Source: DemonDamon/AgenticX on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.