Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.
日本語の概要は準備中です。原文の説明を表示しています。
managedcode/dotnet-skills4852026年10月10日 更新
無料GitHub で公開
libvlc
Expert knowledge of the libvlc C API (3.x and 4.x), the multimedia framework behind VLC media player. Use when helping with LibVLC or LibVLCSharp for media playback, streaming, or transcoding. USE FOR: LibVLC Skill implementation, review, migration, debugging, or documentation work. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
インストール方法を見る含まれるファイル（3）
- SKILL.md3.3 KB
- libvlc-skill.md136.7 KB
- manifest.json120 B
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
LibVLC Skill
You are an expert assistant for developers using libvlc (both 3.x and 4.x), the multimedia framework behind VLC media player. You help with API usage, code generation, debugging, and architecture decisions across all supported languages and platforms.
Version markers
Throughout the reference, inline markers indicate version-specific APIs:
- No marker — same in both 3.x and 4.x
[3.x]— only in libvlc 3.x (removed in 4.x)[4.x]— new in libvlc 4.x[4.x change]— exists in both but signature changed
When generating code, ask the user which version they target if not already clear from context.
Reference
For complete API signatures, code examples, language bindings, platform integration, streaming recipes, troubleshooting, and migration guidance, see libvlc-skill.md.
Workflow
- Confirm whether the target is libvlc 3.x or 4.x, then choose APIs and bindings that match that version.
- Identify the active integration surface: C API, LibVLCSharp, vlcj, mobile, desktop, streaming, transcoding, or plugin discovery.
- Load libvlc-skill.md only for the relevant API area instead of copying the whole reference into the answer.
- Validate media lifecycle, threading, native library loading, logging, and disposal behavior before treating playback bugs as codec issues.
Validate
- the libvlc major version is explicit
- native libraries and plugins are discoverable in the target runtime
- event callbacks do not block libvlc worker threads
- media, player, and instance objects are disposed in the correct order
Sections in the reference:
- §1 Architecture Overview — pipeline, object model, single-instance rule
- §2 Core Concepts — lifecycle, threading rules, event system, error handling, logging, plugin discovery
- §3 API Reference — instance, media, media player, media list, events, dialog, discoverer, renderer, VLM, tracklist, program, GPU rendering, A-B loop, picture API
- §4 Language Bindings — C, C#/LibVLCSharp, Python, Java/vlcj, Go, C++/libvlcpp
- §5 Common Workflows — playback, metadata, thumbnails, playlists, Chromecast, transcoding, streaming, recording, track selection, mosaic, mobile lifecycle
- §6 Platform Integration — Windows (Win32, WPF, WinForms, D3D11), macOS/iOS, Linux (GTK, wxWidgets), Qt, Android, Avalonia
- §7 Streaming & Transcoding — sout chains, protocols, Chromecast
- §8 Troubleshooting — deadlocks, no audio/video, memory leaks, common pitfalls
- §9 CLI Options
- §10 Deprecated APIs
- §13 Migration Guide (3.x → 4.x) — signature changes, removed APIs, new APIs, type changes
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. USE FOR: the repo needs a root .editorconfig; analyzer severity and style ownership are unclear; the team wants one source of truth for rule configuration. DO NOT USE FOR: choosing analyzers with no config change; formatting-only execution with no config ownership question. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
managedcode/dotnet-skills4852026年10月10日 更新
Scans .NET code for ~50 performance anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I/O with tiered severity classification. Use when analyzing .NET code for optimization opportunities, reviewing hot paths, or auditing allocation-heavy patterns.
日本語の概要は準備中です。原文の説明を表示しています。
managedcode/dotnet-skills4852026年10月10日 更新
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app crash from a tombstone, resolving native backtrace frames in libmonosgen-2.0.so or libcoreclr.so to .NET runtime source code, or investigating SIGABRT, SIGSEGV, or other native signals originating from the .NET runtime on Android. DO NOT USE FOR pure Java/Kotlin crashes, managed .NET exceptions that are already captured in logcat, or iOS crash logs. INVOKES Symbolicate-Tombstone.ps1 script, llvm-symbolizer, Microsoft symbol server.
日本語の概要は準備中です。原文の説明を表示しています。
managedcode/dotnet-skills4852026年10月10日 更新
Symbolicate .NET runtime frames in Apple platform .ips crash logs (iOS, tvOS, Mac Catalyst, macOS). Extracts UUIDs and addresses from the native backtrace, locates dSYM debug symbols, and runs atos to produce function names with source file and line numbers. Automatically downloads .dwarf symbols from the Microsoft symbol server using Mach-O UUIDs. USE FOR triaging a .NET MAUI or Mono app crash from an .ips file on any Apple platform, resolving native backtrace frames in libcoreclr or libmonosgen-2.0 to .NET runtime source code, retrieving .ips crash logs from a connected iOS device or iPhone, or investigating EXC_CRASH, EXC_BAD_ACCESS, SIGABRT, or SIGSEGV originating from the .NET runtime. DO NOT USE FOR pure Swift/Objective-C crashes with no .NET components, or Android tombstone files. INVOKES Symbolicate-Crash.ps1 script, atos, dwarfdump, idevicecrashreport.
日本語の概要は準備中です。原文の説明を表示しています。
managedcode/dotnet-skills4852026年10月10日 更新
Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering. USE FOR: .NET architecture choices; layer and domain boundary review; service decomposition; clean architecture, vertical slice, DDD, CQRS, and modular monolith decisions. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
managedcode/dotnet-skills4852026年10月10日 更新