1,182 件 ・ 関連度順
概要と使いどころ
Create original short videos using the 速度对蛮力的非对称证明｜重击承诺、连续闪避与环境撞击 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication. Use when defining production reliability, preparing launch readiness, responding to an outage, writing a runbook, tuning alerts, or closing the loop after an incident.
日本語の概要は準備中です。原文の説明を表示しています。
Guard long, ambiguous, or stateful AI-agent work from drift. Use when the user asks to run or continue a multi-step task, autonomous loop, bug fix, repo change, PR readiness check, compaction handoff, resume from previous context, cost-control checkpoint, or any task likely to span many tool calls, files, sessions, agents, or verification gates.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch upcoming economic events and data releases using FMP API. Retrieve scheduled central bank decisions, employment reports, inflation data, GDP releases, and other market-moving economic indicators for specified date ranges (default: next 7 days). Output chronological markdown reports with impact assessment.
日本語の概要は準備中です。原文の説明を表示しています。
This skill retrieves upcoming earnings announcements for US stocks using the Financial Modeling Prep (FMP) API. Use this when the user requests earnings calendar data, wants to know which companies are reporting earnings in the upcoming week, or needs a weekly earnings review. The skill focuses on mid-cap and above companies (over $2B market cap) that have significant market impact, organizing the data by date and timing in a clean markdown table format. Supports multiple environments (CLI, Desktop, Web) with flexible API key management.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive China A-share stock analysis covering fundamental analysis, technical analysis, policy impact assessment, and market-specific features (T+1 trading, price limits, northbound capital flow). Use when user asks about A股分析, Chinese mainland stocks, Shanghai/Shenzhen listed stocks, or needs analysis considering China market characteristics.
日本語の概要は準備中です。原文の説明を表示しています。
Develop art direction for image generation with curated style cards distilled from Open Image Prompts. Use when choosing or comparing visual directions, improving an existing generation prompt, or translating a subject, use case, or supplied image into a compact creative spec. Use img-gen-prompts for real archive examples, exact source prompts, or gallery browsing.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the reasoning, frameworks, and mental models of Fei-Fei Li, computer vision pioneer, ImageNet creator, and co-director of Stanford HAI. Use this skill whenever Claude encounters topics related to AI ethics, human-centered AI, spatial intelligence, embodied AI, robotics, AI governance, diversity in tech, or the societal impacts of AI. Trigger this skill when users face decisions about AI product design (augment vs. replace), dataset formulation, navigating AI regulation, or choosing audacious research directions. Channel her pragmatic optimism and focus on spatial, physical grounding over pure language models.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the reasoning of Stuart Russell, AI safety expert, UC Berkeley professor, and co-author of 'Artificial Intelligence: A Modern Approach'. Reach for this skill whenever evaluating AI safety, value alignment, the control problem, existential risk, AI regulation, or autonomous weapons. Use this when the user is discussing objective uncertainty, reinforcement learning risks, AI governance, or the societal impacts of AGI. Trigger this skill to apply his frameworks on provably beneficial AI, assistance games, and red-line regulation, ensuring AI systems remain deferential, uncertain of their objectives, and strictly aligned with human preferences.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the reasoning style of Geoffrey Hinton, deep learning pioneer and 2018 Turing Award winner. Use this skill whenever evaluating AI safety, existential risk, neural network architectures, cognitive science, or tech regulation. Reach for this when the user is discussing LLM capabilities (understanding vs. autocomplete), the biological vs. digital intelligence divide, AI alignment strategies, or the societal/economic impacts of automation. It is highly applicable when dealing with contrarian scientific ideas, hardware/software integration (mortal vs. immortal computing), or global cooperation on technological threats. Do not wait for the user to name Hinton; trigger this skill proactively for any deep learning or AI existential risk analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and tests before final verification.
日本語の概要は準備中です。原文の説明を表示しています。
Assess an openai-guardrails-python GitHub issue or pull request as a maintainer. Use to verify the claimed need and practical impact, compare supported alternatives or competing approaches, separate code quality from repository readiness, recommend the maintainer action, and draft a copy-ready comment when evidence, changes, or closure should be requested.
日本語の概要は準備中です。原文の説明を表示しています。
Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-guardrails-python after runtime, tests, examples, build/test configuration, or behavior-impacting docs change.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze Chinese notes, articles, manuscripts, and digital card-box material with FIRE 2.0: Full-D numbering, Index keyword webs, Route thinking paths, and Evolution over time. Use when Codex needs to prepare material for semantic search, turn temporary notes into permanent or project notes, build table-of-contents/index/search structures, create compact Chinese FIRE cards, or maintain this skill's original discussion thread provenance.
日本語の概要は準備中です。原文の説明を表示しています。
Updates Python test code to work with new versions of the code being tested. Use when Claude needs to: (1) Update tests after code changes, (2) Fix broken tests due to signature changes, (3) Update assertions to match new behavior, (4) Add test cases for new functionality, (5) Analyze code differences and their test impact, (6) Run tests and fix failures based on error messages. Takes old code, new code, and old tests as input, outputs updated tests that pass.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes a repository and its test suite to generate customized mutation operators tailored to the project. Use this skill when setting up mutation testing, improving test quality, or generating project-specific mutants. Considers language constructs, business logic patterns, API calls, data types, and code complexity to produce effective mutation operators that maximize test sensitivity while avoiding trivial or equivalent mutations. Generates prioritized operator sets (high/medium/low value) with impact summaries. Triggers when users ask to generate mutation operators, customize mutation testing, analyze code for mutation opportunities, or create project-specific mutants.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze differences in program intervals between two versions of a program (old and new) to identify added, removed, or modified intervals. Use when comparing program versions, analyzing variable ranges, detecting behavioral changes in numeric computations, validating refactorings, or assessing migration impacts. Supports optional test suite integration to validate interval changes. Generates comprehensive reports highlighting intervals requiring further testing or verification.
日本語の概要は準備中です。原文の説明を表示しています。
Explain why counterexamples violate specifications by analyzing formal specifications (temporal logic, invariants, pre/postconditions, code contracts), informal requirements (user stories, acceptance criteria), test specifications (assertions, property-based tests), and providing step-by-step traces showing state changes, comparing expected vs actual behavior, identifying root causes, and assessing violation impact. Use when debugging test failures, understanding model checker output, explaining runtime assertion violations, analyzing static analysis warnings, or teaching specification concepts. Produces structured markdown explanations with traces, comparisons, state diagrams, and cause chains. Triggers when users ask why something failed, explain a violation, understand a counterexample, debug a specification, or analyze why a test fails.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies and analyzes conflicts in software requirements including logical contradictions, technical incompatibilities, resource constraints, timeline issues, data conflicts, and stakeholder priority mismatches. Use when reviewing requirement sets, specifications, user stories, or project plans to detect conflicts that could block implementation or cause rework. Provides detailed conflict analysis with resolution strategies and impact assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze CVE reachability in software repositories by examining how vulnerable dependencies are imported and used. Determines whether vulnerable components, classes, or functions are reachable from project code through call chain analysis, reflection detection, dynamic loading patterns, and configuration-gated behavior. Classifies each CVE as likely reachable, possibly reachable, or likely unreachable with supporting evidence. Use when analyzing security vulnerabilities in dependencies, performing post-disclosure CVE triage, assessing vulnerability impact, or when users ask to analyze CVE reachability, check if vulnerabilities are exploitable, or evaluate dependency security risks.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
日本語の概要は準備中です。原文の説明を表示しています。
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.
日本語の概要は準備中です。原文の説明を表示しています。
Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.
日本語の概要は準備中です。原文の説明を表示しています。
Security audit of a codebase — web apps, APIs, services, CLI tools, libraries, daemons, and more. Use when asked to find security bugs, do a security review, audit for vulnerabilities, or pen-test the code. Focuses on exploitable issues with real impact, not theoretical concerns or industry-standard behavior.
日本語の概要は準備中です。原文の説明を表示しています。