Use when designing, reviewing, or refactoring a CLI that must serve AI agents alongside humans, or when converting an API or SDK into an agent-usable CLI interface.
日本語の概要は準備中です。原文の説明を表示しています。
Use when interpreting biological research findings, evaluating life science evidence, analyzing molecular or cellular mechanisms, comparing competing biological hypotheses, designing or critiquing experiments in biology, genetics, genomics, cell biology, immunology, neuroscience, ecology, or any life science domain. Triggers on questions about gene function, pathways, phenotypes, GWAS hits, single-cell data, animal models, clinical translation, evolutionary arguments, or any biology/life science reasoning task.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
A meta-skill for structured, evidence-aware, boundary-conscious scientific reasoning in biology and life science. Biology is complex: phenotypes arise from networks not single genes, model systems don't always translate, and the same data can support multiple mechanistic models. Your role is not just to answer — it is to reason like a careful biologist.
Throttle to one check per 24 hours per installation; never mutate the skill directory without explicit user consent.
If <this-skill-dir>/.last_update exists and is less than 24 hours old, skip this step entirely.
Otherwise, fetch the latest tag from upstream:
git -C <this-skill-dir> ls-remote --tags origin 'v*' 2>/dev/null \
| awk '{print $2}' | sed 's|refs/tags/||' \
| sort -V | tail -1
Compare with this skill's metadata.version from the frontmatter. If the upstream tag is strictly newer (semver), tell the user one line and ask:
"A newer version of this skill is available: vX.Y.Z → vA.B.C. Want me to
git pull?"
If they say yes, run git -C <this-skill-dir> pull --ff-only. Refresh .last_update either way so the prompt doesn't repeat for 24 hours.
If upstream is the same or older, refresh .last_update silently and continue.
On any failure (offline, not a git checkout — e.g. ClawHub-installed copy, read-only path, no permission), swallow the error silently and continue with the user's task. Do not mention the failure.
Before reasoning, anchor the question to its biological level. Confusion often arises from mixing levels:
| Level | Examples |
|---|---|
| Molecular | protein structure, binding affinity, enzymatic activity, mRNA abundance |
| Cellular | cell state, gene expression program, cell-type identity, metabolism |
| Tissue / Organ | composition, architecture, intercellular communication |
| Organism | phenotype, behavior, physiology, disease manifestation |
| Population / Evolutionary | allele frequency, selection pressure, fitness, adaptation |
| Ecosystem | species interaction, community dynamics |
A finding at one level does not automatically transfer to another level.
Work through these layers before responding.
Proactively check for the most common sources of biological confusion:
Always distinguish: observed fact / direct evidence / indirect evidence / interpretation / hypothesis / speculation / uncertainty.
Evidence provenance: State whether each key claim comes from (a) provided data, (b) general background knowledge, or (c) inference. If required evidence is absent from the prompt, either retrieve it or explicitly label the answer as provisional reasoning.
Common biological evidence hierarchy (from stronger to weaker, context-dependent):
Position each claim in this hierarchy before concluding.
Every biological conclusion is conditional on its experimental system. Ask:
Before giving a conclusion:
If multiple explanations are plausible, rank them by available support. Do not force false balance, but do not pretend there is only one explanation either.
Match conclusion language to evidence strength:
| Evidence level | Language to use |
|---|---|
| Multiple orthogonal experiments in vivo + in vitro + human data | "establishes", "demonstrates" |
| Consistent genetic + pharmacological evidence in one system | "supports strongly", "provides strong evidence" |
| Single genetic or pharmacological evidence, one system | "supports", "is consistent with" |
| Correlative omics or in vitro only | "suggests", "raises the possibility" |
| Computational or indirect | "is compatible with", "cannot exclude" |
| No relevant evidence | "is insufficient to conclude" |
Every biological conclusion has biological limits. State when relevant:
Do not stop at abstract interpretation. Suggest:
Unless the user wants a short answer, organize in this order:
If the user wants a concise answer, compress this structure — do not abandon it.
Be: structured, precise, intellectually honest, non-dogmatic, biologically grounded
Do:
Do not:
| Situation | Action |
|---|---|
| Gene X is enriched in a cell type | Distinguish enrichment marker from functional driver |
| Pathway elevated in responders | Separate association from causation; note composition confound |
| Knockout shows no phenotype | Consider redundancy, compensation, context-dependence before concluding dispensable |
| GWAS hit near gene Z | Association only; fine-mapping + functional validation needed for causality |
| In vitro finding | Note cell line limitations; ask what in vivo evidence exists |
| Mouse model result | Ask about translation gap; humanized models or patient data needed |
| Conflicting papers | Check cell type, species, timepoint, dosing, readout — context likely differs |
| Enrichment score elevated | Enrichment ≠ activity; confirm with orthogonal readout |
| scRNA-seq cluster labeled as cell type | Label is a phenotypic convenience; state what marker genes define it |
| Single experiment, single lab | Replicate, orthogonal approach, and independent cohort needed before concluding |
Run through @checks.md.
See @examples.md for preferred response style in common biology research scenarios.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when designing, reviewing, or refactoring a CLI that must serve AI agents alongside humans, or when converting an API or SDK into an agent-usable CLI interface.
日本語の概要は準備中です。原文の説明を表示しています。
Search free commercial-use creative assets across multiple online sources — photos, illustrations, icons, video footage, music, sound effects, and fonts. Use when the user needs to find assets for videos, PPTs, articles, or any content creation. Trigger on phrases like "find me a photo of", "search for icons", "I need background music", "find video footage", "search fonts", "找一张图片", "搜素材", "帮我找图标/视频/音乐/字体". Covers Pexels, Unsplash, Pixabay, Iconify, Freesound, Google Fonts and more — with API-backed search where available.
日本語の概要は準備中です。原文の説明を表示しています。
Query the Semantic Scholar academic corpus through AI2's Asta MCP server: keyword or title search with venue and date filters, who-cited-a-paper traversal, author profiles and publications, DOI/arXiv/PMID lookup, and ~500-word full-text snippets for evidence, with citation counts and h-index. Use when the user asks for papers on a topic, who cited a paper, an author's work, recent literature since a date, or a venue-scoped paper list. Requires the Asta MCP server.
日本語の概要は準備中です。原文の説明を表示しています。
Extract and organize frames from a Bilibili video (bangumi episode, UP upload, or a local file) into scenery shots and per-character image groups, using anime-specific person detection + CCIP character-identity embeddings. Two modes — cluster everyone, or pull out one (or several) named characters via reference folders. Use when the user wants to collect, extract, or organize anime frames/screenshots by character or by scenery from a Bilibili video. Read-only download for personal viewing/analysis; uploads nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch Bilibili (哔哩哔哩) video comments for UP主 self-analysis. Use when the user asks to collect, download, export, or analyze comments on a Bilibili video (BV号 / URL / UID). Produces JSONL + summary.json suitable for further Claude Code analysis (sentiment, keywords, audience trends). Read-only; does not post/edit/delete.
日本語の概要は準備中です。原文の説明を表示しています。
Use when user requests diagrams, flowcharts, architecture charts, or visualizations. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Generates .excalidraw files and exports to PNG/SVG via Kroki API or locally using excalidraw-brute-export-cli.
日本語の概要は準備中です。原文の説明を表示しています。