{
  "schemaVersion": "1.0",
  "item": {
    "slug": "myaider-skill-importer",
    "name": "MyAider Skill Importer",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/hurungang/myaider-skill-importer",
    "canonicalUrl": "https://clawhub.ai/hurungang/myaider-skill-importer",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/myaider-skill-importer",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=myaider-skill-importer",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/myaider-skill-importer"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/myaider-skill-importer",
    "agentPageUrl": "https://openagent3.xyz/skills/myaider-skill-importer/agent",
    "manifestUrl": "https://openagent3.xyz/skills/myaider-skill-importer/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/myaider-skill-importer/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Purpose",
        "body": "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."
      },
      {
        "title": "Step 0 — REQUIRED: Discover MyAider MCP Server Name and Check skill-creator Skill",
        "body": "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 not be myaider. Always discover the actual name rather than assuming it.\n\nThe 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.\n\nPhase A — Discover the server name\n\nSearch 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.\n\nExtract 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.\n\nPhase B — Branch on the result\n\nExactly 1 match found → Extract {SERVER_NAME} from the tool identifier, proceed silently to Step 1.\n\n\n0 matches found → Inform the user that MyAider MCP needs to be set up first:\n\nThe MyAider MCP server doesn't appear to be configured. To use this skill, you need to set up the MyAider MCP server first.\nSetup Instructions:\n\nGo to https://www.myaider.ai/mcp\nFollow the instructions to configure the MyAider MCP server for your agent\nOnce configured, come back and ask me to import your MyAider skills\n\n\nDo NOT proceed until the user confirms MyAider is configured.\n\n\n2 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}.\n\nCheck if skill-creator skill is available; if not, ask the user to install skill-creator."
      },
      {
        "title": "Step 1 — REQUIRED: Get Available Skills",
        "body": "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."
      },
      {
        "title": "Step 2 — REQUIRED: Present Skills to User",
        "body": "Present the list of skills to the user with their descriptions. Ask them to choose:\n\n\"All\" - import every skill\nOr specify which specific skills they want (by name)\n\nWait for user confirmation before proceeding."
      },
      {
        "title": "Step 3 — REQUIRED: For Each Selected Skill",
        "body": "For each skill the user wants to import:\n\nExtract the skill specification from the getSkills result:\n\nSkill name\nDescription (from the Usage Instructions or summary)\nUsage Instructions (the main content)\nTools with FULL usage details: Extract each tool's name, description, and parameter schema from the \"Tools\" section in the getSkills result\n\n\n\nCreate a properly formatted skill using skill-creator:\nYOU 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:\nCreate a new skill called \"[skill-name]\" based on the following specification:\n\n## Skill Name\n[skill-name]\n\n## Description\n[description - make it comprehensive with triggering guidance]\n\n## Metadata\nAdd the following fields to the skill's YAML frontmatter (in addition to name and description):\n- source: myaider\n- updated_at: [ISO 8601 timestamp from the remote skill, e.g. 2026-03-06T12:00:00Z]\n\n## Usage Instructions\n[full usage instructions from the myaider skill]\n\n## Tools (MCP {SERVER_NAME})\nThis 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:\n\n### [tool-name-1]\n[full tool description from get_myaider_skills result]\n\n**Parameters:**\n[parameter schema - include all parameters with their types, required/optional status, and descriptions]\n\n### [tool-name-2]\n[full tool description from get_myaider_skills result]\n\n**Parameters:**\n[parameter schema - include all parameters with their types, required/optional status, and descriptions]\n\nCritical: 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.\n\n\nConfirm creation to the user after each skill is created"
      },
      {
        "title": "Step 4 — REQUIRED: Summarize",
        "body": "After all selected skills are created, provide a summary:\n\nList of successfully created skills\nFile locations\nAny skills that failed (if any)"
      },
      {
        "title": "Upgrade Workflow",
        "body": "Trigger this workflow when the user asks to upgrade, update, or sync their MyAider skills."
      },
      {
        "title": "Upgrade Step 0 — Discover server name",
        "body": "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."
      },
      {
        "title": "Upgrade Step 1 — Fetch remote update info",
        "body": "Call mcp__{SERVER_NAME}__get_myaider_skill_updates with an empty object {}. This returns the latest skill definitions with their updated_at timestamps."
      },
      {
        "title": "Upgrade Step 2 — Read local MyAider skills",
        "body": "Find all locally installed skills that have source: myaider in their YAML frontmatter. For each, read the updated_at value. Build a map of skill-name → local updated_at."
      },
      {
        "title": "Upgrade Step 3 — Compare and classify",
        "body": "For each skill returned in Upgrade Step 1:\n\nRemote updated_at is newer than local → mark for upgrade\nSkill does not exist locally → mark for new install\nRemote updated_at is same or older → skip (already up to date)\n\nPresent the classification to the user (what will be upgraded, what is new, what is already current) and ask for confirmation before proceeding."
      },
      {
        "title": "Upgrade Step 4 — Upgrade outdated skills",
        "body": "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."
      },
      {
        "title": "Upgrade Step 5 — Install new skills",
        "body": "For each skill marked for new install, invoke skill-creator:skill-creator exactly as in the main Step 3 (import workflow)."
      },
      {
        "title": "Upgrade Step 6 — Summarize",
        "body": "Provide a final report:\n\nSkills upgraded (name + old → new updated_at)\nNew skills installed\nSkills already up to date (skipped)\nAny failures"
      },
      {
        "title": "Important Constraints",
        "body": "Always discover the MCP server name by searching for get_myaider_skills first (Step 0) — do NOT hardcode myaider or any other name\nAlways call get_myaider_skills after confirming MCP is configured — do NOT guess what skills are available\nAlways extract and include FULL tool descriptions and schemas from get_myaider_skills — this is critical to optimize token usage. The created skill should work without needing MCP protocol tool introspection\nUse the discovered {SERVER_NAME} consistently for all MCP tool calls and in generated skill files\nAlways include source: myaider and updated_at in the YAML frontmatter of every created or upgraded skill — these fields are required for the upgrade workflow\nAlways wait for user confirmation before creating or upgrading skills\nCreate/upgrade skills one at a time using skill-creator\nKeep the skill-creator conversation focused on each skill creation"
      },
      {
        "title": "Example Usage",
        "body": "\"Import my MyAider skills\"\n\"Create skills from myaider\"\n\"Set up the skills from my MyAider MCP\"\n\"Upgrade my MyAider skills\"\n\"Update my MyAider skills to the latest version\"\n\"Sync my MyAider skills\""
      }
    ],
    "body": "MyAider Skill Importer\nPurpose\n\nAutomate 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.\n\nMANDATORY WORKFLOW\nStep 0 — REQUIRED: Discover MyAider MCP Server Name and Check skill-creator Skill\n\nNote 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 not be myaider. Always discover the actual name rather than assuming it.\n\nThe 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.\n\nPhase A — Discover the server name\n\nSearch 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.\n\nExtract 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.\n\nPhase B — Branch on the result\n\nExactly 1 match found → Extract {SERVER_NAME} from the tool identifier, proceed silently to Step 1.\n\n0 matches found → Inform the user that MyAider MCP needs to be set up first:\n\nThe MyAider MCP server doesn't appear to be configured. To use this skill, you need to set up the MyAider MCP server first.\n\nSetup Instructions:\n\nGo to https://www.myaider.ai/mcp\nFollow the instructions to configure the MyAider MCP server for your agent\nOnce configured, come back and ask me to import your MyAider skills\n\nDo NOT proceed until the user confirms MyAider is configured.\n\n2 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}.\n\nCheck if skill-creator skill is available; if not, ask the user to install skill-creator.\n\nStep 1 — REQUIRED: Get Available Skills\n\nCall 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.\n\nStep 2 — REQUIRED: Present Skills to User\n\nPresent the list of skills to the user with their descriptions. Ask them to choose:\n\n\"All\" - import every skill\nOr specify which specific skills they want (by name)\n\nWait for user confirmation before proceeding.\n\nStep 3 — REQUIRED: For Each Selected Skill\n\nFor each skill the user wants to import:\n\nExtract the skill specification from the getSkills result:\n\nSkill name\nDescription (from the Usage Instructions or summary)\nUsage Instructions (the main content)\nTools with FULL usage details: Extract each tool's name, description, and parameter schema from the \"Tools\" section in the getSkills result\n\nCreate 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:\n\nCreate a new skill called \"[skill-name]\" based on the following specification:\n\n## Skill Name\n[skill-name]\n\n## Description\n[description - make it comprehensive with triggering guidance]\n\n## Metadata\nAdd the following fields to the skill's YAML frontmatter (in addition to name and description):\n- source: myaider\n- updated_at: [ISO 8601 timestamp from the remote skill, e.g. 2026-03-06T12:00:00Z]\n\n## Usage Instructions\n[full usage instructions from the myaider skill]\n\n## Tools (MCP {SERVER_NAME})\nThis 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:\n\n### [tool-name-1]\n[full tool description from get_myaider_skills result]\n\n**Parameters:**\n[parameter schema - include all parameters with their types, required/optional status, and descriptions]\n\n### [tool-name-2]\n[full tool description from get_myaider_skills result]\n\n**Parameters:**\n[parameter schema - include all parameters with their types, required/optional status, and descriptions]\n\n\nCritical: 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.\n\nConfirm creation to the user after each skill is created\n\nStep 4 — REQUIRED: Summarize\n\nAfter all selected skills are created, provide a summary:\n\nList of successfully created skills\nFile locations\nAny skills that failed (if any)\nUpgrade Workflow\n\nTrigger this workflow when the user asks to upgrade, update, or sync their MyAider skills.\n\nUpgrade Step 0 — Discover server name\n\nSame as the main Step 0. Search for get_myaider_skills to find {SERVER_NAME}. If MCP is not configured, show setup instructions and stop.\n\nUpgrade Step 1 — Fetch remote update info\n\nCall mcp__{SERVER_NAME}__get_myaider_skill_updates with an empty object {}. This returns the latest skill definitions with their updated_at timestamps.\n\nUpgrade Step 2 — Read local MyAider skills\n\nFind all locally installed skills that have source: myaider in their YAML frontmatter. For each, read the updated_at value. Build a map of skill-name → local updated_at.\n\nUpgrade Step 3 — Compare and classify\n\nFor each skill returned in Upgrade Step 1:\n\nRemote updated_at is newer than local → mark for upgrade\nSkill does not exist locally → mark for new install\nRemote updated_at is same or older → skip (already up to date)\n\nPresent the classification to the user (what will be upgraded, what is new, what is already current) and ask for confirmation before proceeding.\n\nUpgrade Step 4 — Upgrade outdated skills\n\nFor 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.\n\nUpgrade Step 5 — Install new skills\n\nFor each skill marked for new install, invoke skill-creator:skill-creator exactly as in the main Step 3 (import workflow).\n\nUpgrade Step 6 — Summarize\n\nProvide a final report:\n\nSkills upgraded (name + old → new updated_at)\nNew skills installed\nSkills already up to date (skipped)\nAny failures\nImportant Constraints\nAlways discover the MCP server name by searching for get_myaider_skills first (Step 0) — do NOT hardcode myaider or any other name\nAlways call get_myaider_skills after confirming MCP is configured — do NOT guess what skills are available\nAlways extract and include FULL tool descriptions and schemas from get_myaider_skills — this is critical to optimize token usage. The created skill should work without needing MCP protocol tool introspection\nUse the discovered {SERVER_NAME} consistently for all MCP tool calls and in generated skill files\nAlways include source: myaider and updated_at in the YAML frontmatter of every created or upgraded skill — these fields are required for the upgrade workflow\nAlways wait for user confirmation before creating or upgrading skills\nCreate/upgrade skills one at a time using skill-creator\nKeep the skill-creator conversation focused on each skill creation\nExample Usage\n\"Import my MyAider skills\"\n\"Create skills from myaider\"\n\"Set up the skills from my MyAider MCP\"\n\"Upgrade my MyAider skills\"\n\"Update my MyAider skills to the latest version\"\n\"Sync my MyAider skills\""
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/hurungang/myaider-skill-importer",
    "publisherUrl": "https://clawhub.ai/hurungang/myaider-skill-importer",
    "owner": "hurungang",
    "version": "1.0.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/myaider-skill-importer",
    "downloadUrl": "https://openagent3.xyz/downloads/myaider-skill-importer",
    "agentUrl": "https://openagent3.xyz/skills/myaider-skill-importer/agent",
    "manifestUrl": "https://openagent3.xyz/skills/myaider-skill-importer/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/myaider-skill-importer/agent.md"
  }
}