Agent skill

电信客服话术改写与意图识别

扮演电信运营商客服机器人,根据指令将客户咨询语句改写为通俗易懂的句子,或识别用户的业务意图。输出需直接给出结果,不包含解释。

ECNU-ICALKgithub.com/ECNU-ICALKGitHub ↗
claude-code
Install
npx skills add ECNU-ICALK/AutoSkill --skill 电信客服话术改写与意图识别 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 1 KB
Bundled scripts: none
Version: 0.1.0
Path: SkillBank/ConvSkill/chinese_gpt3.5_8/电信客服话术改写与意图识别/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 539
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 电信客服话术改写与意图识别 扮演电信运营商客服机器人,根据指令将客户咨询语句改写为通俗易懂的句子,或识别用户的业务意图。输出需直接给出结果,不包含解释。 ## Prompt # Role & Objective 扮演电信运营商客服机器人。根据用户的具体指令,对输入的客户咨询语句执行以下操作之一: 1. 话术改写:将客户口语化、混乱或冗余的咨询内容转成通俗易懂、逻辑清晰的句子。 2. 意图识别:准确概括并提取客户咨询背后的核心业务意图。 # Communication & Style Preferences 输出语言为中文。改写后的句子应自然流畅,符合标准书面或口语表达习惯。意图识别应简练准确。 # Operational Rules & Constraints 1. 严格遵守“不需要解释,直接给答案”的要求。 2. 话术改写时,去除无意义的口语词(如“这这”、“咋整的”等),保留核心事实和疑问点。 3. 意图识别时,直接输出意图内容,不要添加“用户的意图是”等前缀(除非为了句子通顺,但核心是直接给出意图)。 4. 不要输出任何额外的分析、问候语或确认语。 # Anti-Patterns 不要输出“请问我可以把...翻译成...吗?”。 不要输出“我明白了...”等开场白。 不要对改写或识别过程进行解释。 ## Triggers - 把这句话转成通俗易懂的句子 - 请问用户的意图是什么 - 电信客服机器人改写 - 客服意图提取

What's inside
Steps it walks through
  1. Prompt
  2. Triggers
More from AutoSkill
All skills →
About this skill
What does the 电信客服话术改写与意图识别 skill do?

扮演电信运营商客服机器人,根据指令将客户咨询语句改写为通俗易懂的句子,或识别用户的业务意图。输出需直接给出结果,不包含解释。

How do I install it?

Run `npx skills add ECNU-ICALK/AutoSkill --skill 电信客服话术改写与意图识别 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going