---
name: filename-tool
description: Create canonical filenames from plain-language requirements by using FilenameTool.com's live structured-input schema and browser interface. Use when asked to make, compose, generate, normalize, or propose a filename with dates, projects, descriptions, formats, creators, devices, dimensions, durations, qualities or codecs, flags, program provenance, colors, frame rates, or other Filename Tool conventions.
---

# Filename Tool

Translate the user’s request into Structured JSON, submit it to Filename Tool, and return the tool’s actual output. Treat Filename Tool—not a hand-built approximation—as authoritative for normalization and component order.

## Workflow

1. Fetch `https://filenametool.com/filename-tool-input.schema.json` once for the current request.
2. Open `https://filenametool.com/` with an available browser-control capability.
3. Translate only supported facts from the request into Structured JSON:
	- Resolve relative dates in the user’s timezone.
	- Use schema metadata for supported formats, format-specific qualities, flag definitions, and linked flag values.
	- Put linked values in `flagValues`; do not also add their IDs to `flags`.
	- Use `customFlags` only when no built-in flag expresses the requested meaning.
	- Omit unsupported or unspecified fields.
	- Prefer reasonable, reportable assumptions over interrupting for minor ambiguity.
4. Use the stable controls:
	- Open automation: `[data-ai-control="open-automation"]`
	- JSON input: `[data-ai-control="structured-input"]`
	- Validate: `[data-ai-control="validate-structured"]`
	- Apply: `[data-ai-control="apply-structured"]`
	- Result: `[data-ai-output="full-filename-with-extension"]`
5. Wait for validation to succeed and for the result’s `data-result-revision` to change. Read the displayed filename verbatim.
6. Return the displayed filename, and any material assumptions. Do not rename, move, upload, or modify files unless the user separately and explicitly requests it.
7. Return the Structured JSON if the user requests it.

Never construct, reorder, normalize, or repair the filename yourself. If live schema metadata conflicts with this skill, follow the schema.

## Failure handling

- If validation fails, correct the JSON using the displayed errors and retry once.
- If the available browser-control method fails, try another available browser-control method.
- If Filename Tool cannot be operated, return clearly labeled proposed Structured JSON and state that no authoritative filename was obtained. Direct the user to input the Structured JSON into the Filename Tool manually. Do not imitate Filename Tool’s output from memory.

For image or video files already containing the exact `-INFO-` component, follow the separate instructions at `https://filenametool.com/docs/replace-info-with-ai-description/`.