'transcripts' 검색 결과

Query Ensembl for genomic data. Use when user asks about gene coordinates, genomic sequences, variants, gene structure, exons, transcripts, or species comparison. Triggers on "ensembl", "gene coordinates", "genomic location", "exon", "transcript", "variant location", "rsid", "rs number".

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

Extract full transcripts and captions from YouTube videos for content analysis, summarization, note-taking, and repurposing. Supports multiple languages and auto-generated captions. Ideal for research, content creation, and accessibility workflows.

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

Use when changing REPL clear/reset/resume/surface behavior (onClearTerminal, transcriptSeq remount, Ink Static paths, Ctrl+O/Ctrl+E transitions). Enforces single-owner reset transaction and prevents black-screen/flicker/duplicate-row regressions.

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

Use when mining coding-agent session history, archived transcripts, memories, or repeated local work to discover recurring workflows that should become new Agent Skills.

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

Gmail AI transcript notifications → meeting Notes: URLs + mark read. Args: (none). Invoked standalone or as step 1 of /meeting wrap.

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

Fetch & embed AI transcripts as Obsidian callouts. Args: <path>, all, refresh <path>. Prompts for URLs if empty.

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

Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

Find web sources with query-relevant page excerpts and optional full-page content, and discover workflows, data APIs, and indexes. Use for web research or finding structured records, listings, transcripts, and datasets. Supports semantic tool discovery, domain matching, and progressive catalogue browsing.

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

Clean up raw interview transcripts while preserving meaning and speaker voice. Use after conducting interviews.

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

Edit English prose to remove repetitive AI phrasing, inflated language, and mechanical structure while preserving meaning and the author's voice. Use for requests to humanize, de-slop, rewrite naturally, or fix tone. Also compose from the author's English notes or transcripts and ask targeted questions when real details are missing. For Brazilian Portuguese, use the companion humanizar skill.

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

Write and edit Brazilian Portuguese prose with natural rhythm and the author's voice while preserving facts, meaning, and intent. Use for PT-BR requests to humanizar, tirar cara de IA, remover AI slop, reescrever com voz, simplify language, or write a post, email, article, or bio. Also use the author's notes or transcripts and ask targeted questions when essential facts are missing. For English text, use the bundled human-ai skill.

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

Edit English prose to remove repetitive AI phrasing, inflated language, and mechanical structure while preserving facts, meaning, and the author's voice. Use for requests to de-slop, humanize, rewrite naturally, fix tone, or review generic English drafts. Also compose from the author's English notes or transcripts and ask targeted questions when real details are missing. For Brazilian Portuguese, use the bundled humanizar skill.

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

Draft professional emails, feedback (SBI/BID), difficult conversations, meeting notes, and escalation templates. Covers tone matrix, cross-cultural communication, Slack/Teams async patterns, and structured notes from raw transcripts.

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

Research YouTube topics, analyze competitor videos, deconstruct viral content, and query the YouTube Data API. Use when researching a video topic before planning, analyzing video transcripts for viral patterns, searching competitor channels, or fetching video and channel stats via the YouTube Data API v3.

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

Find web sources with query-relevant page excerpts and optional full-page content, and discover workflows, data APIs, and indexes. Use for web research or finding structured records, listings, transcripts, and datasets. Supports semantic tool discovery, domain matching, and progressive catalogue browsing.

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

Fetches YouTube video metadata and transcripts (genesis web_fetch MCP tool first, yt-dlp via Bash as the fallback). Activate when the user shares a YouTube URL (youtube.com, youtu.be), asks to 'fetch this video', 'get the transcript', 'what does this video say', 'summarize this YouTube video', or references video content that needs to be retrieved. Also activate when processing multiple YouTube URLs in batch. Do NOT use for non-YouTube video platforms, local video files, or audio-only podcast URLs.

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

Facilitate a full design-thinking engagement (Empathize, Define, Ideate, Prototype, Test) grounded in real user evidence. Use whenever the user wants to understand users deeply and design a solution for them: "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "prototype this concept", "design a usability test", "our users are churning and we don't know why", in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when they never say "design thinking". Also use when the user drops raw interview notes, transcripts, or survey exports and wants insights, personas, or product decisions. Not for "is there a market for X" desk questions (market-researcher).

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

Write a kolu blog post grounded in the real build history — mine the Claude Code session logs behind a feature for the actual story (for large efforts, fan out over the transcripts with an ultracode workflow), draft it in the author's voice, and wire it into the Astro site. Use when asked to write a blog post or engineering essay about something that was built, especially one that should read as a narrative of what actually happened rather than invented marketing copy.

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

Jobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".

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

Run a user interview — produce an interview guide and synthesize the output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", "build a persona from this feedback", "find the JTBD in these transcripts", or "analyze this interview data".

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

Spawn-count analytics for the tonone roster — which agents this project actually uses, from local session transcripts. Use when "which agents do we actually use", "show tonone stats", "prune the roster", or before running apex-profile.

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

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

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