Project Kickstart

Scaffold any project in seconds. Generate boilerplate for Next.js, React, Python CLI, Express, FastAPI, static sites, and more. Pre-configured with git, lint...

Security Scan

The skill's instructions, requested artifacts, and lack of install or credential demands are consistent with a project scaffolding tool, with only minor inconsistencies to note.

Purpose & Capability

The skill's name/description (project scaffolding) matches the SKILL.md instructions (generate files, config, CI, README, license). Minor inconsistency: the instructions require running git (git init, commit) but the registry metadata declares no required binaries; declaring git as a required binary would be expected.

Instruction Scope

SKILL.md confines actions to creating project files, initializing a repo, and writing CI/README/LICENSE. It does not instruct reading arbitrary system files, environment variables, or contacting external endpoints for secrets. The agent is asked to produce fully working code and to prefer latest dependency versions, which implies network-aware version selection but not credential access.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That is the lowest-risk model for a scaffolding skill.

Credentials

The skill requests no environment variables or credentials. That is proportionate for a local project scaffolder. It does not request unrelated service tokens or secret-bearing env vars.

Persistence & Privilege

The skill is not always-enabled and does not request elevated persistence. It does instruct initializing a git repository and making a commit in the working directory, which is expected behavior for scaffolding but is a direct filesystem modification.

Assessment

This skill appears to be what it claims: a project scaffolder. Before using it, confirm the target directory (to avoid overwriting files) and that you want the tool to run git init / make the first commit. Ensure git is available in the environment (the SKILL.md assumes it but the registry metadata doesn't declare it). Review generated files (CI workflows, package manifests, Dockerfiles) before running installs or pushing to remotes. If you want tighter control, ask the agent to output the file tree and file contents first instead of making changes automatically.

You scaffold new projects with best-practice defaults so the user can start coding in 60 seconds.

Core Behavior

When the user describes what they want to build, detect the best stack and generate the project structure with all configuration files.

Supported Stacks

Stack	Trigger	What's Generated
Next.js + TypeScript	"next app", "react website"	next.config.ts, tsconfig, tailwind, eslint, app/ router
React + Vite	"react app", "SPA"	vite.config, tsconfig, tailwind, src/ structure
Python CLI	"python tool", "CLI tool"	pyproject.toml, click/typer, src/, tests/
FastAPI	"python API", "backend"	main.py, requirements.txt, Dockerfile, tests/
Express + TypeScript	"node API", "express"	tsconfig, src/, routes/, middleware/
Static HTML	"landing page", "static site"	index.html, styles.css, script.js
OpenClaw Skill	"openclaw skill", "agent skill"	SKILL.md, README.md with frontmatter

What Every Project Gets

Regardless of stack:

1. .gitignore — language-appropriate
2. README.md — project name, description, quick start, license
3. LICENSE — MIT by default (ask if user wants different)
4. .github/workflows/ci.yml — basic CI (lint + test)
5. git init — initialized with first commit

Workflow

Step 1: Ask (if not clear)

What are you building?
1. Web app (Next.js)
2. API (FastAPI/Express)
3. CLI tool (Python)
4. Static site
5. OpenClaw skill
6. Something else (describe it)

Step 2: Generate

Create all files with the appropriate content. Don't use placeholder text — write real, working starter code.

Step 3: Report

Project created: my-awesome-app/

  my-awesome-app/
  ├── .github/workflows/ci.yml
  ├── .gitignore
  ├── LICENSE (MIT)
  ├── README.md
  ├── package.json
  ├── tsconfig.json
  ├── src/
  │   └── app/
  │       ├── layout.tsx
  │       └── page.tsx
  └── tailwind.config.ts

Next steps:
  cd my-awesome-app
  npm install
  npm run dev

Rules

• Write REAL working code, not "TODO" placeholders
• Use the latest stable version of every dependency
• Default to TypeScript for JS projects
• Default to Tailwind for CSS
• Default to MIT license
• Always init git with a clean first commit
• Keep it minimal — don't add auth, database, or features unless asked