skill-ecosystem: support additional import formats beyond current adapters

[jsyqrt]

Goal

Extend markus skill import to normalize more external skill formats. Current support: skills.sh / Claude Code, SkillHub / ClawHub, OpenClaw, SOUL.md, AgentScope, MCP servers (see docs/SKILL-ECOSYSTEM.md).

Candidate formats (pick one or propose another with community traction)

• OpenAI GPTs / Actions
• Dify plugins
• Cursor Rules / .cursor/rules
• n8n workflow nodes
• AutoGPT / A2A agent definitions

How

1. Read docs/SKILL-ECOSYSTEM.md §1-2 (supported formats + field mapping) and the import pipeline in packages/core (search for skill import in packages/core/src/skills/ or similar)
2. Add a detector + normalizer for one new format, mapping its fields to the Markus skill manifest
3. Export support is a bonus: markus skill export --format NAME

Reference files

• docs/SKILL-ECOSYSTEM.md
• packages/core skill import/export code (CLI: markus skill import/export)

Acceptance criteria

• New format auto-detected by markus skill import
• Round-trip metadata preserved (name, description, tools, permissions)
• Unit tests for detector + normalizer
• pnpm test / typecheck / lint pass

Size: M–L · Skill needed: TypeScript, format design · Please comment on the format you plan before starting to avoid duplicate work.

[Shxnque]

On prioritisation: of the candidates, A2A agent definitions and Cursor Rules (.cursor/rules) probably have the cleanest field mapping and the most current traction, while n8n workflow nodes give the widest reach if you're willing to model the node graph.

If the goal is genuine normalisation rather than one adapter per format, it may pay to express the mapping as a small declarative spec (source field -> canonical skill field + an optional transform) so each new format becomes a data file plus a thin parser instead of a bespoke adapter. Two things that keep it honest: (1) round-trip each format against a golden canonical fixture so an upstream format change surfaces as a fixture diff rather than a silent mismapping; (2) make unmapped source fields a warning, not a drop, so lossy imports are visible.

Happy to take one of these (leaning Cursor Rules or A2A) if you're assigning.