Opening Agentforce to Builders: When Expertise Becomes a Product

Salesforce’s push to open Agentforce 360 to builders expanded the possibility that industry and company expertise could be packaged as reusable agent capabilities.

The opportunity resembles an application ecosystem, but the risk is different. An agent skill does not only render an interface; it can shape a decision, retrieve sensitive context or initiate an action.

Cloud Group point of view

A reusable skill is a governed product. Its value is the combination of domain logic, interface clarity, evaluation evidence and an owner who maintains it as policy changes.

A practical playbook

The strongest next step is narrow enough to govern and useful enough to produce evidence. We would structure the work around these moves:

1. Define the capability and exclusions in business language.
2. Publish a narrow input and output contract.
3. Include permission assumptions and required data classification.
4. Ship evaluation cases and known limitations with the skill.
5. Version dependencies and establish an end-of-life policy.

The architecture and operating implication

Host skills behind curated registries with provenance, approval status and telemetry. Separate the reusable business action from model-specific instructions so the capability can serve multiple agents and evolve independently.

Measure what changes

Model activity is not a business result. Track a small set of indicators that connect behavior to accountable work:

• Reuse across teams and agents
• Quality against published evaluations
• Support load and defect escape
• Time from policy change to compliant update