Agent skill
create-new-static-website
Create a new GitHub repo from instructa/astro-website-starter using gitpick, initialize git, and push to GitHub. Use when asked to spin up a new Astro static/SSR site starter from instructa/astro-website-starter, set repo visibility/owner, and then configure Alchemy.
Install this agent skill to your Project
npx add-skill https://github.com/regenrek/agent-skills/tree/main/skills/create-new-static-website
SKILL.md
Create New Static Website
Workflow
- Collect inputs (ask first)
- Project folder name (for
npx gitpick instructa/astro-website-starter <name>) - GitHub owner/org + repo name
- Visibility: public or private
- Whether to push immediately after init (default: yes)
- Scaffold from template
- From
~/projects, run:npx gitpick instructa/astro-website-starter <project-name>cd <project-name>
- If folder exists, ask to rename or delete (use
trash).
- Initialize git + create GitHub repo
git initgit add -Agit commit -m "feat: init"gh repo create <owner>/<repo> --public|--private --source . --remote origin --push- If user says no push: omit
--pushand inform them how to push later.
- If user says no push: omit
- Alchemy config (ask after repo creation)
- Ask if they want to configure Alchemy now.
- If yes:
cp .env.example .env- Set
ALCHEMY_PASSWORDin.env(ask for value or instruct user to set). pnpm exec alchemy login- Confirm any Cloudflare/Alchemy prompts and ensure
pnpm run devworks.
Notes
- Keep commands non-interactive when possible.
- Use
ghfor repo creation. - Don’t delete without confirmation (use
trash).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
shadcn-vite-iconify-landing-page
Build, critique, and iterate high-converting marketing or product landing pages using React + Vite + TypeScript + Tailwind and shadcn/ui components, with all icons sourced from Iconify. Use when the user asks for a landing page, sales page, signup page, CRO improvements, above-the-fold vs below-the-fold structure, hero + CTA copy, section order, or wants production-ready shadcn + Vite code.
security-leak-guardrails
Sets up secret-leak prevention guardrails with forbidden path checks, gitleaks config, CI secret scanning, and dependency updates. Use when hardening repos against credential leaks or when adding gitleaks, trufflehog, git hooks, or security checks.
homebrew-publish
Publish CLIs/TUIs to Homebrew via a personal tap. Use when asked to create or manage a Homebrew tap repo, generate or update formulae, compute sha256, test installs, or ship new releases for Go, Rust, Node/TypeScript, Python, or prebuilt binaries.
architecture-ownership
Determine runtime owner, first-fix layer, and canonical long-term module or package owner in layered codebases. Use when placing code across UI vs platform shell vs runtime orchestration vs domain or application vs shared core vs adapter or integration layers, debugging ownership issues, removing duplicate policy paths, or answering "where should this live?" architecture questions.
codex-analysis
Run Codex CLI for deep code analysis and second-opinion reviews. Use when the user explicitly asks for Codex analysis, Codex help, or wants a second opinion from Codex on code, architecture, or debugging questions.
go-local-health
Run local Go health checks (tests, coverage, lint) in Go repositories that contain go.mod/go.sum. Use when the user asks to run or interpret local Go test/coverage/lint workflows using tools like lazygotest, gocovsh, tparse, and golangci-lint. Do not use for Rust or non-Go projects.
Didn't find tool you were looking for?