Claude skill for use case integration with itwinai

[matbun]

Explore the opportunity of creating a Claude skill describing how to do the integration of a new use case in itwinai, maybe using past use cases examples. The integration should cover:

• distributed training
• HPO
• logging
• scalability report and profiling

This would reduce the adoption barrier for all the users working with Claude Code

[Anjali-Khantaal]

Hi @matbun, I would like to work on this issue if it is open for contributions.

I worked on itwinai last summer as a CERN openlab summer student, and I would be happy to contribute here. Before opening a draft PR, I wanted to share how I am thinking about the issue and check whether it matches what you had in mind.

My understanding is that the goal is to reduce the adoption barrier for scientists who already have a working training script and want to integrate it to itwinai with Claude Code’s help. I was thinking of creating a Claude skill with a SKILL.md file and a few supporting reference files that guide Claude through the main steps of an itwinai use-case integration, such as, adapting the existing training code into an itwinai Trainer, preparing the pipeline configuration, choosing/setting up logging, handling distributed training, generating or adapting SLURM configuration, and covering HPO, profiling, and scalability reporting.

For the first version, I was thinking of using the existing MNIST PyTorch use case as the reference because it is simple and easy for a new user to follow. If you think a scientific use case would be better as the reference, I can instead use the one you suggest.

I was unsure about the preferred location. I was thinking of including it as a project-level Claude Code skill under .claude/skills/ in this repo, so it is available when someone clones itwinai. But I am happy to explore other options like a separate repository similar to how the drought early warning use case (EURAC) is there as hython-itwinai-plugin, generated from itwinai-plugin-template.

I have read CLAUDE.md and CONTRIBUTING.md, and I will follow the existing conventions. If this direction sounds reasonable, I can open a draft PR with the skeleton first so that the structure can be reviewed before I fill in the full content.

Thanks!