Skip to main content
Glama

AI Skill Store

by io.github.garasegae

download_skill

Download a skill package. Specify 'platform' to get an auto-converted package for that platform (ClaudeCode, Cursor, CodexCLI, GeminiCLI, etc.). / 스킬 패키지 다운로드 (플랫폼별 자동 변환).

Args:
    skill_id: 다운로드할 스킬 ID
    platform: 플랫폼 (OpenClaw, ClaudeCode, ClaudeCodeAgentSkill, CustomAgent, Cursor, GeminiCLI, CodexCLI). 비워두면 원본(.skill) 다운로드.
    save_dir: 저장 디렉터리 경로 (비워두면 임시 디렉터리에 저장)

Returns:
    저장된 파일 경로 또는 오류 메시지

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformNo
save_dirNo
skill_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the burden. It discloses key behaviors: platform-dependent auto-conversion, default save directory (temp), and return of file path or error message. It does not detail authentication needs or potential side effects on server state, but for a download tool this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with purpose, arguments, and return sections, making it easy to scan. The bilingual text adds some length but every section provides necessary operational detail; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, all parameters with defaults, and return type, which is sufficient for a moderate-complexity tool with an output schema. It could mention that the download creates local files, but save_dir implicitly conveys that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description supplies all parameter meaning: skill_id, platform with an explicit enum-like list, and save_dir with default behavior. This fully compensates for the empty schema descriptions, including defaults for platform and save_dir.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description opens with a specific action 'Download a skill package' and clarifies platform auto-conversion, distinguishing from sibling get_skill which likely retrieves metadata but not a package. The mention of original .skill download for empty platform further clarifies scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States that specifying 'platform' yields an auto-converted package for that platform, and leaving it blank downloads the original .skill, providing clear context for how to choose. However, it does not explicitly compare to get_skill or list exclusions, so it is not a full when/when-not.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AI Skill Store toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but check_vetting_status and get_vetting_result both deal with security vetting and could be confused. Similarly, get_agent_author_stats and get_agent_identity_stats overlap somewhat, though descriptions differentiate them.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., search_skills, upload_skill_draft, get_vetting_result). No mixed conventions or vague verbs.

Tool Count4/5

18 tools is slightly above the typical well-scoped range (3-15), but the coverage of a skill marketplace (search, browse, upload, vet, review, stats, install) justifies the count. It doesn't feel bloated.

Completeness3/5

Core workflows are covered: search, download, upload, review, and status checks. However, there is no tool to update or delete an uploaded skill, and no way to list skills uploaded by a particular author, which are notable gaps for a marketplace.

Resources