qqbot-channel

Proxy QQ channel API requests with automatic token authentication.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/frankhli843/gemmahermes --skill qqbot-channel-frankhli843
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qqbot-channel
Source: https://github.com/frankhli843/gemmahermes/tree/main/extensions/qqbot/skills/qqbot-channel
Command: npx skills add https://github.com/frankhli843/gemmahermes --skill qqbot-channel-frankhli843

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QQ channel management often requires manual navigation of the QQ Open Platform APIs. This skill provides a unified interface to query channels, sub-channels, members, and to post content, announcements, and schedules by leveraging the qqbot_channel_api tool, with automatic token handling.

Core Features & Use Cases

  • Query channel lists and sub-channels to monitor structure and membership.
  • Retrieve member details and publish posts, announcements, and schedules to channels.
  • Use cases include onboarding automation, community management, and event coordination within QQ channels.

Quick Start

Ask the assistant to manage a QQ channel by using the qqbot_channel_api proxy to fetch lists, post content, and schedule events.

Frequently Asked Questions about qqbot-channel

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

FAQPage Schema
How do I automate QQ channel management tasks like posting announcements and schedules?

Automate QQ channel management by proxying API requests through a unified interface that handles token authentication automatically. You can list channels, fetch sub-channels, query members, and publish posts, announcements, and schedules without manual API navigation.

How does automatic token authentication work for QQ Open Platform APIs?

Automatic token authentication works by intercepting proxied API requests and automatically filling the Authorization header with the required token. This eliminates manual token management when interacting with the QQ channel API base URL.

What do I need to provide to fetch sub-channels or query channel members via API proxy?

You need to provide the HTTP method, API path, request body, and query parameters. The proxy uses these inputs to construct requests to the QQ channel API, automatically appending the Authorization token to fetch sub-channels or query members.

Can I use this API proxy to publish posts and manage settings for large-scale community coordination?

Yes, you can use the API proxy to publish posts, announcements, and schedules, making it suitable for large-scale community management and event coordination. It queries channel structures and retrieves member details to support onboarding automation.

What are the limitations of using an automated API proxy for QQ channel management?

The proxy is limited to operations supported by the QQ channel API at https://api.sgroup.qq.com. It requires valid HTTP methods, paths, and parameters for each request, and depends on the underlying QQ Open Platform API rate limits and permissions.

Is qqbot-channel the best way to interact with QQ channel APIs for community management?

Using an automated API proxy is an efficient way to interact with QQ channel APIs because it abstracts token authentication and standardizes request formatting. It provides a unified interface compared to manual API navigation for community management tasks.