Menu

Individual skill

file-access-preflight

0upvotes

Run the pre-flight checklist before an agent gets filesystem access — the scope boundary (which directories, read vs write), the secrets-exposure sweep, the destructive-operation gates, and the path-traversal and untrusted-file defenses. Use when asked let my agent access my files safely, is it safe to give the agent file/computer access, guardrails before the agent touches my filesystem, or scope down my coding agent's reach. Produces the scope boundary, the secrets sweep, the write/delete gates, and the untrusted-content rules.

skills/file-access-preflight/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,541
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# File Access Preflight Skill

Filesystem access is where an agent goes from talking to *doing* — and the two failure modes are opposite: reading too much (the agent slurps your `.env`, SSH keys, and password manager export into its context and thence into logs and API calls) and writing too much (a confused or hijacked agent overwrites, deletes, or `rm -rf`s outside its lane). The seatbelt: draw the scope boundary tightly, sweep for the secrets that must never enter context, gate the destructive operations, and treat file *contents* as untrusted input — because a file the agent reads can carry instructions just like an email or a web page.

## What This Skill Produces

- **The scope boundary** — the exact directories the agent may read and (separately, more narrowly) write, and everything explicitly out of bounds
- **The secrets sweep** — the credential-bearing files that must be excluded from the agent's reachable scope, checked before go-live
- **The destructive-operation gates** — which writes/deletes/moves require confirmation, and the never-outside-scope rule
- **The untrusted-content defenses** — the rule that file contents are data, and the path-traversal guard

## Required Inputs

Ask for these if not provided:
Back to top