Federate Quark installation and LLM PTQ skills

[amd-zhaofeng]

What

Federate quark-install and quark-torch-llm-ptq into the AMD Skills catalog using copies imported from amd/Quark.

Why

Quark publishes versioned release branches and has no main branch. Track release/* so federation follows the newest matching release branch.

How

• Register both source directories and import them from release/0.13 at commit 313cb0b78ef364cb937598bc3431c46e28a226f4, with .federated.json provenance records.
• Map the upstream skills/quark-torch-ptq directory to the catalog name quark-torch-llm-ptq through the importer.
• Keep this submission scoped to catalog intake. The marketing team selects the showcase bundle separately; marketplace manifests and its routing room match the base branch.

Test

• ./.github/scripts/publish.sh completed successfully; generated manifests match the base branch.
• ./.github/scripts/check.sh passed: 10 skill folders, 77 evaluation cases plus 5 shared negative cases, 190 internal references, and all plugin manifest checks.
• git diff --check passed.
• Prior CI on commit 03ca0cb validated the unchanged Quark skill content: 10/10 routing cases passed, and both skills passed their behavioral evaluations on Linux and Windows. The current showcase routing room does not include these two skills.

[danielholanda]

The two skills work as expected in Claude. I found no broken links or any big problems worth raising here, so I'm happy to approve this. That said, there are some non-blocking issues (like the PTQ skill labeling layer exclusions as Quark's defaults without first checking Quark), which can be addressed directly on the Quark repo.