CJ_portability-audit

To audit skill portability, run a check that compares declared portability fields against actual executed dependencies within a git repository. This process verifies root scripts, config files, and the manifest to ensure skill declarations are honest.

A strict tier ladder evaluates dependency portability by ranking requirements from standalone to local-only to workbench. This mechanism ensures skill declarations match actual executed dependencies without hidden system requirements.

Yes, you need Bash and Grep to check declared dependencies in your config files. The portability audit requires these specific tools to perform static file checks across root scripts and the manifest.

Yes, you can manually adjudicate dependency requirements for bundled scripts using the portability_requires field. This allows you to handle bundled scripts and self-resolution preambles that deviate from standard static dependency linting.

Static dependency lint fails when declared portability fields do not match actual executed dependencies. The audit catches mismatches where skills claim standalone or local-only status but rely on workbench-level dependencies.

The best way to validate skill declarations is running a portability audit that compares declared fields against actual dependencies. This checks root scripts, config files, and the manifest to ensure declarations are honest.