OpenParable
Skip to content
← Back to skills

F8 Tools Io Filesystem Workflow

Development
f8-tools-io-filesystem-workflow

F8 Tools Io Filesystem Workflow is an Agent Skill for development published in the TippingGame/F8Framework repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when working with IO/FileSystem tools — file read/write, directory operations, and path utilities in F8Framework.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/TippingGame/F8Framework/blob/HEAD/Tests/AISkills/f8framework-skills/tools/f8-tools-io-filesystem-workflow/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/f8-tools-io-filesystem-workflow, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

IO/FileSystem Tools Workflow

Use this skill when

  • The task involves file I/O, directory management, or path manipulation.
  • The user needs to read/write files, copy/move/delete, or manage directories.

Path resolution

  1. Source: Assets/F8Framework/Runtime/Utility/IO.cs (~35KB)

Sources of truth

  • Source file: Assets/F8Framework/Runtime/Utility/IO.cs

Key capabilities

  • File read/write (text, bytes, streams)
  • Directory creation, deletion, enumeration
  • File copy, move, rename
  • Path manipulation and normalization
  • File existence checking
  • File size and metadata queries
  • Platform-specific path handling
  • Recursive directory operations

Workflow

  1. Use Util.IO or FileTools class (check actual class name in source).
  2. All methods are static — no initialization needed.
  3. Handle platform differences: use Application.persistentDataPath for writable paths.
  4. Be careful with StreamingAssets on Android (read-only, in APK).

Common error handling

ErrorCauseSolution
File write failsPath not writableUse Application.persistentDataPath
StreamingAssets read fails on AndroidFiles inside APKUse SyncStreamingAssetsLoader
Path separator issuesWindows vs Unix pathsUse Path.Combine() and normalize

Output checklist

  • File operation type identified.
  • Platform-appropriate paths used.
  • Error handling for I/O exceptions.