「find」の検索結果

AiZynthFinder retrosynthetic route planning (CASP) from AstraZeneca Molecular AI. Monte Carlo tree search guided by a template-based neural expansion policy recursively disconnects a target SMILES until precursors are found in a purchasable stock. Covers config.yml (v4 format), aizynthcli batch screening, the AiZynthFinder/AiZynthExpander Python API, one-step disconnections, custom stocks via smiles2stock, scorers, Retro*/breadth-first/DFPN search alternatives, and reading output.json.gz / trees.json. Use for synthesis route planning, synthesizability screening, and building-block/precursor search. For reaction barriers use neb-irc-activation-energy; for 2D reaction scheme drawing use rdkit-chemdraw-cdxml.

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

Find and rank influencers by niche, engagement, and authenticity using Xpoz. Searches Twitter, Instagram, and Reddit for active voices in any topic. Use when asked to "find influencers", "discover thought leaders", "who's talking about X", "influencer research", or "find KOLs".

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

Manage files and folders on the Unique AI Platform using the unique-cli command-line tool. Use when the user asks to upload, download, delete, rename, list, find, restore versions, list versions, look for, or organize files and folders on Unique, or to read / view / quote the text contents of a known file (optionally by page or page range, e.g. "what's on page 5?", "read pages 10-12"), or when working with scope IDs (scope_*) or content IDs (cont_*). IMPORTANT: When a user says they are "looking for a file" or wants to "find a file", they typically mean locating it within the Unique AI Platform knowledge base — not on the local filesystem. Use this skill to browse and list folders/files on Unique to help them find it. This is also the preferred approach for locating Excel (.xlsx/.xls), CSV (.csv), and image files, as these file types are not full-text indexed and cannot be found via vector/full-text search.

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

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

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

How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and emit findings into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the findings it emitted, and assessing a scout's health and performance over time (cadence, success rate, emit rate, signal-to-noise). Read-only and exploratory — to write or tune a scout, use `authoring-signals-scouts` instead. Trigger on "what are my scouts doing", "how is my <x> scout performing", "show me recent scout runs", "why did this scout find/emit nothing", "what has the fleet learned", "explore scout run <id>", "is my scout working".

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

Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching. Use when the user asks which sessions or replays to watch, wants help finding interesting / useful recordings, says they don't know where to start in session replay, or wants to watch sessions about a goal (signup, pricing, onboarding, checkout, a feature, rageclicks, errors, mobile, a specific person) without naming exact filters. Turns a vague intent into a focused RecordingsQuery via `query-session-recordings-list`, then deep-links the best few and hands off to `investigating-replay`. Do NOT use when the user already has a recording/session ID (use investigating-replay) or wants the replay for a known error issue (use finding-replay-for-issue).

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

メモリディレクトリの過去タスク・issue をキーワードや変更対象ファイルのパスで検索し、関連する作業履歴を表示する。/findmem 実行時、Phase 1.0 の過去タスク・issue 参照時、編集予定のファイルに既知の指摘が無いか確認する時に使用。

Adversarial triage of open review findings on a PR. Every finding (Codex, Claude bot, Gemini) is a hostile hypothesis to REFUTE — fix only what is proven real, reachable, in the PR's scope, and above the round's severity bar. The bar rises every review round. Everything else is declined or filed as an issue. Use for 'fix the PR findings', '/fix', '/fix 123', or before any fix commit in a review loop.

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

Find the right skill for a capability. Load when a user or skill needs to check if a skill exists for a given task, when process-decomposer assigns skills to steps, or when agent-builder checks skill availability. Triggers on "what skill does this need", "find a skill for", "is there a skill that", "which skill handles", "does a skill exist for", "skill lookup", "check skill library". Prevents skill sprawl by always checking existing skills before creating new ones. The gatekeeper for all skill creation.

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

Research a skill domain before building or improving a skill. Searches academic papers, practitioner blogs, and GitHub skill repos in parallel to find current best practices, domain gotchas, and existing skill patterns. Called by universal-skill-creator and improve-skills before writing any skill. Also load directly when the user asks to research a domain for a skill, find existing skills on a topic, discover best practices for a skill, check what research exists before building an agent skill, or says "what does current research say about", "find best practices for".

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

Apply validated research paper insights to the current project codebase — improving architecture, code patterns, testing strategies, documentation, or workflows based on empirical findings. Load when learn-from-paper routes insights to the current project, or when the user asks to apply paper findings to this project, improve this codebase with research, use this paper to improve my project, or apply research to my code. Also triggers on "apply this to my project", "how can this paper help my codebase", "use these findings here", "implement paper recommendations", "use research to improve my code". Always called AFTER learn-from-paper has completed credibility and security checks — never ingests papers directly.

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

Find and identify the CDecoyProjectile_Create factory in CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the decoy projectile spawn factory. It is a non-virtual, direct-call static factory found via the entity classname string "decoy_projectile" it references (excluding the RTTI class string "CDecoyProjectile"). Emits a unique IDA-style byte signature and a func YAML. Mirrors the find-CDecoyProjectile_Create.py preprocessor (xref_strings FULLMATCH:decoy_projectile). Trigger: CDecoyProjectile_Create, CDecoyProjectile::Create, decoy projectile Create

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

