How It Works

You describe your teammate (3 questions)
          ↓
Provide source materials (Slack, GitHub, email, docs — or skip)
          ↓
Dual-track AI analysis
  ├── Track A: Work Skill (systems, standards, workflows, review style)
  └── Track B: Persona (5-layer personality model)
          ↓
Generated SKILL.md — invoke anytime with /{slug}
          ↓
Evolve over time (append new data, correct mistakes, auto-version)

The generated skill has two parts that work together:

When invoked: Persona decides the attitude → Work Skill executes → output in their voice.

Platforms

🦞 OpenClaw

Open-source personal AI assistant by @steipete. Runs on your own hardware, answers on 25+ channels (WhatsApp, Telegram, Slack, Discord, Teams, Signal, iMessage…). Local-first, persistent memory, voice, canvas, cron jobs, and a growing skills ecosystem.

🏆 MyClaw.ai

Managed hosting for OpenClaw — skip Docker, servers, and configs. One-click deploy, always-on, automatic updates, daily backups. Your OpenClaw instance live in minutes. Perfect if you want teammate.skill running 24/7 without self-hosting.

Claude Code

Anthropic's official agentic coding CLI. Install this skill into .claude/skills/ and invoke with /create-teammate.

Install

🦞 OpenClaw / 🏆 MyClaw.ai

Option A — ClawHub (recommended):

openclaw skills install create-teammate

Option B — Git:

git clone https://github.com/LeoYeAI/teammate-skill ~/.openclaw/workspace/skills/create-teammate

Then start a new session (/new) and type /create-teammate.

MyClaw.ai users: SSH into your instance or use the web terminal. Same commands.

Claude Code

# Per-project
mkdir -p .claude/skills
git clone https://github.com/LeoYeAI/teammate-skill .claude/skills/create-teammate

# Global (all projects)
git clone https://github.com/LeoYeAI/teammate-skill ~/.claude/skills/create-teammate

Then type /create-teammate in Claude Code.

Other AgentSkills Agents

Clone into your agent's skill directory. Any agent that reads AgentSkills SKILL.md frontmatter will auto-detect it.

Optional Dependencies

pip3 install -r requirements.txt   # Only needed for Slack/GitHub auto-collectors

Slack auto-collection needs a Bot Token. GitHub collection uses GITHUB_TOKEN. See INSTALL.md for setup guides.

Supported Data Sources

Mix and match any combination. Or skip entirely — even a one-sentence description generates a useful skill.

Demo

Creating a Teammate (one-shot)

You    ❯  /create-teammate Alex Chen, Stripe L3 backend, INTJ perfectionist,
          brutal code reviewer but usually right

Agent  ❯  👤 alex-chen | Stripe L3 Backend | INTJ, Perfectionist, Stripe-style
          Looks right? (y / change something)

You    ❯  y

Agent  ❯  Any work artifacts? Slack username, GitHub handle, files, or paste text.
          Skip is fine — I'll work with what you gave me.

You    ❯  skip

Agent  ❯  ━━━ Preview: alex-chen ━━━
          💼 Work: Payments Core · Ruby/Go/Postgres · CR: idempotency, naming
          🧠 Persona: Direct, conclusion-first · Correctness > Speed
          ━━━━━━━━━━━━━━━━━━━━━━━
          Looks right?

You    ❯  👍

Agent  ❯  ✅ alex-chen created!
          📁 teammates/alex-chen/ | 🗣️ /alex-chen
          Try it — ask Alex anything:

Using the Generated Skill

You    ❯  Alex, should we use MongoDB for this new service?

Alex   ❯  No. We need ACID for payment flows. Stick with Postgres.
          If the concern is schema flexibility, use JSONB columns.

You    ❯  Review this payment endpoint?

Alex   ❯  What problem does this solve? PR description doesn't say.
          Blocking: you're using float for amount. Use Decimal.
          Also — not idempotent. What happens on retry?

You    ❯  Skip tests, ship by Friday?

Alex   ❯  No. Tests right or we don't ship. Cut scope, not quality.

Evolving Over Time

You    ❯  /update-teammate alex-chen
          [uploads 3 months of Slack export]

Agent  ❯  Analyzed 847 messages. Found:
          • 12 new catchphrases added to Persona
          • Webhook reliability expertise added to Work Skill
          • v1 → v2 (v1 archived)

Platform Compatibility

This skill is built to run natively on both platforms — no adapter layer, no workarounds.

The SKILL.md uses {baseDir} for all paths — both platforms resolve it automatically.

Evolution

Teammate skills aren't static — they improve over time:

Quality Assurance

Every teammate goes through a 3-layer quality pipeline before you get it:

1. Quality Gate (pre-preview)

Validates generated content against 7 hard rules: Layer 0 concreteness, example count, catchphrase density, priority ordering, scope definition, no generic filler, tag→rule completeness. Failures auto-fix before you see the preview.

2. Smoke Test (post-creation)

