[Docs]: Sync issue template categories with registry (add creative, security)

[rosspeili]

Type of fix

Doc drift (catalog, examples index, agent loops)

What needs to be fixed?

Problem

The New Skill Proposal template (.github/ISSUE_TEMPLATE/01_skill_proposal.yml) category dropdown is out of date vs the live registry and CONTRIBUTING.md § Skill categories.

Contributors proposing skills under creative/ or security/ must pick “Propose new category (describe below)” even though those categories already exist with shipped skills:

Category	Registry skills (current)
creative	creative/bg_remover
security	security/prompt_injection_firewall

This adds friction and noise in issues (e.g. deck_builder proposal, security skills).

Scope

In scope (small PR):

1. .github/ISSUE_TEMPLATE/01_skill_proposal.yml — add dropdown options:

   • creative
   • security
   • Keep existing options aligned with CONTRIBUTING (no removals needed).
   • Optional polish: sort options alphabetically (except keep “Propose new category…” last).

2. Template intro markdown (same file) — one line linking to CONTRIBUTING category table so future drift is obvious.

3. .github/labels.json (optional but recommended) — add a creative label (e.g. color/description similar to examples) for issue/PR filtering. security label already exists.

4. Run label sync if labels.json changes — .github/workflows/sync-labels.yml / scripts/sync_labels.py per repo convention.

5. CONTRIBUTING.md (one line, maintainer checklist) — under issue templates or release checklist: when adding a new top-level category under skills/, update 01_skill_proposal.yml dropdown + category table in the same PR.

Out of scope:

• Changing skill folder layout or adding new categories to the registry
• templates/python_skill/ default category: utility (legacy placeholder; separate cleanup if ever needed)
• Other issue templates — only 01_skill_proposal.yml has a category dropdown today; no other template file needs category options unless we add dropdowns later

Acceptance criteria

• 01_skill_proposal.yml lists creative and security alongside all categories in CONTRIBUTING’s category table
• Dropdown matches CONTRIBUTING (11 categories + “Propose new category…”)
• No duplicate or obsolete category names
• If creative label added: sync-labels workflow applied or documented for maintainer
• Quick manual check: open “New Skill Proposal” on GitHub and confirm new options appear

Reference — canonical category list (CONTRIBUTING)

creative, compliance, data_engineering, defi, dev_tools, finance, monitoring, office, optimization, security, wellness

Suggested dropdown order (alphabetical, propose-last)

compliance, creative, data_engineering, defi, dev_tools, finance, monitoring, office, optimization, security, wellness, Propose new category (describe below)

Affected Page(s)

.github/ISSUE_TEMPLATE/01_skill_proposal.yml, .github/labels.json CONTRIBUTING.md, docs/contributing/ai_native_workflow.md, only if we add a one-line “pick category from template” note

[UroojFatima-052]

Hi @rosspeili ! I'd like to take this one.

Plan is to update the dropdown in 01_skill_proposal.yml with all 11 categories in the alphabetical order you listed, keep "Propose new category…" last, and add the one-line note linking to CONTRIBUTING at the top of the template. For the creative label in labels.json, I'll match the format of the existing security one.

Just wanted to confirm should I run sync_labels.py locally after adding the label or leave that for maintainers?

[rosspeili]

Hey @UroojFatima-052, welcome, and sure, go for it. That is a good q, and if you decide to add creative as a new label, it will sync on CI and if not I'll run the action.