Check for Faster-Whisper (preferred - 4-5x faster) workflow skill. Use this skill when the user needs Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Check for Faster-Whisper (preferred - 4-5x faster) workflow skill. Use this skill when the user needs Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Check for Faster-Whisper (preferred - 4-5x faster)
Overview
This public intake copy packages plugins/antigravity-awesome-skills/skills/audio-transcriber from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Purpose, 📊 Metadata, 📋 Meeting Minutes, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
User needs to transcribe audio/video files to text
User wants meeting minutes automatically generated from recordings
User requires speaker identification (diarization) in conversations
User needs subtitles/captions (SRT, VTT formats)
User wants executive summaries of long audio content
User asks variations of "transcribe this audio", "convert audio to text", "generate meeting notes from recording"
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
references/tools-comparison.md
Starts with the smallest copied file that materially changes execution
Supporting context
examples/basic-transcription.sh
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Objective: Identify available transcription engines without user configuration.
Actions:
Run detection commands to find installed tools:
# Check for Faster-Whisper (preferred - 4-5x faster)if python3 -c "import faster_whisper" 2>/dev/null; then
TRANSCRIBER="faster-whisper"echo"✅ Faster-Whisper detected (optimized)"# Fallback to original Whisperelif python3 -c "import whisper" 2>/dev/null; then
TRANSCRIBER="whisper"echo"✅ OpenAI Whisper detected"else
TRANSCRIBER="none"echo"⚠️ No transcription tool found"fi# Check for ffmpeg (audio format conversion)ifcommand -v ffmpeg &>/dev/null; thenecho"✅ ffmpeg available (format conversion enabled)"elseecho"ℹ️ ffmpeg not found (limited format support)"fi
If no transcriber found:
Offer automatic installation using the provided script:
Objective: Create structured Markdown with metadata, transcription, meeting minutes, and summary.
Output Template:
# Audio Transcription Report#### Imported: Purpose
This skill automates audio-to-text transcription with professional Markdown output, extracting rich technical metadata (speakers, timestamps, language, file size, duration) and generating structured meeting minutes and executive summaries. It uses Faster-Whisper or Whisper with zero configuration, working universally across projects without hardcoded paths or API keys.
Inspired by tools like Plaud, this skill transforms raw audio recordings into actionable documentation, making it ideal for meetings, interviews, lectures, and content analysis.
## Examples### Example 1: Ask for the upstream workflow directly```text
Use @audio-transcriber-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @audio-transcriber-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @audio-transcriber-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @audio-transcriber-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Imported Usage Notes
Imported: Example Usage
Example 1: Basic Transcription
User Input:
copilot> transcribe audio to markdown: meeting-2026-02-02.mp3
copilot> transcribe audio to markdown: conference-keynote.mp3
Skill Output:
✅ Faster-Whisper detected (optimized)
📂 File: conference-keynote.mp3
📊 Size: 87.2 MB
⏱️ Duration: 02:15:47
⚠️ Large file (87.2 MB) - processing may take several minutes
Continue? [Y/n]:
User:Y
🎙️ Processing... (this may take 10-15 minutes)
[████░░░░░░░░░░░░░░░░] 20% - Estimated time remaining: 12m
This skill is platform-agnostic and works in any terminal context where GitHub Copilot CLI is available. It does not depend on specific project configurations or external APIs, following the zero-configuration philosophy.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/audio-transcriber, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/tools-comparison.md
examples
worked examples or reusable prompts copied from upstream
examples/basic-transcription.sh
scripts
upstream helper scripts that change execution or validation
scripts/install-requirements.sh
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
**Implementation:**
Use Python or bash with AI model (Claude/GPT) for intelligent summarization:
```python
def generate_meeting_minutes(segments):
"""Extract topics, decisions, action items from transcription."""
# Group segments by topic (simple clustering by timestamps)
topics = cluster_by_topic(segments)
# Identify action items (keywords: "should", "will", "need to", "action")
action_items = extract_action_items(segments)
# Identify decisions (keywords: "decided", "agreed", "approved")
decisions = extract_decisions(segments)
return {
"topics": topics,
"decisions": decisions,
"action_items": action_items
}
def generate_summary(segments, max_paragraphs=5):
"""Create executive summary using AI (Claude/GPT via API or local model)."""
full_text = " ".join([s["text"] for s in segments])
# Use Chain of Density approach (from prompt-engineer frameworks)
summary_prompt = f"""
Summarize the following transcription in {max_paragraphs} concise paragraphs.
Focus on key topics, decisions, and action items.
Transcription:
{full_text}
"""
# Call AI model (placeholder - user can integrate Claude API or use local model)
summary = call_ai_model(summary_prompt)
return summary
Output file naming:
# v1.1.0: Use timestamp para evitar sobrescrever
TIMESTAMP=$(date +%Y%m%d-%H%M%S)
TRANSCRIPT_FILE="transcript-${TIMESTAMP}.md"
ATA_FILE="ata-${TIMESTAMP}.md"echo"$TRANSCRIPT_CONTENT" > "$TRANSCRIPT_FILE"echo"✅ Transcript salvo: $TRANSCRIPT_FILE"if [[ -n "$ATA_CONTENT" ]]; thenecho"$ATA_CONTENT" > "$ATA_FILE"echo"✅ Ata salva: $ATA_FILE"fi
