Define Documentation onyx-mcp integration

[JoCa96]

Why?

As a dev I want to use Coding assistants which use the best onyx context to create the best code.

Acceptance criteria

• Create PoC for Documentation to Skill/MCP-Resource transformation

Implementation details

• Documentation first => use most detailed source as basis for (summed-up) skills
• evaluate skill agent creator
  • https://skillsmp.com/skills/openclaw-openclaw-skills-skill-creator-skill-md
• gemini skills
  • https://geminicli.com/docs/cli/tutorials/skills-getting-started/
  • https://geminicli.com/docs/cli/skills/
• MCP vs Skill
  • MCP resources fulfill the same purpose as skills and are triggered the same way
  • => MCP first
• basis for everything LLM related is the onyx-MCP
  • implement as (version-independent) resources
  • if skills are preferable, provide CLI command to generate them

DEV handover checklist

Storybook

DEV handover done with: @ADD_DEV_NAME_HERE

Documentation

• "New" badge in Storybook is added, see storybook-addon-tag-badges
• Storybook code snippets are checked
• component status has been updated in the docs overview

Other

• follow-up tickets were created if necessary (add links below)