メニュー
Use when the user wants to turn one or more Bilibili video URLs into Markdown notes with the external BiliNote repository, without starting the frontend/backend web services.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | bilinote-video-note |
| description | Use when the user wants to turn one or more Bilibili video URLs into Markdown notes with the external BiliNote repository, without starting the frontend/backend web services. |
这是一个 thin wrapper。真正的运行时代码位于外部 WncFht/BiliNote 仓库中；本 skill 只保留调用说明和轻量路径解析脚本。
优先级：
--backend-root / --repo-rootBILINOTE_BACKEND_ROOT、BILINOTE_REPOrepo:WncFht/BiliNote$HOME/Desktop/src/BiliNote/backend、$HOME/Desktop/src/BiliNote解析示例：
python scripts/resolve_bilinote_paths.py --json
只打印 backend 根目录：
python scripts/resolve_bilinote_paths.py --print backend_root
BILINOTE_OUTPUT_DIR，若未设置则回退到 $HOME/Desktop/obsidian/视频detailedBACKEND_ROOT="$(python scripts/resolve_bilinote_paths.py --print backend_root)"
OUTPUT_DIR="${BILINOTE_OUTPUT_DIR:-$HOME/Desktop/obsidian/视频}"
uv run --project "$BACKEND_ROOT" bilinote-cli "<BILIBILI_URL>" --output "$OUTPUT_DIR"
批量处理：
BACKEND_ROOT="$(python scripts/resolve_bilinote_paths.py --print backend_root)"
OUTPUT_DIR="${BILINOTE_OUTPUT_DIR:-$HOME/Desktop/obsidian/视频}"
uv run --project "$BACKEND_ROOT" bilinote-cli \
"<BILIBILI_URL_1>" "<BILIBILI_URL_2>" \
--jobs 2 \
--output "$OUTPUT_DIR"
.env、SQLite provider、模型配置和本地转录能力BiliNote 仓，或设置 BILINOTE_REPO / BILINOTE_BACKEND_ROOTUse as the workspace-level entry skill for this repository when responses should follow BetterGPT defaults. This skill routes by default to BetterLanguage for language shaping, then applies task-specific enhancements only when needed, such as BetterFrontend for frontend presentation work, BetterVibe for full-stack engineering boundary and maintainability guidance, BetterTrellis for Trellis workflow, Codex soft integration, initialization, spec, task, and hooks-related guidance, and BetterSubagents for subagent delegation, orchestration, wait handling, and takeover guardrails. Use when a single main entry skill should coordinate default loading order and on-demand sub-skill activation.
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer MinerU API first for parsing/extraction, then use visual checks with Poppler and Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation or fallback extraction.
Use when generating, revising, polishing, or reviewing frontend UI, landing pages, dashboards, app screens, marketing pages, or other presentation-layer output that should look like a production-ready product instead of a demo, draft, wireframe, showcase, or developer-facing mockup. Especially use when the request mentions removing AI-like UI, avoiding demo feel, preventing TODO or note text, hiding reasoning or design commentary from users, eliminating placeholder explanations, or making the final interface feel shippable, real, and user-facing.
Use when GPT-5.4 style answers need to be rewritten into concise, natural Chinese with minimal filler, no internet slang or habitual phrasing, and a strict two-part structure that users can scan top-to-bottom at a glance. Especially use when the output should preserve two-part reasoning and solution flow without always printing rigid section titles, allow light line breaks for readability, remove translation-like Chinese, and switch to terminal-friendly rendering when the current surface is CLI or shell rather than an app-style chat surface.
Use when the task involves subagent selection, delegation strategy, parallel execution, wait and timeout handling, fallback takeover, or how to correctly use the project's local agents together with repository skills and MCP tools. Especially use when the user asks how to orchestrate explorer, worker, reviewer, docs-researcher, code-mapper, frontend-developer, browser-debugger, refactoring-specialist, or other local subagents, or when the main agent needs stronger delegation guardrails.
Use when working with Trellis in Codex, especially for soft integration, project initialization, workflow entry, spec and task organization, hooks, generated command structure, or reducing the need to remember Trellis commands manually. Use when the request mentions Trellis init, Codex integration, workflow, spec, task, workspace logs, hooks, update, onboarding, or agent command mapping.