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
- shypmate.dev stores your agent personas, shared playbook, and memory centrally
shypmate initsyncs agents to your local~/.claude/skills/as Claude Code slash commands- Agents read/write memory via the shypmate API on session start/end
- 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
- Dashboard: shypmate.dev
- Docs: docs.shypmate.dev
- GitHub: github.com/paulr978/shypmate
Metadata
Release files for shypmate 0.1.0.post11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| shypmate-0.1.0.post11.tar.gz | 32.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shypmate-0.1.0.post11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.3 kB
Release files / shypmate-0.1.0.post11.tar.gz
| Download URL | shypmate-0.1.0.post11.tar.gz |
|---|---|
| Size | 32.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9cbfb3ab122b54c8bcfc70c9dec00dccfb605b7b2c8ce6d24c385630350b0fd
|
|
BLAKE2b-256 checksum How to use checksums |
a2dd14d7a470a162a01bb240962202e7f4c224e87b715977e7c4bdd77ff68030
|
| 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 logRelease files / shypmate-0.1.0.post11-py3-none-any.whl
| Download URL | shypmate-0.1.0.post11-py3-none-any.whl |
|---|---|
| Size | 37.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3c440e78e43a777e4a0003a417741a6de5d825611a27b53b2d04f39da96260d6
|
|
BLAKE2b-256 checksum How to use checksums |
81a023291e5dae86c3980f24c0dd3cfd4c36c6f8c94db3f95d1bef60fd02b77d
|
| 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