Strix (STRIX) — utils

docs / modules / utils

← all docs

Strix (STRIX) — utils

flowchart LR IN["IN: file paths, API spec\nfiles, secret-bearing config"] --> ACT["ACT: resolve paths,\nparse specs, guard secrets"] ACT --> VAL["VAL: — none\n(pure helper functions)"] VAL --> OUT["OUT: resolved paths /\nparsed spec objects /\nredacted output"]

What this is

strix/utils is the small-helpers package — path resolution, OpenAPI/Postman spec parsing (for the API-testing target mode), and secret-file handling utilities used across several other packages.


Technical details

flowchart LR IN["IN: file paths, API spec\nfiles, secret-bearing config"] --> ACT["ACT: resolve paths,\nparse specs, guard secrets"] ACT --> VAL["VAL: — none\n(pure helper functions)"] VAL --> OUT["OUT: resolved paths /\nparsed spec objects /\nredacted output"]

Package: strix/utils/ Depends on: nothing else in strix/ (leaf helpers). Depended on by: strix.interface.scan_setup (API-spec staging for --target ./openapi.yaml), strix.config.loader (secret-file write helpers for ~/.strix/cli-config.json).

Files at a glance

File Role
api_spec.py Parses OpenAPI/Swagger and Postman collection files into a normalized target-endpoint list, per the README's "API Testing" usage.
resource_paths.py Resolves bundled resource paths (skills, prompts, static assets) whether running from source or a packaged build.
secret_files.py write_secret_text() and similar — writes files like ~/.strix/cli-config.json with restrictive (mode 0600) permissions.

Files & functions, explained

Entirely deterministic — parsing, path math, and file-permission handling, no model calls anywhere in this package.

Related: STRIX — Architecture (HLD), interface.md, config.md.