Problem

ECC now has a large and growing skill surface, but generated/imported/learned skills do not yet have a clear long-term placement and provenance policy.

This creates several problems:

• unclear separation between curated skills and generated/learned skills
• validator noise around directories that may or may not exist locally
• weak provenance for imported or machine-generated skill content
• uncertainty about where future automated learning outputs should live

As ECC grows, the repo needs explicit rules for where generated skill artifacts belong and how they are identified.

Scope

Define a repo-wide policy for:

• curated vs generated vs imported skill placement
• provenance metadata requirements
• validator behavior for optional/generated skill directories
• whether generated skills are shipped, ignored, or materialized during install/build steps

Non-Goals

• Building a full external skill marketplace
• Rewriting all existing skill content in one pass
• Solving every content-quality issue in the same issue

Acceptance Criteria

• A documented placement policy exists for generated/imported skills
• Provenance requirements are explicit
• Validators no longer produce ambiguous behavior around optional/generated skill locations
• The policy clearly states what is publishable vs local-only
• Follow-on implementation work is split into concrete, bounded PR-sized steps