with one click
new
Create a new project to start development quickly
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Create a new project to start development quickly
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Configure IM platform channels (Feishu, WeCom, Weixin, Discord, Telegram, DingTalk) for openclacky. Uses browser automation for navigation; guides the user to paste credentials and perform UI steps. Trigger on: "channel setup", "setup feishu", "setup wecom", "setup weixin", "setup wechat", "setup discord", "setup telegram", "setup dingtalk", "channel config", "channel status", "channel enable", "channel disable", "channel reconfigure", "channel doctor", "send message to weixin", "send message to feishu", "send message to wecom", "send message to discord", "send message to telegram", "send message to dingtalk". Subcommands: setup, status, enable <platform>, disable <platform>, reconfigure, doctor, send.
Debug an OpenClacky extension that won't load, throws errors, or whose panel/api/skill/agent isn't showing up. Use when the user reports something broken with their extension, when `clacky ext verify` reports issues, or when a change didn't take effect. Reads structured verify errors and fixes manifest and file problems.
Pack and publish an OpenClacky extension to the marketplace, publish a new version, list published extensions, or unpublish one. Use when the user wants to ship, release, publish, update, or take down an extension. Handles packing, the license requirement, versioning, and the already-published case.
Scaffold a new OpenClacky extension from an idea. Use when the user wants to create, start, or bootstrap a new extension, plugin, panel, agent, or skill container. Maps the idea to the right contributes types and generates a working skeleton in the local layer.
Summarize a completed meeting from its transcript. Produces a structured summary with key decisions, action items, and discussion highlights. Triggered automatically when a meeting ends.
Customize, fix, override or extend openclacky itself — change a built-in tool's behavior, intercept/audit/block tool calls, plug in a new IM channel (Slack, in-house IM…), or add UI to the Web UI (panel, button, settings tab). Trigger on "patch openclacky", "block dangerous commands", "audit tool use", "add Slack channel", "extend the web ui", "改 openclacky 内置", "拦截工具调用", "扩展 web 界面". Do NOT trigger for ordinary feature work in the user's own project that doesn't touch openclacky.
| name | new |
| description | Create a new project to start development quickly |
| agent | coding |
| disable-model-invocation | false |
| user-invocable | true |
When user wants to create a new Rails project:
Before doing anything, use request_user_feedback to ask the user two things:
project_type: "demo" or "production"
requirement: one-sentence description of what they want to build
Card content:
Based on user's choice:
Before running the setup script, check if current directory is empty:
glob("*", base_path: ".")Execute the create_rails_project.sh script (see Supporting Files below) in current directory.
Use the exact absolute path shown in the Supporting Files section:
<absolute path to create_rails_project.sh from Supporting Files>
The script will automatically:
Step 1: Clone Template
Step 2: Check Environment
Step 3: Install Project Dependencies
Step 4: Project Setup Complete
After the script completes, read the .1024 config file in the project root
to find the run_command, then start it in the background via the terminal tool:
# First, read .1024 to get the run_command (usually `bin/dev` for Rails):
file_reader(path: ".1024")
# Then start the server in the background:
terminal(command: "<run_command from .1024>", background: true)
Important: If the terminal call returns a session_id (and no error), the server has started successfully. You can inspect logs later by polling the same session_id with an empty input.
Then inform the user and ask what to develop next:
✨ Rails project created successfully!
The development server is now running at: http://localhost:3000
You can open your browser and visit the URL to see the application.
What would you like to develop next?
./bin/setup manuallyUser: "/new"
Response: