skill-installer

Migrate source skill metadata and workflows into DeepCode Next.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Void0312Aurora/RAAS --skill skill-installer-void0312aurora
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-installer
Source: https://github.com/Void0312Aurora/RAAS/tree/main/skills/skill-installer
Command: npx skills add https://github.com/Void0312Aurora/RAAS --skill skill-installer-void0312aurora

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Importing and installing skills from local projects or external repositories into DeepCode Next, while preserving compatibility with the skills mechanism.

Core Features & Use Cases

  • Inspect source skill metadata and portability: frontmatter, core workflow, and resources.
  • Adapt metadata to DeepCode Next fields and restructure for current workflow stages.
  • Create or update the target directory under skills/<skill-name>/ with cleaned resources and documentation.
  • Use the helper script to perform an import and validate discoverability.

Quick Start

Execute the import_skill helper to migrate a local skill into the skills directory.

Frequently Asked Questions about skill-installer

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

FAQPage Schema
How do I import and install external skills into DeepCode Next?

To import and install skills into DeepCode Next, execute the import_skill helper script. This migrates the source skill's metadata, core workflow, and resources into the skills directory while preserving compatibility.

How does skill migration handle unsupported runtime concepts?

Skill migration applies portability rules to replace unsupported runtime concepts during the import process. It rewrites the frontmatter and restructures the metadata to adapt to DeepCode Next fields and current workflow stages.

Can I migrate local project skills into the DeepCode Next skills directory?

Yes, you can migrate local project skills into the DeepCode Next skills directory. The import process identifies the source skill's portability, cleans the resources, and places the result under skills/<skill-name>/.

What is the best way to validate if an imported skill is discoverable?

The best way to validate an imported skill's discoverability is by checking its presence via skills/*/SKILL.md. The helper script performs this validation automatically after placing the migrated skill in the target directory.

Why does my imported skill need frontmatter rewriting?

Imported skills need frontmatter rewriting to adapt the source metadata to DeepCode Next fields. This restructuring ensures the migrated skill aligns with the current workflow stages and maintains compatibility with the skills mechanism.

Do I need a helper script to perform a skill migration?

You need the provided import_skill helper script to perform a local skill migration into DeepCode Next. It automates the inspection, adaptation, and validation steps required for a successful import.