1,124 件 ・ 関連度順
概要と使いどころ
テストカバレッジのギャップを体系的に分析し、実際に動くテストコードを提案するスキル。 以下のようなときに使う： - テストカバレッジを改善したい・不足テストを特定したい - 「テストが足りない」「カバレッジを上げたい」「どこをテストすべき」 - 「未テストの関数」「what tests am I missing」「improve test coverage」「coverage gap」 t-wada式TDDの原則に基づき、テストの抜け漏れを特定して優先度付きで補完する。 引数: 分析対象ファイル・ディレクトリ（省略時はプロジェクト全体）
Bootstrap full agent infrastructure for an existing, already-coded project without modifying a single line of source code. Surveys the repo, infers conventions from manifests, README, git history, and source samples, then generates the missing AGENTS.md, docs/architecture.md, docs/product-soul.md, ADR backfill, and seeded docs/memory/ files. Asks the user only about gaps the repo cannot reveal. Load when the user asks to "retroactive project setup", "backfill agent infrastructure", "bootstrap agents for this existing repo", "onboard agents to a legacy codebase", "set up agents without touching code", or "fill in missing agent context for this project".
日本語の概要は準備中です。原文の説明を表示しています。
Seed minimal agent harness v0 — manifest, eval checks stub, governance. AUTO-INVOKED after project-setup or retroactive-project-setup when docs/harness/manifest.json is missing. Also triggers on: generate harness, scaffold agents, agent bootstrap, first time agents in this repo, new project agent setup, set up agent harness, agent onboarding files, missing agent configuration, agent instructions setup, make agents read project rules, agent reliability setup, agents not configured. Pairs with project-setup. Evolution is harness-evolution.
日本語の概要は準備中です。原文の説明を表示しています。
Build the smallest, highest-signal context package for an AI coding task — goal, constraints, repo facts, boundaries, and a verification plan. Load when prompts are underspecified, the agent is missing key files or decisions, the user says "use the right context", "here's the repo", or when work is drifting due to missing constraints. Also triggers on "context engineering", "gather context", "what do you need from me", "before you start". Not for cross-session continuity (use memory-startup/memory-recall).
日本語の概要は準備中です。原文の説明を表示しています。
Audit required bioinformatics command-line tools against Lmod or Environment Modules on Linux HPC clusters, resolve executable and version requirements, and reproducibly deploy missing software through a site-approved EasyBuild, Spack, Bioconda/micromamba, Apptainer, binary, or source-build workflow. Use when Codex must inspect module availability, diagnose a missing or wrong-version bioinformatics tool, install scientific software on Slurm/PBS clusters, publish or validate modulefiles, or produce an auditable and rollback-ready cluster software deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Improve Coval trace quality after basic ingestion works. Use when traces are sparse, missing useful STT/LLM/TTS/tool spans, missing attributes needed for Coval built-in metrics, or when a customer wants maximum debugging and observability value from agent traces.
日本語の概要は準備中です。原文の説明を表示しています。
Local-first year-round tax memory system for individuals, freelancers, and small businesses. Use when users mention tax documents, receipts, expenses, tax notices, filing preparation, missing forms, accountant meetings, or year-end organization. Captures tax-relevant facts as they happen, tracks what may be missing, and prepares CPA-ready handoff summaries. NEVER provides tax advice, legal interpretations, filing positions, or final tax calculations.
日本語の概要は準備中です。原文の説明を表示しています。
Build or refine UI color systems, warmth, semantic color, and color-based hierarchy in designs that are too gray, monochromatic, or missing color meaning. Use when the user mentions dull colors, gray UI, missing warmth, weak semantic color, or a need for stronger color hierarchy.
日本語の概要は準備中です。原文の説明を表示しています。
WPA/WPA2/WPA3-Enterprise (802.1X / EAP) attack methodology — EAP method identification (PEAP-MSCHAPv2, EAP-TTLS, EAP-TLS, EAP-GTC, EAP-PWD, EAP-FAST), evil-twin RADIUS attacks with eaphammer for credential capture, MSCHAPv2 challenge-response cracking, EAP-TLS client certificate theft paths (DPAPI, NDES, AD CS auto-enrollment), supplicant validation bypass (missing server cert validation, missing CN pinning, BYOD misconfigurations), and post-capture pivots into AD via cracked domain credentials. Use for corporate Wi-Fi engagements where the network is 802.1X authenticated.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt Missing/Weak Rate Limiting — login brute force, OTP/2FA brute force (10^6 keyspace), password-reset-token brute, credential stuffing, username/email enumeration via error-string / status-code / timing differences, weak password policy, missing CAPTCHA (CAPTCHA token replay / single-use / concurrency-window bypass specifics → hunt-captcha-bypass), IP-based rate-limit bypass via X-Forwarded-For and friends, ReDoS. Distinguishes hard lockout vs soft IP-throttle vs CAPTCHA-injection vs silent shadow-throttling (avoids false-negative 'no rate limit' conclusions). Medium to Critical depending on what the brute reaches (OTP→ATO = Critical).
日本語の概要は準備中です。原文の説明を表示しています。
DiscordのローカルアーカイブからメッセージやDMを検索し、期間を絞った確認や要約に役立てるスキル。保存データの鮮度と取得範囲も確認します。
Eight SleepのPodの状態確認や電源・温度調整をエージェントに頼めるスキル。アラームとスケジュールの管理、音声再生やベースの角度操作にも対応します。
課題や外部からのPRを分類し、報告内容の検証や不足情報の整理を進めます。対応状況を管理し、エージェントや人が着手するための作業説明を残すスキル。
指定したコミットやブランチなどを基準にコードの変更を確認し、開発規約への適合と仕様の実現を別々にレビューします。二つの観点の指摘を分けて報告するスキルです。
Run the ECC engineering process retroactively against an existing project slice. Audit current state, reconstruct past decisions, produce a four-axis gap register (thinking, coding practice, missing features, technology selection), then execute fixes forward through the plan-TDD-review pipeline. Use when adopting ECC mid-project, taking over an inherited codebase, or asking what was missed and what would have been built differently from day one.
日本語の概要は準備中です。原文の説明を表示しています。
Javaのtinystructで、端末とWebの両方から使える処理を実装するスキル。起動スクリプトの生成からAPI、データ保存、テストまで開発手順を案内します。
Viteを使う開発で、設定ファイル、環境変数、APIへの接続、プラグイン、ビルド出力を整え、開発サーバーや依存関係の不具合調査を支援するスキル。
配送の遅延・破損・紛失・数量不足に対し、証拠収集から補償請求、運送会社との交渉までを整理し、損失額や顧客への影響に応じた対応判断を支えるスキル。
Kotlinのコード作成・レビュー・改修を支援します。nullの扱い、不変データ、非同期処理、型安全な設定記述を見直し、読みやすく保守しやすい構成に整えます。
曖昧な機能要望や影響の大きい変更を、作業範囲・前提・リスクとともに整理し、期待する動作と検証方法が明確な受け入れ基準や引き継ぎ資料にまとめるスキル。
DartとFlutterのコード作成・レビューで、状態管理、画面遷移、通信、例外処理、テストの実装パターンを参照し、アプリの構成を整えるスキル。
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.
日本語の概要は準備中です。原文の説明を表示しています。
Quality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.
日本語の概要は準備中です。原文の説明を表示しています。
Quality review of a diff: bugs, security, real load, missing tests, speed, and what to delete. Each finding says what goes wrong and how to fix it.
日本語の概要は準備中です。原文の説明を表示しています。