Define capability boundaries and ownership rules for file navigation systems.
npx skills add https://github.com/AesopScott/mojo --skill path-queries
Please help me install this Agent Skill. Skill: path-queries Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/path-queries Command: npx skills add https://github.com/AesopScott/mojo --skill path-queries
This skill addresses the risk of uncontrolled file access and over-privileged system operations by providing a structured framework for defining capability boundaries and ownership rules.
Use the path-queries skill to define a new capability boundary for the file navigation system by identifying the missing ownership rule and proposing a minimal configuration change.
High-intent search queries and answers about installing and using this skill.
To enforce capability boundaries during architectural refactoring, use a structured framework to map code to capabilities and proofs, strictly bounding new edits by ownership rules to prevent unauthorized access to sensitive paths.
Capability-to-code-to-proof mapping is a structured schema defining how a system links code to specific capabilities and verifications, ensuring strict adherence to boundary constraints and preventing over-privileged system operations.
Prevent unauthorized system expansion by precisely configuring ownership-rule sources to control file navigation and capability boundaries, verifying both positive and negative test cases to ensure no accidental access to sensitive paths occurs.
The best way to verify boundary constraints for security-sensitive path control is to execute strict verification of positive and negative test cases, ensuring the file navigation system adheres to defined capability and ownership rules.
Yes, you need defined ownership rules to control file navigation and prevent over-privileged operations, as they provide the boundary constraints to stop uncontrolled file access and unauthorized system expansion.
HechaoYannetGenerate a master architecture document from GDDs, ADRs, and governance constraints.
AesopScottManage session lifecycle hooks and capability boundaries in the Session Manager harness.
AesopScottManage trust-state transitions and expiry policies for AI system routes.
wfvueConfigure Tauri v2 permission controls with allow/deny rules and capability mappings.
