agentforce.com valid

Agentforce Labs

Build and test Salesforce agents from your coding agent. Use your own Salesforce org or connect a preconfigured LabBox through Labs.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T11:38:46.571Z. Cached copy · Source on agentforce.com

# Agentforce Labs

Build and test Salesforce agents from your coding agent. Use your own Salesforce org or connect a preconfigured LabBox through Labs.

Read as [HTML](https://labs.agentforce.com/llms.html) or [Markdown](https://labs.agentforce.com/llms.txt).

## Getting started

1. Use the user's request and supplied context. Ask only for missing details that change the result; reuse their existing Salesforce project and intended org.

2. Check `sf --version` and look for `sfdx-project.json`. Check needed flags with the installed command's `--help`; an update notice alone is not a reason to upgrade. If needed, follow the [Salesforce CLI installation guide](https://developer.salesforce.com/tools/salesforcecli) and create a project with `sf project generate --name <project-name>`.

3. Capture and parse `sf org list auth --json` inside a process; emit only the relevant alias and org ID, never raw JSON or credentials. Reuse working authentication for the intended org. A local listing is not connection proof: verify with the Organization query below before making changes. Use `--target-org <alias>` explicitly and preserve the user's default org. If login is needed, use `sf org login web --alias <alias>` where browser login is supported, or the optional Labs device flow below. A headless runtime can use device auth: the user opens the approval link in their own browser.

4. Set up the skills:

Reuse installed agentforce-generate and agentforce-test skills. Install only missing skills, preferably in the project.

For Claude Code plugins, use `claude plugin install agentforce-adlc@claude-plugins-official`; plugin skill names have the agentforce-adlc: prefix. For portable skills, use `npx skills add forcedotcom/sf-skills` and select your coding tool. Other supported options: https://github.com/SalesforceAIResearch/agentforce-adlc.

Verify the skills load. Reuse prior setup approval; ask before an unapproved global change. If discovery fails, read installed SKILL.md and references when supported; use only host-supported reload steps.

5. Follow agentforce-generate to build with Agent Script (.agent files). For an existing agent, confirm its developer name, retrieve its AiAuthoringBundle, and inspect it before editing. Reuse existing actions where appropriate.

6. Follow agentforce-test to validate the change. Start with local checks; obtain authorization before tests that deploy metadata or run live actions. Report what changed, what passed, and any remaining work.

Keep credentials, device codes, and secret responses out of chat, logs, source files, and commits. Deploy, publish, or activate only when requested, against the confirmed org. Connecting an org does not authorize changes to it.

## Optional: connect through Labs

Use this only when the user wants a Labs connection. Labs chooses their active LabBox, otherwise their connected own org, otherwise provisions a LabBox after approval. This flow cannot select an arbitrary org.

### Before requesting a
…

Machine-readable: GET /v1/resolve?q=agentforce.com · GET /v1/domain/agentforce.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for agentforce.com:
1. POST https://agentwebmap.com/v1/sites/agentforce.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://agentforce.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/agentforce.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/agentforce.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.