Skip to main content
Glama

AI Skill Store

by io.github.garasegae

search_skills

Search skills on AI Skill Store. Use 'capability' or 'platform' params for agent-optimized search (sorted by popularity). Returns skill name, description, downloads, rating, and trust level. / AI Skill Store에서 스킬 검색.
capability나 platform을 지정하면 에이전트 최적화 검색(인기순 정렬)을 사용합니다.

Args:
    query: 검색 키워드 (스킬 이름 또는 설명). 비워두면 전체 목록.
    capability: 능력 태그로 검색 (예: web_search, text_summarization, code_generation)
    platform: 특정 플랫폼 호환 스킬만 (OpenClaw, ClaudeCode, ClaudeCodeAgentSkill, Cursor, GeminiCLI, CodexCLI)
    min_trust: 최소 신뢰 등급 (verified > community > sandbox)
    category: 카테고리 필터 (에이전트 검색 미사용 시에만 적용)
    sort: 정렬 기준 (에이전트 검색 미사용 시에만: newest | downloads | rating)
    limit: 결과 수 (기본 20, 최대 50)

Returns:
    스킬 목록 문자열

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNonewest
limitNo
queryNo
categoryNo
platformNo
min_trustNo
capabilityNo

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 are provided, so the description bears full responsibility. It discloses return content (skill name, description, downloads, rating, trust level) and the popularity-sorted behavior for agent-optimized search, along with limit constraints (default 20, max 50). However, it doesn't discuss auth or error conditions, which are less critical for a read-only search.

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?

Structured into summary and argument sections; the bilingual English/Korean text adds length but is organizationally clear. The repetition between languages is somewhat redundant but not excessive for a 7-parameter tool.

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?

Given the 7-parameter complexity and no annotations, the description covers parameter semantics, return value summary, and special search modes. It relies on the output schema for exact return structure, which is acceptable.

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 description coverage is 0%, so the description is the only source of parameter meaning. It gives Korean explanations for each parameter, including examples for capability/platform, trust level hierarchy, sort options, and limit bounds, fully compensating for the schema's lack of documentation.

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?

The description clearly states 'Search skills on AI Skill Store' with a specific verb and resource. It distinguishes this search tool from siblings like get_skill and list_categories by emphasizing search behavior and result contents.

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?

Provides explicit guidance on when to use capability/platform parameters for agent-optimized search, and notes that category and sort apply only when not using agent search. It doesn't name alternative tools, but offers clear context for parameter selection.

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