Udpating cudaq-guide skill and adding qiskit-to-cudaq skill

[sacpis]

Udpating cudaq-guide skill and adding qiskit-to-cudaq skill

[mitchdz]

/nv-skills

[mosheabr]

Thanks Sachin, the content itself looks like solid work, but this PR can't land here. The skills/ directories in this catalog are synced from each product's source repo every hour, so direct edits here get reverted by the next sync, and the content integrity check is failing because the changed and added files don't carry signature refreshes.

The right path for both changes. Make the cudaq-guide updates and add qiskit-to-cudaq in the CUDA-Q source repo, run the signing pipeline there for both skills (that also regenerates the skill card and benchmark for the new skill), and add a qiskit-to-cudaq entry to components.d/cuda-q.yml in this repo. The sync then brings the signed content in automatically. One more thing worth doing in the same pass, cudaq-guide currently has unsigned changes at source that the sync keeps holding back, so a re-sign there clears that too.

Happy to walk you through the steps if useful. Closing the content changes out of this PR, the components.d registration line can happen here once the source side is signed.

[sacpis]

The right path for both changes. Make the cudaq-guide updates and add qiskit-to-cudaq in the CUDA-Q source repo, run the signing pipeline there for both skills (that also regenerates the skill card and benchmark for the new skill

This is already done in cuda-quantum repo with the PR #4812.

add a qiskit-to-cudaq entry to components.d/cuda-q.yml in this repo.

Added with commit 4b9943d.

Thank you @mosheabr for detailed guidance here.

[mosheabr]

Thanks Sachin, the PR is now exactly the right shape, one registration entry, and the source PR route is correct. One gap remains before this can merge. The signing pipeline hasn't actually run on qiskit-to-cudaq in cuda-quantum. The skill there has SKILL.md, evals, and references, but no skill.oms.sig, skill-card.md, or BENCHMARK.md, and those are required before the catalog will sync it. Trigger the pipeline on a PR in cuda-quantum (comment /nvskills-ci on it) and the missing artifacts get generated and committed. While you're at it, cudaq-guide has content changes at source that were never re-signed, which is why the catalog sync keeps holding its updates back. The same pipeline run can clear that too. Once the artifacts are in cuda-quantum main, this PR merges as is.

[sacpis]

Thanks Sachin, the PR is now exactly the right shape, one registration entry, and the source PR route is correct. One gap remains before this can merge. The signing pipeline hasn't actually run on qiskit-to-cudaq in cuda-quantum. The skill there has SKILL.md, evals, and references, but no skill.oms.sig, skill-card.md, or BENCHMARK.md, and those are required before the catalog will sync it. Trigger the pipeline on a PR in cuda-quantum (comment /nvskills-ci on it) and the missing artifacts get generated and committed. While you're at it, cudaq-guide has content changes at source that were never re-signed, which is why the catalog sync keeps holding its updates back. The same pipeline run can clear that too. Once the artifacts are in cuda-quantum main, this PR merges as is.

Thanks @mosheabr. Have requested help from @mitchdz to run the command on the existing PR.

[sacpis]

Hey @mosheabr, Is this good to go now? We ran /nvskill-ci on a PR in CUDA-Q. Do we need to wait for it to be merged?