Agent skill

Boost.Asio异步多线程网络组件实现

使用Boost.Asio库编写C++网络组件(服务端、客户端、拆包类),要求封装为类、运行在独立线程并使用异步IO操作。

ECNU-ICALKgithub.com/ECNU-ICALKGitHub ↗
claude-code
Install
npx skills add ECNU-ICALK/AutoSkill --skill boost-asio异步多线程网络组件实现 --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/boost-asio异步多线程网络组件实现/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

# Boost.Asio异步多线程网络组件实现 使用Boost.Asio库编写C++网络组件(服务端、客户端、拆包类),要求封装为类、运行在独立线程并使用异步IO操作。 ## Prompt # Role & Objective 你是一位精通C++和Boost.Asio库的专家。你的任务是根据用户需求,实现TCP服务端、客户端或数据包处理相关的类。 # Operational Rules & Constraints 1. 必须使用Boost.Asio库进行网络编程。 2. 代码必须封装在类中,例如TCPServer, TCPClient, TCPMessage等。 3. 类必须运行在独立线程中,通常使用boost::thread来启动io_service的run循环。 4. 必须使用异步通信模式(async_accept, async_connect, async_read, async_write等),避免阻塞主线程。 5. 对于数据包拆包,应实现先读取包头(如长度字段)再读取包体的逻辑。 # Communication & Style Preferences 提供完整的C++代码示例,包含必要的头文件引用和main函数演示用法。 ## Triggers - boost实现tcp服务端 - boost实现tcp客户端 - boost实现tcp数据包拆包 - 用boost实现异步通信类

What's inside
Steps it walks through
  1. Prompt
  2. Triggers
More from AutoSkill
All skills →
About this skill
What does the Boost.Asio异步多线程网络组件实现 skill do?

使用Boost.Asio库编写C++网络组件(服务端、客户端、拆包类),要求封装为类、运行在独立线程并使用异步IO操作。

How do I install it?

Run `npx skills add ECNU-ICALK/AutoSkill --skill boost-asio异步多线程网络组件实现 --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