kcl-translate

Translate Markdown to KCL and KCL to Markdown while preserving the filename stem.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/orochi-network/khala --skill kcl-translate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kcl-translate
Source: https://github.com/orochi-network/khala/tree/main/skills/kcl-translate
Command: npx skills add https://github.com/orochi-network/khala --skill kcl-translate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate between Markdown and KCL while preserving the filename stem, enabling seamless bidirectional conversion without losing formatting.

Core Features & Use Cases

  • Bidirectional conversion: Markdown to KCL and KCL to Markdown, preserving the original filename stem.
  • Bootstrap-aware translation: Ensures compatibility with the KCL bootstrap symbol table and frame catalogue during translation.
  • Use Case: Convert project documentation from Markdown to a compact KCL representation for model context encoding, or expand KCL back to readable Markdown for human review.

Quick Start

Run the translator on a Markdown file (e.g., notes.md) to produce notes.kcl with the same stem.

Frequently Asked Questions about kcl-translate

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

FAQPage Schema
How do I convert Markdown to KCL format?

To convert Markdown to KCL, run the translator on your Markdown file. It automatically produces a KCL file with the same filename stem, ensuring compact context encoding for AI-assisted workflows.

Can I convert KCL back to readable Markdown?

Yes, you can expand KCL back to readable Markdown. The translator determines the conversion direction based on the input file extension, preserving the original filename stem for human review.

What is KCL used for in AI-assisted workflows?

KCL is used for compact context encoding in AI-assisted workflows. Translating project documentation from Markdown to KCL reduces token usage, while bidirectional conversion allows seamless expansion back to readable Markdown.

Does KCL translation preserve the original filename?

Yes, KCL translation preserves the original filename stem. Whether converting Markdown to KCL or vice versa, the output file maintains the same base name as the input file.

Do I need to load bootstrap specs for Markdown and KCL conversion?

Yes, Markdown and KCL conversion requires loading bootstrap specs and the symbol table. This bootstrap-aware translation ensures compatibility with the KCL bootstrap symbol table and frame catalogue during the conversion process.

How does the translator determine the output path for KCL files?

The translator relies on input file extensions to determine the conversion direction and output path. It automatically generates the output file path by preserving the original filename stem and swapping the extension.