novel-check

Tests LLM provider connectivity with minimal real Generate calls per configured model.

116|21|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/Xiaoyangy/novel-studio --skill novel-check-xiaoyangy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: novel-check
Source: https://github.com/Xiaoyangy/novel-studio/tree/main/skills/novel-check
Command: npx skills add https://github.com/Xiaoyangy/novel-studio --skill novel-check-xiaoyangy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before starting a long novel-generation run, a misconfigured provider (stopped local proxy, expired API key, wrong base_url) only surfaces when the first real call fails. This Skill runs a minimal real Generate round-trip against the default model and every role model (coordinator / architect / writer / editor), reporting per-target availability so configuration problems are caught before writing begins. ## Core Features & Use Cases - Per-target connectivity check: Deduplicates by provider/model and pings each target once, reporting latency or the exact error for both primary and configured fallback models. - Per-role availability summary: Reports whether each named role is usable, degraded to fallback, or fully down, with a non-zero exit code when any role has no working path. - Ad-hoc provider validation: Test a spare provider/model pair without changing configuration to confirm it can serve as a fallback. - Use Case: Before launching a multi-chapter generation pipeline, run the check to discover that the local proxy for one provider is not running, fix the base_url, and confirm all roles pass. ## Quick Start Ask the assistant to run the novel-studio connectivity self-check to verify that the default model and all role models are reachable before starting creation.

Frequently Asked Questions about novel-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test LLM API connectivity before running a generation pipeline?

Run the novel-studio check command, which sends one minimal real Generate request per unique provider/model target. It reports success with latency or the exact failure reason for each target, including configured fallbacks.

How do I verify a fallback model works without changing my config?

Pass the provider and model flags to the check command to test a spare provider directly. This confirms whether a candidate fallback is reachable before you add it to your role configuration.

Why does the LLM check fail with connection refused?

A connection refused error means the base_url for that provider points to a service that is not running, such as a local proxy. Start the proxy service or correct the base_url in the configuration, then rerun the check.

What does a 401 or invalid api key error mean during connectivity testing?

A 401 response means the api_key configured for that provider is expired or mistyped. Update the key in the configuration and rerun the check to confirm the provider authenticates successfully.

Can I adjust the timeout for slow LLM providers?

Yes, the check accepts a timeout flag that overrides the default 30-second limit per call. Increase it, for example to 60 seconds, when testing providers with higher latency.