Cloudflare
hodgef/apiker
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF…
Deploy applications and infrastructure to Cloudflare with the cf CLI and typed cloudflare.config.ts.
$ npx skills add mizchi/skills --skill cloudflare-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mizchi/skills cloudflare-deploy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mizchi/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cloudflare-deploy .claude/skills/cloudflare-deploy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cloudflare-deploy" agent skill from https://github.com/mizchi/skills/tree/main/cloudflare-deploy into .claude/skills/cloudflare-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloudflare-deploy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mizchi/skills/tree/main/cloudflare-deployType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mizchi/skills --skill cloudflare-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mizchi/skills cloudflare-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mizchi/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cloudflare-deploy .agents/skills/cloudflare-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cloudflare-deploy" agent skill from https://github.com/mizchi/skills/tree/main/cloudflare-deploy into .agents/skills/cloudflare-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloudflare-deploy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mizchi/skills --skill cloudflare-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mizchi/skills cloudflare-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mizchi/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cloudflare-deploy .cursor/skills/cloudflare-deploy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cloudflare-deploy" agent skill from https://github.com/mizchi/skills/tree/main/cloudflare-deploy into .cursor/skills/cloudflare-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloudflare-deploy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mizchi/skills.git --path cloudflare-deploy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mizchi/skills --skill cloudflare-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mizchi/skills cloudflare-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mizchi/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cloudflare-deploy .gemini/skills/cloudflare-deploy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cloudflare-deploy" agent skill from https://github.com/mizchi/skills/tree/main/cloudflare-deploy into .gemini/skills/cloudflare-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloudflare-deploy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mizchi/skills cloudflare-deployInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mizchi/skills --skill cloudflare-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mizchi/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/cloudflare-deploy .github/skills/cloudflare-deploy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cloudflare-deploy" agent skill from https://github.com/mizchi/skills/tree/main/cloudflare-deploy into .github/skills/cloudflare-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloudflare-deploy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mizchi/skills --skill cloudflare-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mizchi/skills cloudflare-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mizchi/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cloudflare-deploy .opencode/skills/cloudflare-deploy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cloudflare-deploy" agent skill from https://github.com/mizchi/skills/tree/main/cloudflare-deploy into .opencode/skills/cloudflare-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cloudflare-deploy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cloudflare-deployDeploy applications and infrastructure to Cloudflare with the cf CLI and typed cloudflare.config.ts.
Cloudflare Deploy is an agent skill from mizchi/skills. Deploy applications and infrastructure to Cloudflare with the cf CLI and typed cloudflare.config.ts. Use when deploying Workers, migrating a Wrangler project to cf, or setting up Cloudflare resources and CI.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 377 other files, including reference files and assets (for example `README.md`, `agents/openai.yaml` and `references/agents-sdk/README.md`).
It sits in DevOps & Cloud. It works with Cloudflare and Cloudflare Workers. The repository describes itself as: Agent skills by mizchi, distributed via APM. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 62f5808. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pnpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
API_SECRETCLOUDFLARE_API_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cloudflare Deploy loads about 2.9k tokens when it runs, and up to ~345k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 709 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
exec cf deploy --dry-run --secrets-file .env.productionpnpm exec cf deploy --secrets-file .env.productionPut `API_SECRET` in an ignored `.env.production` for deployment and `.dev.vars` for local development. Declaring `bindinAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mizchi/skills at commit 62f5808, republished under its Apache-2.0 licence (© mizchi). 709 words, ~2,859 tokens.
.claude/skills/cloudflare-deploy/SKILL.md (or your agent's skills folder). This skill also uses 372 other files; get the full folder from GitHub.Use cf for Cloudflare operations. Use the decision trees below to pick a product, then read its runtime/API references and the current cf CLI guide.
cf, not @cloudflare/cf.cf in project devDependencies and commit the lockfile. The checked example uses cf@1.0.0-beta.5 and @cloudflare/vite-plugin@beta; recheck help and types when upgrading.cloudflare.config.ts. For an existing Wrangler project, run cf migrate --dry-run, then cf migrate and resolve its follow-up items before project commands. Automatic configuration does not import the old bindings.Verify auth before publishing or mutating account resources:
pnpm exec cf auth whoamiSee authentication. Use pnpm exec cf auth login locally; cf has its own login credentials. In CI set CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID. A deploy dry run needs no credentials.
pnpm exec cf cli search "create a D1 database"
pnpm exec cf schema d1 create
pnpm exec cf d1 create --helpDescribe only the operation and resource type in search queries. Pass names and IDs to the discovered command, not to search. API commands return JSON on stdout and progress on stderr. Resource commands usually use IDs and remote data; inspect --local support instead of copying Wrangler's --remote, --env, --json, or --yes flags.
references/Current CLI, migration, configuration and build guidance lives in references/cf/. Product references retain SDK and runtime knowledge; files marked as legacy preserve old CLI/config examples only as migration input. Do not execute those Wrangler examples or generate new Wrangler configuration from them. Translate the intended operation using cf search/schema and typed bindings.
Rules of thumb:
references/<picked-product>/cloudflare.config.ts? Read configuration first.Start with this Worker, one KV binding and one secret. Apply the TypeScript setup from the configuration reference before typechecking:
// cloudflare.config.ts
import { bindings, defineConfig } from "cf/config";
import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };
export default defineConfig({
worker: {
name: "my-worker",
entrypoint,
compatibilityDate: "2026-09-30", // Today's date for a new Worker
observability: { enabled: true },
env: {
CACHE: bindings.kv({ id: "REPLACE_WITH_KV_ID" }),
API_SECRET: bindings.secret(),
},
},
});// vite.config.ts
import { cloudflare } from "@cloudflare/vite-plugin";
import { defineConfig } from "vite";
export default defineConfig({ plugins: [cloudflare()] });// src/index.ts
export default {
async fetch(req: Request, env: Env): Promise<Response> {
const hit = await env.CACHE.get("greeting");
return new Response(hit ?? "hello");
}
} satisfies ExportedHandler<Env>;Bootstrap commands:
pnpm add -D cf @cloudflare/vite-plugin@beta vite typescript
pnpm exec cf kv namespaces create --title CACHE # Copy the returned ID into config
pnpm exec cf workers types # Generates .cloudflare/types/index.d.ts
pnpm exec cf dev # Vite reports the local URL
pnpm exec cf deploy --dry-run --secrets-file .env.production
pnpm exec cf deploy --secrets-file .env.productionPut API_SECRET in an ignored .env.production for deployment and .dev.vars for local development. Declaring bindings.secret() makes that value required at deploy validation; dotenvx values in the CLI process are not automatically Worker secrets. Include .cloudflare/types in tsconfig.json; see the configuration reference for the full TypeScript setup. Change an existing Worker's compatibility date deliberately.
Live log streaming and legacy Pages asset deployment are not implemented in the checked cf beta, even when a command appears in search/help. Use Workers Logs in the dashboard for inspection and Workers static assets for new web projects. For a legacy Pages project, keep its deployment working while planning migration; do not invent a cf pages deploy replacement. See limitations.
For Pages / D1 / Durable Objects / multi-env / CI — descend into references/.
Need to run code?
├─ Serverless functions at the edge → workers/
├─ Full-stack web app with Git deploys → workers/ (framework) + static-assets/
├─ Maintain or migrate an existing Pages app → pages/ (legacy reference)
├─ Stateful coordination/real-time → durable-objects/
├─ Long-running multi-step jobs → workflows/
├─ Run containers → containers/
├─ Multi-tenant (customers deploy code) → workers-for-platforms/
├─ Scheduled tasks (cron) → cron-triggers/
├─ Lightweight edge logic (modify HTTP) → snippets/
├─ Process Worker execution events (logs/observability) → tail-workers/
└─ Optimize latency to backend infrastructure → smart-placement/Need storage?
├─ Key-value (config, sessions, cache) → kv/
├─ Relational SQL → d1/ (SQLite) or hyperdrive/ (existing Postgres/MySQL)
├─ Object/file storage (S3-compatible) → r2/
├─ Message queue (async processing) → queues/
├─ Vector embeddings (AI/semantic search) → vectorize/
├─ Strongly-consistent per-entity state → durable-objects/ (DO storage)
├─ Secrets management → secrets-store/
├─ Streaming ETL to R2 → pipelines/
└─ Persistent cache (long-term retention) → cache-reserve/Need AI?
├─ Run inference (LLMs, embeddings, images) → workers-ai/
├─ Vector database for RAG/search → vectorize/
├─ Build stateful AI agents → agents-sdk/
├─ Gateway for any AI provider (caching, routing) → ai-gateway/
└─ AI-powered search widget → ai-search/Need networking?
├─ Expose local service to internet → tunnel/
├─ TCP/UDP proxy (non-HTTP) → spectrum/
├─ WebRTC TURN server → turn/
├─ Private network connectivity → network-interconnect/
├─ Optimize routing → argo-smart-routing/
├─ Optimize latency to backend (not user) → smart-placement/
└─ Real-time video/audio → realtimekit/ or realtime-sfu/Need security?
├─ Web Application Firewall → waf/
├─ DDoS protection → ddos/
├─ Bot detection/management → bot-management/
├─ API protection → api-shield/
├─ CAPTCHA alternative → turnstile/
└─ Credential leak detection → waf/ (managed ruleset)Need media?
├─ Image optimization/transformation → images/
├─ Video streaming/encoding → stream/
├─ Browser automation/screenshots → browser-rendering/
└─ Third-party script management → zaraz/Need IaC? → pulumi/ (Pulumi), terraform/ (Terraform), or api/ (REST API)| Product | Reference |
|---|---|
| Workers | references/workers/ |
| Pages | references/pages/ |
| Pages Functions | references/pages-functions/ |
| Durable Objects | references/durable-objects/ |
| Workflows | references/workflows/ |
| Containers | references/containers/ |
| Workers for Platforms | references/workers-for-platforms/ |
| Cron Triggers | references/cron-triggers/ |
| Tail Workers | references/tail-workers/ |
| Snippets | references/snippets/ |
| Smart Placement | references/smart-placement/ |
| Product | Reference |
|---|---|
| KV | references/kv/ |
| D1 | references/d1/ |
| R2 | references/r2/ |
| Queues | references/queues/ |
| Hyperdrive | references/hyperdrive/ |
| DO Storage | references/do-storage/ |
| Secrets Store | references/secrets-store/ |
| Pipelines | references/pipelines/ |
| R2 Data Catalog | references/r2-data-catalog/ |
| R2 SQL | references/r2-sql/ |
| Product | Reference |
|---|---|
| Workers AI | references/workers-ai/ |
| Vectorize | references/vectorize/ |
| Agents SDK | references/agents-sdk/ |
| AI Gateway | references/ai-gateway/ |
| AI Search | references/ai-search/ |
| Product | Reference |
|---|---|
| Tunnel | references/tunnel/ |
| Spectrum | references/spectrum/ |
| TURN | references/turn/ |
| Network Interconnect | references/network-interconnect/ |
| Argo Smart Routing | references/argo-smart-routing/ |
| Workers VPC | references/workers-vpc/ |
| Product | Reference |
|---|---|
| WAF | references/waf/ |
| DDoS Protection | references/ddos/ |
| Bot Management | references/bot-management/ |
| API Shield | references/api-shield/ |
| Turnstile | references/turnstile/ |
| Product | Reference |
|---|---|
| Images | references/images/ |
| Stream | references/stream/ |
| Browser Rendering | references/browser-rendering/ |
| Zaraz | references/zaraz/ |
| Product | Reference |
|---|---|
| RealtimeKit | references/realtimekit/ |
| Realtime SFU | references/realtime-sfu/ |
| Product | Reference |
|---|---|
| cf CLI | references/cf/ |
| Miniflare | references/miniflare/ |
| C3 | references/c3/ |
| Observability | references/observability/ |
| Analytics Engine | references/analytics-engine/ |
| Web Analytics | references/web-analytics/ |
| Sandbox | references/sandbox/ |
| Workerd | references/workerd/ |
| Workers Playground | references/workers-playground/ |
| Product | Reference |
|---|---|
| Pulumi | references/pulumi/ |
| Terraform | references/terraform/ |
| API | references/api/ |
| Product | Reference |
|---|---|
| Email Routing | references/email-routing/ |
| Email Workers | references/email-workers/ |
| Static Assets | references/static-assets/ |
| Bindings | references/bindings/ |
| Cache Reserve | references/cache-reserve/ |
If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the deploy with escalated permissions (use sandbox_permissions=require_escalated). The deploy requires escalated network access when sandbox networking blocks outbound requests.
Example guidance to the user:
The deploy needs escalated network access to deploy to Cloudflare. I can rerun the command with escalated permissions—want me to proceed?© mizchi, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 372 other files (references, assets) in cloudflare-deploy of mizchi/skills.
Open the folder on GitHubat commit 62f5808
Cloudflare Deploy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cloudflare Deploy this skillmizchi/skills | 356 | — | ~2.9k | Automated safety check: Notes | Apache-2.0 | |
| Cloudflarehodgef/apiker | 127 | 7 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Nextjs On Cloudflarecloudflare/skills | 3k | 2 repos | ~678 | Automated safety check: Pass | Apache-2.0 | |
| Cloudflaredmmulroy/cloudflare-skill | 728 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template | 786 | — | ~5.9k | Automated safety check: Notes | MIT | |
| Workers Best Practicescloudflare/skills | 3k | 2 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 |
hodgef/apiker
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF…
cloudflare/skills
Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext.
dmmulroy/cloudflare-skill
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and…
LubomirGeorgiev/cloudflare-workers-nextjs-saas-template
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.
cloudflare/skills
Cloudflare Workers best practices for production applications.
every-app/open-seo
Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, and a known-noise filter list applied automatically.
mizchi/skills
Package, publish, verify and update an agent skill through a Claude Code plugin marketplace, APM or the npx skills CLI.
mizchi/skills
Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English.
mizchi/skills
Review screenshots or other images with OpenRouter vision models via bundled Deno scripts.
mizchi/skills
Post-generation safety checks for sqlc-gen-moonbit + Cloudflare D1.
mizchi/skills
Reference for APM (Agent Package Manager) — apm.yml syntax, install / uninstall / update commands, target detection, lockfile workflow.
mizchi/skills
Operate ast-grep as a project lint tool. An agent skill from mizchi/skills.
Works with
Categories
Deploy applications and infrastructure to Cloudflare with the cf CLI and typed cloudflare.config.ts. Cloudflare Deploy is an agent skill from mizchi/skills.ts.
Cloudflare Deploy fits situations like: deploying Workers; migrating a Wrangler project to cf; setting up Cloudflare resources and CI.
Run `npx skills add mizchi/skills --skill cloudflare-deploy -a claude-code`. Or copy the skill folder (cloudflare-deploy in mizchi/skills) into .claude/skills/cloudflare-deploy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mizchi/skills --skill cloudflare-deploy -a codex`. Or copy the skill folder (cloudflare-deploy in mizchi/skills) into .agents/skills/cloudflare-deploy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mizchi/skills --skill cloudflare-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloudflare-deploy, .gemini/skills/cloudflare-deploy, .github/skills/cloudflare-deploy and .opencode/skills/cloudflare-deploy in your project.
Going by SKILL.md and its folder, Cloudflare Deploy needs the command-line tools its instructions call (pnpm) and credentials named API_SECRET and CLOUDFLARE_API_TOKEN. Our summary lists: Node.js; A credential in CLOUDFLARE_API_TOKEN; A credential in API_SECRET.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Cloudflare Deploy is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 342k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Cloudflare Deploy: Cloudflare (hodgef/apiker, 127 stars), Nextjs On Cloudflare (cloudflare/skills, 3k stars), Cloudflare (dmmulroy/cloudflare-skill, 728 stars) and Prepare Cloudflare Production Deployment (LubomirGeorgiev/cloudflare-workers-nextjs-saas-template, 786 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mizchi (a GitHub user) maintains it in mizchi/skills, which has 356 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on October 2, 2026.
Source: mizchi/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.