Skip to content

feat: add trtc-ai-service skill for Conversational AI (AI customer service)#8

Open
Burgerham4R wants to merge 8 commits into
Tencent-RTC:mainfrom
Burgerham4R:feature/trtc-ai-service
Open

feat: add trtc-ai-service skill for Conversational AI (AI customer service)#8
Burgerham4R wants to merge 8 commits into
Tencent-RTC:mainfrom
Burgerham4R:feature/trtc-ai-service

Conversation

@Burgerham4R

Copy link
Copy Markdown

Summary

Add a new trtc-ai-service skill that enables users to build AI-powered customer service applications using TRTC Conversational AI — from zero to a working demo, or integrate conversational AI capabilities into an existing project.

Approach: Independent Root Skill (Zero Intrusion)

The AI customer service skill is added as an independent root skill under skills/trtc-ai-service/. A new "Conversational AI fast-path" section in skills/trtc/SKILL.md routes AI customer service requests directly, completely bypassing trtc-topic's Pre-flight check (which only covers Conference Web scenarios in v1).

Zero changes to trtc-topic/SKILL.md — the defense-in-depth gate remains untouched.

Changes

Modified files (8)

File Change
skills/trtc/SKILL.md +33 lines: Conversational AI fast-path after MANDATORY GATE
CLAUDE.md +4 lines: product list + routing for Conversational AI
CODEBUDDY.md +2 lines: product table + routing entry
ai-instructions/base.md +17 lines: Conversational AI routing rules (AGENTS.md source)
AGENTS.md +17 lines: synced routing rules (self-contained for Codex)
bin/cli.js Replaced hardcoded SKILL_NAMES with dynamic getSkillNames() — auto-discovers skill dirs containing SKILL.md, trtc sorted first
README.md +10 lines: Conversational AI product row + supported scenarios
README.zh.md +10 lines: same in Chinese

New files (~174, all under skills/trtc-ai-service/)

  • SKILL.md — Full execution SOP (931 lines): three-key configuration, Path A (Quick Start demo) / Path B (Integrate into My System), error recovery, tool whitelist
  • capabilities/ — 6 atomic capability modules: conversation-core, knowledge-base, human-handoff, tool-calling, session-summary, digital-human
  • scenarios/ — 2 scenario recipes: customer-service (demo UI), custom-builder (integration wizard)
  • auto_adapters/ — 4-class 12-tech-stack adapters: frontend-spa (React/Vue/Angular), java-backend (Spring/Quarkus), node-backend (Express/Fastify/Koa), python-backend (Flask/FastAPI/Django)
  • scripts/ — Automation: credential verification, capability assembly, post-install patch, contract adaptation
  • tests/ — 10 test files
  • start.sh — Bootstrap script

Not modified

  • skills/trtc-topic/SKILL.md0 lines changed (zero intrusion)
  • skills/trtc-onboarding/reference/supported-matrix.md — not needed (AI service bypasses onboarding)
  • knowledge-base/index.yaml — not needed (independent capability model)

Conversational AI — Supported Scenarios

Scenario Status
AI Customer Service ✅ Available
AI Oral Practice Coming soon

Testing

  • ✅ Fork tested locally via npx install — all 7 skills (including trtc-ai-service) correctly installed to .codex/skills/
  • ✅ Trigger words ("AI客服", "智能客服", "build AI customer service") correctly route to trtc-ai-service/SKILL.md
  • ✅ Three-key configuration flow (Tencent Cloud API, TRTC SDK, LLM API) works end-to-end
  • ✅ Path A (Quick Start) generates working voice customer service demo UI
  • ✅ Path B (Integrate) delivers backend API + adapter samples

Why dynamic skill discovery in bin/cli.js

The installer previously used a hardcoded SKILL_NAMES array. This PR replaces it with getSkillNames() that dynamically scans skills/ for directories containing SKILL.md. This ensures future skill additions are automatically discovered and installed without manual code changes.

hamjia added 8 commits June 22, 2026 17:16
- Add skills/trtc-ai-service/ with 6 capability modules, 2 scenario recipes, 12 tech-stack adapters, and automation scripts
- Add AI Service fast-path in skills/trtc/SKILL.md to route AI customer service requests directly, bypassing standard onboarding/topic pre-flight checks
- Register trtc-ai-service in CLAUDE.md product list and routing logic
- Register trtc-ai-service in CODEBUDDY.md product table and routing rules
- Zero changes to trtc-topic/SKILL.md (Plan A: independent root skill, zero intrusion)
….md routing

Root cause: installer used hardcoded SKILL_NAMES array that missed trtc-ai-service,
and AGENTS.md only referenced CLAUDE.md without being self-contained for Codex.

Changes:
- bin/cli.js: Replace hardcoded SKILL_NAMES with dynamic getSkillNames()
  that auto-discovers skill dirs containing SKILL.md. trtc is always first,
  rest sorted alphabetically. Also dynamic listSkills() output.
- ai-instructions/base.md: Add AI Service routing rules so generated
  AGENTS.md / CODEBUDDY.md are self-contained (Codex only installs AGENTS.md)
- AGENTS.md: Sync AI Service routing rules from base.md source
- README.md / README.zh.md: Add AI Service product row with Web check

This ensures any new skill directory added to skills/ is automatically
discovered and installed without manual code changes.
…nversational AI

1. Sync code updates from upstream ai-customer-service-skill:
   - capabilities/conversation-core: server.py, trtc_client.py
   - capabilities/human-handoff: models.py, service.py, router.py, summary_link.py
   - capabilities/human-handoff: NEW feedback_store.py
   - capabilities/session-summary: router.py, summarizer.py
   - scenarios/customer-service: recipe.yaml, README, all UI files (admin-board + voice-customer-service)
   - start.sh, README.md, README.zh-CN.md

2. Rename product 'AI Service' → 'Conversational AI' across all files:
   - README.md / README.zh.md: product table + new Conversational AI scenarios section
   - CLAUDE.md: product identification list
   - CODEBUDDY.md: product table
   - ai-instructions/base.md + AGENTS.md: routing section title and description
   - skills/trtc/SKILL.md: fast-path section title and triggers

Customer Service is now correctly positioned as a scenario of Conversational AI,
not a product itself.
…scenarios

- AI Customer Service: available — describe in plain language
- AI Oral Practice: coming soon — describe in plain language
Remove skill-internal terminology (customer-service/custom-builder) from README
…rvice SKILL.md

The 114-line wrapper was missing critical execution details:
- Three-keys configuration (Tencent Cloud API, TRTC SDK, LLM API)
- Step-by-step beginner guidance (Path A / Path B)
- Environment checks, error recovery, tool whitelist
- Security constraints, design standards

Now uses the complete 900+ line SOP from the upstream
ai-customer-service-skill repo, with official frontmatter and
agent-skills entry points section preserved.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant