AI Coding

Overview
﻿@tencent-rtc/trtc-push-skill is an Agent Skill provided by Tencent Cloud TIMPush. It helps developers integrate TIMPush, configure manufacturer channels, set up APNs, troubleshoot registration, manage badges, and debug server APIs across Android, iOS, Flutter, uni-app, and other projects.
After installation, you can describe your requirements in natural language directly within the AI IDE or Coding IDE's AI plugin, such as "Help me integrate TIMPush". The Agent will automatically detect your project platform and invoke the relevant capabilities to complete integration or troubleshooting step by step.
Capability list
When you mention keywords like TIMPush, offline push, manufacturer channel, or APNs, the Skill will be triggered automatically—no slash command required.
Scenario
Capability description
Examples
Start from scratch
Detects Android / iOS / Flutter / uni-app and walks through the SDK, credentials, config files, registerPush, and build verification
“Help me integrate TIMPush”, “Set up Tencent Cloud offline push”
Android vendor channels
Guides FCM console setup, signing fingerprints, package-name consistency, and credential checks
“Android offline push is not received”
iOS APNs
Checks certificates / P8, Bundle ID, aps-environment, BusinessID, deviceToken reporting, and the registration flow
“iOS registerPush succeeds but offline push is not received”
Flutter / uni-app
Handles plugins, native channels, and validation for cross-platform projects, and avoids running a pure Android / iOS wizard by mistake
“Integrate TIMPush in a Flutter project”, “How do I add offline push to uni-app”
Registration and callback troubleshooting
Analyzes registerPush, registrationID, error codes, and callback logs
“registerPush returns 800006”, “registrationID is empty”
Delivery and display troubleshooting
Separates registration failure, server-side send failure, vendor-delivered-but-not-shown, killed-process delivery, and message-category limits
“Push is delivered but not displayed”, “No push after the app is force-killed”
Click jump and callbacks
Investigates no-op notification clicks, deep links, empty ext, and onNotificationClicked
“Tapping the notification does not jump”, “ext is empty on click”
Chat SDK log analysis
Guides xlog collection, decodes logs locally, and extracts registration / offline-push evidence
“Analyze this Chat log”, “Does this xlog contain registerPush”
Installation guide
Note:
Do not use npm install to install this package. npm install only downloads the npm package; it does not install the Skill or configure the MCP Server. Please use the npx command below to run the installer.
Project-level installation is strongly recommended.
Install to AI IDE
If you are using AI IDEs such as Cursor, Claude Code, CodeBuddy, or Codex, run the following in your project directory:
# cd to the root directory of your app project
cd root-directory-of-your-app-project
﻿
# Automatically detects installed IDEs and installs to all IDEs
npx -y @tencent-rtc/trtc-push-skill@latest add
﻿
# Install to a specific AI IDE only
npx -y @tencent-rtc/trtc-push-skill@latest add --ide cursor
npx -y @tencent-rtc/trtc-push-skill@latest add --ide claude
npx -y @tencent-rtc/trtc-push-skill@latest add --ide codebuddy
npx -y @tencent-rtc/trtc-push-skill@latest add --ide codex
Install to an AI plugin in a Coding IDE
If you are using an AI plugin in a traditional Coding IDE, you can use the same installer. Common scenarios include:
CodeBuddy plugin in Android Studio / IntelliJ IDEA / JetBrains IDEs.
Cursor plugin or plugins compatible with Cursor project configuration in Visual Studio Code / Cursor IDEs.
AI coding plugins in Visual Studio Code / JetBrains IDEs that support MCP or Agent Skill project configuration.
Other AI plugins that can read project-level .cursor/, .codebuddy/, .claude/, or .codex/ configuration directories.
The installer currently supports the --ide parameters cursor, claude, codebuddy, and codex. If your plugin is compatible with one of these project configuration directories, select the corresponding parameter for installation.
Example 1: Android Studio + CodeBuddy plugin
When using the CodeBuddy plugin in Android Studio, run the following in your Android project:
npx -y @tencent-rtc/trtc-push-skill@latest add --ide codebuddy
After installation, .codebuddy/skills/ and the project-root .mcp.json are generated. Restart Android Studio or reload the CodeBuddy plugin to start using it.
Example 2: VS Code / Cursor plugin
When using Cursor-related plugins or plugins compatible with Cursor configuration in Visual Studio Code, run the following in your project:
npx -y @tencent-rtc/trtc-push-skill@latest add --ide cursor
After installation, .cursor/skills/ and .cursor/mcp.json are generated in the project.
Post-installation checklist: confirm MCP is enabled
The Skill is powered by the trtc-push-mcp MCP server for guided workflows. Regardless of the installation method, the workflow only works when MCP is enabled and loaded. Use the table below to verify.
Installed to an AI IDE:
IDE
Activation action
Cursor
Project-level MCP is disabled by default (newer Cursor versions no longer show a pop-up prompt).
Open the Cursor sidebar > Customize > MCP, enable the trtc-push-mcp switch, then reload the window.
﻿
Claude Code
No action required. The installer pre-approves MCP in .claude/settings.local.json. Restart the claude session;
if approval is still prompted, use /mcp to approve.
CodeBuddy
No action required. MCP is automatically enabled from the project-root .mcp.json. Reload CodeBuddy to activate.
﻿
Codex
Run codex in the project and accept the trust prompt; the project .codex/config.toml (including MCP) will then load.
Installed to an AI plugin in a Coding IDE:
Plugin type
MCP configuration location
Activation action
Android Studio / JetBrains + CodeBuddy plugin
Project-root .mcp.json
Restart the IDE or reload the CodeBuddy plugin.
VS Code / Cursor plugins
.cursor/mcp.json
Enable trtc-push-mcp in the plugin MCP panel, then restart the IDE.
Other compatible plugins
Depends on the configuration directory the plugin reads (.cursor/ / .codebuddy/ / .claude/ / .codex/)
Confirm the configuration is generated, enable it in the plugin, then restart the IDE.
How to use
After installation and restarting the IDE / plugin, enter the following directly in the Agent conversation:
Help me integrate TIMPush
Or:
My Android offline push is not arriving; help me troubleshoot
iOS registerPush succeeded, but offline push is not received after the process is killed
﻿

