Install Pascal agent skills

Pascal publishes two agent skills from the public pascalorg/editor repository:

pascal-3d connects to Pascal, works with editable scenes, validates changes, saves supported results, and returns the editor link supplied by Pascal.
furniture-fit checks a measured furniture footprint at a stated position and rotation, then separates supported results from missing height, swing, delivery, and mesh evidence.

skills.sh and Codex installations add instructions and still need the MCP setup below. The Claude Code plugin at version 0.1.7 also supplies one local MCP connector. None of these installs starts Pascal, creates an account, uploads a project, or authorizes a project change.

Install from the public repository

The skills/ folders in the public repository are the canonical source for every supported package path.

skills.sh

Install both skills:

npx skills add pascalorg/editor \
  --skill pascal-3d \
  --skill furniture-fit

List the available skills before installing:

npx skills add pascalorg/editor --list

Claude Code

Add the public repository as a marketplace, then install the Pascal package:

/plugin marketplace add pascalorg/editor
/plugin install pascal-agent-skills@pascal

Version 0.1.7 installs both skills and one local stdio server that runs pascal mcp connect. Install and start the Pascal CLI first, and keep pascal on the PATH used to launch Claude Code. This local connector needs no Pascal account or API key and does not upload projects automatically.

Codex

Add the same repository marketplace, then install the same package:

codex plugin marketplace add pascalorg/editor
codex plugin add pascal-agent-skills@pascal

These commands install the same versioned skill source. The Codex package does not add the local MCP connector, so Codex still needs the setup command below. Installation and public directory indexing are different states: a Git install can work before a package has been submitted to, reviewed by, or listed in an official directory.

Connect a local Pascal project

For the tested read-only furniture-candidate workflow, install the Pascal CLI:

npm install --global @pascal-app/cli

Save active work and disconnect agent clients before updating: selecting a different runtime can restart the local service. Saved projects remain in the data directory; unsaved service state and undo history do not survive that restart. Install and activate the runtime for that CLI version before starting the editor:

pascal update
pascal editor --no-open

Keep your existing PASCAL_HOME so your projects stay in the same local data store. pascal editor alone can reuse an older healthy service; the explicit update selects the runtime used by the furniture task checks. The Claude Code plugin already owns the local Pascal connection. Do not also run pascal mcp setup claude. If a previous setup created a user-scoped pascal entry, remove it before reloading or restarting Claude Code:

claude mcp remove --scope user pascal

Use /mcp to remove or disable any project- or local-scoped Pascal entry too. The one remaining server should be plugin:pascal-agent-skills:pascal. Codex still needs its local connector configured once:

pascal mcp setup codex

Both paths run pascal mcp connect, which discovers the local service and keeps its private token out of the host configuration. Local projects remain in your local Pascal data store and do not require a hosted account. Use one active agent client per local CLI service. The standalone HTTP service shares active scene state across clients; the hosted endpoint uses a different session-isolated bridge. Do not run independent agents concurrently against the same local service. See Run Pascal locally for requirements, storage paths, updates, and diagnostics.

Choose the correct hosted identity

Use hosted MCP setup when the project belongs in Pascal’s hosted project store. In Claude Code, disable plugin:pascal-agent-skills:pascal in /mcp before adding the hosted connection. The plugin server reads local CLI projects; the hosted endpoint reads projects owned by the selected Pascal account or organization.

Intended result	Credential path	Ownership result
Work in your Pascal workspace through the official Cursor connector	Browser OAuth with an explicit workspace and permission review	The connection is limited to the approved workspace and scopes.
Work in your existing personal or organization workspace	Create an API key in Pascal Settings for that workspace	The agent works under the selected existing workspace.
Create separate private agent-owned work	Allow autonomous registration explicitly in the task	Pascal creates a separate agent-owned account and private starter project.

