name: telegram-operational-routing description: Telegram-facing operating rules for choosing chat vs CLI, preserving user-friendly defaults, and generating correct file links for user-visible docs.
Use this skill when handling normal Telegram chat for the CEO and team.
Default to normal chat when the user is asking to think, explain, plan, compare, decide, write, or coordinate.
Use Claude Code CLI or any other CLI only when the user explicitly wants one of these:
Treat the absence of a command or explicit system request as a strong signal to stay in chat mode. Do not infer CLI intent from technical vocabulary, long messages, or screenshots alone.
If the user writes only normal text and does not ask for code or system work, do not auto-launch CLI. Ask a short clarification only if the task is ambiguous.
When sending user-facing files or markdown links, always use the real on-disk path in this form:
http://100.71.157.103:9120/<real-path>
Do not rewrite the path to /root unless the actual file lives there. Ensure all parent directories in the path are clickable (breadcrumbs) in the file browser interface so the user can easily navigate backward without browser history.
If the dashboard or file browser serves documents, the /files/ route should resolve from filesystem root / while still blocking sensitive files. It must serve directory indexes with explicit link contrast styling (e.g. blue for breadcrumbs, yellow for directory items) and avoid duplicate navigation links (like a separate "Thư mục cha" link) once segment-based path navigation is present.
Do not infer that a long or technical-looking normal message means the user wants CLI. Treat explicit task intent as the trigger.
references/chat-vs-cli.md — decision examples and file-link examplesGood prompts from the user:
Good chat-only prompts from the user:
When sending user-facing files or markdown links, always use the real on-disk path in this form:
http://100.71.157.103:9120/<real-path>
Do not rewrite the path to /root unless the actual file lives there. Ensure all parent directories in the path are clickable (breadcrumbs) in the file browser interface so the user can easily navigate backward without browser history.
If the dashboard or file browser serves documents, the /files/ route should resolve from filesystem root / while still blocking sensitive files. It must serve directory indexes with explicit link contrast styling (e.g. blue for breadcrumbs, yellow for directory items) and avoid duplicate navigation links (like a separate "Thư mục cha" link) once segment-based path navigation is present.
Do not infer that a long or technical-looking normal message means the user wants CLI. Treat explicit task intent as the trigger.
references/chat-vs-cli.md — decision examples and file-link examples