メニュー
Use when you need to share a file or directory with the user via a clickable link. The CharlieBot server has a built-in file browser that serves any file on the host filesystem.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Enforces explicit user approval before implementing any plan. Use when presenting a plan, receiving plan feedback, or about to delegate implementation.
CharlieBot repo structure, architecture, and development conventions. Use when modifying charlie-bot code.
How to write effective improve loop goal prompts — for the master CC agent that writes the --goal-file content.
methodology for iterative improve loop workers.
CharlieBot skill directory layout, sync rules, and CLI tool mappings. Use when creating, installing, or syncing skills across Claude Code, Codex, Gemini, OpenCode, and Antigravity.
This skill should be used when the user asks to read, create, or edit Feishu/Lark documents, search docs in their Feishu workspace, or fetch content from a Feishu wiki or docx URL.
| name | file-server |
| description | Use when you need to share a file or directory with the user via a clickable link. The CharlieBot server has a built-in file browser that serves any file on the host filesystem. |
| version | 1.0.0 |
Share files and directories with the user by generating links to the CharlieBot file server. The server serves any file on the host filesystem via the /files/ endpoint.
<base_url>/files/<absolute-path>
Where <base_url> is the CharlieBot URL resolved from HOST MEMORY (look for the CharlieBot URL entry).
The path after /files/ is the absolute filesystem path (without leading /). Examples:
| Filesystem path | URL |
|---|---|
/path/to/trace.json | <base_url>/files/path/to/trace.json |
/path/to/results/ | <base_url>/files/path/to/results/ |
Whenever you need to present a file to the user (logs, traces, checkpoints, images, configs, etc.), generate the URL instead of dumping file contents into chat. This is especially useful for:
Always verify the file/directory exists before sharing the link (use ls or Glob)
Resolve base URL from HOST MEMORY — never hardcode hostnames or ports
Present the link in markdown format: [descriptive text](url)
If the file is a Perfetto/Chrome trace (.json trace from training/profiling, or a directory of rank traces), ALWAYS also include a Perfetto viewer link alongside the file link. Read the perfetto skill for how to construct the viewer URL.
Trace indicators: filename matches trace_rank*.json / *trace*.json, lives under a trace/ or profile/ dir, or the user called it a "trace"/"profile"/"perf capture".