Javdb Cli Media

Community

FlanChanXwO

javdb-cli-media

Develop or review javdb-cli media assets, image decoding, HLS decryption, TS/MP4 remuxing, streaming probes, and no-replace file publication. Use for asset/download correctness, media corruption, memory regressions, or transport changes; not for full-movie or magnet downloading.

Overview

Publisher	FlanChanXwO
Repository	`javdb-cli`
Skill name	`javdb-cli-media`
Stars	76
Forks	15
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by FlanChanXwO on GitHub. Read the source before you install it.

Installation

Install the Javdb Cli Media AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/FlanChanXwO/javdb-cli/tree/main/.agents/skills/javdb-cli-media
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/FlanChanXwO/javdb-cli.git /tmp/javdb-cli
mkdir -p .claude/skills
cp -r /tmp/javdb-cli/.agents/skills/javdb-cli-media .claude/skills/javdb-cli-media

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Javdb Cli Media in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Javdb Cli Media on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Javdb Cli Media is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Maintain javdb-cli Media

Read AGENTS.md, internal/cli/commands/assets, the public asset SDK methods, and the affected files in internal/javdb/appapi/media. Trace the real path before choosing a fix. Keep CLI selection/presentation separate from SDK/media transfer and validation.

Preserve the contract

assets list applies selectors before optional streaming metadata probes. Probe failures can leave optional width/height/duration absent; do not confuse that documented result with a successfully downloaded asset.
Piped list output is TYPE<TAB>URL, not javdb.pipeline/v1. assets download consumes that stream; -d generates names, -o accepts exactly one asset, and successful stdout lists final paths only.
Images must be decoded/validated after any required XOR restoration. HLS processing owns playlist, key, IV, padding, segment, media-model, and final-container integrity. Never publish encrypted, truncated, or partially verified bytes as success.
Preserve the supported MP4 H.264/AAC-LC, PID, ADTS-block, and mono/stereo constraints in the current parser and tests. TS-preservation mode has a different contract; do not impose MP4-only restrictions on it. Timed ID3 is not an MP4 audio track.
Keep no-replace atomic publication and cleanup: existing targets survive, partial files remain private and are removed on failure, and cancellation is distinguishable from corruption. Cross-filesystem and permission errors must remain visible.
Spooling reduces retained payload, but the implementation still keeps the current PES and sample metadata. Do not claim constant memory without measurement, or add buffering limits based on a guessed file size.

Test before changing behavior

Create the smallest complete synthetic fixture that reproduces the defect; run it and observe the expected failure. Use existing media test builders rather than downloaded production media or a new codec dependency. Then implement the narrow correction and run related media, SDK, and CLI asset tests.

Depending on the change, cover valid and corrupt image input, playlist/key/IV handling, missing or malformed segments, timestamp normalization, sample boundaries, repeated track changes, cancellation, short writes, existing targets, and cleanup. Select cases from the actual failure/contract, not every imagined format combination. Assert produced media semantics and status, not exact internal function order.

For transport/probe/concurrency changes, run the relevant race checks and show request count/order or measured memory evidence where that is the requirement. A local remux fixture is not proof of a live upstream preview; live requests require separate authorization and must not leak signed URLs or keys.

Finish

Use javdb-cli-test and javdb-cli-review, then update the affected SDK/CLI documentation and product skill. Keep the supported thumbnail/preview scope explicit. Do not add transcoding, ffmpeg, full-movie downloading, or a new background service as an incidental fix.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Javdb Cli Media AI skill do?

Why use Javdb Cli Media on TypingMind?

Because you install it once and use it with any model. Javdb Cli Media is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Javdb Cli Media in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FlanChanXwO/javdb-cli/tree/main/.agents/skills/javdb-cli-media. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Javdb Cli Media?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Javdb Cli Media?

As many as you like. As long as a model supports skills, you can use Javdb Cli Media with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Javdb Cli Media AI skill free?

Yes. It is published on GitHub by FlanChanXwO under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Hyperframes

nexu-io

OrganizationPopular

Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML. Use when asked to build any HTML-based video…

Audio Jingle

Audio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or…

Proof Video

Add subtitles, captions, narration cues, or zoom to a proof video or PR recording using repo-local capture helpers and a system ffmpeg renderer.

Facetime

Inspect FaceTime internal stages, place an approved call to a configured owner handle, and request hangup through facetime_call.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Maintain javdb-cli Media

Preserve the contract

Test before changing behavior

Finish

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now