ClaudeSuperPower
SubmitLog in

scribe

Skill

Turn meeting recordings into notes with an unbroken chain of custody from audio to claim. Use when the user has recordings or audio to transcribe or summarize, or when an existing transcript or auto-summary reads as garbled or untrustworthy.

0Productivity

Install

git clone https://github.com/ooiyeefei/ccc.git ~/.claude/skills/scribe

What is scribe?

Turn meeting recordings into notes with an unbroken chain of custody from audio to claim. Use when the user has recordings or audio to transcribe or summarize, or when an existing transcript or auto-summary reads as garbled or untrustworthy.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~60 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

A summariser cannot hear. Hand it a garbled span and it launders the noise into a clean fact — "some paying customer" becomes "~8,000 users" — and nothing downstream can separate that from a real figure. This skill holds a chain of custody: every claim in the notes traces back to audio the model actually heard well, and a claim whose custody is broken says so.

Scripts are in scripts/. They need a Python with httpx; --provider local also needs faster-whisper.

1. Establish the recording's context

Ask the user, or read it off the surrounding material — the files, the repo, an existing transcript:

  • Language — the ISO code to pin. Left unpinned, per-window detection flaps on code-switched speech and the decoder emits fluent, confident text in the wrong language.
  • Speakers — how many, plus names and roles.
  • Domain vocabulary — product names, people, companies, jargon, currencies.

Done when you can state the language code, the speaker count, and at least five domain terms.

2. Transcribe

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

claude-mem

Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More

88.9K stars

obsidian-skills

Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.

43.6K stars

command-development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs gu

32.8K stars

Subagents

All subagents →

patch-generator

Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.

32.8K stars

claude-security

The dedicated Claude Security orchestrator. Hand it an unattended job — "fully scan this repository and patch what you find; I understand it will use a lot of tokens" — and it runs the whole thing itself: capturing the revision, driving the multi-agent scan through the claude-security:scan workflow,

32.8K stars

patch-verifier

The single verifier per fix round — reviews the workspace's staged diff against the finding, runs the tests, and states the three confidence claims a patch file must earn; dispatched by the fix job, not for direct invocation.

32.8K stars