AGENT SKILLS · ミッション装備
実際に使われている Agent Skills
公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。
- 掲載範囲
- 検証済み
- Skills
- 22,603
- リポジトリ
- 3475
- 最終同期
- 2026/10/30
mdsmithaustinwhy
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
- 1時間の導入数
- 1
- GitHub Stars
- 4
- 更新日
- 10月15日
ckorhonenswe:change-validation-planner
- Plans the narrowest trustworthy validation path for a scoped code change or diff. Use when a user asks what to run before merging, how to validate a specific change, whether the current checks are enough, or wants a bounded command order from narrow to broad. Do NOT use for writing tests, fixing the code change itself, broad QA sweeps, or generic debugging that needs root cause analysis.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 9月26日
ckorhonenswe:ownership-risk-map
- Maps engineering ownership risk in a repository using repo evidence such as git history, churn, bus factor, CODEOWNERS coverage, test density, and orphaned or unclear-owner surfaces. Use when a user says map ownership risk, find bus factor hotspots, which files look orphaned, high-change low-test areas, or asks for a recurring maintenance pass that identifies risky surfaces before they become incidents. Do NOT use for org charts, HR ownership assignments, or generic maintainer lists without re
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 9月26日
rasengan-devrasengan-ecosystem
Rasengan.js ecosystem package patterns. Covers @rasenganjs/kurama (state management), @rasenganjs/image (optimized images), @rasenganjs/theme (light/dark/system), @rasenganjs/i18n (internationalization), @rasenganjs/kage-demo (guided tours), and @rasenganjs/mdx (MDX content). Use when integrating ecosystem packages into a Rasengan.js project.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 7月24日
rasengan-devrasengan-optimizing
Optimization patterns for Rasengan.js. Covers static assets via the public/ directory, asset handling best practices, and performance optimization. Use when managing static files, serving assets, or optimizing resource delivery in a Rasengan.js project.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 7月24日
rasengan-devrasengan-server-validation
Schema validation patterns for @rasenganjs/server using @rasenganjs/validators. Covers zodAdapter, app.configureValidation({ adapter, onError }), per-route schemas (router.post(path, handler, { body, params, query })), controller-level schemas dictionaries matched by handler.name, the arrow-function/bound-method name-loss gotcha, schema precedence (per-route overrides controller-level), and custom validation error handlers. Use when adding request validation to a controller's routes.
- 1時間の導入数
- 1
- GitHub Stars
- 3
- 更新日
- 7月24日
jinhyeonseo01analyze-stock-decision
Combine point-in-time equity data, deterministic factor/risk calculations, sourced business evidence, and explicit AI causal reasoning to produce conditional entry, hold, reduce, exit, stop, and time-exit judgments for 20-, 60-, or 120-session horizons. Use when Codex is asked to assess a stock or equity universe, compare candidates, propose price-conditioned buy or sell timing, balance quantitative signals against a reasoned business outlook, size hypothetical risk, backtest a factor workflow,
- 1時間の導入数
- 1
- GitHub Stars
- 2
- 更新日
- 8月12日
johnnygrecopanel-review
Panel review, deep review, or review until clean.
- 1時間の導入数
- 1
- GitHub Stars
- 1
- 更新日
- 10月15日
moooaitakeout-coupon
调用外卖优惠券API，一键获取美团、饿了么/淘宝闪购、京东外卖红包与隐藏优惠券口令，附带聚合领券页面。返回优惠券代码和领取说明，用户复制口令到对应APP即可领券，天天领外卖红包。
- 1時間の導入数
- 1
- GitHub Stars
- 1
- 更新日
- 10月15日
qinglele-hychinese-citation-ready-writing
Use when the user wants finished Chinese prose for thesis sections, research background, significance, course reflections, experiment summaries, or report paragraphs; prioritize concrete cases, measurable indicators, citation-friendly wording, and directly pasteable Chinese instead of generic background.
- 1時間の導入数
- 1
- GitHub Stars
- 1
- 更新日
- 6月1日
basmiliusbasmilius
- Use when a project imports from the @basmilius npm scope (by Bas Milius): @basmilius/utils (Luxon date, number, color, download, DOM, timing, geo and PRNG helpers), @basmilius/http-client (the typed DTO data layer) and @basmilius/common (Vue 3 app primitives on Pinia and Vue Router). Trigger on any @basmilius/ import; on formatDate / formatNumber, hexToRGB / hslToRGB, debounce / waitFor, downloadBlob, mulberry32, getSeason / getMoonPhase; on @dto / @adapter, HttpClient, RequestBuilder, BaseSer
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月7日
basmiliusvue-component-anatomy
- Use when writing, editing, or reviewing a single Vue 3 Single File Component (a .vue file with ). Covers block order and template root, the compiler-macro order (defineOptions - defineEmits - defineModel - defineProps - defineSlots, defineExpose last), the ordering inside (imports - macros - constants - stores - state - composables - computed - watch - lifecycle - functions), function-vs-arrow style, prop and emit typing, v-model via defineModel, and scoped/module styling. Triggers on editing
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月7日
ckorhonenhone:broken-windows-hunt
- Detects entropy signals in a codebase: stale TODOs, disabled tests, lint suppressions, commented-out code, dead imports, empty catch blocks, and deprecated API usage. Designed for daily runs to catch quality erosion early. Do NOT use for feature work, refactoring planning, or security audits.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 9月26日
ckorhonenhone:test-naming-audit
- Checks that test method and function names read as complete sentences describing behavior. Flags cryptic names like test1, testFoo, or abbreviated names that do not describe what is being tested. Designed to run on every PR. Do NOT use for test coverage, test structure, or non-test code.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 9月26日
daizhouchenprism-research
对产品、公司、技术、概念或人物做系统性深度研究，结合纵向发展史、横向比较、机制分析和带来源的情景推演，产出 Markdown 与 HTML 报告。用于明确需要全面研究或比较的请求；简单概念解释、单点查询与普通摘要无需加载完整流程。
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 9月27日
fandhe-aicreate-design-doc
UX/UI デザイナーの専門家として、アイデア・要件文書から UI/UX 設計資料一式 (design-doc.md・画面遷移図・ストーリーボード・HTML ワイヤーフレーム・PC/モバイル スクリーンショット) を生成。「UI設計して」「ワイヤーフレーム作って」「画面遷移図作って」 「デザイン資料まとめて」「PO承認会用の画面説明資料を作って」で使用。主役成果物は storyboard.png（縦長1枚、主要シナリオの流れに沿って各画面の表示要素を日本語説明）。 Figma ではなく自己完結 HTML + Playwright でワイヤーフレームを作る。企画は create-pitch-deck が担当し、両スキルは concept-brief.md を介して整合する。推奨実行順序: create-design-doc → create-pitch-deck（pitch が画面素材を取り込むため）。
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月14日
galileo-studio-devdesigning-error-handling
Decides where and how failures are handled. Use when writing or reviewing code that can fail — database, HTTP, queue, file, payment or auth provider calls, webhooks, background jobs, parsing of external input — and when deciding whether to add a try/catch, fallback, default value, retry, or timeout. Also use when a reviewer flags swallowed exceptions, silent failures, or defensive checks for states that cannot happen.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月5日
galileo-studio-devexecuting-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月5日
galileo-studio-devfinishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月5日
galileo-studio-devgrill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月5日
galileo-studio-devinstrumenting-for-observability
Adds logging, metrics, tracing, and error reporting that let someone else diagnose a failure. Use when instrumenting a new handler, job, or integration, wiring Sentry or a logger, deciding what to log, or when a log line might include request bodies, tokens, emails, or other personal data. Also use when a failure investigation finds no useful trace.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月5日
galileo-studio-devlearning-codebase-conventions
Discovers and follows the conventions of the codebase being changed. Use before writing or changing code in an existing repository, especially in an area not yet read this session — before creating a file, naming anything, choosing an error-handling or logging idiom, writing a test, or adding a utility. Also use when generated code looks foreign to the codebase or duplicates something that already exists.
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月5日
galileo-studio-devowasp-security
Use when reviewing code for security vulnerabilities, implementing authentication/authorization, handling user input, or discussing web application security. Covers OWASP Top 10:2025, ASVS 5.0, LLM Top 10 (2025), and Agentic AI security (2026).
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月5日
galileo-studio-devponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest
- 1時間の導入数
- 1
- GitHub Stars
- 0
- 更新日
- 10月5日