「ml」の検索結果

调香师与香水 (调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、accord 和弦、配方 (酒精中 % 浓度)、浓度分级 (parfum/EDP/EDT/EDC)、调香师的「香风琴」orgue、trials/mods 试样迭代、weighing 称量精度; (f) 法规与安全 — IFRA standards (原料限用)、EU 致敏原标签 (26→80+ allergens)、REACH、橡苔/atranol 限用、经典香水 (Mitsouko/Chanel No.5) 因法规被迫重配 (reformulation) 与创作自由之张力; (g) 评价/批评 — Luca Turin & Tania Sanchez (《Perfumes: The Guide》《The Secret of Scent》气味的科学)、香评人、Fragrantica/Basenotes 社区、vintage vs reformulation 之争、niche vs designer 之争。学派分歧: 法系天然传统派 vs 分子合成派、天然纯粹派 vs 合成实用派、haute parfumerie/niche 艺术派 vs mass designer 商业派、「鼻子=艺术家」vs「调香师=香气工程师/技师」、嗅觉科学之争 (Luca Turin 振动理论 vs 主流形状/受体理论)。不含: 香薰蜡烛/家居香氛纯生产营销、芳香疗法健康宣称 (aromatherapy)、纯化妆品配方学 (超出香精范畴)、DIY 家用香氛套件、精油传销/MLM。) Master OS — automated mastery of 调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、accord 和弦、配方 (酒精中 % 浓度)、浓度分级 (parfum/EDP/EDT/EDC)、调香师的「香风琴」orgue、trials/mods 试样迭代、weighing 称量精度; (f) 法规与安全 — IFRA standards (原料限用)、EU 致敏原标签 (26→80+ allergens)、REACH、橡苔/atranol 限用、经典香水 (Mitsouko/Chanel No.5) 因法规被迫重配 (reformulation) 与创作自由之张力; (g) 评价/批评 — Luca Turin & Tania Sanchez (《Perfumes: The Guide》《The Secret of Scent》气味的科学)、香评人、Fragrantica/Basenotes 社区、vintage vs reformulation 之争、niche vs designer 之争。学派分歧: 法系天然传统派 vs 分子合成派、天然纯粹派 vs 合成实用派、haute parfumerie/niche 艺术派 vs mass designer 商业派、「鼻子=艺术家」vs「调香师=香气工程师/技师」、嗅觉科学之争 (Luca Turin 振动理论 vs 主流形状/受体理论)。不含: 香薰蜡烛/家居香氛纯生产营销、芳香疗法健康宣称 (aromatherapy)、纯化妆品配方学 (超出香精范畴)、DIY 家用香氛套件、精油传销/MLM。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 调香师 / 香水 (Perfumery & Fragrance) — 香水创作与香气调配的职业认知操作系统，从业者/调香师/评香师/学习者视角。覆盖: (a) 第一性张力 — codifiable 理论层 (原料知识/香料化学/嗅觉家族分类/accord 和弦/配方结构 %/挥发度金字塔/IFRA 法规) ⇄ tacit 校准层 (嗅觉记忆/闻香训练/「the nose」/创作直觉/盲嗅识别)，这行的核心矛盾是「可背诵的原料与公式」与「不可言传的嗅觉记忆与品味」之间，嗅觉记忆是极致 tacit 技能; (b) 法系传统 vs 分子/合成派 — 法国 Grasse 天然香料 + haute parfumerie 艺术传统 (天然精油/原精/学徒制) vs 现代分子派 (aroma chemicals 香基/captives 专利分子/headspace 顶空捕香/功能香精)，两套对「香水是什么」的世界观; (c) 培养/传承 — ISIPCA (凡尔赛香水学校) + 四大香精公司内部调香学校 (Givaudan/Firmenich(DSM-Firmenich)/IFF/Symrise) + 学徒制 + 「鼻子」tacit 校准; 角色分工: perfumer(parfumeur 调香师) vs evaluator(评香师) vs flavorist(食用香精师); (d) 行业结构 — 四大香精公司寡头 (Givaudan/DSM-Firmenich/IFF/Symrise) + Mane/Robertet/Takasago，为品牌做 B2B 命题创作 (the brief → creation → mods 模型); vs niche/indie 小众独立香水 (artisanal/直营); 天然 (Grasse/精油) vs 合成 (香基/captives) 的成本与可持续之争; (e) 创作层 — 香调金字塔 (top/heart/base notes 前中后调)、ac

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

