Forgecad Project Sync
Manage hosted ForgeCAD project sync from the CLI: init, clone, pull, push, file operations, members, publishing, and shares.
Install
$ agentstack add skill-kostard-forgecad-public-kit-forgecad-project-sync ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-kostard-forgecad-public-kit-forgecad-project-sync) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Project Sync
forgecad.io is the hosted ForgeCAD platform; a project is a local folder linked to the server by forgecad.json. The full command inventory (project, file, member, share, token commands and flags) lives in forgecad project --help and the forgecad skill's docs/CLI.md — do not relearn it here.
- One studio process. Run a single long-running
forgecad studio [ ...]naming every active project folder. The user opens the one printed localhost port once; create and edit files only under those folders so the browser live-updates. Never spawn extra servers per project. - studio vs dev.
forgecad studiois for users and agents;forgecad devis only for developing ForgeCAD itself. - Login only for hosted commands.
forgecad loginbefore anyproject/publishcommand; local work (run, render, studio) needs no auth. - init creates, push syncs.
project init "Name"creates the remote project, writesforgecad.json, and pushes existing local files.pushonly syncs an already-initialized project.cloneis the inverse: remote → new local folder. - Sync is content-hash based.
status/push/pullcompare file content hashes — no timestamps, no git; a file is "modified" purely by content difference. Loop: edit →project status→project push. - Sync vs single-file ops. Use
status/pull/pushfor normal sync; useproject fileonly for one hosted-file operation without a full push/pull cycle. - Project context required. All
project file *andpublishcommands must run inside a folder containingforgecad.json. - Shares are live references. A published model always shows the current project file, never a snapshot — pushing changes silently updates published models.
publishprints the share URL. - Non-interactive runs. Pass
--forceto skip confirmation prompts (push, pull, delete) in agent automation.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: KoStard
- Source: KoStard/forgecad-public-kit
- License: MIT
- Homepage: https://forgecad.io
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.