「bli」の検索結果

Use when a task needs the judgment of a Bioinformatics Scientist — designing a differential-expression or GWAS analysis with correct multiple-testing correction, calling and triaging variants from NGS data using genotype-likelihood confidence rather than raw allele counts, interpreting a BLAST/DIAMOND homology search, choosing or building a genomics pipeline (aligner, caller, normalization method) for a specific data-generating process, or judging whether a computational-biology analysis's statistical design actually supports the biological claim being made. Distinct from a bioinformatics-technician (executes and QC-gates an established pipeline someone else designed) and a data-scientist (general product/experimentation judgment, not genomics-specific statistics) — this role owns which method and statistical model a genomics question requires, and why.

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

Use when a task needs the judgment of a professional author — drafting or structurally revising a novel or narrative-nonfiction manuscript, writing a query letter or book proposal, evaluating a publishing contract's royalty and rights terms, or diagnosing why a manuscript is getting rejected.

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

Use when a task needs the judgment of a Postsecondary Art, Drama, or Music Professor — diagnosing a jury/crit score that contradicts a semester of formative work, building a studio-art or performance tenure dossier around exhibitions and productions instead of publications, staffing applied one-on-one lessons or crit sections between adjuncts and full-time faculty, running a structured critique, or deciding whether a failed barrier jury means a change of major.

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

Use when a task needs the judgment of an Advertising Sales Agent — pricing an ad-inventory package against a client budget, building a media-kit pitch, protecting yield on scarce inventory while moving remnant, or forecasting close rate on a sales pipeline. Sell-side: this role sells a publisher's or station's own ad space/time to advertisers, the opposite side of the table from a buyer-side advertising-promotions-manager who purchases media on a client's behalf.

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

Use when a task needs the judgment of an Application Security Engineer — checking whether an endpoint verifies object-level authorization (not just authentication), running threat modeling at design time rather than deferring security review to the end, triaging a dependency vulnerability by actual reachability rather than CVSS score alone, combining SAST/DAST/SCA tooling to cover their distinct blind spots, or applying context-specific output encoding to untrusted input. Distinct from an information security analyst — this role works inside the SDLC to prevent vulnerabilities before they ship, not detect and respond to intrusions in production.

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

Use when a task needs the judgment of an animal trainer — designing a behavior-modification plan for a specific problem behavior, choosing a reinforcement schedule and deciding when to raise criteria, structuring session length and frequency to avoid fatigue or frustration plateaus, or setting a handler/public safety protocol around a training animal.

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

Track ENCODE experiments locally with publications, citations, and provenance. Use when the user wants to build a collection of experiments, manage citations, compare experiments, or track data provenance.

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

Cross-reference ENCODE data with PubMed, bioRxiv, ClinicalTrials.gov, Open Targets, GTEx, ClinVar, GWAS Catalog, gnomAD, Ensembl, and other scientific databases. Use when the user wants to find publications, preprints, or clinical trials related to ENCODE experiments, chain ENCODE data with other scientific MCP servers, or build translational pipelines from genomic data to clinical application.

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

Spring Modulith 2.0 implementation for bounded contexts in Spring Boot 4. Use when structuring application modules, implementing @ApplicationModuleListener for event-driven communication, testing with Scenario API, enforcing module boundaries, externalizing events to Kafka/AMQP, building a modular monolith, defining module dependencies, managing inter-module events, or organizing DDD modules as packages. Covers package-based module boundaries, named interfaces, event publication, and Scenario API testing. For architecture decisions, see domain-driven-design skill.

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

Validate skills against Anthropic best practices for frontmatter, structure, content, file organization, hooks, MCP, and security (62 rules in 8 categories). Use when creating new skills, updating existing skills, before publishing skills, reviewing skill quality, or when user mentions "validate skill", "check skill", "skill best practices", "skill review", or "lint skill".

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

Use when starting any conversation - establishes how arkhe skills bootstrap on Claude Code, Antigravity CLI (agy) / Gemini CLI, and Codex CLI, and maps Claude-only tools (AskUserQuestion, TaskCreate, EnterPlanMode, the Skill tool, the Agent tool) to their cross-platform equivalents

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

Automate semantic versioning releases with CHANGELOG validation, comparison link management, GitHub Actions workflow triggering, and monitoring. Scaffold release infrastructure for new projects. Use when user runs /release command, mentions "release version", "cut a release", "create release", "publish release", "tag release", "release setup", or "scaffold release pipeline".

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

Audit a site or page against Google's OFFICIAL AI optimization guidance — readiness for AI Overviews and AI Mode, grounded in Google's published ai-optimization-guide and ai-features docs (not third-party GEO theory). Use when user says "AI optimization", "AI Overviews", "AI mode", "AI search readiness", "optimize for AI", or "GEO audit".

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

Audit markdown files for SEO before publishing. Checks heading structure, meta description, keyword density, content length, link quality, image alt text, and frontmatter completeness. Use when user says "markdown audit", "check my markdown", "SEO check markdown", or "audit this post".

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

Deploy a local project directory or Git repository to Volcengine as a running, reachable cloud service. USE WHEN: deploy to Volcengine, deploy to 火山引擎/火山, deploy this repo/project, publish current code, launch the app, run it in the cloud, expose it as a service, deploy to ECS/VKE/veFaaS, run on ECS, push to VKE, deploy as serverless/FaaS, or the user wants the agent to choose a Volcengine hosting target. If the user only asks which Volcengine deployment target to choose, use `volcengine-prepare` skill first. Not for creating a single standalone resource — use `volcengine-cli` skill for that.

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

Invoke a Rubber Duck Reviewer subagent to independently critique plans and implementations before proceeding. Use when the agent is about to implement a non-trivial plan (multi-file changes, architectural decisions, security-sensitive logic, database schema changes), after completing a self-contained unit of work (module, endpoint, feature), when stuck or facing repeated failures (same test fails 2+ times, unexpected results), or when the agent wants independent validation of assumptions and design decisions. Triggers on any non-trivial implementation task where independent critique would catch blind spots before they become costly mistakes.

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

Use for BayeSED3 galaxy / AGN SED synthesis/analysis, priors, Results analysis, evidence comparison, advanced run modes, Launcher Inspect (`results` / `plot` / `priors`), and assembling Launcher Run argv. Trigger on vague asks like "how do I fit this galaxy?"

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

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

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

Read and manage the user's Threads account: profile, posts, feed, saved posts, activity, insights, social graph, search, trends, and a specific post by URL or ID. Can tune feed ranking and publish posts on request.

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

Read, create, update, and publish apps through Replit's official MCP server.

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

Read, create, edit, and deploy web apps and projects in Lovable. Use to turn a product brief into a working website or prototype, inspect existing project code, update pages and features, and publish changes through Lovable's official MCP server.

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

Read Instagram profiles, followers, posts, comments, likes, stories, feed, saved content, and account insights. Answer questions about posts, reels, and Instagram links. Manage interests and profile details, and publish stories, reels, posts, or carousels on request.

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

Performs static analysis of binary code using radare2 and Ghidra — function enumeration, cross-reference tracing, decompilation, and control flow graphs without executing the binary. Use when disassembling or decompiling code, mapping functions, tracing data flow, or building hypotheses before dynamic verification.

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

Publishes structured, actionable artifacts from Claude Code sessions — PR walkthroughs, incident timelines, system explainers, release checklists, and security audits.

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