Generate
Start from a prompt
Describe the workflow in ordinary language. Generation requires a Plugin Forge Boost; the extension saves the result as a draft that can be previewed before activation.
Atomcal extensionPlugin Forge
Describe a calendar workflow.
Review a plugin draft.
Plugin Forge turns a plain-language request into a generated plugin draft for a calendar. Review its plan and routes before activation; publish only if you want to share it with other calendars.
- Draft before activation
- Private by default
- Curated sandbox APIs
Walkthrough video placeholder
Video walkthrough
Feature walkthrough placeholder
Add the real product walkthrough embed here when the approved video is available.
Prompt → plan → review
Build a small calendar automation with guardrails
Plugin Forge can draft form fields, routes, recurring jobs and webhook handlers from a prompt. The author reviews the output and chooses whether to activate or publish it.
Run
Keep each plugin in its own lane
The runtime exposes a curated Atomcal API and private plugin collections. The validator blocks arbitrary module loading, filesystem access and environment-variable reads; handlers run with a timeout.
Share
Publish only when you choose
Generated plugins start private to their calendar. Publishing makes an extension available to others; subscribing calendars stay pinned to the version they enabled until they choose to upgrade.
Extra capabilities are gated. Scheduled tasks and outbound HTTP are disabled unless the calendar’s Boost/config permits them. Outbound calls are restricted to declared hostnames; plugins cannot write into Scrims-owned collections. Inspect generated code and the validation report before activation.
FAQ
Plugin Forge, with review built in
Does a generated plugin go live immediately?
No. The normal flow stores a draft for review and preview; a calendar member activates it, subject to the calendar’s approval settings and Boost gate.
Can a plugin read any database collection or server secret?
No. The runtime exposes a curated API, namespaces plugin-owned data and blocks unrestricted filesystem, environment and module access.
What happens if plugin generation cannot use the model?
The implementation can fall back to a basic starter stub when the model is unavailable or generation fails. Review the draft and generator metadata; a saved draft is not proof that the requested automation was generated correctly.
Keep generated automation reviewable
Write a narrow prompt, inspect the draft and validator output, then choose whether to activate it for your calendar.