4,911 件 ・ 関連度順
概要と使いどころ
Dependency vulnerability remediation workflow for this repository. Use when fixing CVE, BDSA, GHSA, OSV, npm, PyPI, Dependabot, Black Duck, Snyk, or other package vulnerability findings, especially when the user asks for minimal package-only updates, validation, commits, branches, or pull requests.
日本語の概要は準備中です。原文の説明を表示しています。
Explicit request only -- never invoke implicitly, never expose signing secrets. Prepares and publishes one exact-SHA RIPDPI release via the release contract. Use when asked to prepare or publish a version.
日本語の概要は準備中です。原文の説明を表示しています。
Explicit invocation only; never for abusing third-party infrastructure. Generates ranked, owner-controlled VPN/proxy protocol and topology experiment ideas for restrictive networks (TURN/ICE/MASQUE/QUIC/WebTransport).
日本語の概要は準備中です。原文の説明を表示しています。
Never invoke implicitly; use only when explicitly asked for Play Store assets. Builds or updates RIPDPI's marketing screenshots and feature graphic (Next.js generator in play-store-screenshots/).
日本語の概要は準備中です。原文の説明を表示しています。
Never tags, pushes, edits, or publishes. Read-only evidence pack and curated RIPDPI release notes from Git/GitHub history for a stable-tag-to-candidate-SHA range. Use when preparing a changelog or release notes.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and explain bmad-loop run artifacts under `.bmad-loop/runs/`. Use for live health checks ("is it stuck?", "is the loop alive?", "what is the agent doing?") and post-run forensics ("what happened?", "why did story X fail?", "where did the tokens go?"). Also triggers on "monitor/check/summarize the loop", "why did the run pause?", Vietnamese "theo dõi bmad loop", "phân tích run", "đọc log của run", and equivalent requests in other languages. Use only for bmad-loop's own run artifacts, not application runtime logs or CI-provider build logs.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and run manual tests of the project's running app. Runs a session in one of five modes: exploratory, verification, smoke, assessment (UX, localization, accessibility, improvement review), or AI probe. Also writes a manual test plan that holds only what automated tests cannot judge. Use whenever the user asks, in any language, for something to be tested by hand or for a manual test plan — "manual test", "exploratory test", "bug hunt", "verify the bug fix", "smoke test", "QA this screen", "review this screen's UX", "what would you improve", "check the localized copy", "test the AI agent's answers", "write manual test cases", "kịch bản test manual" — or assigns a test design, test plan or test-case IDs to execute by hand. Not for writing automated tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing Spring Boot 4 / Java 17+ code with concrete files or diffs — pull requests, modules, or pasted Java/Spring sources — for migration risks, architecture boundary leaks, JSpecify null-safety gaps, security flaws, performance regressions, or Spring Data pitfalls. Not for Kotlin-only code, non-Spring frameworks, or generic review advice without code context.
日本語の概要は準備中です。原文の説明を表示しています。
Operate the Ryuumonbuchi MCP server for headless Ghidra reverse engineering. Use when driving decompilation, disassembly, patching, type and symbol recovery, memory edits, transactions, and Ghidra project analysis through a Ryuumonbuchi server (stdio or streamable HTTP). Covers the safe read-only-first workflow, session and address discipline, mutation and transaction rules, headless.run, task and error recovery, raw ghidra.call/ghidra.eval/ghidra.script escape hatches, and a sleep/timing-gate bypass recipe.
日本語の概要は準備中です。原文の説明を表示しています。
把缠论分析变成先定级别、再认结构、先写失效点的可执行研究流程。Use for A-share, HK-stock, ETF, index, or futures analysis with 中枢、分型、笔、线段、背驰、区间套、三类买卖点 and multi-level recursion, or for converting Chan theory into reproducible backtest rules. Research and study only; never issue stock tips or promise returns.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when the user explicitly invokes /longgraph or names this skill. Routes and authors a durable longgraph run. Do not use unless named. Do not execute or resume generated runtime node files.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when the user explicitly invokes /loop-converge or names this skill. Authors a loop-converge run. Do not use unless named. Do not execute or resume generated runtime node files.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when the user explicitly invokes /loop-deliver or names this skill. Authors a loop-deliver run. Do not use unless named. Do not execute or resume generated runtime node files.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when the user explicitly invokes /loop-graph or names this skill. Compiles a custom loop-graph run. Do not use unless named. Existing runtime nodes are self-contained.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when the user explicitly invokes /loop-research or names this skill. Authors a loop-research run. Do not use unless named. Do not execute or resume generated runtime node files.
日本語の概要は準備中です。原文の説明を表示しています。
GitLab CI migration to GitHub Actions — syntax mappings and the migration report template for Pipelines, includes, Pages, environments, rules/only/except, parallel jobs, GitLab-specific variables. Load with `migration-core` when migrating GitLab CI sources to GitHub Actions.
日本語の概要は準備中です。原文の説明を表示しています。
The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.
日本語の概要は準備中です。原文の説明を表示しています。
Foundation skill for warp-route updates. Reads the current on-chain config of a warp route via `hyperlane warp read`, enumerates every artifact (router, ProxyAdmin, ISM, hook, fee contracts) per chain, classifies each artifact's owner (auto-detects Safe / ICA / EOA; asks the user for everything else — Turnkey, Privy, MPC, custom multisig, timelock, etc.), and persists a per-artifact owner table that downstream update skills consume to know which signing path each batch needs. Read-only — no signing, no on-chain mutations.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate merkle root mismatch alerts between relayer and validators. Use when alerts mention "merkle root mismatch", "checkpoint root does not match canonical root", or when asked to debug relayer merkle tree issues for a chain. This skill only investigates - use /fix-merkle-root-mismatch to apply fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch and decode a pending Safe (multisig) governance batch from the Safe Transaction Service into a chain-tagged transactions JSON file that `/warp-route-check` (or any downstream consumer with the same input shape) ingests. Safe-API integration only — no forks, no replay, no simulation.
日本語の概要は準備中です。原文の説明を表示しています。
Estate Planning & Legacy Protection for the Owens family. Tracks wills, trusts, beneficiary designations, life insurance, survivor benefits, and powers of attorney. Ensures Lindsey and the kids are protected if something happens to Tory. Triggers on: "Estate plan", "Will", "Life insurance", "Beneficiaries", "What happens if", "Legacy", "Survivor benefits", "Power of attorney", "Trust", "Estate check", "Beneficiary audit", "SGLI", "FSGLI", "Dependent education", "Chapter 35". The only estate plan that fails worse than a bad one is no plan at all.
日本語の概要は準備中です。原文の説明を表示しています。
Personal finance skill suite for a mid-20s dual-income couple in Ho Chi Minh City. Covers budgeting, emergency fund building, investments, insurance, tax optimization, goal planning, and couple dynamics — all calibrated to Vietnam's financial ecosystem. Use when the user asks about budgeting, saving, investing, insurance, taxes, or financial goal planning — trigger phrases include "review our budget", "how should we invest", "do we have enough insurance", and "plan for a home purchase". Use even if the user only mentions one financial topic without asking for a full review.
日本語の概要は準備中です。原文の説明を表示しています。
Query the BuildAI PostgreSQL database (read-only). Returns results as JSON for construction project data — projects, RFIs, submittals, budgets, change orders, daily logs, punch lists, insurance, vendors, pay applications.
日本語の概要は準備中です。原文の説明を表示しています。
Route new policy briefing, policy update, regulatory update deck, regulatory change deck, compliance change summary, legal update deck, or legal/product policy presentation requests here before generic AIPPT. Use this whenever the user wants a new policy interpretation deck with timelines, impacts, risks, and recommended actions. Do not use this scene pack for email memos, FAQ-only outputs, compliance copy polishing, or non-deck legal writing.
日本語の概要は準備中です。原文の説明を表示しています。