Javdb Cli Docs logo

Javdb Cli Docs

Community
FlanChanXwO
javdb-cli-docs

Edit javdb-cli public or maintainer documentation, repository agent contracts, maintenance skills, and the distributed operator skill. Use after changes to CLI/SDK behavior, configuration, architecture, test commands, PR policy, or publication workflows.

Overview

PublisherFlanChanXwO
Repositoryjavdb-cli
Skill namejavdb-cli-docs
Stars
76
Forks
15
Bundled files
1
LicenseMIT
Links
  • 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 Docs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/FlanChanXwO/javdb-cli/tree/main/.agents/skills/javdb-cli-docs
  4. 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.
2

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-docs .claude/skills/javdb-cli-docs
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Javdb Cli Docs 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 Docs 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 Docs 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 Documentation

Read AGENTS.md and the documentation guidelines. Establish behavior from the relevant implementation/tests and workflow before writing it down; do not copy Pixiv-specific layers, tooling, authentication, or release semantics.

Update the actual owner: README for entry/install, locale CLI/SDK pages for public contracts, docs/maintainers/ for engineering details, and .agents/skills/ for task workflows. Keep root agent instructions short with precise routes. Public English/Simplified Chinese pages describe the same behavior; maintainer agent instructions, both skill trees, references, and UI metadata are English.

For CLI changes, verify arguments, number versus internal-ID semantics, output modes/cardinality, batch errors, authentication, and side effects. Preserve the asset stream's separate contract. Explain optional probe metadata and partial failures without inventing success. Read code or help before changing default-host or retry claims.

Maintenance skill names start with javdb-cli-; the distributed product skill remains javdb-cli. Keep descriptions task-specific and workflows usable through direct file reading without global skills. Product bundles must work outside a checkout: include required references and use official public URLs rather than broken repository-relative links.

Do not invent mandatory PR release-note fields or changelog fragments. Ordinary PRs state changes, verification and the current checklist; only authorized release preparation changes versioned bilingual notes and skill versions. Do not publish a skill merely because its instructions changed.

Validate metadata, local links, referenced files and commands, and English skill text. Read the result as a fresh contributor with no CCS setup. Run git diff --check and relevant existing script/tool checks; no separate documentation test framework is required. Root instructions are not automatically docs-only according to CI's path policy. Report the checks actually performed, not a claimed application regression run.

Bundled files

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

Frequently asked questions

What does the Javdb Cli Docs AI skill do?

Edit javdb-cli public or maintainer documentation, repository agent contracts, maintenance skills, and the distributed operator skill. Use after changes to CLI/SDK behavior, configuration, architecture, test commands, PR policy, or publication workflows.

Why use Javdb Cli Docs on TypingMind?

Because you install it once and use it with any model. Javdb Cli Docs 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 Docs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FlanChanXwO/javdb-cli/tree/main/.agents/skills/javdb-cli-docs. 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 Docs?

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 Docs?

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

Is the Javdb Cli Docs 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