'notes' 검색 결과

Search Xiaohongshu (XHS / RedNote) notes by keyword with full field extraction including body text, topics/tags, image list URLs, video stream URL, publish timestamp, and all engagement stats (likes, collects, comments, shares). Supports all page filter options: sort order (general, latest, most liked, most commented, most collected), note type (image-text, video), publish time range (within 1 day, 1 week, 6 months), search scope (seen, unseen, followed), and location distance (same city, nearby). Use when user mentions search xiaohongshu notes, xhs keyword search, rednote note search, search xiaohongshu posts, scrape xhs search results, xiaohongshu note discovery, rednote content search, collect xhs notes by keyword, xiaohongshu topic search, xhs note body text, xiaohongshu video notes, xiaohongshu image notes, rednote post filter, xhs search with filters, xiaohongshu full note data, xhs note details from search, extract rednote posts, xiaohongshu content monitoring, xhs search scrape.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migrate notes between Apple Notes, Obsidian, Notion, and other platforms. Trigger: "apple notes migration".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assemble an Apple Notes list video ad from a note + end-card JSON — a frame-accurate fake iPhone screen recording of a short list being typed into Apple Notes (character by character, key pops, blinking caret, the note scrolling up as it fills) crossfaded into a checklist end card (the note's picks as ticked rows, real product photos, logo, CTA, in the brand's colours and fonts), with an optional music bed. FREE assembly (Playwright + ffmpeg); the recipe supplies the per-brand note + end card and gates the paid music call to its own capability. The Apple Notes sibling of render-imessage-chat and render-chatgpt-chat. Use for the apple-notes format.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when users provide YouTube, Bilibili, or X/Twitter lecture URLs and want reader-first Chinese LaTeX/PDF notes with source-faithful claims, fluent authored prose, and verified teaching figures, especially requests phrased as lecture notes, 视频转PDF, 课程笔记, 讲义, YouTube笔记, B站笔记, X/Twitter lecture notes, or BV号; do not produce transcript dumps, quota-padded prose, or screenshot galleries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

