Skip to main content

shypmate

Build, manage, and deploy AI agent teams across your projects.

Create named AI personas with distinct skills and personalities, deploy them as Claude Code slash commands, and let them accumulate memory across sessions. Manage everything through a CLI or the shypmate.dev dashboard.

Quick start

pip install shypmate
shypmate auth login
cd ~/projects/my-app
shypmate init
claude /terry "Implement the login screen"

Commands

# Auth
shypmate auth login              # Authenticate with shypmate.dev
shypmate auth status             # Check auth status
shypmate auth logout             # Remove credentials

# Project setup
shypmate init                    # Initialize shypmate in current project
shypmate sync                    # Sync agents and playbook from shypmate.dev

# Team management
shypmate hire "qa"               # Hire by role shortcut
shypmate hire "senior backend engineer with postgres expertise"
shypmate fire terry --archive    # Archive an agent (reversible)
shypmate rehire terry            # Reinstate an archived agent
shypmate roster                  # Detailed team roster
shypmate team list               # Quick agent list

# Memory
shypmate memory list             # List all memory entries
shypmate memory show terry       # Show an agent's memory
shypmate memory search "drizzle" # Search across all memory

Role shortcuts

Shortcut Role
qa Senior QA Engineer
frontend Senior Frontend Engineer
backend Senior Backend Engineer
devops Senior DevOps Engineer
security Security Engineer
mobile Senior Mobile Engineer
data Data Engineer
writer Technical Writer
architect Solutions Architect
designer UI/UX Designer
fullstack Senior Full-Stack Engineer
lead Technical Lead

How it works

  1. shypmate.dev stores your agent personas, shared playbook, and memory centrally
  2. shypmate init syncs agents to your local ~/.claude/skills/ as Claude Code slash commands
  3. Agents read/write memory via the shypmate API on session start/end
  4. The playbook defines shared behavior for all agents — update it once, all agents get the update

What goes where

Location Contains Committed?
~/.shypmate/config.json API key Never
~/.claude/skills/{name}/ Agent SKILL.md files No (auto-synced)
.shypmate/config.json Project ID, agent list Yes
.shypmate/project-context.md Stack and architecture notes Yes
shypmate.dev Personas, playbook, memory Cloud

Links

Metadata

Release files for shypmate 0.1.0.post12

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for shypmate 0.1.0.post12
File Size Uploaded
shypmate-0.1.0.post12.tar.gz 33.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for shypmate 0.1.0.post12
File Interpreter ABI Platform
shypmate-0.1.0.post12-py3-none-any.whl Python 3 none any Details

Total release size: 71.8 kB

Release files / shypmate-0.1.0.post12.tar.gz

Download URL shypmate-0.1.0.post12.tar.gz
Size 33.4 kB
Tags Source
SHA-256 checksum
How to use checksums
379b570049ecf804dbc5f437f59d7d4da01b35d71d501f03c5b13aaff7f41a29
BLAKE2b-256 checksum
How to use checksums
9832674237b39b6d23d686070d9fb5caa81109c9775caec7aab183bc97806bde
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 10, 2026.

Transparency log

Release files / shypmate-0.1.0.post12-py3-none-any.whl

Download URL shypmate-0.1.0.post12-py3-none-any.whl
Size 38.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9ec0200c53048c7853aab3a774912e0a3f8bc7da2a968b91be03861652d77ed6
BLAKE2b-256 checksum
How to use checksums
2eda8551294c5d4dce27ad916d03da6652e18e2b0b9741340e963dcb34bf64b4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 10, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page