transformable-frontmatter

Strip adapter-specific frontmatter from SKILL.md files for cross-adapter portability.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill transformable-frontmatter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: transformable-frontmatter
Source: https://github.com/xiongxianfei/rigorloop/tree/main/tests/fixtures/adapters/transformable-frontmatter
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill transformable-frontmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of lock-in to a single adapter by converting Skill definitions to a portable, adapter-agnostic format that preserves the core identity (name) and description while removing adapter-specific frontmatter.

Core Features & Use Cases

  • Remove frontmatter fields tied to a specific adapter, leaving a clean, universal YAML header.
  • Preserve the body instructions for direct execution or interpretation by compatible runtimes.
  • Enable cross-adapter reuse of skills without editing the embedded payload or behavior.

Quick Start

Run the transformer to strip adapter-specific frontmatter from SKILL.md.

Frequently Asked Questions about transformable-frontmatter

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

FAQPage Schema
How do I remove adapter-specific frontmatter from SKILL.md files?▼

To remove adapter-specific frontmatter, run a transformation that strips adapter-only metadata from the YAML header. This ensures the SKILL.md file retains a valid name and description while preserving the operational body for execution.

What is the best way to make skills portable across different adapters?▼

Making skills portable across adapters requires converting Skill definitions to an adapter-agnostic format. This process drops adapter-only frontmatter fields, leaving a clean, universal YAML header that enables cross-adapter reuse.

Does converting SKILL.md to a portable format preserve the execution instructions?▼

Converting SKILL.md to a portable format preserves the body instructions for direct execution. The transformation only drops adapter-specific frontmatter metadata while keeping the operational payload intact for compatible runtimes.

Can I reuse skills in cross-adapter environments without editing the embedded payload?▼

Reusing skills in cross-adapter environments is possible by removing adapter-specific frontmatter. This action prevents adapter lock-in by cleaning the YAML header, allowing cross-adapter reuse without altering the embedded behavior or payload.

Why does my skill fail to run when switching to a different adapter environment?▼

Skills fail when switching adapters due to lock-in from adapter-specific frontmatter fields. Removing these adapter-only metadata entries from the YAML header converts the Skill definition to a portable, adapter-agnostic format.

What metadata is required in the YAML frontmatter after a portable transformation?▼

A portable transformation requires the YAML frontmatter to contain a valid name and description. All other adapter-only metadata is dropped to ensure the skill remains portable across different adapter environments.