clacky-ai/openclacky/lib/clacky/default_skills/new/SKILL.md
new
Create a new project to start development quickly
- Source repository stars
- 1,160
- Declared platforms
- 0
- Static risk flags
- 4
- Last source update
- 2026-08-04
- Source checked
- 2026-08-04
Decision brief
What it does—and where it fits
Create a new project to start development quickly
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/clacky-ai/openclacky --skill "lib/clacky/default_skills/new"Inspect the Agent Skill "new" from https://github.com/clacky-ai/openclacky/blob/faaa347a1fd5a855f8e205c379c4994e757b703c/lib/clacky/default_skills/new/SKILL.md at commit faaa347a1fd5a855f8e205c379c4994e757b703c. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Usage
When user wants to create a new Rails project: - "help me create a new Rails project" - "I want to start a new Rails project" - "/new"
"help me create a new Rails project""I want to start a new Rails project""/new" - 02
Process Steps
Before doing anything, call requestuserfeedback with a structured prompt. Use the following as a guide:
If Demo: do NOT follow the Rails setup steps below. Instead, freely build a simple HTML/CSS/JS (or React) prototype directly in the working directory based on their requirement. Use your creativity.If Production: continue with steps 1–3 below (full Rails flow).Use glob tool to check if directory has files: glob("", basepath: ".") - 03
2. Run Setup Script
Execute the createrailsproject.sh script (see Supporting Files below) in current directory. Use the exact absolute path shown in the Supporting Files section:
Clone rails-template-7x-starter to a temporary directoryMove all files to current directoryDelete template's .git directory - 04
0. Ask Project Type and Requirement
Before doing anything, call requestuserfeedback with a structured prompt. Use the following as a guide:
If Demo: do NOT follow the Rails setup steps below. Instead, freely build a simple HTML/CSS/JS (or React) prototype directly in the working directory based on their requirement. Use your creativity.If Production: continue with steps 1–3 below (full Rails flow).Before doing anything, call requestuserfeedback with a structured prompt. Use the following as a guide: - 05
1. Check Directory Before Starting
Before running the setup script, check if current directory is empty: - Use glob tool to check if directory has files: glob("", basepath: ".") - If directory is NOT empty, ask user for confirmation: "Current directory is not empty. Continue anyway? (y/n)" - If user declines, abo…
Use glob tool to check if directory has files: glob("", basepath: ".")If directory is NOT empty, ask user for confirmation: "Current directory is not empty. Continue anyway? (y/n)"If user declines, abort and suggest creating project in an empty directory
Permission review
Static risk signals and limitations
Runs scripts
The documentation asks the agent to run terminal commands or scripts.
### 2. Run Setup ScriptRuns scripts
The documentation asks the agent to run terminal commands or scripts.
Execute the `create_rails_project.sh` script (see Supporting Files below) in current directory.Writes files
The documentation asks the agent to create, modify, or delete local files.
Delete template's .git directoryReads files
The documentation asks the agent to read local files, directories, or repositories.
After the script completes, read the `.1024` config file in the project rootNetwork access
The documentation includes network, browsing, or remote request actions.
The development server is now running at: http://localhost:3000Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 84/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 1,160 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- clacky-ai/openclacky
- Skill path
- lib/clacky/default_skills/new/SKILL.md
- Commit
- faaa347a1fd5a855f8e205c379c4994e757b703c
- License
- MIT
- Collected
- 2026-08-04
- Default branch
- main
View the original SKILL.md
Create New Project
Usage
When user wants to create a new Rails project:
- "help me create a new Rails project"
- "I want to start a new Rails project"
- "/new"
Process Steps
0. Ask Project Type and Requirement
Before doing anything, call request_user_feedback with a structured prompt. Use the following as a guide:
zh:
{
"question": "请选择项目类型,并用一句话描述你想做什么:",
"context": "开始新项目前需要知道项目类型和需求,请先完成填写。",
"options": ["⚡ Demo — 无数据库,AI 自由发挥,快速原型", "🏗️ Production — 真实应用,可部署,完整 Rails 配置"]
}
en:
{
"question": "Choose a project type and describe what you want to build in one sentence:",
"context": "Tell us what kind of project to create so we can get started.",
"options": ["⚡ Demo — no database, AI builds freely, quick prototype", "🏗️ Production — real app, ready to deploy, full Rails setup"]
}
Based on user's choice:
- If Demo: do NOT follow the Rails setup steps below. Instead, freely build a simple HTML/CSS/JS (or React) prototype directly in the working directory based on their requirement. Use your creativity.
- If Production: continue with steps 1–3 below (full Rails flow).
1. Check Directory Before Starting
Before running the setup script, check if current directory is empty:
- Use glob tool to check if directory has files:
glob("*", base_path: ".") - If directory is NOT empty, ask user for confirmation: "Current directory is not empty. Continue anyway? (y/n)"
- If user declines, abort and suggest creating project in an empty directory
2. Run Setup Script
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
- Clone rails-template-7x-starter to a temporary directory
- Move all files to current directory
- Delete template's .git directory
- Initialize new git repository with initial commit
Step 2: Check Environment
- Run rails_env_checker.sh to verify dependencies:
- Ruby >= 3.3.0 (auto-installed via mise if missing or too old — supports CN mirrors)
- Node.js >= 22.0.0 (will install automatically if missing on macOS/Ubuntu)
- PostgreSQL (will install automatically if missing on macOS/Ubuntu)
- Script automatically installs missing dependencies without prompting
Step 3: Install Project Dependencies
- Run ./bin/setup to:
- Install Ruby gems (bundle install)
- Install npm packages (npm install)
- Copy configuration files
- Setup database (db:prepare)
Step 4: Project Setup Complete
- Script completes successfully
- Project is ready to run
3. Start Development Server
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?
Error Handling
- Directory not empty → Ask user confirmation, abort if declined
- Git clone fails → Check network connection, verify repository URL
- Ruby < 3.3 or missing → Automatically installs Ruby 3.3 via mise (with CN mirror support); exits with instructions if mise install fails
- Node.js < 22 → Script installs automatically (macOS/Ubuntu)
- PostgreSQL missing → Script installs automatically (macOS/Ubuntu)
- bin/setup fails → Show error, suggest running
./bin/setupmanually - Dev server fails to start → Poll the terminal session (empty input) to check logs, verify database status
Example Interaction
User: "/new"
Response:
- Checking if current directory is empty...
- Running create_rails_project.sh in current directory
- Cloning Rails template from GitHub...
- Checking environment dependencies...
- Installing project dependencies...
- Project setup complete!
- Starting development server via terminal (background)...
- ✨ Server running! Visit http://localhost:3000