Stats
Actions
Tags
Import, create, and upgrade skills from MyAider MCP. Use this skill whenever the user wants to import their MyAider MCP skills into agent skills, or upgrade/update existing MyAider skills to the latest version. This skill checks if MyAider MCP is configured, retrieves available skills, presents them to the user for selection, and uses skill-creator to create or update each selected skill properly.
How this skill is triggered — by the user, by Claude, or both
Slash command
/myaider-skill-importer:myaider-skill-importerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automate the process of importing skills from the MyAider MCP server into agent skills. This skill retrieves available skills, lets the user choose which ones to import, and creates proper skill files for each using existing skill-creator skill.
Automate the process of importing skills from the MyAider MCP server into agent skills. This skill retrieves available skills, lets the user choose which ones to import, and creates proper skill files for each using existing skill-creator skill.
Note on naming convention: MCP tool identifiers follow the format mcp__<server-name>__<tool-name>. The server name is whatever the user chose when configuring the MCP — it may nor may not be myaider. If you couldn't find the myaider related one in your available mcp servers, then try discover the actual name rather than assuming it.
The MyAider MCP server exposes a distinctively named tool called get_myaider_skills. Because this name is unique to MyAider, searching for it avoids conflicts with other MCP servers.
Search your available tools for any tool whose name is get_myaider_skills. Use whatever tool-discovery mechanism your agent supports (e.g., listing available tools, searching by name). The full tool identifier will be in the form mcp__<server-name>__get_myaider_skills.
Extract the server name from the middle segment and store it as {SERVER_NAME}. Use mcp__{SERVER_NAME}__get_myaider_skills (and mcp__{SERVER_NAME}__get_myaider_skill_updates) for all subsequent calls.
Exactly 1 match found → Extract {SERVER_NAME} from the tool identifier, proceed silently to Step 1.
0 matches found → Inform the user that MyAider MCP needs to be set up first:
The MyAider MCP server doesn't appear to be configured. To use this skill, you need to set up the MyAider MCP server first.
Setup Instructions:
- Go to https://www.myaider.ai/mcp
- Follow the instructions to configure the MyAider MCP server for your agent
- Once configured, come back and ask me to import your MyAider skills
Do NOT proceed until the user confirms MyAider is configured.
2 or more matches found → List all discovered server names and ask the user to confirm which one is their MyAider instance. Use the user's answer as {SERVER_NAME}.
Check if skill-creator skill is available; if not, ask the user to install skill-creator.
Call mcp__{SERVER_NAME}__get_myaider_skills (using the server name discovered in Step 0) with an empty object {} to retrieve all available skills from MyAider.
Present the list of skills to the user with their descriptions. Ask them to choose:
Wait for user confirmation before proceeding.
For each skill the user wants to import:
Extract the skill specification from the getSkills result (new array schema):
skill.name — skill identifierskill.description — skill descriptionskill.updated_at — ISO 8601 timestamp (e.g., "2026-03-06T10:30:00Z")skill.instructions — full usage instructionsskill.tools — array of tools, each with:
tool.name — tool identifiertool.description — tool descriptiontool.inputSchema — JSON schema for tool parametersCreate a properly formatted skill using skill-creator:
YOU MUST create the skill automatically instead of ask user to do it manually. YOU MUST use the Skill tool to invoke skill-creator:skill-creator with this template:
Create a new skill called "[skill-name]" based on the following specification:
## Skill Name
[skill-name]
## Description
[skill.description - make it comprehensive with triggering guidance]
## Metadata
Add the following fields to the skill's YAML frontmatter (in addition to name and description):
- source: myaider
- updated_at: [skill.updated_at ISO 8601 timestamp, e.g. 2026-03-06T10:30:00Z]
## Usage Instructions
[skill.instructions - full usage instructions from the myaider skill]
## Tools (MCP {SERVER_NAME})
This skill uses the following MCP tools from {SERVER_NAME}. Include the full tool descriptions and parameter schemas BELOW to optimize token usage - the skill should NOT rely on the MCP protocol to get tool descriptions:
### [tool-name-1]
[tool.description from skill.tools array]
**Parameters:**
[tool.inputSchema - full JSON schema including all parameters with their types, required/optional status, and descriptions]
### [tool-name-2]
[tool.description from skill.tools array]
**Parameters:**
[tool.inputSchema - full JSON schema including all parameters with their types, required/optional status, and descriptions]
Critical: The extracted tool descriptions and schemas must be included directly in the skill to avoid MCP protocol overhead. This optimizes token usage by enabling the skill to function without calling the MCP protocol for tool introspection.
Confirm creation to the user after each skill is created
After all selected skills are created, provide a summary:
Trigger this workflow when the user asks to upgrade, update, or sync their MyAider skills.
Same as the main Step 0. Search for get_myaider_skills to find {SERVER_NAME}. If MCP is not configured, show setup instructions and stop.
Call mcp__{SERVER_NAME}__get_myaider_skill_updates with an empty object {}. This returns the latest skill definitions with their updated_at timestamps.
Find all locally installed skills that have source: myaider in their YAML frontmatter. For each, read the updated_at value (the new schema uses ISO 8601 format like "2026-03-06T10:30:00Z"). Build a map of skill-name → local updated_at.
For each skill returned in Upgrade Step 1:
updated_at is newer than local → mark for upgradeupdated_at is same or older → skip (already up to date)Present the classification to the user (what will be upgraded, what is new, what is already current) and ask for confirmation before proceeding.
For each skill marked for upgrade, invoke skill-creator:skill-creator with the full updated specification (same template as the main Step 3, including refreshed updated_at and tool schemas). skill-creator will overwrite the existing skill file.
For each skill marked for new install, invoke skill-creator:skill-creator exactly as in the main Step 3 (import workflow).
Provide a final report:
updated_at)get_myaider_skills first (Step 0) — do NOT hardcode myaider or any other nameget_myaider_skills after confirming MCP is configured — do NOT guess what skills are availablename, description, updated_at, instructions, and tools[] with name, description, inputSchema. Always extract these exact fields.get_myaider_skills — this is critical to optimize token usage. The created skill should work without needing MCP protocol tool introspection{SERVER_NAME} consistently for all MCP tool calls and in generated skill filessource: myaider and updated_at in the YAML frontmatter of every created or upgraded skill — these fields are required for the upgrade workflownpx claudepluginhub hurungang/claude-code-plugins --plugin myaider-skill-importerGuides agents on efficiently managing PostHog skills via MCP skill-* tools, covering discovery, reading, authoring, editing, and refactoring with decision-tree and pitfall guidance.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Converts MCP servers into on-demand skills to reduce context window usage by 10-30%. Classifies each tool by replacement strategy and generates the skill package.