skill-conversion

Sorry, I can't answer that.

4|1|Updated Apr 23, 2026

Search Tags:#migration #skill #convert #workflows #frontmatter #open-code

Ready to run

npx skills add https://github.com/johnnyasantoss/opencode-config --skill skill-conversion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-conversion
Source: https://github.com/johnnyasantoss/opencode-config/tree/main/skills/skill-conversion
Command: npx skills add https://github.com/johnnyasantoss/opencode-config --skill skill-conversion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts skills from Claude Code, VS Code, Cursor, or other ecosystems into OpenCode-native format for consistent discovery and deployment within the OpenCode platform.

Core Features & Use Cases

Enables translation of existing skills into the OpenCode structure with proper frontmatter and directory layout.
Maintains trigger phrases and intent while standardizing metadata for cross-platform compatibility.
Facilitates migration workflows for teams updating legacy skills to OpenCode standards.

Quick Start

Identify the source skill, map its structure to OpenCode conventions, and produce a compliant OpenCode-native skill directory.

Frequently Asked Questions about skill-conversion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate Claude Code and Cursor skills into the OpenCode format?▼

To convert Claude Code, Cursor, or VS Code skills into OpenCode format, identify the source skill, map its structure to OpenCode conventions, and generate a compliant OpenCode-native directory with proper frontmatter and layout for deployment.

What does converting a skill to OpenCode-native format actually do?▼

Converting to OpenCode-native format standardizes metadata, enforces proper frontmatter and directory structure, and maintains original trigger phrases to ensure consistent skill discovery and deployment within the OpenCode platform.

Do I need to update frontmatter manually when migrating workflows to OpenCode?▼

Manual frontmatter updates are unnecessary because the conversion process automatically enforces OpenCode frontmatter and directory structure, ensuring cross-platform compatibility while maintaining the original trigger phrases and intent.

Can I translate VS Code skills for OpenCode discovery without losing trigger phrases?▼

Yes, translating VS Code skills into OpenCode structure maintains the original trigger phrases and intent while standardizing metadata, ensuring consistent discovery and cross-platform deployment within the OpenCode ecosystem.

What is the best way to standardize legacy skill directories for OpenCode deployment?▼

The best way to standardize legacy skill directories for OpenCode deployment is mapping the existing structure to OpenCode conventions, applying progressive disclosure, and enforcing OpenCode frontmatter standards throughout the conversion process.