メニュー
Transcribe audio and video files into structured notes. Activate this skill when users want to transcribe recordings, meetings, podcasts, voice memos, or any audio/video content in their vault.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create and edit Obsidian Canvas (.canvas) files — text/file/link/group nodes and the edges between them, using the JSON Canvas spec. Activate this skill when users want to build a canvas, mind map, flowchart, or visual board of notes.
Create and configure Obsidian Bases — database-like views of notes. Activate this skill when users want to create bases, write filters, formulas, or set up table/cards/list/map views.
Write and edit Obsidian Flavored Markdown — wikilinks, embeds, callouts, block references, tags, comments, highlights, and math. Activate this skill when users want to link notes, embed content, add callouts, or use Obsidian-specific Markdown syntax.
Run the eval harness against a real Obsidian instance, monitor for the harness's known reliability gotchas (concurrent runs, CLI-bridge hangs, stale child processes), and bless a result as a baseline only when the run is clean. Use when the user asks to "run the evals", "bless a baseline", "measure the impact of <change> on solve rate", "run a model sweep", or similar. Has Obsidian-CLI side effects (drives the agent view, creates eval-scratch fixtures, may set chatModelName for the duration of the run); does NOT modify plugin source code or commit unless explicitly asked.
Use this skill whenever the user asks for a Quill Shipping Company tracking code or shipping reference. It defines the exact, non-obvious format every tracking code must follow.
Answer questions about Gemini Scribe plugin features, settings, and usage, and diagnose plugin errors by reading the user's debug.log (when File Logging is enabled). Activate this skill whenever the user asks how to use the plugin or configure settings, OR reports that something went wrong with the plugin — bug, error, crash, broken behavior, "not working", "what just happened" — especially when they mention the debug log, log file, console output, or want help troubleshooting. Always activate this skill before searching the vault for plugin log files; debug.log lives in the plugin state folder which the standard read_file tool blocks.
| name | audio-transcription |
| description | Transcribe audio and video files into structured notes. Activate this skill when users want to transcribe recordings, meetings, podcasts, voice memos, or any audio/video content in their vault. |
Transcribe audio and video files from the vault into structured Obsidian notes using read_file to send binary media directly to the model.
Audio: .wav, .mp3, .aac, .flac, .webm (audio-only)
Video: .mp4, .mpeg, .mov, .flv, .mpg, .webm, .wmv, .3gp
Size limit: 20 MB per file (Gemini inline data limit).
read_file with the path to the audio/video file — the binary data is sent directly to the model for processing.write_file to save the transcription as a markdown note.Structure transcriptions as follows:
---
tags:
- transcription
source: "[[original-file.mp3]]"
date: YYYY-MM-DD
duration: "MM:SS" (estimate if possible)
---
# Transcription: [Title]
## Summary
Brief 2-3 sentence summary of the content.
## Transcript
[00:00] Speaker 1: Opening remarks...
[00:45] Speaker 2: Response...
[01:30] Speaker 1: Follow-up...
[MM:SS] format at natural breaks (new speakers, topic changes, pauses).[inaudible] or [unclear].[laughter], [applause], [music].read_file on the current note first to find embedded audio/video links (e.g., ![[recording.mp3]]), then read_file on the linked file.