Find and identify the CCSPlayerPawn_SnapEyeAngles function in CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the non-virtual SnapEyeAngles method. It is the one caller of the shared apply helper (CCSPlayerPawn_ApplyEyeAngleNetworkChange) that is NOT CCSPlayerPawn_SnapViewAngles. Emits a unique IDA-style byte signature and a func YAML. Mirrors the find-CCSPlayerPawn_SnapEyeAngles.py preprocessor (xref_funcs apply-helper, exclude_funcs SnapViewAngles). Trigger: CCSPlayerPawn_SnapEyeAngles, SnapEyeAngles

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

Find and identify the CCSGameRules_PostCleanUp function in CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the post-round entity-cleanup routine. It is non-virtual and has no unique string of its own, so it is found via the CCSGameRules_ResetRound predecessor: PostCleanUp is the entity-cleanup call ResetRound makes. Emits a unique IDA-style byte signature and a func YAML. Mirrors the find-CCSGameRules_PostCleanUp.py preprocessor (LLM_DECOMPILE CCSGameRules_ResetRound). Trigger: CCSGameRules_PostCleanUp, PostCleanUp, CGameRules::PostCleanUp

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

Find and identify the CCSGameRules::TerminateRound function in the CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the round-end-processing function by finding the code that references both the bare "TerminateRound" debug tag string and the "TerminateRound: unknown round end ID %i\n" warning-format string — both are referenced from the same function. Trigger: CCSGameRules_TerminateRound

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

Find and identify the CCSNavArea_IsValidNavMesh function in CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the nav-mesh validity predicate. It is a tiny non-virtual-looking helper that returns `g_pNavMesh != nullptr` (15 bytes), referenced only from a vtable slot, with no debug string of its own. Emits a unique IDA-style byte signature and a func YAML. Mirrors the find-CCSNavArea_IsValidNavMesh.py preprocessor (xref_gvs g_pNavMesh intersected with the tail signature `48 83 38 ? 0F 95 C0 C3`). Trigger: CCSNavArea_IsValidNavMesh, IsValidNavMesh, g_pNavMesh predicate

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

Find and identify the CBaseTrigger::StartTouch and CBaseTrigger::EndTouch overridden virtual functions in the CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering server.dll or libserver.so to locate the trigger-volume touch-list add/remove handlers by RTTI-walking CBaseTrigger's and CBaseEntity's primary vtables and diffing them slot-by-slot to find CBaseTrigger's overrides, then identifying which two overridden slots implement "add pOther to the touching-entities list" (StartTouch) versus "remove pOther from the touching-entities list" (EndTouch). Trigger: CBaseTrigger_StartTouch, CBaseTrigger_EndTouch

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

Find and identify the CBaseEntity::TakeDamageOld function in the CS2 server binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the legacy damage-application entry point by finding the code that references its self-identifying assert/warning message "CBaseEntity::TakeDamageOld: damagetype %d with info.GetDamageForce() == Vector::vZero". Trigger: CBaseEntity_TakeDamageOld

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

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

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

This skill detects and analyzes arbitrage opportunities across cryptocurrency exchanges and DeFi protocols. It aggregates prices from multiple sources Detect profitable arbitrage opportunities across CEX, DEX, and cross-chain markets in real-time. Use when scanning for price spreads, finding arbitrage paths, comparing exchange prices, or analyzing triangular arbitrage opportunities. Trigger with phrases like "find arbitrage", "scan for arb", "price spread", "exchange arbitrage", "triangular arb", "DEX price difference", or "cross-exchange opportunity".

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

Track Apple devices/AirTags via FindMy.app on macOS.

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

Cross-cutting methodology for the CVE-hunting pipeline (ported from find-cve-agent): when a bug is design-vs-real, false-positive avoidance, version checking before reporting, responsible disclosure norms, acceptance-rate expectations per vuln class, vulnerability chaining playbook, known false-positive patterns, maintainer-response patterns, secure-pattern reference (what NOT to flag), and a self-criticism checklist to run before claiming a finding. Use this alongside the cve-hunter/cve-exploiter/cve-validator agents and the /cve-hunt pipeline — load it whenever judging if a finding is real, worth reporting, or already fixed.

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

Discover and list all URLs on a website, with optional search filtering. Use this skill when the user wants to find a specific page on a large site, list all URLs, see the site structure, find where something is on a domain, or says "map the site", "find the URL for", "what pages are on", or "list all pages". Essential when the user knows which site but not which exact page.

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

Discover and list all URLs on a website without extracting content, via the Tavily CLI. Use this skill when the user wants to find a specific page on a large site, list all URLs, see the site structure, find where something is on a domain, or says "map the site", "find the URL for", "what pages are on", "list all pages", or "site structure". Faster than crawling — returns URLs only. Essential when you know the site but not the exact page. Combine with extract for targeted content retrieval.

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