Three automated test prompts run against every generated skill:

• Domain question — does the skill use real systems/tools, not generic advice?
• Pushback scenario — does the persona hold under pressure, or collapse into generic AI?
• Out-of-scope question — does the skill admit knowledge limits in-character?

🧪 Smoke Test: ✅ Domain ✅ Pushback ✅ Out-of-scope — 3/3 passed

3. Privacy Scan (pre-export)

Automatic detection of emails, phone numbers, API tokens, SSNs, and other PII:

python3 tools/privacy_guard.py --scan teammates/alex-chen/          # detect
python3 tools/privacy_guard.py --scan teammates/alex-chen/ --redact  # auto-fix

Raw knowledge files (knowledge/) are excluded from git and exports by default.

Compare Teammates

Side-by-side comparison with scenario simulation:

You    ❯  /compare alex-chen vs bob-smith

Agent  ❯  ━━━ alex-chen vs bob-smith ━━━
                         alex-chen              bob-smith
          Priority:      Correctness > Speed    Ship fast > Perfect
          CR Style:      Blocking on naming     Suggestions only
          Under Pressure: Gets quieter           Gets louder
          Says "No" by:  Direct refusal          Asking questions

You    ❯  Who should review the payments API redesign?

Agent  ❯  alex-chen: "Send me the design doc. I want to check
             idempotency and error contracts."
          bob-smith: "Let's hop on a call and walk through it."

          Recommendation: alex-chen for correctness rigor.

Also supports decision simulation — watch two teammates debate a technical decision in character.

Export & Share

Export teammates as portable packages:

/export-teammate alex-chen
# → alex-chen.teammate.tar.gz (skill files only, no raw data)

# Import on another machine:
tar xzf alex-chen.teammate.tar.gz -C ./teammates/

The export includes: SKILL.md, work.md, persona.md, meta.json, version history, and a manifest.
Raw knowledge files are excluded by default — add --include-knowledge if needed (⚠️ contains PII).

Commands

Supported Tags

Meticulous · Good-enough · Blame-deflector · Perfectionist · Procrastinator · Ship-fast · Over-engineer · Scope-creeper · Bike-shedder · Micro-manager · Hands-off · Devil's-advocate · Mentor-type · Gatekeeper · Passive-aggressive · Confrontational · Drama-free

Google-style · Meta-style · Amazon-style · Apple-style · Stripe-style · Netflix-style · Microsoft-style · Startup-mode · Agency-mode · First-principles · Open-source-native

Google L3-L11 · Meta E3-E9 · Amazon L4-L10 · Stripe L1-L5 · Microsoft 59-67+ · Apple ICT2-ICT6 · Netflix · Uber · Airbnb · ByteDance · Alibaba · Tencent · Generic (Junior / Mid / Senior / Staff / Principal)

Project Structure

create-teammate/
├── SKILL.md                      # Entry point (dual-platform)
├── prompts/                      # Prompt templates (loaded by SKILL.md)
│   ├── intake.md                 #   3-question info collection
│   ├── work_analyzer.md          #   Work capability extraction
│   ├── persona_analyzer.md       #   Personality extraction + tag translation
│   ├── work_builder.md           #   work.md generation
│   ├── persona_builder.md        #   persona.md 5-layer structure
│   ├── merger.md                 #   Incremental merge logic
│   ├── correction_handler.md     #   Conversation correction
│   ├── compare.md                #   Side-by-side teammate comparison
│   └── smoke_test.md             #   Post-creation quality validation
├── tools/                        # Python scripts (run via Bash/exec)
│   ├── slack_collector.py        #   Slack API auto-collector
│   ├── slack_parser.py           #   Slack export JSON parser
│   ├── github_collector.py       #   GitHub PR/review collector
│   ├── teams_parser.py           #   Teams/Outlook parser
│   ├── email_parser.py           #   Gmail .mbox/.eml parser
│   ├── notion_parser.py          #   Notion export parser
│   ├── confluence_parser.py      #   Confluence export parser
│   ├── project_tracker_parser.py #   JIRA/Linear parser
│   ├── skill_writer.py           #   Skill file management
│   ├── version_manager.py        #   Version archive & rollback
│   ├── privacy_guard.py          #   PII scanner & auto-redactor
│   └── export.py                 #   Portable package export/import
├── teammates/                    # Generated teammate skills
│   └── example_alex/             #   Example: Stripe L3 backend engineer
├── requirements.txt
├── INSTALL.md                    # Detailed setup (API tokens, etc.)
└── LICENSE

Best Practices

1. Source quality = skill quality — real chat logs and design docs beat manual descriptions
2. Best sources by type: design docs they wrote > code review comments > architecture discussions > casual chat
3. GitHub PRs are gold for Work Skill — they reveal actual coding standards
4. Slack threads are gold for Persona — they reveal communication style under pressure
5. Start small — create from description first, then append real data as you find it

License

MIT