# File Manager

> Manage File Management assets when the assistant has concrete, user-authorized file targets.

- Skill: `zgiai/file-manager` (Agent Skill)
- Install (CLI): `npx skillmds@latest add zgiai/file-manager`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zgiai/file-manager/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: zgiai (https://skillmd.com/u/zgiai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/zgiai/file-manager

---


# File Manager Skill

Use this skill for governed File Management asset operations. It is intentionally separate from `file-reader` and `file-generator`: reading and summarizing file contents belongs to `file-reader`, generating temporary downloadable artifacts belongs to `file-generator`, and creating or deleting File Management assets belongs here.

## Workflow

1. Use this skill only when the user explicitly asks to change File Management, such as deleting a visible file or saving a generated/external file into the current Files page.
2. Do not invent file IDs. For existing files, use a file ID supplied by resolved page context or governed asset resolution.
3. For deletion requests with a resolved target, call `delete_file` with exactly that `file_id`.
4. For create/save/import requests where file content still needs to be produced, first use the appropriate artifact-producing skill to create a temporary artifact, then call `save_file_to_management` with `source_type=tool_file`, the returned `tool_file_id`/`file_id`, and the destination filename.
   - Use `file-generator` for regular files and generic SVG/vector files.
   - Use `chart-generator` only for chart, graph, and data visualization artifacts.
5. For create/save/import requests where the user supplied a public file URL, call `save_file_to_management` with `source_type=url`, the URL, and the destination filename.
6. Do not ask for a separate natural-language confirmation before governed operations. Tool governance owns the approval card and will stop execution when approval is required.
7. If the target or destination filename is ambiguous or missing, ask one concise clarification instead of calling a mutating tool.
8. If governance says approval is required, tell the user the operation has not run yet and wait for the approval result. If approval is rejected, continue with a safe alternative.
9. Mention the file name when confirming a create or deletion. Do not expose internal file IDs unless the user explicitly asks for them.

## Tool Usage

`delete_file` accepts:

- `file_id`: required file ID from resolved context. Deletes exactly one file after governance allows execution.
- Success evidence: the tool result must indicate success for the requested `file_id`, such as `deleted_count > 0`, `deleted=true`, or an equivalent successful status. If the tool returns an error, a missing file, or an approval rejection, do not say the file was deleted.

`save_file_to_management` accepts:

- `source_type`: required, `tool_file` for a generated artifact or `url` for a public external URL.
- `tool_file_id`: required when `source_type=tool_file`; use the generated artifact ID returned by the generation tool.
- `url`: required when `source_type=url`; must be an absolute public HTTP or HTTPS URL supplied by the user.
- `filename`: required destination filename shown in File Management. Include a suitable extension.
- `workspace_id`: optional target workspace ID. Usually omit it so the current assistant workspace context is used. Do not invent IDs.
- Success evidence: the tool result must include a managed File Management identity such as `managed_file_id`, `upload_file_id`, or a successful saved-file record plus the saved `filename`. If only a temporary artifact exists, do not say the file was saved into File Management.

## Truthfulness Contract

- Treat tool results as authoritative. A planned File Management operation is complete only when the matching tool result has success evidence for the exact target.
- If the tool fails, approval is rejected, or success evidence is missing, state that the operation was not confirmed and include the short failure reason when useful.
- Retry at most once with corrected arguments when the error is recoverable. Do not repeat the same mutating call with identical arguments after a failure.