「actors」の検索結果

Give a coding agent symbol-aware lookup, cross-file rename, and structural edit tools before it starts making brittle text-only changes.

日本語の概要は準備中です。原文の説明を表示しています。

Structures S-1/F-1 prospectus content with business description, risk factors, MD&A, and financial presentation requirements. Use when preparing IPO prospectuses, drafting SEC filings, or structuring offering documents.

日本語の概要は準備中です。原文の説明を表示しています。

Creates debt offering memoranda with credit overview, financial analysis, industry section, and risk factors for investor marketing. Use when preparing debt OMs, writing credit marketing materials, or structuring lender presentations.

日本語の概要は準備中です。原文の説明を表示しています。

Assesses country-level investment risk with political stability, rule of law, corruption indices, and expropriation history analysis. Use when evaluating country risk, assessing political exposure, or scoring sovereign investment environments.

日本語の概要は準備中です。原文の説明を表示しています。

Constructs proprietary factor definitions with signal specification, universe application, and orthogonalization methodology. Use when defining custom factors, creating proprietary signals, or building factor libraries.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates ESG strategy with materiality assessment, stakeholder analysis, and value creation linkage for corporate decision-making. Use when analyzing ESG strategy, assessing material ESG factors, or linking sustainability to value.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates cross-border transaction complexities including tax treaties, currency, regulatory approvals, and cultural factors. Use when structuring international deals, assessing cross-border risk, or navigating multi-jurisdiction closings.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates signal half-life, turnover implications, and capacity constraints for systematic alpha factors. Use when analyzing signal persistence, evaluating factor decay, or estimating strategy capacity.

日本語の概要は準備中です。原文の説明を表示しています。

Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating recurring issues, or to share systemic learnings across teams.

日本語の概要は準備中です。原文の説明を表示しています。

Appraise gemstone value using the four Cs (color, clarity, cut, carat), origin assessment, treatment detection, and market factor analysis. Advisory educational guidance only — not a certified appraisal. Use when understanding factors that determine a gemstone's value, pre-screening stones before a professional appraisal, evaluating whether a seller's asking price is reasonable, learning gemstone grading methodology, or understanding how treatment status affects value.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs. Use this skill when the user provides chart images and requests technical analysis, trend identification, support/resistance levels, scenario planning, or probability assessments based purely on chart data without consideration of news or fundamental factors.

日本語の概要は準備中です。原文の説明を表示しています。

Use when code mixes units, fixed-point precisions, scaling factors, rates, prices, shares, or conversions. Not for type-level unit modeling: use type-driven.

日本語の概要は準備中です。原文の説明を表示しています。

Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly. Not for additive refactors that must preserve the old path.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to simplify, clean, or refine code. Not for new abstractions or whole-codebase refactors.

日本語の概要は準備中です。原文の説明を表示しています。

60-Second Stock Snapshot — fast assessment with signal (BUY/HOLD/SELL/AVOID), key bullish/bearish factors, and key levels. No subagents. Terminal output only. Triggered by "trade quick <TICKER>" or "quick look at <TICKER>".

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to audit, review, or diagnose SEO issues, plan site architecture, or implement schema markup. Use when someone says 'SEO audit', 'technical SEO', 'site architecture', 'schema markup', 'internal linking', 'why isn't my site ranking', 'site health check', 'crawl issues', 'fix my SEO', 'my traffic dropped', 'rankings fell', or 'site not ranking'. Also trigger when someone wants to plan URL structure, design navigation, add structured data, or review any website for search performance. Three modes: Full Audit (comprehensive health check), Architecture (URL structure and internal linking), Schema (JSON-LD structured data). Covers crawlability, indexation, Core Web Vitals, and on-page factors.

日本語の概要は準備中です。原文の説明を表示しています。

Use when writing Swift code for Apple platforms - iOS, macOS, visionOS. Covers Swift 6 concurrency, actors, Sendable, async/await, SwiftUI, MVVM architecture, Metal GPU programming, RealityKit ECS, visionOS scenes, interpolation/animation, advanced collection types, property wrappers, Combine bridging, error handling, testing, and API design patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks about Russian state-sponsored cyber operations or specific actors (APT28/Fancy Bear, Sandworm, Cozy Bear/APT29, Turla, GRU-affiliated hacktivist fronts like CARR/NoName057), wartime ICS/OT campaigns, or pro-RU information operations. Self-updating knowledge cell.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks about North Korean state-sponsored cyber operations or specific DPRK actors (Lazarus, APT38, BlueNoroff, Andariel, Kimsuky, etc.), revenue-generation campaigns, IT-worker schemes, or DPRK targeting of cryptocurrency / supply chain. Self-updating knowledge cell.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks about Chinese state-sponsored cyber operations or specific PRC-aligned actors (APT41, Volt Typhoon, Mustang Panda, APT10, APT31, Salt Typhoon, etc.), MSS/PLA-attributed campaigns, or PRC sector targeting. Self-updating knowledge cell.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need Liberty91 platform intelligence — what actually happened (deduplicated Threat Events with every source, Admiralty reliability/credibility and verification stage), whether an IOC is already known to your account, the canonical threat library (actors, malware, vulnerabilities, clusters, ATT&CK TTPs), alert matches, or which of your customer organizations an occurrence affects — or when you need to push intelligence back: ingesting your own report, generating an intelligence package, or uploading an organization document. Also supplies event provenance fields, when the platform returns them, and Threat Library alias resolution to /source-provenance and /quality-of-information-check. Two-way, first-party integration. Commonly invoked by /ip-investigation and friends, /ioc-enrichment-workflow, /threat-actor-profiling, /campaign-tracking and /vulnerability-intelligence. Reads $LIBERTY91_API_KEY.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Dead code cleanup and consolidation specialist. Removes unused code, duplicates, and refactors for maintainability.

日本語の概要は準備中です。原文の説明を表示しています。

"Apply Bourdieu's field theory to analyze power relations through the interplay of field, capital, and habitus. Use this skill when the user needs to map positions and position-takings within a social field, analyze how different forms of capital (economic, cultural, social, symbolic) structure competition, explain why actors behave as they do within institutional settings, or when they ask 'why do people in this industry act this way', 'who has power and why', or 'how does this field reproduce inequality'.".

日本語の概要は準備中です。原文の説明を表示しています。