path-types Skill
Choose Rust types for operating system paths across the Codex repository. Use when defining new path-bearing types or explicitly migrating existing ones. Published by openai in codex.
Decision snapshot
Is this a fit?
Developers using codex, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
28 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is path-types Skill?
Choose Rust types for operating system paths across the Codex repository. Use when defining new path-bearing types or explicitly migrating existing ones. Published by openai in codex. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using codex
Declared skill metadata
- Source file: .codex/skills/path-types/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use path-types Skill
- Use it for developers using codex.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/codex
- Skill file: .codex/skills/path-types/SKILL.md
What it does
Choose Rust types for operating system paths across the Codex repository. Use when defining new path-bearing types or explicitly migrating existing ones.
Skill instructions
Path Types Apply this guidance when defining new types. Change existing code only when explicitly requested, and keep edits minimal and proportional. Treat these rules as the target state of an ongoing migration; if compliance is difficult, ask the user how to proceed. - In app-server protocol types, use LegacyAppPathString for backwards compatibility during the URI migration. At the protocol boundary, convert it to PathUri and use PathUri internally. For host-local logic, such as some config values, use AbsolutePathBuf or PathBuf instead. - In exec-server protocol types, use PathUri. Internally, use PathUri or AbsolutePathBuf as appropriate. - In dependencies shared by both servers, use PathUri or separate APIs that decouple their use cases. - Tool call arguments that the model is expected to generate should be deserialized as regular Strings with feature-specific path handling code. Migration requirements Keep these requirements in mind while migrating code to conform with the above
Verified compatibility and discovery
Frequently asked questions
What is path-types?
path-types is a open-source AI agent skill with Copy skill directory. Choose Rust types for operating system paths across the Codex repository. Use when defining new path-bearing types or explicitly migrating existing ones.
Who is path-types best for?
path-types is best for reusing agent instructions, scripts, and references.
How do I install path-types?
Install or run path-types using Copy skill directory. Check path-types for the latest setup command.
Is path-types actively maintained?
path-types may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
