community-publish

To publish a local skill safely, use a workflow that strips PII, scans for secrets, and generates a clean submission package with PR-ready artifacts for the community catalog.

Secret scanning and PII stripping work by enforcing safety checks during a dry-run packaging workflow, ensuring sensitive data and contributor metadata are sanitized before submission.

Yes, you can prepare PR-ready artifacts without leaking secrets by applying a dry-run packaging workflow that enforces safety checks and explicit user approvals before submission.

The best way to package agent templates for community submission is to use a workflow that enforces contributor metadata, applies dry-run packaging, and generates a clean submission package.

Your submission requires explicit user approvals and contributor metadata because the workflow safety and governance process enforces these checks before publishing to the community catalog.

Yes, you need a dry-run packaging workflow to share org templates externally, as it ensures PII is removed, secrets are scanned, and a clean submission package is prepared for the community.