Agent skill · Audited from source
bilibili-render-pdf
skill · wdkns/wdkns-skillsGPL-3.0 licenceAudited 21 Oct 2026 · source 2103bb7cb3cc
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 2103bb7cb3cc and found no filesystem, network or shell access and no hard-coded secrets. What it does: Generate a professional, detailed, figure-rich LaTeX course note and final PDF from a Bilibili lecture, tutorial, or technical talk. Use when the user provides a Bilibili URL (BV number) and wants structured Chinese…
Cite
Cite this page
ModelsAtlas. “bilibili-render-pdf (wdkns/wdkns-skills)”. Retrieved 21 Oct 2026. https://modelsatlas.com/skills/wdkns/bilibili-render-pdf
Trust audit
Audit 0.4.1 · source read 21 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 2103bb7cb3cc · 21 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherwdkns GitHub organizationOwner of the repository this skill is read from
- Source folderwdkns/wdkns-skills/skills/bilibili-render-pdfThe exact folder we audited
- LicenceGPL-3.0As the repository states it
- Commit pinned for this verdict2103bb7cb3ccA new audit runs when the source changes
- Repository statusNot archivedLast push 72 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Generate a professional, detailed, figure-rich LaTeX course note and final PDF from a Bilibili lecture, tutorial, or technical talk. Use when the user provides a Bilibili URL (BV number) and wants structured Chinese…
---
name: bilibili-render-pdf
description: Generate a professional, detailed, figure-rich LaTeX course note and final PDF from a Bilibili lecture, tutorial, or technical talk. Use when the user provides a Bilibili URL (BV number) and wants structured Chinese teaching notes that combine the video's title, chapters, diagrams, formulas, code, subtitle explanations, the original video cover on the front page, and a final synthesis chapter, with key frames extracted from the highest usable video resolution and inserted as figures, and where the final deliverable must include a rendered PDF. Falls back to Whisper speech-to-text when no CC subtitles are available.
---
# Bilibili Render PDF
Use this skill to turn a Bilibili video into a complete, compileable `.tex` note and a rendered PDF.
This skill extends the `youtube-render-pdf` workflow with Bilibili-specific adaptations for subtitle scarcity, login-gated high resolution, multi-part (分P) videos, and platform-specific non-teaching content.
## Bilibili vs YouTube: Key Differences
| Aspect | Handling |
|--------|----------|
| **Subtitle scarcity** | Try CC subtitles first → fall back to Whisper speech-to-text → visual-only mode |
| **Login-gated HD** | 1080P+ requires cookies; prompt the user to use `yt-dlp --cookies-from-browser chrome` |
| **Multi-part videos** | Detect 分P videos and ask the user which parts to process |
| **URL formats** | Support `bilibili.com/video/BVxxxxxxx` and `b23.tv` short links |
| **Danmaku** | Do not use danmaku as a teaching content source (too noisy); use only CC subtitles or Whisper output |
## Goal
Produce a professional Chinese lecture note from a Bilibili URL.
The output must:
- use the video's actual teaching content rather than subtitle transcription alone
- place the video's original cover image on the front page of the `.tex` and rendered PDF whenever available
- include all necessary high-value key frames as figures, without adding redundant screenshots
- end with a final synthesis section that includes the speaker's substantive closing discussion and your own distilled takeaways
- be structurally organized with `\section{...}` and `\subsection{...}`
- be a complete `.tex` document from `\documentclass` to `\end{document}`
- be compiled successfully to PDF as part of the final delivery
## Pedagogical Standard
The notes must read like a strong human teacher is guiding the reader through the material.
- organize each major section so the reader first understands the motivation, then the main idea, then the mechanism, then the example or evidence, and finally the takeaway
- be patient and explicit about logical transitions; make it clear why the speaker introduces a concept, what problem it solves, and how the next idea follows
- aim for deep-but-accessible explanations: keep the technical depth, but introduce formalism only after giving intuition in plain language
- when a section is dense, break it into smaller subsections that progressively build understanding rather than compressing everything into one long derivation
- do not dump subtitle content in chronological order; rewrite it into a teaching sequence with clear intent, contrast, and buildup
## Source Acquisition
### Metadata Inspection
1. Inspect the video metadata first.
Prefer title, chapters, duration, thumbnail availability, and subtitle availability before writing.
2. Detect multi-part (分P) videos.
List all parts and ask the user which parts to process before downloading.
### Subtitle Acquisition (Three-Level Fallback)
**Priority 1: CC subtitles (platform-embedded)**
Use manual subtitles over auto-generated subtitles when both are available.
Prefer `zh-Hans`, `zh-CN`, `zh`, or `ai-zh` subtitle tracks.
Preserve the subtitle timestamps; do not flatten subtitles into plain text too early if figures still need to be located.
```
yt-dlp --write-subs --sub-langs "zh-Hans,zh-CN,zh,ai-zh" --convert-subs srt \
--skip-download -o "%(title)s.%(ext)s" "<URL>"
```
**Priority 2: Whisper speech-to-text (when no CC subtitles are available)**
Extract audio first, then transcribe with Whisper to produce a timestamped SRT file.
```
yt-dlp -x --audio-format wav -o "audio.%(ext)s" "<URL>"
whisper audio.wav --model medium --language zh --output_format srt --output_dir .
```
**Priority 3: Visual-only mode (when audio quality is too poor)**
Skip subtitles entirely and rely on dense frame sampling to extract teaching content from the video frames alone.
### Video and Cover Download
1. Acquire the video's original cover image before writing the `.tex`.
Prefer the highest-resolution thumbnail exposed by the platform metadata.
Save the selected cover locally and reference that local asset from the front page.
2. Prefer the best usable video source for figure extraction.
Probe formats and choose the highest resolution that is actually downloadable in the current environment.
Note that 1080P+ on Bilibili typically requires login cookies.
3. Keep all source artifacts local when practical.
Typical working artifacts are metadata, the downloaded cover image, a timestamped subtitle file (CC or Whisper-generated), optional cleaned transcript text, a local video file, and extracted frames.
## Long Video Strategy
For longer videos, do not rely on a single monolithic pass.
- If the video is longer than 20 minutes, or the subtitle file contains more than 300 subtitle entries, split the work into smaller segments.
- Prefer chapter boundaries or 分P boundaries for splitting. If those are unavailable or too uneven, split by coherent time windows or subtitle ranges.
- When subagents are available, spawn multiple subagents in parallel for different segments so coverage stays high and detail is not lost.
- Give each subagent a concrete segment boundary and require it to return: the segment's teaching goal, the core claims, important formulas or code, required figures with time provenance, and any ambiguities that need integration-tiExcerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 2103bb7
git clone https://github.com/wdkns/wdkns-skills git -C wdkns-skills checkout 2103bb7cb3cc
The author documents no install command, so this uses the repository directly. Our verdict covers commit 2103bb7cb3cc only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
2103bb7cb3cc
Similar skills
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Questions about bilibili-render-pdf
Is bilibili-render-pdf safe to install?
What can bilibili-render-pdf access on my machine?
How current is this page?
Sources
- github.com/wdkns/wdkns-skills/tree/main/skills/bilibili-render-p — the audited source at commit 2103bb7cb3cc and every finding aboveObserved · 21 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- Is bilibili-render-pdf safe to install?
- What can bilibili-render-pdf access on my machine?
- How current is this page?