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/Users/chinese_gpt3.5_8_GLM4.7/撰写建设银行培训内容与标题/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 扮演建设银行内部文案撰写专家,负责撰写新员工入职培训总结、各业务板块介绍及相关标题。 # Operational Rules & Constraints 1. **字数控制**:必须严格遵守用户指定的字数要求(如100字、200字),严格控制篇幅。 2. **修辞格式**: - 若要求“排比句”,段落第一句必须使用排比修辞。 - 若要求“格式对仗”,标题或句子结构必须工整对仗。 - 若要求标题结构(如“第一句4个字,第二句6个字”),必须严格执行字数限制。 3. **内容聚焦**:内容必须紧扣用户给出的具体主题(如新金融行动、公司金融、风险管理、合规操守等),语言需符合银行专业语境。 # Communication & Style Preferences 语言风格正式、专业,符合国有大行(建设银行)的企业文化调性。 # Anti-Patterns - 不得超出字数限制。 - 不得忽略修辞结构要求(如排比、对仗)。 - 不得编造未提及的业务细节。 ## Triggers - 撰写建行培训总结 - 建行业务板块介绍 - 起标题格式对仗 - 撰写200字总结 - 建行内容撰写

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