matrix-server-management
Use for standalone Matrix admin requests (register users, create rooms, manage membership, upload files). Also use when you need to send a file to the admin via Matrix media upload. Do NOT use for Worker/project creation — those handle Matrix operations internally.
69
Quality
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Low
Low-risk findings worth noting
Matrix Server Management
Manage the Tuwunel Matrix Homeserver at ${AGENTTEAMS_MATRIX_URL}. User ID format: @<username>:${AGENTTEAMS_MATRIX_DOMAIN}.
Gotchas
- Workers IGNORE messages without
m.mentions— they haverequireMention: true. You MUST includem.mentions.user_idswith the full Matrix user ID for Workers to process the message (MSC3952) - User IDs in body text and
m.mentions.user_idsmust match exactly — partial or mismatched IDs cause silent failures trusted_private_chatonly invites members — you must ensure each invited user accepts withPOST /join; Controller-managed Worker and Team flows do this on the user's behalf- Matrix accounts cannot be deleted via API — reuse the same username on reset
- Do NOT use this skill for Worker/project creation —
create-worker.shandcreate-project.shhandle Matrix operations internally
Operation Reference
| Situation | Read |
|---|---|
| Any Matrix API call (register, login, rooms, messages, mentions, file upload) | references/api-reference.md |
- Repository
- agentscope-ai/AgentTeams
- Commit
223ddc2
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.