06-reference/research

cortex agent cowork skill native publish

2026-07-08·research-brief·source: deep-research
snowflakecortex-agentssnowflake-coworkphdatapackaging

A phData Cortex Agent surfaces natively in Snowflake CoWork — but as an agent object, not a "Skill"; the cross-tenant partner publish path is still hardening

The question

"Can a phData-built Cortex Agent be natively published as a CoWork Skill so business users discover it inside the CoWork UX without a custom app, and what is the Snowflake partner publish path?" Context: if phData deliverables surface through CoWork's native store, the pitch becomes "the client's users get it for free through CoWork" and time-to-adoption drops; if not, every phData agent needs a bespoke Streamlit or MCP app — which changes how the DSA scopes and prices delivery. Open follow-up #4 from [[2026-07-07-snowflake-intelligence-vs-cortex-ai-boundary]]. ("CoWork" = Snowflake's Summit-2026 rebrand of Snowflake Intelligence — confirmed current name.)

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The headline for the DSA pitch is genuinely good, with one precise caveat. For a standard engagement, a phData-built Cortex Agent reaches the client's business users natively through Snowflake CoWork with no custom front-end build: create the agent object (Snowsight/SQL/REST), add it to the account's Snowflake Intelligence Object, and grant RBAC — CoWork renders the chat UX, identity, access control, and monitoring for free. That flips the old default. The bespoke Streamlit or MCP app moves from "every agent needs one" to "only when the client wants embedded/branded UX outside Snowflake, a non-CoWork portal, or a specialized interaction pattern." In scoping terms, this deletes a recurring front-end line item and re-weights the estimate toward where phData's actual value sits: the governed Cortex layer (semantic view for Analyst, Search services with RBAC-aware retrieval, agent configuration and tool boundaries, eval harness) plus the visibility/RBAC/Intelligence-Object wiring. Pricing narrative shifts from "we build you an app" to "we make the layer under CoWork trustworthy and governed, and CoWork gives your users the door for free."

But the DSA must not over-claim a marketplace that doesn't exist yet. "Natively surfaces in CoWork" is an in-account capability, not phData publishing an accelerator to a cross-client CoWork store that any customer installs. If the client hears "your users get it for free through CoWork," that is accurate for the agent phData stands up in their account. It is not accurate as "phData ships one agent and all our clients' users discover it." That cross-tenant, productized-IP motion is the Snowflake Marketplace / Native App Framework / Cortex Knowledge Extensions track — a different SKU, different validation, and partly preview (Agent Studio and Skill Catalog were "GA soon" at Summit; the ARD partner-publish workflow is not yet documented). Selling reusable accelerators as public CoWork installs is premature; selling a governed agent that lives in the client's CoWork is deliverable today.

Skills are the complementary packaging lever, and they connect to the Brigade thesis. Beyond the agent, phData can codify repeatable capabilities as SKILL.md skills (Claude Code-compatible per [[2026-07-05-brigade-skills-snowflake-cortex-code]]) stored in stages/Git, which the delivered agent auto-discovers and which the client's Skill Catalog/User Skills surface for reuse. This is where phData IP becomes reusable, governed, discoverable within the client account — and it dovetails with the Brigade already shipping as a native Cortex Code plugin distributable via a Snowflake connection profile. So the packaging story is two-tier: (1) the agent rides CoWork's native UX for end users; (2) skills package the repeatable capability IP the agent runs on, surfaced in the client's Skill Catalog.

Naming discipline for the field. In a client conversation, translate "publish it as a CoWork Skill" to "register the agent object and add it to the Snowflake Intelligence Object so it appears in CoWork; optionally package repeatable capabilities as Skills in the Skill Catalog." And keep the two Coworks apart: the client's Snowflake CoWork (where the delivered agent surfaces) versus phData's internal Anthropic Claude Cowork (where the sales org and CAF skills live). Blurring them will confuse both the client and the internal team.

Open follow-ups

Related

Sources

Vault:

Web: