bili-rs

What This Skill Does

The bili-rs skill provides a comprehensive development environment for the bilibili-cli-rust project. It acts as an assistant for developers maintaining or extending this high-performance Rust CLI tool, which serves as a feature-parity rewrite of the original Python-based Bilibili command-line interface. The skill enforces strict architectural patterns to ensure the codebase remains maintainable, performant, and reliable, handling everything from API client management to terminal output formatting and CLI command definition.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/18621063286/bili-rs

Use Cases

• Implementing New API Endpoints: Add support for new Bilibili features by following the strict layer-based workflow, ensuring logic flows from CLI structs to client HTTP requests.
• Authentication Management: Handle SESSDATA and bili_jct credentials securely while implementing WBI request signing for protected Bilibili interfaces.
• CLI Refactoring: Update or extend command-line arguments using clap while strictly separating business logic from interface presentation.
• Output Formatting: Standardize data display across JSON, YAML, and formatted tables, ensuring compliance with the project's output envelope requirements.

Example Prompts

1. "Implement a new command to list user favorites that requires WBI signature, following the existing structure in src/client/user.rs."
2. "Refactor the command handling in src/commands/video.rs to correctly map the API error codes and utilize the existing formatter module."
3. "Help me add a new payload normalizer in src/payloads/dynamic.rs to parse the latest Bilibili dynamic feed JSON into our internal struct format."

Tips & Limitations

• Architecture: Always respect the separation of concerns. Never import CLI structs into the client layer; keep the client layer clean of any UI logic.
• Performance: As a Rust-based tool, avoid runtime dependencies. The binary must remain a single, lightweight executable.
• Error Handling: Use the defined map_api_error function in the client layer and ensure all errors are emitted to stderr.
• Quality Control: Before finalizing any code changes, ensure your implementation passes cargo clippy -- -D warnings and cargo fmt --check to maintain project coding standards.