myaider-skill-importer_skill

This skill imports MyAider MCP skills into Claude Code by verifying configuration, listing options, and creating each skill with full tool details.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill myaider-skill-importer

  • _meta.json477 B
  • SKILL.md8.6 KB

Overview

This skill imports and creates Claude Code skills from a MyAider MCP server. It verifies MCP configuration, retrieves available MyAider skills, prompts you to select which to import, and uses the skill-creator to create each selected skill with full tool descriptions and schemas included. The result is self-contained Claude Code skills that do not rely on MCP introspection.

How this skill works

First it checks that MyAider MCP is configured by calling the MCP getSkills endpoint. If configured, it fetches the list of available skills and presents names and descriptions for your selection. For each chosen skill it extracts the usage instructions, tools, full tool descriptions, and parameter schemas, then calls the skill-creator to create a properly formatted skill file. After each creation it confirms success and finally summarizes created files and any failures.

When to use it

  • You want to import all or some skills from your MyAider MCP into Claude Code.
  • You have configured MyAider MCP and want standalone Claude skills that don’t need MCP tool introspection.
  • You need an automated, repeatable way to convert MyAider skill definitions into Claude Code skills.
  • You want full tool descriptions and parameter schemas embedded in each created skill.

Best practices

  • Always run the MCP configuration check first and follow the setup instructions if it fails.
  • Review the presented skill list and choose All or specific skill names before creation proceeds.
  • Import skills one at a time to keep creation logs and confirmations clear.
  • Ensure the MyAider getSkills response contains complete tool descriptions and parameter schemas before creating a skill.
  • Verify created skill files and locations after each creation and report any problems immediately.

Example use cases

  • Import every skill from a configured MyAider account to archive on Claude Code.
  • Select and import only new or updated MyAider skills into a Claude workspace.
  • Migrate MyAider skills to Claude Code while embedding full tool schemas to avoid runtime MCP calls.
  • Create a local backup of MyAider skills with descriptions, usage instructions, and tool schemas preserved.

FAQ

The importer halts and provides step-by-step setup instructions. Do not proceed until you confirm MCP is configured.

Will created skills call MCP at runtime for tool information?

No. Each created skill embeds full tool descriptions and parameter schemas so it can operate without MCP introspection.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational