06-reference/research

snowflake cowork plugin function coverage

2026-09-22·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
snowflake-coworkcortex-sensepluginsclaude-coworknaming-trap

There Is No Snowflake CoWork HR Plugin. "HR" Came From Anthropic's Claude Cowork Plugin Set, and Snowflake's Own Finance/Sales Plugins Have Not Shipped Either

The question

"Is a Snowflake CoWork HR plugin actually shipping, or is 'HR' an extrapolation from the finance/sales plugins? Confirm the real function/vertical coverage before building a positioning talk-track around it."

Context: open follow-up from [[2026-07-08-cowork-industry-plugins-vs-caf-delivery]], whose own question text said "finance, sales, HR" while its evidence only supported finance and sales.

Headline: no Snowflake HR plugin exists, and as of 2026-09-22 no Snowflake prebuilt domain plugin of any kind (including finance and sales) appears in Snowflake's release notes. The "HR" most likely came from Anthropic's Claude Cowork plugin launch (2026-02-24), which did ship an open-source human-resources plugin. That is a different vendor's product.

What we already know (from the vault)

What the web says

Verified plugin coverage table (checked 2026-09-22)

Vendor / product Plugin (function) Status Source
Snowflake CoWork / Cortex Sense Finance Announced 2026-06-02, "private preview soon"; no release note Press release, CoWork blog, 2026 release notes
Snowflake CoWork / Cortex Sense Sales Same as finance Same
Snowflake CoWork / Cortex Sense "Other enterprise functions" Unnamed; not announced Press release ("like finance and sales")
Snowflake CoWork / Cortex Sense HR Does not exist in any Snowflake source Press release, blog, release notes
Snowflake CoCo User/partner-built plugins (generic mechanism, not a Snowflake function plugin) Public Preview 2026-07-24 Release note 2026-07-24
Anthropic Claude Cowork human-resources, finance, sales, legal, marketing, data, customer-support, product-management, operations, engineering, design, enterprise-search, productivity, bio-research, small-business (+ financial-services line) Shipping, open source (HR since 2026-02-24) GitHub knowledge-work-plugins, claude.com/plugins

Convergences and contradictions

Synthesis for RDCO

Do not build a talk-track around a Snowflake HR plugin, and scope the finance/sales talk-track as "announced, not shipping." Any phData deck line that says "Snowflake's finance, sales and HR plugins" is wrong on three counts. HR is not a Snowflake product. Finance and sales are not available. The phrase "CoWork plugins" names a different vendor's shipping catalog. A client or Snowflake account executive (AE) who knows the product would catch the first error immediately. The safe wording is: "Snowflake has announced prebuilt finance and sales plugins for Cortex Sense (private preview, not yet in release notes as of September 2026)." Always name the vendor. Write "Snowflake CoWork," never bare "CoWork," as the naming-standard brief already requires.

The real "just turn on the plugin" competitor today is Anthropic's catalog, and it validates the foundation-first pitch more strongly than Snowflake's would. Anthropic's finance and data plugins are tool-agnostic workflow bundles. They connect to Snowflake through MCP. That is the "frontier agent over Snowflake MCP" configuration, which Snowflake's own benchmark scored lowest (see [[2026-09-20-cowork-plugin-accuracy-unmodeled-midmarket-data]] for the correct wording of that number). So the argument from the parent brief (plugin quality depends on governed context, and the plugin does not create that context) applies directly to a product the client can install this week. For HR, the Anthropic plugin does not reach Snowflake at all. It reads the HRIS and ATS. An "HR on Snowflake" story therefore does not come from either vendor's packaged plugin. It is a custom build over people data, which is phData's lane, with the usual sensitivity and row-access policy (RBAC) work attached.

For the Organizational Intelligence (OI) Intelligence Maturity Assessment, use a four-way routing label instead of "plugin | configure | custom." The better labels are Snowflake plugin (when shipped) | Claude Cowork plugin over Snowflake MCP | configure | custom. Include a date stamp, because Snowflake's column is currently empty. This is also the more accurate competitive map for phData's partner position. Snowflake and Anthropic are both shipping agent surfaces that reach the same governed Snowflake data. The foundation layer (semantic views, access policies, eval) is the shared dependency that neither plugin catalog supplies.

Watch item, not a build item: when Cortex Sense plugins appear in the release notes, re-run the coverage table. The function list at private-preview entry, and whether partners can author or list function plugins through the CoCo plugin-sharing / Cortex Extension path, decide whether phData packages its own recurring use cases as Snowflake-native plugins.

Why this is in the vault

It corrects a factual error ("finance, sales, HR") that is still in the question line of the parent brief and in the research index, one step before it reaches a phData positioning deck. It also moves the "turn on the plugin" competitor framing for the OI assessment from Snowflake's unshipped catalog to Anthropic's shipping one.

Open follow-ups

Related

Sources