1,174 件 ・ 関連度順
概要と使いどころ
Write blameless incident postmortems following Google SRE methodology. Covers timeline reconstruction, root cause analysis (5 Whys), impact assessment, and action items with owners. Use after production incidents, outages, or significant bugs to prevent recurrence.
日本語の概要は準備中です。原文の説明を表示しています。
Identify Open Redirect vulnerabilities where applications route users to arbitrary external URLs based on unvalidated input. Prove maximum impact by chaining Open Redirects with OAuth token theft, SSRF, or Phishing, graduating this typically low-risk finding into a high-severity report.
日本語の概要は準備中です。原文の説明を表示しています。
Detect and exploit Insecure Direct Object Reference (IDOR) vulnerabilities in web applications and APIs. Use this skill when testing for unauthorized access to resources by manipulating object identifiers like user IDs, order numbers, file references, or API endpoints. Covers parameter tampering, UUID prediction, hash manipulation, and chained IDOR attacks for maximum impact in bug bounty programs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when developing plugins, tools, and extensions for OpenCode v1 - plugin contract, crash-prevention rules, ctx/event APIs, subagent lifecycle (abort races, compaction, orphan detection), MCP integration, testing patterns, or publishing to npm
日本語の概要は準備中です。原文の説明を表示しています。
Write effective MCP server instructions for tool compaction support. Use when creating or updating the `instructions` parameter in MaaSProtectedFastMCP server initialization. Helps LLMs understand when to search for tools, workflow patterns, and cross-feature relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Tunes noisy detections by analyzing historical alert data to quantify false-positive sources, recommend allow-list filters and threshold adjustments, and measure precision impact. Activates for requests to tune a detection, reduce false positives, or analyze alert noise and recommend filters.
日本語の概要は準備中です。原文の説明を表示しています。
Hunts for ransomware precursor behavior that precedes encryption — shadow-copy and backup deletion, recovery disabling, security-tool tampering, and mass file modification — so the attack can be stopped before payload detonation. Activates for requests to hunt ransomware precursors, detect shadow-copy deletion, or find pre-encryption recovery sabotage.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes destructive wiper malware by identifying raw-disk and MBR/VBR overwrite primitives, boot-record tampering, mass-deletion and backup-destruction behavior, and distinguishing wipers from ransomware. Activates for requests to analyze a wiper, identify destructive disk-overwrite behavior, or tell a wiper apart from ransomware.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes how a ransomware sample encrypts files: identifying the crypto scheme (symmetric/asymmetric/hybrid), key handling, file targeting and extension/marker changes, shadow-copy deletion, and ransom-note artifacts. Activates for requests to analyze ransomware encryption, assess decryptability, or study ransomware behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a project contains docs/memory/, or when the user asks to remember, retrieve, update, compact, forget, or audit project memory. MemoryCustodian manages local plain-text project memory with minimal context loading.
日本語の概要は準備中です。原文の説明を表示しています。
Compact current session context into a handoff document for seamless continuation in a new session. Use when context window is exhausted, switching machines, handing work to another agent, or ending a long session mid-task.
日本語の概要は準備中です。原文の説明を表示しています。
Inject juice and game feel into gameplay code using the project's chosen middleware. Use when adding screen shake, tweens, particles, audio feedback, haptics, hitstop, or any form of "juice" to gameplay events. Triggers on requests like "add juice", "make this feel better", "add screen shake", "polish this feature", "add feedback to this action", "make the hit feel impactful", "add particles when", "screen shake on damage", "tween this", "add camera shake", "make this snappy", or any game feel, polish, or feedback work. Always reads ProjectConfig.yaml -> feel_tools and docs/GFD.md Feedback Matrix before generating code.
日本語の概要は準備中です。原文の説明を表示しています。
When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.
日本語の概要は準備中です。原文の説明を表示しています。
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
日本語の概要は準備中です。原文の説明を表示しています。
Shape, implement, review, copy-edit, or harden Arcade user interfaces. Use for the website, terminal UI, game HUDs, interaction flows, responsive behavior, accessibility, Geist consistency, and any change affecting what a user sees, understands, chooses, or does. Skip backend-only, telemetry-only, generated-file, and test-only work with no shipped UI impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Equal Opportunity Representative or Officer — running an adverse-impact analysis on hiring or promotion selection rates, conducting an availability analysis to set affirmative action placement goals, evaluating a compensation-equity regression for unexplained pay gaps, or preparing an affirmative action plan (AAP) for an OFCCP audit.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an environmental scientist — scoping or reviewing a Phase I/Phase II environmental site assessment, interpreting soil or groundwater sampling results against regulatory action levels, drafting an environmental impact statement or NEPA scoping document, running a contaminant fate-and-transport screening calc, or assessing ecological risk to a receptor.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Environmental Economist — valuing a non-market environmental good (clean air, a wetland, an endangered species) for a benefit-cost analysis, building a regulatory impact analysis (RIA) for a pollution rule, sizing natural resource damages after a spill or contamination event, or picking a discount rate for a policy with cost and benefit streams decades apart.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Database Architect — choosing a normalization level matched to the actual workload, resolving a CAP theorem tradeoff (consistency vs. availability) for a distributed data store, selecting a sharding/partition key aligned with the dominant query pattern, validating an indexing strategy against real query plans, or deriving RPO/RTO backup and replication requirements from actual business impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Civil Engineer — sizing stormwater detention/drainage systems, checking foundation bearing capacity against a geotechnical report, verifying IBC/ASCE 7 code compliance for site civil work, reviewing construction RFIs against stamped drawings, or evaluating value-engineering changes for safety-margin impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Civil Engineering Technician — running and interpreting a concrete field acceptance test (slump, air content, cylinder breaks against ACI 318 criteria), verifying soil compaction against a Proctor density curve, reconciling a concrete or rebar quantity takeoff against a pay application, or documenting a field condition that deviates from the approved plans for the engineer of record.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Chief Sustainability Officer — evaluating an environmental/social initiative's business case, responding to ESG disclosure or regulatory requirements, assessing greenwashing risk, or prioritizing sustainability investments against their actual impact and cost.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Business Continuity Planner — running a business impact analysis (BIA) to derive recovery time objectives, mapping process dependencies to find single points of failure, evaluating whether current recovery capability meets a process's maximum tolerable downtime, designing or debriefing a tabletop exercise, or building the cost-benefit case for a continuity investment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a licensed Architect — programming a building's spatial/functional requirements against a budget, developing a design concept against a zoning/code envelope, evaluating a fee proposal or scope-creep request, resolving a code-compliance conflict between disciplines, or working through a construction-phase change order's cost and schedule impact.
日本語の概要は準備中です。原文の説明を表示しています。