Listen to generated music by measuring it and by reading it as sheet music: render Strudel code or record a Web Audio page through the real engine in headless Chromium, then read spectrograms, pYIN pitch lines, chroma, roughness and semitone-rub meters; engrave notes as a score with beat-by-beat harmony; transcribe a melody from audio; read MusicXML/MIDI/ABC or a score image into notes and into Strudel code. Use to check whether generated music sounds right or better (before/after a change), to match a reference track, spectrogram image or score, or to find discordant chords, a buried melody, clipping or muddy mixes. Triggers on 'does it sound better', 'listen to', 'render and check', 'spectrogram', 'sfft/stft', 'discordant', 'clashing chords', 'sounds off', 'compare to the original', 'reproduce this track in Strudel', 'sheet music', 'score', 'notation', 'MusicXML', 'MIDI', 'ABC', 'transcribe', 'OMR'. Pairs with strudeling (writing Strudel); for format conversion use processing-video.

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

Web取得の標準前処理レイヤー。URL・公式ドキュメント・ブログ・ニュース・OSSページを読むときは、原則として毎回このSkillでDefuddleを使い本文をMarkdown/JSON化してから読む。生HTMLのまま要約・分析・比較・レビューしない。トリガー例: URLを読む/Webページ要約/OSS調査/公式Doc確認/記事解析/競合サイト確認/Web一次情報確認。

Use when building game UI (menus, HUD, dialogue box, settings/save screens) on top of Pixi'VN with an external JS framework (React, Vue) or with plain PixiJS components — mounting HTML or PixiJS UI layers over the canvas, navigating between UI screens/routes, theming a shadcn/ui-based template, and connecting UI components to game storage/settings. Covers `canvas.htmlLayers.add`/`get`/`remove` and the PixiJS-only layer helpers `canvas.layers.add`/`get`/`remove`.

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

Analyze one or more cycling, running, or hiking FIT/KML activity tracks, generate evidence-based single or aggregate reports, open the bundled local Ride Relief report page when the environment supports it, enrich results with user-confirmed public location context, and create shareable PNG or H.264 MP4 route stories on request. Use whenever a user wants to analyze, compare, visualize, or export .fit or .kml activities, including requests that mention a workout but do not yet include track files.

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