调香师与香水 (调香师 / 香水 (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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate ship-ready release notes from specs and tickets. Use this skill when: - A release is being prepared and you need user-facing release notes - You need internal (engineering) release notes for a deployment - You want to generate release notes from completed specs or tickets

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Obsidian Claw is an ontology-building skill that transforms chaotic notes, raw ideas, voice dumps, and meeting transcripts into a structured, interlinked knowledge base inside Obsidian. Use this skill whenever the user wants to: add new notes to their Obsidian vault and auto-link them to existing ones, build a concept graph or knowledge map, surface forgotten related discussions ("you talked about this with investor X 3 months ago"), extract entities and relationships from unstructured text, or turn scattered thoughts into wiki-style atomic notes. Also trigger when the user mentions "second brain", "Zettelkasten", "PKM", "personal knowledge management", "note graph", "knowledge graph", "link my notes", "organize my vault", "connect ideas", or asks Claude to "remember" something across sessions using Obsidian. If the user is doing anything with Obsidian notes and wants intelligence layered on top, use this skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks SolanaOS to add a note, list notes, search notes, or manage note folders.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turns a list of merged changes, closed work items or commit messages the user provides into DRAFT release notes under the version heading and date the user supplies, grouped as features, fixes and other, in the organisation's tone from the style guide or prior notes given, with every entry traced to its source item, breaking changes and required actions flagged first, and internal-only items held back for the release owner to confirm. Use when the user asks to "write the release notes for this version", "turn these merged pull requests into a changelog", "summarise what shipped this sprint for customers", "draft the what's new for this release" or "group these closed tickets into release notes". Do not use for an announcement email or intranet post about a launch, use announcement-drafter instead; for a change ticket, use change-request-pack; for a how-to article about one fix, use knowledge-article-drafter. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

HeroUI Pro React の新リリースを公式サイトから調査し、 指定されたリリースノートドキュメントを追記更新するスキル。 「できるようになったこと・作れるようになったもの」を主軸に、 自然な日本語でユーザーストーリーとして記述する。 Trigger: HeroUI Pro リリースノート更新, heroui-pro release notes, heroui-pro更新, /dev:heroui-pro-release-notes

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Clawdbot to add a note, list notes, search notes, or manage note folders.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Granola 로컬 보관 자료에서 회의 메모, 녹취록, 패널을 검색하고 가져옵니다. 동기화 상태를 확인하고 필요할 때 갱신하며, 읽기 전용 SQL로 정확한 개수와 순위를 구합니다.

• 주제로 지난 회의 메모 찾기
• 메모의 녹취록과 패널 가져오기
• 최근 정보 검색 전 동기화 상태 확인

Search and edit notes in a SiYuan knowledge base through its API. Find text, read individual content blocks, create documents, update paragraphs, rename or delete notes, and export documents as Markdown.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Search existing notes by keyword
• Save meeting notes as a new document
• Append or update paragraphs in a note

회의 메모나 전사문에서 근거가 있는 결정 사항과 담당자·기한을 정리합니다. 기존 작업과 중복을 확인하고 회의록, 티켓, 후속 메시지 초안을 만듭니다.

• 회의 메모에서 작업 추출
• 결정 사항과 담당자·기한 확인
• 회의 약속과 기존 작업 대조

Keep project documentation consistent with recent code changes. Find outdated instructions, update affected reference pages and examples, and write release notes focused on user impact while leaving unchanged sections intact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update documentation after a feature ships
• Check documentation before a release
• Fix outdated defaults and instructions

Create a single HTML page that organizes release highlights, additions, fixes, breaking changes, known issues, and upgrade guidance. Missing information is explicitly labeled, helping readers distinguish supplied details from information that was not provided.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing release notes for a version update
• Sharing additions and fixes on one page
• Documenting breaking changes and upgrade steps

Turn scattered messages, meeting notes, and documents into sourced action lists and status briefs. The skill reconciles updates, separates facts from tentative inferences, and highlights decisions, dependencies, risks, and unanswered questions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a sourced action list from meeting notes
• Combine messages and documents into a status brief
• Assess feasibility using dependencies and blockers

Search meeting notes, summaries, and transcripts saved in Granola. Ask questions in everyday language to find past discussions, then read detailed transcripts when you need the exact wording of a conversation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find past discussions by asking a question
• Read meeting notes and summaries
• Check exact wording in meeting transcripts

Read and create Evernote notes through its official MCP server, which connects the agent to Evernote tools. The workflow checks connection status, discovers available operations, and requires the relevant approval before creating notes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reading existing Evernote notes
• Creating a new Evernote note
• Checking the Evernote connection and starting authorization

Prepare a Cherry Studio release by checking changes against the published version, writing English and Chinese release notes, updating version metadata, and creating a release branch after review to start the build workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a patch, minor, or major release
• Preparing a beta or release candidate
• Writing release notes from final user-visible changes

Turn JSON or CSV data into Markdown notes using Knap templates. Apply formatting rules and conditional sections, generate files in batches, or shape web content extracted by Defuddle into a consistent note format.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generate Markdown notes from JSON or CSV data
• Create multiple notes with a shared template
• Format Defuddle output into a note

Create and edit Obsidian Bases files to organize notes into tables, cards, and lists. Filter notes by tags or properties, calculate values such as days until a deadline, and configure grouping and summaries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a task table with deadlines and status
• Organize books and articles into reading cards
• Create an index of daily notes

Turn git changes since the last tag into clear App Store release notes. Identifies updates users will notice, groups new features, improvements, and fixes, removes internal work and duplicates, and checks each bullet against the actual changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting App Store What's New text for a release
• Turning technical commits into plain release notes
• Collecting user-visible changes between specified tags

Prepare the next Prisma 8 release by updating workspace versions, assembling upgrade guides, and drafting release notes. Open release and documentation pull requests for maintainer review; merging the release request triggers automated publication.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing the next Prisma 8 release candidate
• Updating versions across workspace packages
• Assembling upgrade guides and release notes