1.2万 件 ・ 関連度順
概要と使いどころ
This skill should be used before answering "does Genesis have X", "does Genesis lack X", auditing Genesis capabilities, comparing Genesis to an external system, or reviewing/summarizing the architecture. It routes to the canonical judgment-layer subsystem map so audits start from the map, not from a cold grep. Also fires after changing a subsystem's capabilities, to keep the map current.
日本語の概要は準備中です。原文の説明を表示しています。
Carbon chemistry, functional groups, IUPAC nomenclature, isomerism, reaction mechanisms (substitution, elimination, addition), polymers, and biochemistry basics. Covers hydrocarbon classes (alkanes, alkenes, alkynes, aromatics), common functional groups (alcohols, aldehydes, ketones, carboxylic acids, esters, amines, amides), stereochemistry, condensation and addition polymerization, and the four biomolecule classes (carbohydrates, lipids, proteins, nucleic acids). Use when analyzing organic structures, predicting reaction products, or connecting chemistry to biology.
日本語の概要は準備中です。原文の説明を表示しています。
Generative Engine Optimization plus agent readiness. Use this skill whenever the user asks about GEO, AEO, LLMO, optimizing content for AI search engines (ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Copilot), getting cited by LLMs, brand mentions in AI responses, llms.txt, robots.txt for AI crawlers, Schema.org JSON-LD, FAST framework, agent readiness, MCP server discovery, Web Bot Auth, OAuth for agents, API Catalog, agentic commerce (x402, ACP, UCP), Markdown content negotiation, or auditing a site or page for AI visibility. Also trigger when the user says "AI SEO", asks how to "rank in ChatGPT", "show up in Perplexity", "appear in AI Overviews", or wants a site to "speak to AI agents". Trigger even when the request is implicit, such as "review this article so AI search picks it up" or "make our docs agent-friendly".
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end SEO operations for B2B SaaS organic visibility. Use this skill when you need keyword research, technical SEO audits, content optimization, link building strategy, international expansion, AI/AEO optimization, schema markup, Core Web Vitals improvements, and organic traffic growth planning. Also triggers on: SEO, keyword research, can we rank for this keyword, which keywords are actually worth it, qualify these keywords, check the SERPs, keyword shortlist, too many keywords, technical SEO, link building, content optimization, international SEO, hreflang, x-default, multilingual site, translated pages not ranking, our German site gets no traffic, language switcher, auto-redirect by country, machine translation SEO, content parity, ccTLD vs subfolder, AI search, AEO, GEO, Core Web Vitals, schema markup, organic traffic, G2 listing, Capterra, TrustRadius, review-platform category page, best software roundup, listicle placement, directory submissions, do we need a Google Business Profile in [country], local SEO with no office, Google Business Profile eligibility, virtual office address SEO, coworking address business profile, business profile suspended, NAP consistency, local citations for SaaS, LocalBusiness schema, server log analysis, log file analysis, what is Googlebot crawling, is Googlebot hitting errors, verify Googlebot, fake Googlebot, crawl budget, do we have a crawl budget problem, Crawl Stats report, new pages not getting crawled.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Business Teacher, Postsecondary — grading case analysis on the rigor of business reasoning rather than matching a single "correct" answer, updating stale textbook examples against current market conditions rather than teaching them as still-current, distinguishing taught analytical frameworks from personal business opinion presented as universal fact, and preserving the incomplete-information trade-offs of real business decisions rather than simplifying problems into false certainty.
日本語の概要は準備中です。原文の説明を表示しています。
Access ENCODE uniform analysis pipelines, generate user-specific Nextflow/WDL pipelines, manage compute resources, and integrate with cloud platforms. Use when the user wants to understand ENCODE pipelines, run pipelines on their own data, generate custom Nextflow workflows from ENCODE pipeline code, check compute requirements (CPU/GPU/memory), run pipelines in background, or integrate with Google Cloud, AWS, or other cloud platforms. Also use when the user asks about ENCODE pipeline outputs, processing standards, software versions, or wants to replicate ENCODE processing. Covers local execution, HPC, and cloud deployment with resource-aware scheduling. Use this skill for ANY pipeline execution, workflow generation, or compute resource management task involving ENCODE data.
日本語の概要は準備中です。原文の説明を表示しています。
Language-specific guidelines for producing high-quality Traditional Chinese (zh-TW) content: script, full-width punctuation, spacing, forms of address, grammar constraints, and Taiwan terminology. Includes the no-calque rule against literal translations of English phrasal verbs such as 折入 for fold in. Use when writing any kind of Chinese content. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing Chinese content for language and terminology compliance. Always apply `writing-style-guideline` alongside this skill for structure, tone, rhetorical constraints, and banned phrases.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "map out our business model", "business model canvas", "how does our business work", "what are our key resources", "define our value proposition", "revenue model design", "cost structure", "who are our key partners", "lean canvas", "business model design", "how do we make money", or wants to document, stress-test, or redesign how [your startup] creates, delivers, and captures value.
日本語の概要は準備中です。原文の説明を表示しています。
Write a Business Requirements Document. Use when the user says "write a BRD", "business requirements", "document the business need", "vision and scope document", "business case for this feature", "what does the business need", "strategic requirements", "document why we need this" - even if they don't explicitly say "BRD".
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to configure SLA enforcement for Salesforce Field Service (FSL) using Work Order entitlement processes: designing entitlement processes of type Work Order, defining FSL milestones (response time, on-site arrival, resolution), wiring milestone actions, and aligning Business Hours with service territory Operating Hours. NOT for Case SLAs and Case entitlement processes — use admin/entitlements-and-milestones. NOT for defining the SLA tier table and escalation matrix — use architect/sla-design-and-escalation-matrix.
日本語の概要は準備中です。原文の説明を表示しています。
Configure and troubleshoot Salesforce Case Escalation Rules: time-based escalation entries, business hours configuration, escalation actions (email alerts and reassignment), and diagnosing why cases are not escalating. Covers the EscalationRules metadata shape, businessHoursSource and escalationStartTime semantics, staged escalationAction thresholds, deploy-inactive parallel-run cutover, and monitoring escalated cases. Trigger keywords: escalation rule, case not escalating, SLA breach notification, escalate after X hours, reassign case automatically, IsEscalated. NOT for SLA milestone timers — use admin/entitlements-and-milestones. NOT for case routing on creation — use admin/assignment-rules. NOT for the calendar itself — use admin/business-hours-and-holidays.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to 'plan my day', 'help me plan today', 'morning planning', 'what should I work on today', 'daily planner', 'evening reflection', 'reflect on my day', 'migrate tasks', 'carry tasks forward', 'rapid log', 'brain dump my tasks', or mentions ADHD-friendly planning, time-blindness, swim lanes, energy-based task management, bullet journal for ADHD, or dopamine menu. Provides a BuJo-style daily planning system with swim lanes, migration, reflection, and dopamine rewards. Part of the ADHD-founder.com ecosystem.
日本語の概要は準備中です。原文の説明を表示しています。
[user] Business Legal Counsel / CLO level contract drafting, review, and legal risk assessment. Handles domestic Chinese contracts (中文), cross-border contracts, and offshore international contracts in Chinese and English. Jurisdictions: PRC law (Civil Code, Company Law, Anti-Unfair Competition Law), US law (UCC, common law), Hong Kong law (common law, HK ordinances). Combines relevant laws, regulations, and litigation case precedents in contract analysis. Generates Word (.docx) files with track changes and persuasive margin comments for contract review markup. Use when user mentions contracts, legal review, contract drafting, legal risk assessment, NDA, agreement, 合同, 法律, 审核, 起草, 合同审查, 法务, legal negotiation, due diligence, 尽职调查, 风险评估, 条款谈判, 反不正当竞争, or any contract-related task.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses the quality and completeness of a genome annotation with BUSCO (conserved single-copy ortholog recovery), OMArk (proteome completeness, consistency, and contamination), CheckM2 (prokaryotic completeness/contamination), and a gene-set sanity panel (gene count, mono-exonic fraction, protein-length distribution, mRNA:gene ratio, coding density). Covers the assembly-BUSCO-vs-proteome-BUSCO diagnostic, what BUSCO-Duplicated really means, why gene count is a vanity metric, and the QC of transferred annotations. Use when judging whether an annotation is good enough to publish or submit, diagnosing a suspect annotation, or comparing annotation completeness across pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies essential genes from CRISPR-Cas9 fitness screens using BAGEL2 (Kim & Hart 2021 Genome Med), a Bayesian classifier scoring per-gene Bayes Factors via log-likelihood ratios over per-sgRNA fold changes, calibrated against CEGv2 core-essentials (Hart 2017 G3, ~684 genes) and NEGv1 non-essentials (Hart 2014, ~927 genes). Covers the fc + bf + pr workflow, the linear-extrapolation improvement over BAGEL1 truncation, multi-target off-target correction, tumor-suppressor sensitivity (BAGEL2 detects enrichment), and BF calibration (BF >6 ≈ 90% posterior per Hart 2017; ~5% FDR by BAGEL convention). Use when classifying essential vs non-essential genes, calibrating BAGEL2 thresholds against PR curves, identifying tumor suppressors alongside essentials, comparing BAGEL2 hits to MAGeCK / drugZ, or generating publication-quality essentiality calls.
日本語の概要は準備中です。原文の説明を表示しています。
Research one agent harness's release (docs, source, runtime) and fill its capability cells in scripts/harness_capabilities.py with cited evidence. Use after a harness version bump, when just harness-probe reports re-research, or when capability cells read unknown.
日本語の概要は準備中です。原文の説明を表示しています。
Audit one or all supported agent harnesses (claude, codex, opencode, pi, omp, antigravity, cursor, grok) for config efficiency, hook overhead, permission friction, plugin and MCP cost, skill metadata portability, dead config, and measured session friction. Use when invoked as `$optimize-harness [harness ...] [focus]`, or when the user asks to optimize or compare agent harness configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Maps every proposed P&ID object from an accepted enrichment draft to the generic family, catalogue class and required attributes the project's intelligent P&ID authoring tool would need, as a readiness table with UNKNOWN wherever the project catalogue extract is not provided, plus connectivity readiness per line and a numbered list of import blockers. Mapping only: it never writes to the tool, never produces an import file and never claims a class exists in the catalogue. Use when the user asks to "build the readiness map", "show how far the draft is from a sandbox import", "list what would block the import", "map the objects to the tool catalogue" or "check attribute readiness against the catalogue extract" after gate G3. Do not use for validating the discipline sections or assembling the review package, use validation-and-review-package instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end SEO operations for B2B SaaS organic visibility. Use this skill when you need keyword research, technical SEO audits, content optimization, link building strategy, international expansion, AI/AEO optimization, schema markup, Core Web Vitals improvements, and organic traffic growth planning. Also triggers on: SEO, keyword research, technical SEO, link building, content optimization, international SEO, hreflang, x-default, multilingual site, translated pages not ranking, our German site gets no traffic, language switcher, auto-redirect by country, machine translation SEO, content parity, ccTLD vs subfolder, AI search, AEO, GEO, Core Web Vitals, schema markup, organic traffic, G2 listing, Capterra, TrustRadius, review-platform category page, best software roundup, listicle placement, directory submissions, do we need a Google Business Profile in [country], local SEO with no office, Google Business Profile eligibility, virtual office address SEO, coworking address business profile, business profile suspended, NAP consistency, local citations for SaaS, LocalBusiness schema.
日本語の概要は準備中です。原文の説明を表示しています。
Create an Estuary derivation that flattens a nested array into one output document per array element. Use for normalising nested JSON, exploding line items, unpacking tags, or producing one-row-per-item tables from arrays. Derivations add complexity and cost — confirm the user wants a derivation before reaching for this (some destinations can `UNNEST` server-side without one). Use when user says "flatten-array derivation", "derivation to explode an array", "transformation to unnest", "derive one row per item", or "flatten nested data with a derivation".
日本語の概要は準備中です。原文の説明を表示しています。
Change the agent harness itself (AOS, AO or CBS hooks, gates, memory, permissions, delegation, plugins, bootstrap) the safe way: look up the matching harness pattern, design against its gotchas, build with /startcycle and a live trail, check every harness, open a PR after GO. Use for "change a hook", "fix the go-gate", "harness work", "plugin change".
日本語の概要は準備中です。原文の説明を表示しています。
Write or edit Japanese articles, reports, guides, and public-facing drafts so the argument is clear and the prose reads naturally. Preserve the author's meaning, evidence, and voice when revising. Use for requests to write from a topic or notes, remove AI臭 / AIっぽさ, improve awkward wording or structure, or format notes as 箇条書き, チーム共有, 社内共有, a decision note, handoff, Slack post, or Teams post. For existing prose, ask Gemini through Antigravity CLI to rewrite naturally by default, then audit against the source; use the current model if unavailable. Do NOT use for ordinary Japanese answers, progress updates, technical explanations, code review, English-only prose that is not a bullet-formatting request, or an explicitly incompatible format.
Assesses the quality and completeness of a genome annotation with BUSCO (conserved single-copy ortholog recovery), OMArk (proteome completeness, consistency, and contamination), CheckM2 (prokaryotic completeness/contamination), and a gene-set sanity panel (gene count, mono-exonic fraction, protein-length distribution, mRNA:gene ratio, coding density). Covers the assembly-BUSCO-vs-proteome-BUSCO diagnostic, what BUSCO-Duplicated really means, why gene count is a vanity metric, and the QC of transferred annotations. Use when judging whether an annotation is good enough to publish or submit, diagnosing a suspect annotation, or comparing annotation completeness across pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies essential genes from CRISPR-Cas9 fitness screens using BAGEL2 (Kim & Hart 2021 Genome Med), a Bayesian classifier scoring per-gene Bayes Factors via log-likelihood ratios over per-sgRNA fold changes, calibrated against CEGv2 core-essentials (Hart 2017 G3, ~684 genes) and NEGv1 non-essentials (Hart 2014, ~927 genes). Covers the fc + bf + pr workflow, the linear-extrapolation improvement over BAGEL1 truncation, multi-target off-target correction, tumor-suppressor sensitivity (BAGEL2 detects enrichment), and BF-to-FDR calibration (BF >6 ≈ FDR 0.05 from Hart 2017). Use when classifying essential vs non-essential genes, calibrating BAGEL2 thresholds against PR curves, identifying tumor suppressors alongside essentials, comparing BAGEL2 hits to MAGeCK / drugZ, or generating publication-quality essentiality calls.
日本語の概要は準備中です。原文の説明を表示しています。