「threat」の検索結果

Analyze indicators of compromise — enrichment, attribution, and response recommendations. Use when asked to "analyze these IOCs", "enrich these indicators", or "what is this hash".

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

Design detection rules for a threat — SIEM queries, alert logic, and MITRE ATT&CK mapping. Use when asked to "write a detection rule", "how do we detect this attack", or "build a SIEM query for this TTP".

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

Pragmatics and communicative competence across languages -- speech acts (Austin/Searle), Grice's conversational maxims and implicature, politeness theory (Brown & Levinson), face-threatening acts, discourse structure, turn-taking, repair strategies, register and formality, cross-cultural communication, communicative strategies (circumlocution, approximation, appeal for assistance), and the gap between grammatical competence and communicative performance. Use when teaching communication skills, analyzing cross-cultural misunderstandings, building conversational fluency, or understanding why grammatically correct sentences can be pragmatically inappropriate.

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

Entrepreneurship, innovation, and disruption for starting, scaling, and defending new ventures. Covers opportunity recognition, jobs-to-be-done, the disruptive innovation framework, sustaining vs disruptive innovation, platform businesses, network effects, minimum viable product, customer development, and the startup lifecycle from idea to exit. Use when evaluating a venture idea, positioning a new product, interpreting a competitive threat, or designing a platform.

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

Analyze code changes for security vulnerabilities using LLM reasoning and threat model patterns. Use for PR reviews, pre-commit checks, or branch comparisons.

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

Reviews an existing conjoint study for threats to inference and returns severity-ranked findings on design, estimation, measurement error, external validity, and interpretation. Use when checking whether a conjoint design or analysis holds up, or answering referee comments on one.

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

Reviews an existing conjoint study for threats to inference and returns severity-ranked findings on design integrity, estimation, measurement error, external validity, and interpretation, including the guardrail against reading an AMCE as majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation or interpretation. New designs go to conjoint-design, reshaping to conjoint-cleaning.

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

Run deep research on a single competitor. Produces a dossier with executive summary, position + messaging, status-quo alternatives, key differentiators, pricing position, where-they-win / where-they-lose, threat assessment, and what to watch. Writes to marketing/competitors/MMYY-{competitor-slug}.md. Triggers - "competitor research", "competitive analysis", "research competitor X", "battlecard prep", "analyze [competitor name]

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

Audit AuthCrunch security boundaries, triage vulnerability reports and scanner findings, reproduce authentication or authorization failures, and prepare evidence-backed remediation. Covers trust, credentials, redirects, concurrency, diagnostic logging, and dependency exposure.

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

威胁建模时使用。适用于新功能 / 新系统的安全设计评审。融合 STRIDE + Attack Tree + Microsoft SDL。

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

Use for security and trust boundaries. Triggers: auth, secrets, XSS, CSRF, SQL injection, JWT, OAuth, OWASP, PII, uploads, payments, supply chain, CI integrity, agent security, threat model.

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

Maps competitive dynamics with market positioning, feature comparison, funding histories, and differentiation assessment. Use when analyzing startup competition, mapping market landscapes, or identifying competitive threats.

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

Security architecture and threat modeling. OWASP Top 10 2025 analysis, OWASP Agentic AI Top 10 (ASI01-ASI10), AI/LLM security patterns, supply chain security, modern API authentication (OAuth 2.1, DPoP, Passkeys/WebAuthn), vulnerability assessment, and security review for code and infrastructure.

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

Build a mental and visual map of the target application before hunting — entry points, trust boundaries, data flows, and high-value functionality. Use when user has scope parsed and wants to plan WHERE to hunt rather than diving into recon.

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

AI pressure redirection — handling conflicting demands, tool failures, and competing constraints by blending with incoming force then reframing. Use when receiving contradictory instructions from different sources, during tool failure cascades where the planned approach becomes unviable, when scope pressure threatens to expand the task beyond what was asked, or when user frustration or correction needs to be absorbed rather than deflected.

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

Cultivate defensive situational awareness, threat assessment, and mental clarity under pressure. Covers the Cooper color code awareness system, body language reading and intent detection, verbal de-escalation, moving mindfulness in public spaces, combat focus and the OODA loop, rapid grounding techniques for acute stress, context-specific integration, and ongoing review and refinement of awareness skills. Use when entering unfamiliar or potentially hostile environments, needing to assess a situation for safety, de-escalating a verbal confrontation, or integrating awareness practice into daily movement.

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

Use when the user asks about CTI standard operating procedures (daily triage, IOC processing, flash-report cadence, threat-actor profile updates, briefing schedule), or wants to look up a specific SOP.

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

Use when the user asks to write a threat / risk / vulnerability assessment, or wants the appropriate template for each type. Distinct structures and section ordering per assessment kind. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Confidence is capped by the weakest load-bearing claim, and at Moderate when the evidence is ungraded.

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

STIX 2.1 bundle creation reference. Object types, relationships, and JSON templates for structured threat intelligence sharing. Includes the per-claim mapping of evidence grades (access level and claim support) from /quality-of-information-check to STIX confidence, and the reverse mapping on import.

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

Use when the user asks about supply-chain attacks, third-party / vendor compromise (SolarWinds, Kaseya, 3CX, MOVEit, XZ-utils-style), software-bill-of-materials risks, or library / dependency-injection attacks. Self-updating knowledge cell.

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

Use when you need to know where a piece of reporting actually came from — the user gives an article URL and asks "where does this come from?", "who is the original source?", "is this just a rewrite?", or another skill needs the provenance chain before grading or citing a report. Follows an article's links and named attributions back to the originating vendor, government, victim or actor document and returns the chain, the primary's stated access and confidence language, publication dates, and every hop it could not resolve. Deterministic — a script or the Liberty91 platform resolves the chain; the model does not reconstruct it from memory. Invoked by /quality-of-information-check, /threat-actor-profiling, /campaign-tracking and /intelligence-writing. Works on any URL with no API key.

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

Use when evidence needs grading before anyone reasons from it — the user asks "how reliable is this?", "grade this source", "check this report", "can I trust this article?", "is this corroborated?", or hands over a URL, a pasted report or a Liberty91 event ahead of an ACH or assessment. The Quality of Information Check from the CIA Tradecraft Primer, adapted for vendor and press CTI reporting. Resolves each document to its originating source, splits it into claims, and grades every claim on two written elements, access level (how the source knows) and claim support (what backs the statement), with a stated rationale, using a fixed rubric with hard caps. The grade is not an Admiralty rating. Five outlets citing one vendor report count as one source; anything that cannot be traced to a primary is capped, not guessed. Returns a graded claim table, gaps, a deception screen and JSON. /ach, /threat-assessment and /writing-assessments run it first by default.

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

AlienVault OTX API reference. Community threat intelligence pulses and indicator lookups.

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

Use when you need to check an IP, domain, file hash, or URL against VirusTotal's reputation database. Returns detection ratio, verdict, community score, and key findings. Commonly invoked by investigation skills (/ip-investigation, /domain-investigation, /hash-investigation, /url-investigation) and by analysts enriching IOCs. Other agents/skills can chain this for VirusTotal enrichment.

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