Teamgram Client E2E Flow

Documents the KHF Android client architecture and complete end-to-end data flows for login, messaging, and file operations through all Teamgram Server layers.

This skill is documentation-only and appears to be what it says, so it is coherent to install. Before you use it or apply any of the guidance: - Be careful with the 'unlock' recommendation: it explicitly suggests changing server-side code to bypass enterprise checks. That is an actionable change that can violate licensing, policy, or legal constraints and could create security issues. Do not apply it in production without legal/owner approval and a security review. - Verify the source repository and commit history (the SKILL.md points to github.com/teamgram/teamgram-server) before trusting constants or implementing changes. - Treat APP_ID/APP_HASH as public identifiers per the doc, but never supply or accept secrets that are not documented. - If you intend to follow implementation steps, do so in an isolated test environment and have code reviews; avoid applying bypasses that remove access controls. - If you want higher assurance, request provenance (who published the skill) and a pointer to the exact commit/tag in the referenced repo so you can audit the matching code.

Type: OpenClaw Skill Name: teamgram-client-e2e-flow Version: 1.0.0 The skill bundle consists entirely of technical documentation regarding the architecture and data flows of the Teamgram/KHF Android client and server. It contains no executable code, scripts, or instructions that would cause an AI agent to perform unauthorized actions, exfiltrate data, or compromise the host system (SKILL.md, _meta.json).