3,960 件 ・ 関連度順
概要と使いどころ
Use when characterising a malware sample, the user asks "what does this binary do?" / "analyse this hash deeply", or `/hash-investigation` flags a novel sample warranting deeper review. Static + dynamic methodology, behavioural indicators, sandbox interpretation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks about Iranian state-sponsored cyber operations or specific IRGC/MOIS-aligned actors (APT35/Charming Kitten, APT34/OilRig, MuddyWater, Imperial Kitten, etc.), wiper campaigns, front-group hacktivist personas (Handala, Cyber Av3ngers), or anti-Iran operations such as Predatory Sparrow. Self-updating knowledge cell.
日本語の概要は準備中です。原文の説明を表示しています。
Use when needing 100% type-safe, schema-valid data extraction from LLMs. Keywords: structured output, JSON schema, Pydantic, Zod, type-safe, constrained decoding, validation, tool use.
日本語の概要は準備中です。原文の説明を表示しています。
Use when optimizing token usage, KV cache efficiency, or context window management for LLM agents. Keywords: context optimization, KV cache, prompt caching, token budget, semantic pruning, lost-in-the-middle.
日本語の概要は準備中です。原文の説明を表示しています。
Expert quantitative analyst specializing in financial modeling, algorithmic trading, and risk analytics. Masters statistical methods, derivatives pricing, and high-frequency trading with focus on mathematical rigor, performance optimization, and profitable strategy development.
日本語の概要は準備中です。原文の説明を表示しています。
Validates agent definitions against the Antigravity audit rubric.
日本語の概要は準備中です。原文の説明を表示しています。
Build custom AI agents in Claude Code from a user's problem statement. This skill analyzes the user's use case, asks smart clarifying questions, researches the internet for similar agents (GitHub repos, blogs, Claude Code community patterns), and then architects and builds production-ready Claude Code agents — including subagents, skills, hooks, slash commands, MCP integrations, and CLAUDE.md configuration. Use this skill whenever the user wants to create an agent, build an automation workflow, set up a Claude Code subagent, design a multi-agent system, or says things like 'build me an agent for...', 'automate this with Claude Code', 'I want a subagent that...', 'help me create a workflow', 'set up an agent pipeline', or any variation of wanting Claude Code to do something specialized. Also trigger when the user mentions agent architecture, agent SDK, agentic workflows, or task delegation in Claude Code — even if they don't use the word 'agent' explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Manage knowledge graph for autonomous coding. Use when storing relationships, querying connected knowledge, building project understanding, or maintaining semantic memory.
日本語の概要は準備中です。原文の説明を表示しています。
MATLAB R2026a and Simulink workflow for creating, inspecting, modifying, simulating, validating, and exporting .slx models. Use for Simulink, Stateflow, Simscape, model-based design, parameter sweeps, signal logging, requirements, and simulation automation. On this machine, Simulink tasks should be visual-first: open the model in a visible Simulink window before doing substantial automated modeling or simulation so the user can watch the process.
日本語の概要は準備中です。原文の説明を表示しています。
EXPERIMENT MODE: Timeboxed, throwaway code for rapid validation. Bypasses TDD requirements. Code must be quarantined and cannot be merged to main.
日本語の概要は準備中です。原文の説明を表示しています。
Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Audit, recover, and prepare portable handoffs of existing private PFC2D/PFC3D 5.0 asphalt cases, including integrity manifests, path portability, saved-state claims, cheap restore-first validation, and legacy-state quarantine.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply event study methodology to measure abnormal returns and cumulative abnormal returns (CAR) around corporate or market events. Use this skill when the user needs to quantify the market impact of announcements, design event and estimation windows, or when they ask 'did this event affect stock price', 'how do I calculate abnormal returns', or 'what is the market reaction to this announcement'.".
日本語の概要は準備中です。原文の説明を表示しています。
Build accessible UI—semantic HTML, keyboard support, ARIA when needed, WCAG-oriented checks. Use when implementing or reviewing web UI, forms, modals, and design systems.
日本語の概要は準備中です。原文の説明を表示しています。
"Analyze market structures across perfect competition, monopolistic competition, oligopoly, and monopoly to predict firm behavior and market outcomes. Use this skill when the user needs to classify a market's competitive structure, predict pricing behavior, evaluate antitrust implications, or understand why an industry behaves the way it does — even if they say 'why can they charge so much', 'is this market competitive', or 'will prices come down'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Analyze business cycle phases (expansion, peak, contraction, trough) and their implications for business strategy and policy response. Use this skill when the user needs to identify the current economic phase, anticipate cyclical turning points, or adapt business strategy to macroeconomic cycles — even if they say 'are we heading into a recession', 'how should we prepare for a downturn', or 'when will the economy recover'.".
日本語の概要は準備中です。原文の説明を表示しています。
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility. Use when exact v1 design-taste behavior is needed for frontend design work.
日本語の概要は準備中です。原文の説明を表示しています。
Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
日本語の概要は準備中です。原文の説明を表示しています。
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. Use when building landing pages, portfolios, redesigns, or frontend interfaces that need strong visual taste.
日本語の概要は準備中です。原文の説明を表示しています。
"Optimize SQL query performance using EXPLAIN analysis, indexing strategies, and common anti-pattern fixes. Use this skill when the user needs to speed up slow queries, design indexes, fix N+1 problems, or optimize database performance — even if they say 'this query is slow', 'optimize our database', 'which indexes do we need', or 'our dashboard takes 30 seconds to load'.".
日本語の概要は準備中です。原文の説明を表示しています。
Design API and module boundaries with clear contracts, error semantics, pagination, and additive compatibility. Use before implementing REST/GraphQL endpoints, SDKs, or public module APIs.
日本語の概要は準備中です。原文の説明を表示しています。
"Solve the newsvendor problem for single-period ordering decisions under uncertain demand. Use this skill when the user needs to determine optimal order quantity for perishable goods, seasonal products, or one-time purchase decisions — even if they say 'how much to order for this season', 'perishable inventory', or 'single-period ordering'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Calculate Economic Order Quantity to minimize total inventory cost (ordering + holding). Use this skill when the user needs to determine optimal order size, balance ordering frequency against storage costs, or set reorder points — even if they say 'how much to order', 'optimal batch size', or 'inventory cost minimization'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Calculate Value at Risk to estimate maximum portfolio loss at a given confidence level. Use this skill when the user needs to quantify downside risk, set risk limits, or report regulatory risk measures — even if they say 'worst case loss', 'portfolio risk', or 'how much could we lose'.".
日本語の概要は準備中です。原文の説明を表示しています。