1.6천건 · 관련도순
Detect abuse of legitimate Windows binaries (LOLBins) used for living off the land attacks. Monitors process creation, command-line arguments, and parent-child relationships to identify suspicious LOLBin execution patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect bootkits such as BlackLotus and Bootkitty and Secure Boot bypass via DBX and binary checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build an automated pipeline to defang indicators of compromise (URLs, IPs, domains, emails) for safe sharing and distribute them in STIX format through TAXII feeds and threat intelligence platforms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract frames or short clips from videos using ffmpeg.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Philips Hue lights and scenes via the OpenHue CLI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture frames or clips from RTSP/ONVIF cameras.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces a DRAFT product requirements document from the discovery notes, interview summaries, support themes, analytics notes and stakeholder messages the user provides: problem statement, target users, goals with measures as stated, numbered requirements each with a testable acceptance criterion, non-goals, constraints, dependencies and open questions, with every statement tagged evidenced, assumed or UNKNOWN so each assumption is visible for the product owner to confirm. Use when the user asks to "write a PRD", "draft the product requirements", "turn these discovery notes into requirements", "document what this feature needs to do" or "build the requirements doc for this epic". Do not use for supplier-facing requirements in a tender, use rfp-requirements-pack instead; for a technical design decision, use architecture-decision-record; for the change ticket that ships the work, use change-request-pack. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns a schedule extract (milestone list or planning tool export) and the period's status notes into a DRAFT plain-language slip explanation: which milestones and activities slipped and by how many working days, arithmetic shown, why per the notes as verbatim fragments with source and date, what each slip pushes next per the extract, and the decision each slip needs framed as a question with the options the notes propose and the owner the governance documents name, every missing fact marked UNKNOWN. Use when the user asks to "explain the schedule slip", "what slipped this month and why", "write the schedule commentary for the steering pack", "put the delay in plain language for the sponsor" or "what decisions do these slips need". Do not use for the weekly status report, use project-status-tracker instead; for cost variances, use budget-variance-explainer; for one sprint's carry-over, use sprint-review-summary. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck or plan in character as a Chief Business Officer archetype, covering commercial model, partnerships, deal structure, market positioning, strategic fit and opportunity cost, and returns a DRAFT review with a verdict, findings that cite the exact passage, commercial risks and five interrogation questions. Use when the user asks to "run a CBO review", "pressure-test this partnership", "check the deal structure" or "what would a commercial executive say about this". Do not use for pipeline, quota, sales-motion or forecast reviews, use cro-reviewer instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Flags where a P&ID draft raises a process safety question and points to the candidate evidence an engineer would review (HAZOP register, relief study, SIL assessment, isolation philosophy), as questions and quoted passages with UNKNOWN for missing documents, plus safety functions, relief devices and isolation requirements carried over as stated. Never rates, sizes, classifies, resolves or declares protection adequate. Use when the user asks to "write the process safety flags", "produce the process safety section of the P&ID enrichment", "list which protection questions this P&ID raises" or "map the HAZOP and relief study evidence to the draft" after gate G2, once the piping and instrumentation sections exist. Do not use for proposing loops, alarms or trips from the control philosophy, use instrumentation-and-control-enrichment instead; do not use for checking identifiers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proposes the instrumentation and control content a P&ID adds to an accepted PFD process model: instruments drawn carried over as facts, measurement points and control loops the control philosophy requires, tag structure per the project instrument numbering procedure, system interfaces, and alarms, interlocks, trips and fail actions as quoted. Never assigns safety functions, ranges or setpoints. Use when the user asks to "run the instrumentation and control enrichment", "add the instrument section to the P&ID draft", "list the control loops the philosophy requires" or "carry the PFD instruments into the P&ID" after the piping section. Do not use for safety flags, SIL or trip classification, use process-safety-flags instead; do not use to assign tag numbers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
- Research companies, directors, shareholders and ultimate beneficial ownership in official corporate registries, filings and offshore datasets — OpenCorporates, UK Companies House and the PSC register, SEC EDGAR, US Secretary of State registries, EU business registers, GLEIF LEI… Use when asked who owns or controls a company, to find a person's other directorships, or to unpick a group structure
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
- Track aircraft and vessels from public ADS-B and AIS broadcasts using ADS-B Exchange, Flightradar24, FlightAware,… Use when following a tail number or flight, looking up an ICAO 24-bit hex code, registration or callsign, tracing a ship by IMO number or MMSI, checking a flag of convenience or port-call history, finding who owns a private jet or vessel
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Free a membership slot so a Telegram account can join or create a group. Accounts have a hard ceiling on channels plus supergroups, and at the ceiling both creating and joining fail with an error that misleadingly blames the target chat. Finds the least-valuable current memberships, proposes what to leave, and retries the join. Triggers: "/tg-slot", "cannot join the group", "free a telegram slot".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resize and validate App Store screenshots with current asc screenshot-size data and macOS sips. Use when preparing or fixing screenshots for App Store Connect submission.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
validateSearch, search param validation with Zod/Valibot/ArkType adapters, fallback(), search middlewares (retainSearchParams, stripSearchParams), custom serialization (parseSearch, stringifySearch), search param inheritance, loaderDeps for cache keys, reading and writing search params.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Philips Hue lights, scenes, rooms via OpenHue CLI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write ML papers for NeurIPS/ICML/ICLR: design→submit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a brief, script, shot list, or approved reference into asynchronous text-to-video, image-to-video, or reference-driven clips.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn approved video clips, audio, captions, and timing decisions into an ordered, reviewable draft while preserving a reproducible timeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn one approved topic into a curiosity-led 3D educational short with character sheets, ordered keyframes, motion clips, narration, captions, and an auditable assembly plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find useful moments in long-form video, create ranked short clips, reframe them, and generate captions without losing source provenance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from the NASA Systems Modeling Handbook for Systems Engineering (NASA-HDBK-1009A Rev A, 2025). Use for model-based systems engineering (MBSE) wired into NASA's NPR 7123.1 SE processes: the three aspects of MBSE (language / methodology / framework), the NASA SE Engine and its two OOSEM-derived steps (Model Planning, Setting Up the Model), the Modeling Plan as a SEMP subset, the tool-agnostic NASA SE metamodel of elements and relationships across the four SysML pillars (structure / behavior / requirements / parametrics), worked SysML diagrams and tables for stakeholders, requirements, structure and V&V, generating SE work products (ConOps, MOE, MOP, TPM, V&V), the MBSE Grid framework, alternative modeling approaches (PBR, Scenario, System Specification, Verification), and the ConOps model-content template. Scope is bounded to four common technical processes (Stakeholder Expectation Definition, Technical Requirements Definition, Product Verification, Product Validation). Does NOT teach SysML itself, mandate a tool, define NPR 7123.1 processes, cover technical-management processes 10-17, or reproduce the OMG SysML specification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from MIL-HDBK-338B (Electronic Reliability Design Handbook). Use for electronic reliability engineering: R/M/A theory, reliability specification/allocation/prediction, parts management and derating, reliable circuit and fault-tolerant design, environmental and human performance reliability, FMEA/FMECA/FTA/sneak circuit analysis, design reviews and testability, FRACAS, reliability demonstration and growth testing, and systems-level R&M parameters. Covers selected Part 2 design-guidance topics only; skips large annex/part-stress tables. Guidance handbook — not a contractual requirement text. Does not replace MIL-HDBK-217 prediction libraries, service-specific reliability regs, or safety standards (see mil-std-882).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.