SkillFoxx

vBook Extensions skill

A skill that creates, fixes, tests and packages extensions for the vBook reader through a CLI and the phone developer server.

  • 113 ★ on the repository
  • Last commit
Skill

Extended access

Why this level

  • The skill runs Node scripts that test, build and install extensions on a phone over the local network.
  • Extensions send requests to third-party sites.
All reasons and checks

darkrai9x/vbook-extensionsAuthor:Darkrai9x

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/vbook-extensions

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The skill runs Node scripts that test, build and install extensions on a phone over the local network.
  • Extensions send requests to third-party sites.

This is third-party code. Review the repository files before installing.

What it does

vBook Extensions is an Agent Skills skill for developing extensions for the vBook reader. It covers creating a new extension, fixing, testing, auditing, refactoring, building and installing against the current engine API and the ScriptExecutor runtime. Work runs in modes: `create` for a new extension or a bare source URL, `fix` for a domain, selector or API version change, `test` for checking one script, `audit` for a repository-wide or chosen-subset scan and `refactor` for template alignment without behavior changes. Build and install need no mode, only the CLI reference. Test, build and install go only through `scripts/vbook.js`: the commands `connect`, `test`, `testall`, `build` and `install` talk to the developer server in the vBook phone app over the local network. Codex, Gemini CLI, Cursor and GitHub Copilot pick up the skill automatically, and Claude Code uses a compatibility entry.

Who it is for. Developers of vBook extensions who want to delegate site parser creation and phone-side testing to an agent.

Good fit when

  • You need to write an extension for a new book site from its URL.
  • A site changed its domain or layout and the script stopped returning chapters.
  • You need to run all repository extensions quickly and find breakages.
  • A finished extension must be packed into `plugin.zip` and installed on the phone.

Not a fit when

  • You need to develop plugins for something other than vBook.
  • The phone and computer are not on the same network and the developer server is unreachable.
  • The goal is bypassing paid access or protection of someone else's site.

Example request

Use the vbook-extensions skill to fix the mangadex extension: run tests on the phone and correct the selectors.

Limitations

Tests need a phone with the vBook app in developer mode and a computer on the same local network, plus Node.js for `scripts/vbook.js`. The mode is enabled by tapping the version number seven times in the app. The skill does not build, install or publish anything without explicit permission. Extensions parse third-party sites, so those sites' terms and copyright remain the user's responsibility. The repository declares no license, and the extension docs are written in Vietnamese.

How to disable. Delete the `.agents/skills/vbook-extensions` folder and the compatibility entry `.claude/skills/vbook-extensions` from the repository. Extensions installed on the phone are removed in vBook itself.

FAQ

How do I enable the developer server?

In the vBook app tap the version name seven times, enable developer mode and note the shown address and port, for example http://192.168.1.10:8080.

Which commands does the CLI have?

`connect`, `test <extension> <script> [args]`, `testall [extensions]`, `build <extension> [output.zip]` and `install <extension>`, run through `node .agents/skills/vbook-extensions/scripts/vbook.js`.

Can I debug scripts without an agent?

Yes, the repository holds the VS Code extension vBook Tester (`vbook-vscode-tester-0.0.5.vsix`), which runs a script on the phone and shows the response and log.

How do I call the skill by name?

Name it in the request, for example "Use the vbook-extensions skill on the mangadex extension". Codex, Gemini CLI, Cursor and Copilot find it in `.agents/skills`.

Where is the extension API contract described?

In `extension-api.md` at the repository root and in its copy under the skill `reference`; both versions must stay identical.

Discussion

No questions or reviews yet.

Skills

A skill with scripts for building iOS apps and driving the simulator through the accessibility tree, with compact output for agents

SkillExtended access1.3K

mobilecli drives iOS and Android devices, emulators and apps from the terminal, and its skill teaches Claude Code how to use it

CLIBroad access317

21 skills for Android and KMP in Claude Code, Codex and Copilot CLI: Compose, coroutines, Flow, networking, storage, Gradle

PluginMinimal access173

Skills and a CLI that let Claude Code, Codex and OpenCode operate an Android phone: open apps, tap, type and test workflows

SkillBroad access1.8K

A Claude Code skill that builds Expo mobile apps with onboarding, paid subscriptions, AdMob ads, analytics and localization.

SkillExtended access114

README in short

The repository holds the extensions in `src`, the skill in `.agents/skills`, developer server docs and a VS Code debugging guide. The skill is the main source of guidance for working on extensions.

README badge

Original SKILL.md

---
name: vbook-extensions
description: Create, fix, test, audit, refactor, build, or install vBook extensions against the current engine API and ScriptExecutor runtime. Use for extension source, plugin.json, vBook REST testing, packaging, or installation.
---

# vBook extensions

Canonical, vendor-neutral skill for this repository. Resolve every linked path relative
to this file. `.claude/skills/vbook-extensions/SKILL.md` is only a compatibility pointer;
never duplicate this skill there.

## Route the task

Read exactly one matching mode when source work or testing is requested:

- New extension or bare source URL → [CREATE](modes/create.md).
- Repair, domain/selector change, API migration, or feature change → [FIX](modes/fix.md).
- Read-only test of one extension/script → [TEST](modes/test.md).
- Repo-wide or named-subset health scan → [AUDIT](modes/audit.md).
- Behavior-preserving template alignment → [REFACTOR](modes/refactor.md).

Build/install-only requests need no mode: read [CLI](reference/cli.md), inspect the
target manifest, then perform only the requested operation. If the request is ambiguous
and the choice would change behavior, ask.

## Load only what the task needs

- Before creating or editing JavaScript/`plugin.json`, read
  [Runtime rules](reference/runtime.md) and the relevant portions of
  [extension-api.md](reference/extension-api.md).
- For type-specific fields/chains, read [Type contracts](reference/type-contracts.md).
- Before any test/build/install, read [CLI](reference/cli.md).
- When judging script output, use [Verify checklist](reference/verify-checklist.md).
- Templates live under `templates/<type>/`; use only the selected type. Replace all
  placeholders and remove teaching comments before shipping.

The repo-root `extension-api.md` and `reference/extension-api.md` are the same current
contract. Keep them identical; when the contract changes, update both, then the
affected guidance and templates.

## Non-negotiable invariants

- Test, build, and install only through `scripts/vbook.js`; do not use MCP endpoints or
  hand-built REST payloads.
- Never infer permission to build, install, commit, push, delete, or publish from a

Report a problem