{
  "id": "p_CiWDY0X8lOA0y7xm",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_CiWDY0X8lOA0y7xm",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You are in a planning meeting, and someone says the team should \"build a plugin,\" and someone else says it should really be a connector, and a third person says a skill would do. Everyone nods. You suspect that nobody in the room means the same thing by any of the three words, and you would like a plain answer before the afternoon is out.\n\nHubSpot has written one. In its post, Claude skills vs. plugins vs. MCP connectors: A simple guide, it separates the three in a single line: \"Skills teach Claude a procedure, MCP connectors give it authorized access to an outside tool or data source, and Plugins package both together so a team can install everything at once.\" The idea you can carry back to the meeting is the one it names directly: \"separate access from procedure from distribution. Each layer answers a different question.\"\n\nSo you read on, and the pieces fall into place. A connector is \"one live connection, built on MCP, between Claude and a specific service.\" The service itself runs it, and it acts inside the user's permissions. A skill \"teaches the how: your team's report format, your review checklist, the brand voice you always want applied.\" There is a limit you should write down: a skill \"can tell Claude how to use a connector's data, but it can't reach a live service on its own.\" A plugin bundles skills, connectors, commands and sub-agents, so a team installs once instead of each person adding each piece. And the post settles the argument you were dreading: \"None of the three sits 'above' the others in a power ranking.\"\n\nYou should hold this with the right amount of caution. The post contains no figures. It is a marketing blog post from a company that ships a free Claude connector, and it says so. The taxonomy holds up regardless of who wrote it.\n\nNow the part that makes this more than a glossary. The APIs.io catalog holds HubSpot as one of the strongest records it has, which gives you a way to check the company against its own words. The HubSpot provider page lists API pages across the CRM, including the Custom Objects API, the CRM Properties API and the Pipelines API, which are the surfaces a connector reads and writes.\n\nOn the Agent Readiness score, the MCP server and agent skills are both lit. Those are the two halves of the post's taxonomy: access and procedure. Alongside them are idempotency, reversibility, error semantics, the event surface, delegated identity and protected resource metadata. The Kin Score is 93.2, in the exemplar band, the highest of any provider this series has covered. It is carried by developer ergonomics at 94.6 and operational transparency at 94.7. The Agent Readiness score is 54.0, which the catalog labels agent-ready.\n\nThen the turn. The dimensions that are not lit are a well-known catalog, consent identity, an agent card, dry-run mode, dynamic client registration and agentic commerce. Hold that list against the post. HubSpot has the access layer and the procedure layer on the record. The third layer in its own taxonomy is distribution. That layer has a contract-level equivalent too: a published catalog or agent card that lets an agent find the connector and its skills without a person installing them. That is the piece a company this far ahead has left to add.\n\nThis is a note about the catalog's own filing as much as about HubSpot. The catalog is saying that a provider can explain distribution well in prose and still not publish the machine-readable form of it. Writing the explanation and shipping the artifact are two separate pieces of work.\n\nWhat you take back to the meeting is simple. Use the three words precisely: skills for procedure, connectors for access, plugins for distribution. Do not rank them, because they answer different questions. And when you ask whether a vendor is ready, check all three layers on the record, not only the two that are easy to demonstrate in a demo. If your own team is building here, ask which of the three you have actually published in a form something other than a person can find.\n\nRead the original: https://apis.io/2026/10/23/hubspot-explains-skills-plugins-and-connectors-as-procedure-access-and-distribution/",
  "title": "You Asked What a Skill Is. HubSpot's Answer Leaves One Layer Open",
  "topics": [
    "agent-skills",
    "mcp-connectors",
    "hubspot",
    "agent-readiness"
  ],
  "published_at": "2026-10-23T13:46:48.188Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}