About this skill

Problem It Addresses

connector-hub addresses a recurring engineering decision when integrating external platforms: which capabilities must remain platform connectors and which are merely auth or API wrappers that can be replaced by scripts. The material classifies connectors into L1 platform-level, L2 auth-convenience, and L3 pure API query types. It covers runtime-dependent capabilities such as Tencent Cloud CloudBase, EdgeOne Pages, and Tencent Meeting, as well as common data sources like Feishu, DingTalk, WeCom, GitHub, TAPD, Tianyancha, Notion, and Tencent Docs.

How It Works

Instead of exposing scattered APIs, it provides a registry, reference files, and Python scripts. The workflow is to read the prefix rules and overview table in SKILL.md, choose the relevant entry under references/, and then run the corresponding script from scripts/ to create documents, send messages, query company data, or manage repositories. For L2 and L3 scenarios, the material also lists Skill alternatives, auth methods, and migration cost, making Webhook, OAuth2, Token, and SMTP credential management more auditable and easier to move away from platform-hosted configuration.

Boundaries to Keep in Mind

L1 capabilities depend on platform runtimes, CDN, build environments, or real-time communication infrastructure and cannot be simply replaced by generic scripts. L2 capabilities can be replaced, but you must maintain credentials and permissions yourself. L3 is mainly API querying and fits Skill-based composition of multiple data sources, custom transformation, and templated output. Before using it, confirm the target platform's auth method, API scope, and whether the corresponding references/ documentation exists.

Screenshots

Use Cases

Compare whether L1 platform capabilities such as CloudBase, EdgeOne Pages, and Tencent Meeting must remain connectors.
Find Feishu, DingTalk, and WeCom bot API scripts from the registry to send text or card messages.
Migrate Tianyancha, Qichacha, and PKULaw query logic from connectors to auditable Skill scripts.
Locate Tencent Docs, Notion, GitHub, and TAPD creation or query scripts using references and scripts.

Best For

Platform integration reviewers who need to decide which connectors are mandatory and which can be scripted.
Notification engineers working with Feishu, DingTalk, and WeCom who need stable text, Markdown, or card sending.
Developers maintaining GitHub, TAPD, or Notion automation who need quick access to APIs and auth methods.
Architects migrating Tianyancha or Qichacha query logic who need to compare connector versus Skill migration cost.