4,897 件 ・ 関連度順
概要と使いどころ
Compares two related malware samples to surface what changed between variants using section-level hashing, import-set differences, and fuzzy similarity scoring. Activates for requests to diff two samples, compare malware variants, or measure similarity between two binaries for variant tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Research topic by searching vault and synthesizing findings
日本語の概要は準備中です。原文の説明を表示しています。
Research a topic and save findings to vault
日本語の概要は準備中です。原文の説明を表示しています。
The investigation harness for "why is this slow?" over a Pulp Perfetto trace (.pftrace). Runs the hypothesis→query→drill-down chain-of-evidence loop autonomously and returns a plain-English root cause + evidence + a concrete fix. TRIGGER on "why is my plugin slow to open", "find the slowest frames", "why is the UI stuttering", "why is my plugin using so much CPU", "which DSP node is expensive", "the load meter looks calm but CPU is pinned", or a named `pulp trace gpu-startup|gpu-health|gpu-probe` analysis. Ships Pulp-specific hints for dsp, frame, js, gpu, and cross-platform symptoms.
日本語の概要は準備中です。原文の説明を表示しています。
Maintainer side of an outside contribution — find what has arrived (fork PR, issue, or patches sent out-of-band), adopt it into an in-repo branch with authorship intact, review it against the repo's bar, and ship it through the normal merge path. Use when landing work from someone without write access or without the CI fleet.
日本語の概要は準備中です。原文の説明を表示しています。
Enable a Skia + Dawn GPU build of Pulp (MacGpuWindowHost, Skia Graphite). Covers the prebuilt skia-builder binaries, the headers-only fresh-worktree trap, reusing another checkout's cached libs via SKIA_DIR, FindSkia layouts, verifying PULP_HAS_SKIA / MacGpuWindowHost, and the raster-fallback + GPU-wedge gotchas. Use whenever GPU rendering "doesn't work" or a build silently came up CPU-only.
日本語の概要は準備中です。原文の説明を表示しています。
Update Pulp's pinned Skia, Dawn, and optional V8 prebuilts as one milestone-matched render-toolchain release. Use for requests such as "update Skia/Dawn", "move to chrome/mNNN", "find the matching V8", "update the GPU toolchain", or "use the Skia/Dawn/V8 tuple that goes together". Distinguishes milestone-matched V8 releases from v8-builder's newer weekly LKGR releases, verifies exact upstream provenance and asset hashes, updates every Pulp mirror, and runs the provider-identity/ODR gates.
日本語の概要は準備中です。原文の説明を表示しています。
Finding exoplanets — transit and radial-velocity methods, light-curve vetting, and false-positive rejection.
日本語の概要は準備中です。原文の説明を表示しています。
Organize files so you can find anything: naming conventions, folder structures, archiving, and deduplication. Use when digital clutter slows you down or you're setting up a new system.
日本語の概要は準備中です。原文の説明を表示しています。
Using CMIP6 climate model output — finding data, multi-model means, scenario logic, and bias-aware analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Build a bookmark system you'll actually use: capture, tagging, retrieval, and regular pruning. Use when bookmarks pile up unfindable or you keep losing useful links.
日本語の概要は準備中です。原文の説明を表示しています。
Application performance monitoring — transactions, profiling, and finding slow code — works with any APM platform.
日本語の概要は準備中です。原文の説明を表示しています。
Marketing analytics and data-driven optimization for B2B SaaS campaigns. Use this skill when analyzing marketing performance, optimizing conversion rates, running A/B tests, conducting customer research, creating marketing dashboards, building attribution models, analyzing funnel metrics, or storytelling with data. Also triggers on: marketing ops, performance analytics, CRO, A/B testing, data storytelling, customer insights, tracking plan, event taxonomy, UTM taxonomy, GA4 audit, consent mode, instrumentation contract, sample size calculation, minimum detectable effect, test duration, not enough traffic to A/B test, statistical significance, Bayesian vs frequentist, sample ratio mismatch, experiment feasibility, martech stack, marketing tech stack audit, tool consolidation, build vs buy, vendor evaluation, shadow IT tools, ESP/CRM/platform migration, switching cost, cutover plan, suppression list migration, data portability, customer interviews, survey design, sampling frame, non-response bias, how many people should I interview, thematic saturation, voice of customer, jobs-to-be-done, buyer persona research, is this finding real, data enrichment, which enrichment provider should we buy, waterfall enrichment, contact data quality, match rate, our list data is bad, email verification, catch-all domain, accept-all, bounce rate from bad data, B2B data decay, how often should we re-verify contacts, ZoomInfo vs Apollo vs Clearbit evaluation, cost per usable record, where did this list come from, GDPR Article 14 notice, purchased list compliance, suppression screening, TAM list building, demand planning, marketing plan, how many leads do we need, what pipeline target should marketing carry, funnel model, top-down vs bottom-up plan, plan of record, annual marketing planning, quarterly planning, pipeline coverage we have to create, sales cycle lag, our leads cannot close this quarter, carry-in pipeline, scenario planning, conservative moderate aggressive forecast, stretch target, reforecast, re-forecast triggers, assumption register, capacity ceiling, addressable audience ceiling, marginal cost per lead, blended CPL is wrong, we missed plan and nobody knows why, AI policy for the marketing team, AI governance, AI acceptable use policy, which AI tools are we allowed to use, can I paste customer data into ChatGPT, shadow AI, AI use register, human review of AI output, when can we stop reviewing every AI draft, can the agent send on its own, the AI made a mistake now what, pull back AI autonomy, AI evals, our AI vendor changed the model, AI output went out wrong, prompt injection, can our AI read prospect replies safely, lethal trifecta, the AI leaked internal notes, turn off auto-generated ad assets, auto-applied recommendations, AI literacy training, EU AI Act Article 4, duplicate records in the CRM, dedupe before import, which value wins in a merge, CRM cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.
日本語の概要は準備中です。原文の説明を表示しています。
Search the asset database using the search filter string. Allows you to search for Assets. The string argument can provide names, labels or types (classnames).
日本語の概要は準備中です。原文の説明を表示しています。
Create new material asset with default parameters. Creates folders recursively if they do not exist. Provide proper 'shaderName' - use 'assets-shader-list-all' tool to find available shaders.
日本語の概要は準備中です。原文の説明を表示しています。
Search the built-in assets of the Unity Editor located in the built-in resources: Resources/unity_builtin_extra. Doesn't support GUIDs since built-in assets do not have them.
日本語の概要は準備中です。原文の説明を表示しています。
Unity 6 AI and navigation guide. Use when working with NavMesh, pathfinding, NavMeshAgent, NavMeshSurface, NavMeshObstacle, off-mesh links, or Unity Sentis (ML model inference). Covers AI navigation package, runtime NavMesh baking, and common AI patterns like state machines and behavior trees. Based on Unity 6.3 LTS documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Unity NavMesh pathfinding patterns, safety checks, and performance optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Use when diagnosing or improving frontend performance, Core Web Vitals, bundle size, runtime rendering cost, network waterfalls, memory leaks, long tasks, Lighthouse findings, or performance budgets; Chinese triggers include performance optimization, page freeze, slow first screen, bundle volume, Web Vitals.
日本語の概要は準備中です。原文の説明を表示しています。
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Endoscopy Technician — deciding whether to release or quarantine a scope after a failed leak test or minimum-effective-concentration (MEC) reading, handling a point-of-use treatment delay against the manufacturer's reprocessing window, triaging a borescope finding on a working channel, or troubleshooting equipment and passing accessories during a live GI procedure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an electrician's helper — running the NEC box-fill or conduit-fill calculation for a rough-in before wire gets pulled, bending conduit and pulling wire without exceeding practical bend/tension limits, running a non-contact continuity or polarity check at trim-out, or recognizing when a jobsite finding (reversed polarity, an undersized box, an unlabeled abandoned circuit) is a stop rather than a workaround.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Energy Auditor — running a blower-door/duct-leakage diagnostic sequence on a home or light-commercial building, testing combustion appliances for worst-case backdraft risk before recommending air sealing, reconciling utility billing history against walkthrough findings, ranking retrofit measures by savings-to-investment ratio (SIR) for a weatherization or utility rebate program, or writing the prioritized scope of work an install crew executes without the auditor on site. Distinct from an energy-engineer (industrial/commercial capital planning, IPMVP measurement and verification, calibrated simulation) — this role owns the field diagnostics and the residential/light-commercial audit-to-scope handoff.
日本語の概要は準備中です。原文の説明を表示しています。