executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
cli-scansScan files, directories, or stdin for PII with the Presidio CLI.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when you need the presidio command to scan files, directory trees, or stdin for PII findings.
-../analyze-text/SKILL.md../anonymize-text/SKILL.md../../references/service-and-rest-api.mdreferences/cli-reference.md for command syntax, formats, and scan behaviorreferences/configuration.md for PresidioCLIConfig, config precedence, and YAML fieldsreferences/troubleshooting.md for common failures and recovery stepsscripts/presidio_cli_smoke.sh for a safe help check and tiny scan smoke testscripts/sample_presidiocli.yaml for a portable config templatepresidio--config-data, --config-file, current .presidiocli, then the bundled default config--threshold overrides the loaded config for one runpathspec in gitwildmatch mode--format auto prefers GitHub annotations in GitHub Actions, colored output in a TTY, and standard output otherwisegithub format in CI and parsable format for line-oriented machine parsingIf a scan fails or behaves unexpectedly, check references/troubleshooting.md first. It covers invalid YAML, unknown entity names, missing spaCy model issues, ignore-pattern surprises, threshold confusion, stdin versus file behavior, output-format expectations, and the current exit-code caveat.