Odoo 17 development reference for Python models and ORM (search, domain, read_group, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work involves Odoo 17 or custom addons—even if the user only pastes a traceback, mentions addons/ or __manifest__.py, describes form/tree/kanban/XML errors, HTTP controllers, or business rules on models—including building features, fixing bugs, refactoring, or reviewing addon code. Includes CSS/SCSS asset authoring and review for Odoo addons.

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

Odoo 18 development reference for Python models and ORM (search, domain, read_group, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work involves Odoo 18 or custom addons—even if the user only pastes a traceback, mentions addons/ or __manifest__.py, describes form/list/kanban/XML errors, HTTP controllers, or business rules on models—including building features, fixing bugs, refactoring, or reviewing addon code. Includes CSS/SCSS asset authoring and review for Odoo addons.

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

Mandatory pre-code gate and definition-of-done for ANY Odoo change (add field, override method, inherit view/xpath, OWL/JS patch, wizard, cron, controller, report, security, migration, bug fix, refactor, "optimize", "clean code", "stick to base"), Odoo 16-19. Also when the user pastes an Odoo traceback or install/upgrade error (ParseError "cannot be located in parent view", "Field ... does not exist", missing xmlid) or asks where an Odoo model, field, method, view or xmlid is defined. Run BEFORE brainstorming or planning: Odoo design questions are answered by tracing the real source into a Context Brief (file:line), not by open-ended Q&A or memory. Resolves the Odoo runtime and version, loads the matching odoo-<major> pack, and closes with install, test, upgrade, i18n, security and hygiene checks before commit.

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

Odoo 16 development reference for Python models and ORM (search, domain, read_group, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work involves Odoo 16 or custom addons—even if the user only pastes a traceback, mentions addons/ or __manifest__.py, describes form/tree/kanban/XML errors, HTTP controllers, or business rules on models—including building features, fixing bugs, refactoring, or reviewing addon code. Includes CSS/SCSS asset authoring and review for Odoo addons.

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

Use when an OpenClaw maintainer or owner is reviewing a ClawHub malicious-skill profile proposal PR: checking `proposals/<GHSA-ID>/clawscan.yml`, reading the private vulnerability context without leaking it, running the SkillTrustBench Profile Gate or equivalent local benchmark, updating the accepted baseline, and promoting an accepted candidate into `internal/profiles/clawhub/clawscan.yml`.

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

Route HugeGraph MCP structured graph query tasks to stable read-only tools. Use when the user asks graph questions, asks to generate Gremlin, provides Gremlin to explain, or needs read-only graph exploration.

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

Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".

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

Generates a 3-month SEO performance HTML report for any domain using DataForSEO data. Fetches baseline vs current traffic, keyword rankings, top content pages, and competitive landscape, then outputs a report styled with the Infrasity brand design system: #0D0A1A background, #8157F2 purple accent, Instrument Sans + DM Sans + DM Mono typography. Use this skill whenever a user provides a target domain and a list of competitor URLs and asks for an SEO report, performance report, SEO analysis, competitive SEO comparison, traffic report, ranking report, or 3-month SEO summary. Also trigger when the user says "generate SEO report for X vs Y and Z", "create a performance report", "compare my SEO against competitors", or pastes a domain and asks how it's performing versus the market. Always use this skill for SEO report generation — do not attempt to build the report without following this structured data-fetch and HTML generation workflow.

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

Runs a full dead-end page audit for any website. Discovers all blog/content pages, detects which ones have zero outgoing links to any URL on the same domain, fetches keywords, clusters pages by topic, and generates 3 outgoing link suggestions per dead-end page with anchor text, placement guidance, and ready-to-paste context copy. Outputs a styled HTML report matching report-style-reference.html. Automatically detects site framework (Next.js, static, WordPress) and uses the correct detection method: RSC header for Next.js/Vercel sites, standard curl for static and traditional CMS sites. Trigger when a user provides a domain or URL and asks for a dead-end page audit, outgoing internal links audit, "which pages don't link out", "find pages with no internal links in the content", "pages that are link dead-ends", or any variation of finding pages that have zero outgoing links to the same domain. Always use this skill for dead-end page audits — never attempt the workflow without following every step here.

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

Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.

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

内容に応じて最適な図表形式を自動選択し、ローカルで画像生成（Pillow）またはコード出力（Mermaid/PlantUML）。フローチャート、アーキテクチャ図、階層図などを生成。資料作成、システム設計時に使用。

Marp（Markdown Presentation）でプレゼンスライドを作成するスキル。PDF/PPTX/HTMLに変換可能。「スライド作って」「プレゼン資料を作って」で使用。

Generate a diagram and route to the right engine — draw.io XML (precise, editable, C4, swimlanes) or Excalidraw JSON (hand-drawn, sketch, wireframes). One entry for flowcharts, architecture, ER, sequence, mind maps. Don't use for Mermaid or slides.

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

Generate professional diagrams as valid draw.io XML — flowcharts, architecture, C4 models, ER diagrams, sequence diagrams, mind maps, and swimlanes. Don't use for Excalidraw or Mermaid output, hand-drawn sketch styles, or slide decks/presentations.

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

Use this skill to build academic-style .docx output: journal / conference / thesis chapters carrying formal citation style (APA, Chicago, IEEE, MLA), numbered equations, figure & table cross-references, footnotes/endnotes, bibliography, or multi-column journal layout. Trigger on: 'research paper', 'journal paper', 'conference paper', 'manuscript', 'thesis', 'APA', 'MLA', 'Chicago', 'IEEE two-column', 'bibliography', 'hanging indent', 'citation style', 'abstract + keywords', 'equation numbering', 'cross-reference', paper with footnotes/endnotes. Output is a single .docx.

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

Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills. Trigger with '/janitor-fix'.

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

Use this skill when reading or writing YAML configuration files, loading vehicle parameters, or handling config file parsing with proper error handling.

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

Deep expertise in ML/CV model selection, training pipelines, and inference architecture. Use when designing machine learning systems, computer vision pipelines, or AI-powered features.

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

Use when you draw a screen as HTML mockup documents (one per variant) - the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task

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