Scenario	Capability description	Examples
Start from scratch	Detects Android / iOS / Flutter / uni-app and walks through the SDK, credentials, config files, registerPush, and build verification	“Help me integrate TIMPush”, “Set up Tencent Cloud offline push”
Android vendor channels	Guides FCM console setup, signing fingerprints, package-name consistency, and credential checks	“Android offline push is not received”
iOS APNs	Checks certificates / P8, Bundle ID, aps-environment, BusinessID, deviceToken reporting, and the registration flow	“iOS registerPush succeeds but offline push is not received”
Flutter / uni-app	Handles plugins, native channels, and validation for cross-platform projects, and avoids running a pure Android / iOS wizard by mistake	“Integrate TIMPush in a Flutter project”, “How do I add offline push to uni-app”
Registration and callback troubleshooting	Analyzes registerPush, registrationID, error codes, and callback logs	“registerPush returns 800006”, “registrationID is empty”
Delivery and display troubleshooting	Separates registration failure, server-side send failure, vendor-delivered-but-not-shown, killed-process delivery, and message-category limits	“Push is delivered but not displayed”, “No push after the app is force-killed”
Click jump and callbacks	Investigates no-op notification clicks, deep links, empty ext, and onNotificationClicked	“Tapping the notification does not jump”, “ext is empty on click”
Chat SDK log analysis	Guides xlog collection, decodes logs locally, and extracts registration / offline-push evidence	“Analyze this Chat log”, “Does this xlog contain registerPush”

IDE	Activation action
Cursor	Project-level MCP is disabled by default (newer Cursor versions no longer show a pop-up prompt). Open the Cursor sidebar > Customize > MCP, enable the `trtc-push-mcp` switch, then reload the window.
Claude Code	No action required. The installer pre-approves MCP in `.claude/settings.local.json`. Restart the `claude` session; if approval is still prompted, use `/mcp` to approve.
CodeBuddy	No action required. MCP is automatically enabled from the project-root `.mcp.json`. Reload CodeBuddy to activate.
Codex	Run `codex` in the project and accept the trust prompt; the project `.codex/config.toml` (including MCP) will then load.

Plugin type	MCP configuration location	Activation action
Android Studio / JetBrains + CodeBuddy plugin	Project-root `.mcp.json`	Restart the IDE or reload the CodeBuddy plugin.
VS Code / Cursor plugins	`.cursor/mcp.json`	Enable `trtc-push-mcp` in the plugin MCP panel, then restart the IDE.
Other compatible plugins	Depends on the configuration directory the plugin reads (`.cursor/` / `.codebuddy/` / `.claude/` / `.codex/`)	Confirm the configuration is generated, enable it in the plugin, then restart the IDE.