file-boundaries
Protect Parallel File Work
Parallel implementation can cause agents to overwrite files from other workstreams. This skill defines ownership, read-only access, and blocked workflows for Claude, Codex, and Claude Code.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "file-boundaries" from https://skillstore.io/skills/clouder0-file-boundaries.md and its manifest at https://skillstore.io/api/skills/clouder0-file-boundaries/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "file-boundaries". A task needs to update authentication and reference shared user types.
Expected outcome:
The agent edits only the authentication files, reads the shared types, and reports blocked if a type change is required.
Using "file-boundaries". Two agents need to work on authentication and API routes at the same time.
Expected outcome:
Each agent receives a separate ownership area, read-only dependencies, and a rule to stop before crossing boundaries.
Using "file-boundaries". An implementation plan includes a change to an unowned utility file.
Expected outcome:
The plan is marked blocked with the file name, reason for the requested change, and a suggested ownership update.
Security Audit
SafeAll static external-command findings are false positives caused by Markdown fences or inline code examples in SKILL.md. The blocker finding is also a false positive because the text describes avoiding file conflicts, not system reconnaissance. No prompt injection or malicious intent evidence was found.
Risk Factors
⚙️ External commands (8)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/clouder0-file-boundaries/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/clouder0-file-boundaries?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/clouder0-file-boundaries?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/clouder0-file-boundaries/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/clouder0-file-boundaries.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Clouder0. (2026). file-boundaries security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/clouder0-file-boundaries/audits/8BibTeX citation
@techreport{clouder0-clouder0-file-boundaries-2026,
author = {Clouder0},
title = {file-boundaries security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/clouder0-file-boundaries/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "file-boundaries security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Clouder0"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/clouder0-file-boundaries/audits/8"
identifiers:
- type: other
value: "skillstore:clouder0-file-boundaries:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Coordinate Parallel Feature Work
Split feature implementation across agents while keeping each agent inside assigned files and directories.
Protect Shared Type Files
Allow agents to read shared types or utilities while blocking unapproved edits to those files.
Report Blocked Changes Clearly
Capture boundary violations with the needed file, reason, and suggested ownership update.
Try These Prompts
Use file-boundaries. I own src/auth/login.ts and can read src/types/user.ts. Before editing, confirm the file is inside my ownership.
Use file-boundaries for two agents. Agent A owns src/auth. Agent B owns src/api. List allowed edits and blocked changes.
Apply file-boundaries while adding session logic. I own src/auth. I can read src/types/user.ts. Report blocked if type changes are required.
Review this implementation plan with file-boundaries. Identify files outside ownership, read-only dependencies, and changes that should be blocked before work starts.
Best Practices
- List owned paths and read-only paths before implementation begins.
- Keep ownership narrow enough to prevent unrelated edits.
- Report blocked changes with the file, need, and suggested resolution.
Avoid
- Editing read-only files because the change seems small.
- Assuming ownership from nearby files or directory names.
- Using broad ownership lists that hide real coordination problems.