#SkillRepo stars
- 5569Cloudflare Access App Setupmizchi/skillsOne-shot Cloudflare Access self-hosted application provisioning via the API — app + email allowlist policy + service token. Use when you want to gate a Worker behind Access without a full Pulumi stack.423
- 5570Cloudflare Deploymizchi/skillsDeploy 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.423
- 5571Cloudflare Mbt Worker Bundlemizchi/skillsBundle a Cloudflare Worker combining MoonBit core code with a TypeScript entry through cf and the Cloudflare Vite plugin, with required FFI rewrites and a post-build bundle check.423
- 5572Cloudflare Workers CD Rollbackmizchi/skillsGitHub Actions CD for Cloudflare Workers through cf with automatic traffic rollback on smoke failure, including JSON deployment snapshots, D1 migrations and prebuilt artifacts.423
- 5573Cloudflare Workers Otel Utelsmizchi/skillsCloudflare Worker telemetry at the fetch boundary — OTLP traces / metrics / logs + utels error tracking + D1 Proxy that emits slow-query warnings. Use when adding observability to a Worker without touching handler code.423
- 5574Conventional Changelogmizchi/skillsReference for Conventional Commits and automatic CHANGELOG generation. Compares release-please / changesets / git-cliff / towncrier and covers commit format, Keep a Changelog, and semver tag practices. Use when setting up or unifying a release flow.423
- 5575Creating Internal Agentsmedusajs/medusa-agent-skillsUse when building an internal admin-facing AI agent in a Medusa project. These agents are operated by merchants and store operators — not customers. Covers data models, module service, agent runtime (tools, system prompt, streamText), streaming API routes (NDJSON), and admin UI chat extensions. Load for any internal agent type: store operations assistant, product audit, cohort analysis, customer service tooling for support staff, etc. Do NOT use for customer-facing agents (storefront chatbots, buyer-side assistants).237
- 5576Dep Lib Reviewmizchi/skillsPeriodic dependency review for Node.js/pnpm projects — outdated package triage, security audit, update batching strategy (patch/minor/major), validation checklist. Run monthly or before major releases. Use when asked to review or update dependencies in a repo.423
- 5577Dotenvxmizchi/skillsUse when a project already uses dotenvx or the user explicitly selects it for environment-variable loading, encryption, multiple environments, or CI. Do not adopt dotenvx by default or activate this skill solely because a project has .env files, multiple environments, or secrets to manage.423
- 5578Earn Hunterokx/agent-skillsAutomatically monitors OKX Flash Earn, Fixed Earn and Flexible Earn opportunities, sends push notifications, and guides subscription. 自动监控 OKX 闪赚、定期和活期赚币机会,推送通知并引导申购。Use when user says: 有闪赚通知我, 监控赚币, monitor earn, notify me about earn, 定时检查理财, 执行 earn-hunter 扫描, earn-hunter scan, 活期年化高了通知我, 监控活期.201
- 5579Echo Skillmizchi/skillsUse when the user provides an arbitrary line of text and you must echo it back verbatim, prefixed with "ECHO:".423
- 5580Empirical Prompt Tuningmizchi/skillsMethodology for iteratively improving agent-facing instructions (skills / slash commands / CLAUDE.md / code-gen prompts) via bias-free executor + two-sided evaluation (self-report + instruction-side metrics). Meta-skill, invoke ONLY when the user explicitly asks for an "empirical" eval of a prompt or skill, or for the Iter-0 description / body consistency check. Do NOT auto-invoke after every skill edit; this loop is operator-triggered by name.423
- 5581Extract Glossarymizchi/skills指定されたリポジトリ、複数リポジトリ、または GitHub organization から、ドメイン固有の専門用語、業界用語、社内・プロダクト用語、リポジトリ実装マップ、技術構成、オンボーディング向け Mermaid 構成図を抽出・生成するときに使う。ユーザーが「用語集を作る」「ドメイン辞書を作る」「オンボーディング資料にする」「repo/org を見て専門用語をまとめる」「AI が再確認しなくてよい知識ベースを作る」と依頼したら起動する。423
- 5582Flaker Storage Cache on CImizchi/skillsPersist flaker's DuckDB storage across GitHub Actions runs and feed it from multiple sources (vitest reports, custom adapter reports, etc.). Use when wiring `@mizchi/flaker` into a new repo's CI, adding a new ingest source to an existing flaker setup, or debugging why `flaker apply` / `flaker run --gate ...` "lost its history" between runs. Encodes the cache key shape, fetch-depth requirements, `--changed` derivation, and the import-step placement that internal flaker users converged on.423
- 5583Formal Methods Drift Guardmizchi/skillsUse after a formal model or verifier check already exists and the user wants to maintain it over time. Helps Codex compare specs/docs, implementation code/tests/config/logs, and formal models or CI checks for drift; classify whether the drift is in the spec, code, model abstraction, harness, or unresolved domain decision; run or plan verifier checks; and translate SAT/UNSAT changes, counterexample traces, proof failures, stale models, and CI results into domain-language review questions and ledger entries.423
- 5584Formal Methods Reconcilermizchi/skillsUse when reconciling software specs, docs, tests, configs, code, logs, or incidents with formal methods. Helps Codex extract claims, decide whether docs or implementation are the source of truth, choose an appropriate tool such as Z3, Alloy, TLA+, P, Dafny, MoonBit prove, Lean, Rocq, Why3, Verus, CBMC, Tamarin, or ProVerif, build the smallest useful model, run or plan verifier checks, and translate SAT/UNSAT, traces, proof failures, or proof obligations into domain-language questions and regression guards.423
- 5585Frontend Expertmizchi/skillsFrontend architect perspective for the weekly review. Focuses on component design, state management, DOM usage, developer experience, and build configuration. Reads raw JSON from other audit scripts and produces an opinionated perspective report.423
- 5586Frontend Ops Expertmizchi/skillsFrontend Ops specialist perspective for the weekly review. Focuses on CI/CD, Scheduler, KPI ratchet, release process, Renovate / Dependabot health.423
- 5587Frontend Review CImizchi/skillsUse when CI is slow (>10 min), flaky, or the user asks to optimize GitHub Actions for a frontend project. Analyzes `gh run list` history, identifies bottleneck steps, proposes sharding / cache / concurrency improvements. Runs `scripts/audit-ci.sh`.423
- 5588Frontend Review Depsmizchi/skillsUse when auditing dependency health — outdated packages, CVE triage with attack-vector weighting, deprecated/declining library detection (trend-watch). Runs `audit-deps.sh` and `audit-trend-watch.sh`. Pairs with `frontend-review-security` for the full security picture.423
- 5589Frontend Review Hygienemizchi/skillsUse when assessing code quality hygiene — TypeScript strictness, lint violations, dead code, and duplication. Runs `audit-typescript.sh`, `audit-lint.sh`, `audit-similarity.sh`. Does NOT cover dependency freshness or CVE audit — use `frontend-review-deps` for that.423
- 5590Frontend Review Performancemizchi/skillsUse when reviewing React rendering performance — profiler-first diagnosis, memo/useCallback/useMemo correctness, virtual scroll, useTransition/useDeferredValue, and canvas/WebGL separation for data-heavy UIs. Covers checklist 24-rendering-performance.md.423
- 5591Frontend Review Securitymizchi/skillsUse when conducting a frontend security review — static analysis (risky HTML patterns, env var exposure), authentication/authorization audit (token storage, route guards, logout), and AI self-penetration testing. Runs `scripts/audit-security.sh`. For CVE triage and deprecated library detection, use `frontend-review-deps`.423
- 5592Frontend Review Statemizchi/skillsUse when reviewing state management architecture — classifying state types (server/URL/form/UI), checking for over-globalization, Jotai/Zustand/Redux patterns, derived state, and logout/cache invalidation. Covers checklist 23-state-management.md.423
- 5593Frontend Review Testingmizchi/skillsUse when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging. Produces recommendations for Week 2 testing phase. Runs `scripts/audit-coverage.sh`.423
- 5594Frontend Review Triagemizchi/skillsUse when starting a frontend review engagement or when the user asks for an initial assessment ("triage", "day 0", "what's the state of this repo"). Reads package.json, README, gh issues, and produces a scorecard covering lockfiles, TypeScript strictness, testing, CI, and known issues. Runs `scripts/audit-triage.sh`.423
- 5595Frontend Review Weeklymizchi/skillsUse for the weekly AI review. Orchestrates all frontend-review-* skills in order, runs five perspective reviews, in parallel when authorized or sequentially, diffs against last week's KPIs, and produces a weekly report that feeds the ratchet.423
- 5596Gh Fix CImizchi/skillsUse when GitHub Actions PR checks are failing on a pull request and need to be diagnosed or fixed. Inspects checks / logs via `gh`, drafts a fix plan, and implements only after explicit approval. Trigger on red checks, failing workflow runs, `pr is failing CI` reports — even if the user does not name a specific check. Out of scope: external CI (e.g. Buildkite) — report only the details URL.423
- 5597Gleam Practicemizchi/skillsUse when writing or reviewing Gleam code on the Erlang target — especially Wisp + Mist HTTP services, OTP-based processes (gen_server / supervisor analogues), justfile workflows, gleeunit testing, `gleam format`, GitHub Actions CI, and performance measurement. Trigger on `gleam.toml`, `.gleam` files, or Erlang/BEAM-related symptoms even if the user does not say "Gleam" by name.423
- 5598Justfilemizchi/skillsReference for the `just` command runner — justfile syntax and GitHub Actions integration. Use when an existing repo already has a `justfile` and tasks must be added, modified, or audited. For new mizchi-owned repos, prefer the `pkfire` skill (`Taskfile.pkl` + `pkf`) instead; justfile is kept only for compatibility with existing repos.423
- 5599K8S Crd From Typed Schemamizchi/skillsUse when generating Kubernetes CustomResourceDefinitions from a typed schema source (zod / TypeBox / Valibot / json-schema). Covers the Structural Schema dialect's restrictions, the /status subresource trap, the metadata-prohibition rule, and plural inflection — the four pitfalls that bite on first attempt.423
- 5600Learning Medusamedusajs/medusa-agent-skillsLoad automatically when user asks to learn Medusa development (e.g., "teach me how to build with medusa", "guide me through medusa", "I want to learn medusa"). Interactive guided tutorial where Claude acts as a coding bootcamp instructor, teaching step-by-step with checkpoints and verification.237
- 5601Maintainer Personamizchi/skillsWrite an issue or PR for a repository you do not own so its maintainers can triage it. Measures the target's own history (reviewers, gates, body length, headings, language, how first-time PRs fare) into an editable persona file, branches by context (OSS first-time / OSS returning / another team inside your org), drafts in Japanese and translates only after approval when the target writes English, checks with a fresh reader and a slop lint baselined on the maintainers' own PRs, and gates the send. Use when filing upstream issues, sending a fix or failing-test PR to another project or team, or r423
- 5602Mcloud Authmedusajs/medusa-agent-skillsExecute mcloud authentication and context commands: login, logout, whoami, use, version, and signup. Use when setting up the CLI, switching accounts, verifying auth state, setting the active org/project/environment context, or checking the CLI version.237
- 5603Mcloud Deploymentsmedusajs/medusa-agent-skillsExecute mcloud deployments commands to list deployments, retrieve deployment details, and fetch build logs. Use when listing deployments, checking deployment status, or reading build output for debugging build failures.237
- 5604Mcloud Environmentsmedusajs/medusa-agent-skillsExecute mcloud environments commands to list, get, create, delete, redeploy, or trigger builds for Cloud environments. Use when managing environment lifecycle, redeploying after variable changes, or starting new builds from source.237
- 5605Mcloud Localmedusajs/medusa-agent-skillsExecute mcloud local build to reproduce a Cloud build on the local machine. Use when debugging a build-failed deployment without pushing to the tracked branch, iterating on a build fix, or testing build-variable changes locally. Requires Docker and must run inside the project's Git repo.237
- 5606Mcloud Logsmedusajs/medusa-agent-skillsExecute mcloud logs to fetch and stream runtime logs for Cloud environments. Use when reading backend or storefront logs, filtering by time range, searching for errors, or scoping logs to a specific deployment.237
- 5607Mcloud Organizationsmedusajs/medusa-agent-skillsExecute mcloud organizations commands to list or get Cloud organizations. Use when discovering organizations, resolving organization IDs by name, or retrieving organization details including members and subscription.237
- 5608Mcloud Projectsmedusajs/medusa-agent-skillsExecute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments.237
- 5609Mcloud Variablesmedusajs/medusa-agent-skillsExecute mcloud variables commands to list, get, set, and delete environment variables for a Cloud environment. Use when inspecting, reading, creating, updating, deleting, or exporting environment variables. Never pass --reveal unless the user explicitly requests secret values.237
- 5610Metal Practicemizchi/skillsBuild and review Apple Metal rendering and GPU compute code, including MetalKit views, Metal Shading Language kernels, CPU–GPU data layout, resource synchronization, and performance diagnosis. Use for .metal files, MTL/MTL4 APIs, MTKView, GPU memory hazards, or Metal shader failures on Apple platforms.423
- 5611Mizchi Blog Stylemizchi/skillsJapanese style guide and AI-tone rubric for mizchi-authored blog posts (zenn / dev.to), calibrated on 18 articles / 937 sentences / 766 paragraphs. Scores a draft structure-first — paragraph granularity, heading form, code cadence, closing move — because marker rates (口語・文末・自分) can be hit exactly while the text still reads as pastiche. Use after drafting an article during the style-matching revision loop.423
- 5612Moonbit Js Bindingmizchi/skillsWrite MoonBit bindings to JavaScript with `extern "js"`. Use for FFI declarations against browser/Node/Deno APIs or npm packages, wrapping JS objects in opaque types, bridging Promises (`async fn` / `Promise::wait()`), `moon.pkg` exports (esm/cjs/iife), and null/undefined at the JS boundary.423
- 5613Moonbit Practicemizchi/skillsMoonBit code generation and packaging best practices. Use when writing MoonBit code to avoid common AI mistakes with syntax, tests, and benchmarks, or when defining and publishing a Wasm executable with SKILL.md for the MoonBit Skills Marketplace.423
- 5614Multi Agent Orchestrationmizchi/skillsUse when deciding whether to spawn subagents, choosing sequential vs fan-out vs supervisor vs debate vs dynamic DAG, designing a coding-agent workflow with write-scope isolation, or when extra agents may waste tokens without independent evidence. Trigger on multi-agent, orchestration, fan-out, worktree, blackboard, verifier, AgentTask, or "should I parallelize this".423
- 5615Natural Writing Enmizchi/skillsEnglish prose norm for writing explanatory text that does not read as machine-generated. One diagnostic axis (does a sentence update the situation or the document?) plus measured thresholds for burstiness, hedging, enumeration and paragraph openings, with corrections to widely-cited signals that false-positive on human technical writing. Use when drafting or revising English articles, docs, READMEs or long-form explanations, especially after an LLM produced the draft. For Japanese use natural-writing-ja; for scoring a draft use ai-index.423
- 5616Natural Writing Jamizchi/skillsJapanese prose norm for writing explanatory text that does not read as machine-generated. Built on one diagnostic axis (does a sentence update the situation or the document?) plus register purity, sentence-beat and 体言止め/反問 rules calibrated against 937 sentences of human technical writing. Use when drafting or revising Japanese articles, docs, or long-form explanations, especially after an LLM produced the draft. For English use natural-writing-en; for scoring a draft use ai-index.423