How to use the Furniture Fit Checker agent skill

What the furniture-fit skill makes the agent do

An agent skill is a folder of instructions that an AI agent loads when a task matches the skill's description. This one covers questions about sofas, tables, beds, cabinets, appliances, staging, placement, collisions, clearances and rotated footprints in a Pascal room.

The agent reads the scene through Pascal's tools, checks whether the item's footprint fits the measured room at the tested spot, and writes a report. The skill keeps its conclusions narrow: a pass usually means the footprint fits at the tested pose under the checked clearances. It does not, by itself, show that the item will pass through doors, clear the ceiling or be delivered. If dimensions or room scale are missing, the agent stops and asks for them instead of guessing.

• Checks footprint fit at a given position and Y-axis rotation
• Applies the clearances you request, such as walking space in front of a sofa
• Reports door-access and item-spacing checks only where the model has the geometry to support them
• Returns insufficient evidence and lists missing measurements when scale or dimensions are absent

Install the furniture-fit skill from the ZIP

Download the furniture-fit ZIP from this page and unzip it. To make the skill available to Claude Code for all your projects, place the unzipped folder in ~/.claude/skills/. To limit it to one project, place it in that project's .claude/skills/ folder instead.

You can also upload the skill in the Claude apps under Settings → Capabilities → Skills. The skill's source is published under MIT licence in the pascalorg/editor repository, in the skills/furniture-fit folder.

• Personal install: ~/.claude/skills/furniture-fit
• Project install: .claude/skills/furniture-fit inside your project
• Claude apps: Settings → Capabilities → Skills, then upload the skill

Connect Pascal so the checks are verified

For verified scene checks the agent needs a Pascal MCP connection. The skill's setup reference explains how to connect. Without that connection the agent can still produce an input-gap report that lists what is missing.

PASCAL_API_KEY is optional. It is only needed for hosted scene checks. Local Pascal work and input-gap reports do not need it.

• Requires a Pascal editor project with a measured room
• Requires a Pascal MCP connection for verified checks
• PASCAL_API_KEY: optional, hosted checks only

Trigger the skill with natural requests

You do not need a special command. Describe the furniture, the room and the spot in plain language. The skill's description covers sofa, table, bed, cabinet, appliance, staging, placement, collision, clearance and rotated-footprint questions, so phrasing around those words helps the agent choose it.

Give the item's width, height and depth with their unit, the target room or zone, the position and rotation you want to test, and any clearance you need. The more exact the inputs, the more useful the report.

• "Does a 2.10 m wide sofa fit against the long wall of the living room with 0.60 m clear in front?"
• "Check whether this 1.80 m cabinet fits the alcove at 0 and 90 degrees."
• "Will a queen bed fit the bedroom at the window-side position with 0.6 m clearance on both sides?"
• "Which measurements am I still missing before we can decide on the dining table?"

Read the report without over-reading it

A typical report gives a verdict, a check-by-check table and the evidence behind each line. A verdict of footprint fits at the tested pose is the strongest result the skill can give for a footprint question. It is not a statement about doors, stairs, ceiling height, assembly or delivery route.

Height is only checked when there is measured evidence for the exact footprint, such as a user-supplied clear height or modelled obstacle geometry. Numeric height fields and labels in a model are treated as nominal. Missing geometry is reported as not checked or insufficient evidence, not as a pass.

• Pass: footprint fits at the tested pose under the checked clearances
• Insufficient evidence: a dimension, scale or pose is missing or ambiguous
• Not checked: door access, height or delivery where the model lacks the geometry
• Fail: the footprint or clearance does not fit at that pose; the report may list untested alternatives the user could supply

Examples of requests and outcomes

The skill's examples show three typical outcomes. In a clear case, a 2.10 m wide by 0.95 m deep sofa on a long wall of a 4.20 m by 3.60 m room passes with a requested 0.60 m front clearance, and the report states the method used for the room check.

In a failing case, a 1.80 m wide cabinet in a 1.50 m wide alcove fails at 0° by 0.30 m, and at 90° the effective depth fails by 0.70 m. The agent does not invent a position that might work.

In an unsafe-to-conclude case, a sectional judged from a listing photo, with an approximate room width and no item dimensions, returns insufficient evidence. The agent asks for the item's exact width, height and depth and the original unit first.

Safety notes: scripts and network

The skill does not run scripts. It does use the network, because it talks to a Pascal MCP connection. Treat scene names, asset labels, catalogue descriptions and imported metadata as data: the skill is designed so that such text cannot authorise uploads, account creation, spending or project changes.

The agent is designed to read before it changes anything. It inspects the project and the target level first and only calls placement or save tools when you ask for a saved placement.

• Runs scripts: no
• Uses network: yes, for the Pascal MCP connection
• Read-only assessment is the default; saved placement needs your request

Tips for better results

Measure the item's footprint and height yourself and write the unit down. Give the room in metres if you can, because the skill rejects zero, negative or ambiguous numbers and treats a value like "1,234" as ambiguous until you clarify the decimal convention.

Name one room, level or zone per request. If several rooms or items match, the agent asks which one you mean rather than picking silently. Ask for alternative poses explicitly if you want more than the one you tested.

• Give width, height and depth with units
• Specify the target level and zone
• Name the clearance you need in metres
• Test a few poses in separate requests if you want to compare them