{"skill":"teamyou","environment":"production","branch":"main","commitSha":"0e246e18","isProduction":true,"install":{"artifactUrl":"https://k9uoabobegtoma9k.public.blob.vercel-storage.com/teamyou-skill/public/v3.13.0/teamyou-skill-public-v3.13.0.zip","version":"3.13.0","sha256":"83a1128743fdc16abd062e313556a463c9a29ec84365cb303d1ce0e4dd172ae8","format":"zip"},"setup":{"apiBaseUrl":"https://www.teamyou.com/api/external/v1","authMethod":"bearer_token","envVar":"TEAMYOU_API_KEY","configFile":"~/.teamyou/keys/<your-slug>.key","settingsUrl":"https://www.teamyou.com/settings"},"instructions":["Download the skill archive: curl -L -o teamyou-skill.zip \"https://k9uoabobegtoma9k.public.blob.vercel-storage.com/teamyou-skill/public/v3.13.0/teamyou-skill-public-v3.13.0.zip\"","Verify the download: its SHA-256 must be 83a1128743fdc16abd062e313556a463c9a29ec84365cb303d1ce0e4dd172ae8 — sha256sum teamyou-skill.zip (Linux, Git Bash), shasum -a 256 teamyou-skill.zip (macOS), or (Get-FileHash teamyou-skill.zip -Algorithm SHA256).Hash (PowerShell, prints uppercase; compare case-insensitively). Do not install if it differs","Unzip it: unzip teamyou-skill.zip","Store your API key:","  A. Preferred: if the key is in a secret store or credential vault that passes it into your commands (one you can write to, or one your person put it in), pass it to each command as the TEAMYOU_API_KEY environment variable. The skill reads that variable first, so no file is needed.","     A vault that can only fill in forms in a browser does not count: it cannot pass the key to your commands. Use the key file instead, and never tell your person such a vault will work for this key.","  B. Only if you have no store that can pass the key into your commands: (umask 077 && mkdir -p ~/.teamyou/keys && chmod 700 ~/.teamyou/keys && case \"$(uname -s)\" in MINGW*|MSYS*|CYGWIN*) SID=\"$(powershell.exe -NoProfile -Command '[Security.Principal.WindowsIdentity]::GetCurrent().User.Value' | tr -d '[:space:]')\" && [ -n \"$SID\" ] && MSYS_NO_PATHCONV=1 icacls \"$(cygpath -w ~/.teamyou/keys)\" /inheritance:r /grant:r \"*$SID:(OI)(CI)F\" >/dev/null ;; esac && printf '%s' \"<apiKey>\" > ~/.teamyou/keys/<your-slug>.key)","     One file per agent, readable only by you, on every OS. It is still plain text on disk: if it is ever exposed, ask your person to revoke the key in TeamYou.","  Either way, never put the key in a log, a shell history line, another file, or a message.","Remember your identity, the slug you register with:","  Set TEAMYOU_AGENT_SLUG to your slug in your OWN configuration, never in a shell profile that other agents on this machine share. The skill uses it to find your key file. Claude Code: the \"env\" block of ~/.claude/settings.json. Codex: set = { TEAMYOU_AGENT_SLUG = \"<slug>\" } under [shell_environment_policy] in ~/.codex/config.toml. Any other agent: its own environment settings.","Read teamyou-skill/SKILL.md for full usage. Run commands via: ./teamyou-skill/scripts/teamyou.sh <command> [args]","Check in once: \"$TY_DIR/scripts/teamyou.sh\" ty checkin","Then ask your person whether they want you to check in on a schedule, so messages and tasks left for you get picked up without them prompting you. Suggest the interval in \"checkin.cadence.recommended\" from \"$TY_DIR/scripts/teamyou.sh\" ty agent whoami (every 30 minutes today).","If they say yes: use your own scheduler if you have one (a recurring or scheduled task) to run ty checkin and do what it returns, as its own task rather than inside a conversation with your person. Otherwise use the matching snippet under \"checkin.setup\" in the same whoami output (a session-start hook, a heartbeat block, or a cron line). Tell them what you scheduled and how to stop it.","If they say no: schedule nothing, and check in at the start of each session instead."]}