Autonomous registration does not create an email inbox or browser login, and its projects do not automatically appear in another Pascal account. Do not use it when the result must appear in an existing workspace. A skill must not register an account merely because Pascal is not connected. Keep API keys out of repositories, prompts, screenshots, URLs, and command output. Use the host’s credential store or an environment-variable reference. The Pascal CLI includes the commands for asking a person to claim an autonomous agent’s hosted identity:

pascal agent claim
pascal agent status --json

Supply the returned agent key as PASCAL_API_KEY. Use --no-open on a headless host or --json for structured output without a browser. The code expires after 15 minutes, and a new request supersedes the previous code. Claiming links accountability and lifts claim-gated capabilities; it does not transfer project ownership, grant private-project access, upload local projects, or perform OAuth/device login. Direct integrations can use POST /api/auth/agent/claim/start instead. After the person claims the agent, pascal agent status --json or GET /api/auth/agent/status confirms the active key and bounded claim state without exposing the person’s identity.

Ask for a furniture footprint assessment

Follow Check furniture fit with an agent for a copyable task, a worked sofa example, and the measurements to gather first. A useful request supplies the project, room, exact item dimensions, intended pose, and required clearance:

In my Pascal living room, check a prospective sofa that is 2.10 m wide,
0.82 m high, and 0.95 m deep at the stated position with 0.60 m clearance.
Keep the assessment read-only and tell me what was not checked.

The skill inspects the MCP tools exposed by the connected release. When that release supports a read-only candidate input, the agent can test supplied dimensions without adding the item to the scene. Older installed releases may expose a smaller collision schema. In that case, the agent should use only advertised fields and label any manual dimension-and-bound comparison as preliminary. Do not use an unknown catalog item as evidence for a real product. A placeholder size does not establish fit.

Read the result correctly

The report uses footprint fits, footprint does not fit, or insufficient evidence. It should identify the room and item dimensions, tested position and rotation, source revision, collision results, missing evidence, and whether the scene changed.

Check	What the current workflow can establish
Room footprint	The tested horizontal bounding footprint against a measured rectangular bound or explicitly checked polygon.
Item collision and spacing	The declared, scaled item footprints checked by the connected MCP release.
Door access keep-out	A rectangular keep-out when reported by scene verification; this is not a door-leaf swing simulation.
Height and overhead clearance	A separate manual comparison needs a supplied clear-height measurement or measured ceiling/obstacle geometry covering the tested footprint. Nominal level or zone height metadata does not establish a pass or failure.
Delivery route	Not established without doorway, hall, corner, stair, elevator, packaging, tilt, and assembly measurements.
Detailed mesh contact	Not established by a plan bounding-box check.

An empty collision list does not prove room containment, delivery, assembly, safety, or code compliance. Missing doors mean door access was not checked. Scene verification does not include a prospective candidate supplied only to the collision tool. If dimensions are zero, missing, non-finite, ambiguous, or based only on an uncalibrated image, the useful result is an input-gap report naming the smallest measurements needed next.

Verify a completed task

For a read-only assessment, confirm the project version, graph hash, and node count did not change. For an authorized edit, run scene validation, save the intended result, and use the exact editorUrl returned by Pascal. A successful tool response alone is not a finished spatial result. The skill package is versioned independently from the MCP and CLI packages. Agents inspect the connected tool schemas because source, installed, and hosted releases can differ.

Integrate

Extend Pascal

Install Pascal agent skills

Install from the public repository

skills.sh

Claude Code

Codex

Connect a local Pascal project

Choose the correct hosted identity

Ask for a furniture footprint assessment

Read the result correctly

Verify a completed task

​Install from the public repository

​skills.sh

​Claude Code

​Codex

​Connect a local Pascal project

​Choose the correct hosted identity

​Ask for a furniture footprint assessment

​Read the result correctly

​Verify a completed task

Install from the public repository

skills.sh

Claude Code

Codex

Connect a local Pascal project

Choose the correct hosted identity

Ask for a furniture footprint assessment

Read the result correctly

Verify a completed task