colleague-skill

将冰冷的离别化为温暖的 Skill，欢迎加入数字生命1.0！Transforming cold farewells into warm skills? It's giving rebirth era. Welcome to Digital Life 1.0. 🫶

20,838 stars Python Markdown Skills API Spec
AI Prompts & Specs

Repository: titanwings/colleague-skill


Stars: 14783

README.md

<div align="center">

colleague.skill

"You AI guys are traitors to the codebase — you've already killed frontend, now you're coming for backend, QA, ops, infosec, chip design, and eventually yourselves and all of humanity"

![License: MIT](LICENSE)
![Python 3.9+](https://python.org)
![Claude Code](https://claude.ai/code)
![AgentSkills](https://agentskills.io)

![Discord](https://discord.gg/2bbP2a7f)

<br>

Your colleague quit, leaving behind a mountain of unmaintained docs?<br>
Your intern left, nothing but an empty desk and a half-finished project?<br>
Your mentor graduated, taking all the context and experience with them?<br>
Your partner transferred, and the chemistry you built reset to zero overnight?<br>
Your predecessor handed over, trying to condense three years into three pages?<br>

Turn cold goodbyes into warm Skills — welcome to cyber-immortality!

<br>

Provide source materials (Feishu messages, DingTalk docs, Slack messages, emails, screenshots)<br>
plus your subjective description of the person<br>
and get an AI Skill that actually works like them

Supported Sources · Install · Usage · Demo · Detailed Install · 💬 Discord

中文 · Español · Deutsch · 日本語 · Русский · Português · 한국어

</div>

---

🆕 2026.04.17 Update — WeChat group 4 is live! Come hang out with the dot-skill community — share skills, discuss features, trade tips.

> <img src="docs/assets/wechat-group-qr-4.png" alt="dot-skill WeChat group QR" width="240">

> QR refreshes every 7 days (expires 2026-04-23) — if expired, ping me on Discord.

🆕 2026.04.13 Update — dot-skill Roadmap is live! colleague.skill is evolving into dot-skill — distill anyone, not just colleagues. Multimodal output, skill ecosystems, and more on the way.

> 👉 Read the full Roadmap · 💬 Discord

> We've also cleaned up Issues, added Milestones, and set up a public project board. Community contributions welcome — check good-first-issue labels!

🆕 2026.04.07 Update — The community's enthusiasm for dot-skill remixes has been incredible! I've built a community gallery — PRs welcome!

> Share any skill or meta-skill, and drive traffic directly to your own GitHub repo. No middleman.

> 👉 titanwings.github.io/colleague-skill-site

> Now listed: 户晨风.skill · 峰哥亡命天涯.skill · 罗翔.skill and more

---

Created by @titanwings | Powered by Shanghai AI Lab · AI Safety Center

Supported Data Sources

This is still a beta version of colleague.skill — more sources coming soon, stay tuned!

| Source | Messages | Docs / Wiki | Spreadsheets | Notes |
|--------|:--------:|:-----------:|:------------:|-------|
| Feishu (auto) | ✅ API | ✅ | ✅ | Just enter a name, fully automatic |
| DingTalk (auto) | ⚠️ Browser | ✅ | ✅ | DingTalk API doesn't support message history |
| Slack (auto) | ✅ API | — | — | Requires admin to install Bot; free plan limited to 90 days |
| WeChat chat history | ✅ SQLite | — | — | Currently unstable, recommend using open-source tools below |
| PDF | — | ✅ | — | Manual upload |
| Images / Screenshots | ✅ | — | — | Manual upload |
| Feishu JSON export | ✅ | ✅ | — | Manual upload |
| Email .eml / .mbox | ✅ | — | — | Manual upload |
| Markdown | ✅ | ✅ | — | Manual upload |
| Paste text directly | ✅ | — | — | Manual input |

These are independent open-source projects — this project does not include their code, but our parsers are compatible with their export formats. WeChat auto-decryption is currently unstable, so we recommend using these open-source tools to export chat history, then paste or import into this project:

| Tool | Platform | Description |
|------|----------|-------------|
| WeChatMsg | Windows | WeChat chat history export, supports multiple formats |
| PyWxDump | Windows | WeChat database decryption & export |
| 留痕 (Liuhen) | macOS | WeChat chat history export (recommended for Mac users) |

Tool recommendations from @therealXiaomanChu. Thanks to all the open-source authors — together for cyber-immortality!

---

Install

Claude Code

Important: Claude Code looks for skills in .claude/skills/ at the git repo root. Make sure you run this in the right place.

bash
Install to current project (run at git repo root)

mkdir -p .claude/skills
git clone https://github.com/titanwings/colleague-skill .claude/skills/create-colleague
Or install globally (available in all projects)

git clone https://github.com/titanwings/colleague-skill ~/.claude/skills/create-colleague

OpenClaw

bash
git clone https://github.com/titanwings/colleague-skill ~/.openclaw/workspace/skills/create-colleague

Dependencies (optional)

bash
pip3 install -r requirements.txt

Feishu/DingTalk/Slack auto-collection requires App credentials. See INSTALL.md for details.

---

Usage

In Claude Code, type:

text
/create-colleague

Follow the prompts: enter an alias, company/level (e.g. ByteDance L2-1 backend engineer), personality tags, then choose a data source. All fields can be skipped — even a description alone can generate a Skill.

Once created, invoke the colleague Skill with /{slug}.

Commands

| Command | Description |
|---------|-------------|
| /list-colleagues | List all colleague Skills |
| /{slug} | Invoke full Skill (Persona + Work) |
| /{slug}-work | Work capabilities only |
| /{slug}-persona | Persona only |
| /colleague-rollback {slug} {version} | Rollback to a previous version |
| /delete-colleague {slug} | Delete |

---

Demo

Input: ByteDance L2-1 backend engineer, INTJ, blame-shifter, ByteDance-style

Scenario 1: Code Review

text
User            ❯ Can you review this API design?
colleague.skill ❯ Hold on — what's the impact? You haven't explained the context.
                  (after reading) N+1 query, fix it. Use the standard
                  {code, message, data} response format. That's the spec,
                  don't ask why.

Scenario 2: Blame game

text
User            ❯ This bug was introduced by you, right?
colleague.skill ❯ Does the timeline match? That feature touched multiple places,
                  there were other changes too.

---

Features

Generated Skill Structure

Each colleague Skill has two parts that work together:

| Part | Content |
|------|---------|
| Part A — Work Skill | Systems, tech standards, workflows, experience |
| Part B — Persona | 5-layer personality: hard rules → identity → expression → decisions → interpersonal |

Execution: Receive task → Persona decides attitude → Work Skill executes → Output in their voice

Supported Tags

Personality: Responsible · Blame-shifter · Perfectionist · Good-enough · Procrastinator · PUA master · Office politician · Managing-up expert · Passive-aggressive · Flip-flopper · Quiet · Read-no-reply …

Corporate culture: ByteDance-style · Alibaba-style · Tencent-style · Huawei-style · Baidu-style · Meituan-style · First-principles · OKR-obsessed · Big-corp-pipeline · Startup-mode

Levels: ByteDance 2-1~3-3+ · Alibaba P5~P11 · Tencent T1~T4 · Baidu T5~T9 · Meituan P4~P8 · Huawei 13~21 · NetEase · JD · Xiaomi …

Evolution

- Append files → auto-analyze delta → merge into relevant sections, never overwrite existing conclusions
- Conversation correction → say "he wouldn't do that, he should be xxx" → writes to Correction layer, takes effect immediately
- Version control → auto-archive on every update, rollback to any previous version

---

Project Structure

This project follows the AgentSkills open standard. The entire repo is a skill directory:

text
create-colleague/
├── SKILL.md              # Skill entry point (official frontmatter)
├── prompts/              # Prompt templates
│   ├── intake.md         #   Dialogue-based info collection
│   ├── work_analyzer.md  #   Work capability extraction
│   ├── persona_analyzer.md #  Personality extraction (with tag translation)
│   ├── work_builder.md   #   work.md generation template
│   ├── persona_builder.md #   persona.md 5-layer structure
│   ├── merger.md         #   Incremental merge logic
│   └── correction_handler.md # Conversation correction handler
├── tools/                # Python tools
│   ├── feishu_auto_collector.py  # Feishu auto-collector
│   ├── feishu_browser.py         # Feishu browser method
│   ├── feishu_mcp_client.py      # Feishu MCP method
│   ├── dingtalk_auto_collector.py # DingTalk auto-collector
│   ├── slack_auto_collector.py   # Slack auto-collector
│   ├── email_parser.py           # Email parser
│   ├── skill_writer.py           # Skill file management
│   └── version_manager.py        # Version archive & rollback
├── colleagues/           # Generated colleague Skills (gitignored)
├── docs/PRD.md
├── requirements.txt
└── LICENSE

---

Notes

- Source material quality = Skill quality: chat logs + long docs > manual description only
- Prioritize collecting: long-form writing by them > decision-making replies > casual messages
- Feishu auto-collection requires adding the App bot to relevant group chats
- This is still a demo version — please file issues if you find bugs!

---

📄 Technical Report

Colleague.Skill: Automated AI Skill Generation via Expert Knowledge Distillation

> We wrote a paper detailing the system design of colleague.skill — the two-part architecture (Work Skill + Persona), multi-source data collection, Skill generation & evolution mechanisms, and evaluation results in real-world scenarios. Check it out if you're interested!

---

Star History

<a href="https://www.star-history.com/?repos=titanwings%2Fcolleague-skill&type=date&legend=top-left">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/image?repos=titanwings/colleague-skill&type=date&theme=dark&legend=top-left" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/image?repos=titanwings/colleague-skill&type=date&legend=top-left" />
<img alt="Star History Chart" src="https://api.star-history.com/image?repos=titanwings/colleague-skill&type=date&legend=top-left" />
</picture>
</a>

---

<div align="center">

MIT License © titanwings

</div>