> ## Documentation Index > Fetch the complete documentation index at: https://editor.pascal.app/docs/llms.txt > Use this file to discover all available pages before exploring further. # Install Pascal agent skills > Install Pascal's public agent workflows, connect MCP separately, and understand what a furniture-fit report proves. Pascal publishes two agent skills from the public [`pascalorg/editor`](https://github.com/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. Installing a skill adds instructions to your agent. It does not install or start Pascal, connect MCP, create an account, upload a project, or authorize a project change. Complete the separate MCP setup below. ## 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: ```bash theme={null} npx skills add pascalorg/editor \ --skill pascal-3d \ --skill furniture-fit ``` List the available skills before installing: ```bash theme={null} npx skills add pascalorg/editor --list ``` ### Claude Code Add the public repository as a marketplace, then install the Pascal package: ```text theme={null} /plugin marketplace add pascalorg/editor /plugin install pascal-agent-skills@pascal ``` ### Codex Add the same repository marketplace, then install the same package: ```bash theme={null} codex plugin marketplace add pascalorg/editor codex plugin add pascal-agent-skills@pascal ``` These commands install the same versioned skill source. 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 Start the local editor and its managed MCP service: ```bash theme={null} npm install --global @pascal-app/cli@beta pascal editor --no-open ``` Then configure the agent host you use: ```bash theme={null} pascal mcp setup claude pascal mcp setup codex ``` Run only the setup command for the active host. The configured command is `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](/docs/developers/local-editor) for requirements, storage paths, updates, and diagnostics. ## Choose the correct hosted identity Use [hosted MCP setup](/docs/developers/mcp) when the project belongs in Pascal's hosted project store. | Intended result | Credential path | Ownership result | | -------------------------------------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------- | | 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. ## Ask for a furniture footprint assessment A useful request supplies the project, room, exact item dimensions, intended pose, and required clearance: ```text theme={null} 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 | Not established unless separate measured vertical geometry supports it. | | 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.