check_exists

Check whether a filesystem path exists and return a boolean result.

8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/OpenAuthority/clawthority --skill check-exists
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check_exists
Source: https://github.com/OpenAuthority/clawthority/tree/main/examples/skills/check_exists
Command: npx skills add https://github.com/OpenAuthority/clawthority --skill check-exists

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checks whether a given filesystem path exists (file or directory) and returns a boolean result to drive decision logic.

Core Features & Use Cases

  • Exists check for files and directories, returning { exists: true } or { exists: false }.
  • Use cases include guarding writes, validating configuration paths, and conditioning automation flows on path existence.

Quick Start

Check if a path exists by providing the absolute path to the skill and reading the returned exists boolean.

Frequently Asked Questions about check_exists

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a file or directory path exists without throwing an error?

To check if a path exists without triggering exceptions, provide the absolute path to return a boolean { exists: true } or { exists: false } result. This safely handles missing files and directories for precondition checks.

What is the best way to validate filesystem paths for automation workflows?

Validating filesystem paths for automation involves performing an existence check to return a boolean value. This guards writes and validates configurations by conditioning automation flows on whether the target path exists.

When do I need to verify path existence before writing files?

You need to verify path existence before writing files to prevent overwrites or missing directory errors. Checking existence returns a boolean precondition result, ensuring your filesystem automation only executes when the path state matches expectations.

Does the path exists check work for both files and directories?

The path exists check works for both files and directories, returning a unified boolean result. It processes any valid filesystem path input to determine existence, making it suitable for diverse configuration validation and automation guard scenarios.

How do I validate configuration paths before running an automation script?

Validating configuration paths before running an automation script requires passing the path string to an existence check. The returned boolean directly conditions your automation flow, preventing execution if the required filesystem path is absent.