skill-proposal.yml

name: Skill proposal
description: Propose a new skill for the AMD Skills catalog.
title: "[Skill proposal] <short outcome or skill name>"
labels:
  - skill-proposal
body:
  - type: markdown
    attributes:
      value: |
        Thanks for proposing a skill! Skills earn their keep on **repeated, opinionated AMD workflows**.
        Before filing, please skim `CONTRIBUTING.md` (especially *"Is this task a good fit for a skill?"* and the two contribution paths) so we can route this proposal quickly.

        Fill out the short fields below, then describe the skill in detail at the end.

  - type: input
    id: name
    attributes:
      label: Proposed skill name
      description: Use `lowercase-with-hyphens`, max 64 characters, action- or outcome-oriented (e.g. `porting-cuda-to-hip`, `tuning-mi300x`, `picking-rocm-container`). Avoid generic names like `helper` or `gpu-stuff`.
      placeholder: e.g. tuning-mi300x-inference
    validations:
      required: true

  - type: dropdown
    id: prior_art
    attributes:
      label: Does something like this already exist?
      description: Help us avoid duplicating effort. If you pick a "Yes" option, link the prior art in the description below.
      options:
        - "No — new idea"
        - "Yes — as documentation, a runbook, or internal guide"
        - "Yes — as a similar skill in another catalog or repo"
        - "Not sure — happy to discuss"
    validations:
      required: true

  - type: dropdown
    id: home
    attributes:
      label: Where should this skill live?
      description: See the two contribution paths in `CONTRIBUTING.md`. Path A skills are authored under `skills/` in this repo; Path B skills live in a product repo and are registered here via `catalog/`.
      options:
        - "Path A: incubated in this repo (may move to a product repo and continbue to be registered here)"
        - "Path B: authored in a product repo (HIP, ROCm, Ryzen AI, Lemonade, ...) and registered here"
        - "Not sure yet — needs discussion"
    validations:
      required: true

  - type: dropdown
    id: focus_area
    attributes:
      label: Catalog focus area
      description: Which focus area in the catalog best fits this skill?
      options:
        - "Application integration"
        - "Hardware-native"
        - "Cross-stack porting"
        - "Profiling and delivery"
        - "Other / not sure"
    validations:
      required: true

  - type: textarea
    id: description
    attributes:
      label: Skill description
      description: |
        Describe the skill in as much detail as you can. Useful things to cover:
          - **User goal**: what is the user trying to achieve when this skill should fire?
          - **Trigger surface**: words, phrases, file extensions, error messages, product names that should route to this skill.
          - **Platform Scope**: Is this for client? server? Both?
          - **Inputs and outputs**: what does the agent receive, and what does it produce?
    validations:
      required: true