SkillCheatSheet
pascal-3d
An AI agent skill from pascalorg/editor, scored 70 out of 100 by code.
Code score by group
It loses the most points in Done criteria (11), the group that checks whether there is a checklist and a step that verifies the work.
What the author says it does
Connect to Pascal and use its MCP tools to create, inspect, edit, validate, save, or hand off editable 3D building scenes. Use this skill whenever a user asks an agent to work in Pascal, make a room or building model, inspect a Pascal project, perform spatial edits, connect Pascal MCP, or return a verified Pascal editor link. It also governs safe local, existing-account, and explicitly authorized autonomous setup.
This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.
- Repository
- pascalorg/editor
- Folder
- skills/pascal-3d
- License
- MIT
- GitHub stars
- 25,458
- SKILL.md lines
- 117
- Other files
- 8
Add pascal-3d to your agent
npx skills add pascalorg/editor --skill pascal-3dThe command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.
Labelled for
More skills from pascalorg/editor
-
review-architecture
Review a PR against the Pascal architectural rules — package boundaries (core/viewer/editor/nodes), the registry-driven composition model (def.geometry / def.renderer / def.system…
72B -
furniture-fit
Assess whether furniture fits in a measured Pascal room or layout. Use this skill for sofa, table, bed, cabinet, appliance, staging, placement, collision, clearance, or rotated-fo…
71B -
architect
Use Architect, Pascal's AI building designer, to generate buildings, floor plans, and spatial designs from a brief. Use this skill when a user asks Architect to generate or design…
68C -
open-pr
Open or update a pull request on pascalorg/editor from the current branch, describing only what the branch actually did. Use when the user asks to open/create a PR, push and PR, o…
53D
All skills in pascalorg/editor
Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.