Server generation skill

[dmartinol]

Fix: #721

Motivation and Context

Support developers to draft the server definition document.

How Has This Been Tested?

Tested with Claude Code and a validatino report is attached in the validation sub-folder.

Breaking Changes

NO

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

[dmartinol]

@rdimitrov

[rdimitrov]

@dmartinol - Thanks for filing this! 🙏

@domdomegg - hey, we were chatting with Daniele the other day and he shared he had created a skill to help creating server.json files, so I suggested having it hosted upstream could be of benefit for more people. I have to read more about the best practices around creating Claude Skills to be able to review this properly. I assume you might be able to help review this better but in any case I don't want to put you on the spot 👍

[domdomegg]

Thanks for the contribution! I am unsure about:

• Whether a skill is needed e.g. compared to performance of just reading the docs directly already. Often skills are most helpful when the content is not already documented centrally, or are private information e.g. for a particular organisation.
• If we want a skill, whether we want it to live here

Possibly the answer to both of the above is yes. But I think for now I'd probably lean towards you maybe publishing this separately and linking from the community resources in docs?