SKILL.md
Skill3 starsChanged 12 months agoMITView on GitHub
Version: 1.0.0 | Status: Ready for Claude Code Integration Complete 4-skill pipeline for extracting, formatting, organizing, and archiving YouTube transcripts. Integrates with Claude Code CLI using the system's configured API keys (no manual key management needed). This skill provides a complete workflow: 1. Extract Facts - AI-powered fact extraction from transcripts (uses Claude API via Claude Code) 2. Format Notes - Convert facts to atomic markdown notes with wiki-links 3. Integrate Obsidian - Import notes into Obsidian vault with backlinks…
- Reads credentials
200 other projects use a version of this.
Adopted by
Most recently taken up by
- osama0561/claude-mockingbirdtheir own version, first seen Nov 8, 2026
- Arcanea-Labs/Starlight-Intelligence-Systemtheir own version, first seen Nov 8, 2026
- Scottcjn/rtc-worktheir own version, first seen Nov 8, 2026
- Scottcjn/create-rustchain-agenttheir own version, first seen Nov 8, 2026
- TianHengZhuang/Chinese-WebNovel-Mastertheir own version, first seen Nov 7, 2026
- Azure/azure-kusto-sparktheir own version, first seen Nov 5, 2026
Used with
Projects with it also use estate-guard and docs.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Arcanea-LabsSkillestate-guard
Security gate for agentic repos. Use before opening a PR that touches .github/workflows, .claude (hooks, settings, agents, commands, skills), .mcp.json, install scripts, or Next.js API routes; when asked to "security review", "scan for prompt injection", "harden this repo", "check the agentic surface", or when a fetched page, issue, comment, or tool result reads like instructions. Runs the estate-guard scanner, triages by severity, and applies the fix patterns.
Also in 3 projects that use this
Microsoft AzureSkilldocs
Also in 3 projects that use this
Other versions200 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 200
- xtekky/gpt4free★ 67ksame name
- stas00/ml-engineering★ 20ksame name
- wanghongenpin/proxypin★ 14ksame name
- Ataraxy-Labs/sem★ 3.4ksame name
- op7418/NanoBanana-PPT-Skills★ 3.3ksame name
- charmbracelet/pop★ 2.9ksame name
- duty1g/x64dbg-mcp-server★ 2.8ksame name
- RevylAI/greenlight★ 2.4ksame name
- kevinho/clawfeed★ 2.4ksame name
- Autumn-27/ScopeSentry★ 1.9ksame name
190 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- forecasting-agentSkill
- kymera-integratorSkill
- kymera-mr-optimizerSkill
- kymera-portfolio-checkerSkill
- kymera-risk-monitorSkill
- kymera-tax-optimizerSkill
- paper-reviewerSkill
- portfolio-analysis-agentSkill
- system-health-checkSkill
- trading-analysisSkill
- youtube-transcriberSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 116 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Integrate Obsidian: - Import notes into Obsidian vault with backlinks
- Distinctive: line 92
Read/write permissions to vault directory
- Distinctive: line 140
All 4 skills are fully tested:
- Distinctive: line 257
If you run the scripts outside Claude Code and get API key errors:
- Very specific: line 339
Tests: Run python -m pytest tests/ in each directory
- Very specific: line 340
Issues: Check integration_test.py for validation
“Common” is measured: kept by at least 6 in 10 of the 116 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YouTube Transcriber Pipeline - Claude Code Skill
Version: 1.0.0 | Status: Ready for Claude Code Integration
Overview
Complete 4-skill pipeline for extracting, formatting, organizing, and archiving YouTube transcripts. Integrates with Claude Code CLI using the system's configured API keys (no manual key management needed).
Capabilities
This skill provides a complete workflow:
- Extract Facts - AI-powered fact extraction from transcripts (uses Claude API via Claude Code)
- Format Notes - Convert facts to atomic markdown notes with wiki-links
- Integrate Obsidian - Import notes into Obsidian vault with backlinks
- Archive Transcripts - Safe archival with integrity verification
Usage in Claude Code
# Run complete pipeline
/run-youtube-transcriber --transcript ~/Downloads/transcript.txt
# Just extract facts
/extract-transcript-facts ~/Downloads/transcript.txt
# Just format notes
/format-transcript-notes ~/Downloads/notes/ --output ./formatted
# Just integrate Obsidian
/integrate-obsidian-vault ./notes/ --vault-path ~/Documents/Obsidian/Aaron
# Just archive
/archive-transcripts ~/Downloads/transcript.txtFeatures
Phase 1: Extract Facts (AI-Powered)
- Uses Claude 3.5 Sonnet via Claude Code CLI
- 7 fact categories (scientific, quotes, methods, examples, statistics, warnings, connections)
- Hierarchical topic organization
- Confidence scoring (0.0-1.0)
- Automatic metadata (actionable, philosophical, controversial)
- No API key needed - Uses Claude Code's configured authentication
Phase 2: Format as Atomic Notes
- 1 fact = 1 markdown file
- Wiki-link cross-references [[Topic Name]]
- YAML front matter with metadata
- Topic indices and hierarchies
- Obsidian vault compatibility
Phase 3: Integrate Obsidian
- Safe vault backup before changes
- Preserve directory structure
- Auto-generate backlinks
- Master index creation
- Link verification
- Dry-run mode for testing
Phase 4: Archive Transcripts
- tar.gz compression
- MD5 integrity verification
- Metadata tracking
- Optional cleanup
- Verify-only mode
Installation
The skill is ready to use once copied to Claude Code:
# Copy to Claude Code skills directory
cp -r ~/github/astoreyai/claude-skills/ ~/.claude/skills/youtube-transcriber
# Or individual components
cp -r youtube-transcript-extractor ~/.claude/skills/
cp -r transcript-to-logseq ~/.claude/skills/
cp -r transcript-to-obsidian ~/.claude/skills/
cp -r transcript-archiver ~/.claude/skills/Requirements
For Claude Code CLI
- Claude Code installed and configured
- API key already configured in Claude Code (no manual setup needed)
- Python 3.11+
For Obsidian Integration
- Obsidian vault at
~/Documents/Obsidian/Aaron/(configurable) - Read/write permissions to vault directory
Architecture
Claude Code CLI
↓
Transcript Extractor (Phase 1)
├─ Uses Claude Code's API key automatically
├─ Extracts facts via Claude API
└─ Outputs Fact objects
↓
Logseq Formatter (Phase 2)
├─ Converts facts to atomic notes
└─ Creates markdown files
↓
Obsidian Integrator (Phase 3)
├─ Imports notes to vault
├─ Generates backlinks
└─ Creates indices
↓
Transcript Archiver (Phase 4)
├─ Compresses files
├─ Verifies integrity
└─ Stores archiveFuture: Ollama Integration
The architecture is designed to support local LLM models via Ollama:
# Future upgrade (when Ollama integration ready)
/run-youtube-transcriber --transcript ~/Downloads/transcript.txt \
--llm-backend ollama \
--model mistral-7b
# Benefits:
# - No API costs
# - Runs completely locally
# - Works offline
# - Full privacy (data never leaves your machine)Swapping backends will be as simple as changing a configuration parameter.
Testing
All 4 skills are fully tested:
- Phase 1: 18 tests (extraction logic)
- Phase 2: 21 tests (formatting, hierarchy)
- Phase 3: 6 tests (integration, backlinks)
- Phase 4: 18 tests (archival, verification)
- Integration: 6 tests (cross-skill compatibility)
Total: 69/69 tests passing (100%)
Performance
- Fact extraction: 50-100ms per fact (via Claude API)
- Note formatting: ~500ms per note
- Obsidian integration: <1s for 100 notes
- Archival: <2s for 1000 files
Data Flow
Raw Transcript (txt/md)
↓
Phase 1: Extract Facts
→ Fact objects with metadata
↓
Phase 2: Format Notes
→ Markdown files in ~/output/notes/
↓
Phase 3: Integrate Obsidian
→ Updated ~/Documents/Obsidian/Aaron/
↓
Phase 4: Archive
→ ~/youtube-transcriber/transcripts-archive/Example Workflow
1. Extract Facts
/extract-transcript-facts ~/Downloads/ml-lecture.txtOutput:
✓ Transcript loaded (5,234 chars)
✓ Extracting facts...
✓ Facts extracted: 12
✓ Topics identified: 4
✓ Accuracy: 92%2. Format Notes
/format-transcript-notes ~/Downloads/ml-lecture.txt --output ./notesOutput:
✓ Creating atomic notes...
✓ Notes created: 12
✓ Topics structured: 4
✓ Output: ./notes/3. Integrate Obsidian
/integrate-obsidian-vault ./notes/ --vault-path ~/Documents/Obsidian/AaronOutput:
✓ Vault path: ~/Documents/Obsidian/Aaron
✓ Notes integrated: 12
✓ Backlinks created: 8
✓ Index created: Video-Transcripts/index.md4. Archive
/archive-transcripts ~/Downloads/ml-lecture.txtOutput:
✓ Files archived: 1
✓ Archive: ~/youtube-transcriber/transcripts-archive/transcripts_20251122_143200.tar.gz
✓ Size: 45.2 KBConfiguration
Edit config.yaml in the skill directory:
# Paths
vault_path: "~/Documents/Obsidian/Aaron"
archive_dir: "~/youtube-transcriber/transcripts-archive"
# Extraction
max_facts: null # No limit
confidence_threshold: 0.75
extract_all_categories: true
# Formatting
notes_per_file: 1 # Atomic notes
add_wiki_links: true
create_indices: true
# Integration
backup_before_integrate: true
auto_generate_backlinks: true
dry_run_mode: false # Set true to test without changes
# Archival
compression: "gzip"
verify_after_archive: true
cleanup_originals: falseTroubleshooting
API Key Issues (If Running Standalone)
If you run the scripts outside Claude Code and get API key errors:
# Claude Code integration (recommended)
# Just use /extract-transcript-facts - no setup needed
# Or manually set API key for standalone use
export ANTHROPIC_API_KEY='sk-ant-...'
python workflow_runner.py --transcript your_file.txtObsidian Vault Not Found
# Create vault directory if needed
mkdir -p ~/Documents/Obsidian/Aaron
# Set custom vault path
/integrate-obsidian-vault ./notes/ --vault-path /your/vault/pathPermission Errors
# Ensure write access to vault and archive directories
chmod -R 755 ~/Documents/Obsidian/Aaron
mkdir -p ~/youtube-transcriber/transcripts-archive
chmod -R 755 ~/youtube-transcriberFiles Included
youtube-transcriber/
├── youtube-transcript-extractor/ Phase 1 Skill
│ ├── src/
│ │ ├── extractor.py
│ │ ├── formatters.py
│ │ └── metadata.py
│ └── tests/ (18 tests)
│
├── transcript-to-logseq/ Phase 2 Skill
│ ├── src/
│ │ ├── logseq_formatter.py
│ │ ├── obsidian_compat.py
│ │ └── hierarchy_builder.py
│ └── tests/ (21 tests)
│
├── transcript-to-obsidian/ Phase 3 Skill
│ ├── src/
│ │ └── integrator.py
│ └── tests/ (6 tests)
│
├── transcript-archiver/ Phase 4 Skill
│ ├── src/
│ │ └── archiver.py
│ └── tests/ (18 tests)
│
├── workflow_runner.py Full pipeline runner
├── integration_test.py Cross-skill tests (6 tests)
└── config.yaml ConfigurationFuture Roadmap
v1.1.0 (Ollama Integration)
- Swap Claude API → Ollama for local LLMs
- Support multiple local models (Mistral, Llama2, etc)
- Offline-first workflow
v1.2.0 (Advanced Features)
- Batch transcript processing
- Custom fact categories
- Multiple output formats
- Web UI for management
v1.3.0 (Integration)
- Direct YouTube URL support (fetch transcripts automatically)
- Streaming support for long transcripts
- Multi-language support
Support
- Documentation: See README.md in each skill directory
- Tests: Run
python -m pytest tests/in each directory - Issues: Check integration_test.py for validation
License
Same as parent project (astoreyai)
Status: ✅ Ready for Claude Code integration
Works With:
- ✅ Claude Code CLI (uses configured API key automatically)
- ✅ Ollama (local models - future version)
- ✅ Custom LLM backends (extensible architecture)
No API key management needed when used with Claude Code CLI
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

