Skip to main content
Glama

vibekit_get_skill

Fetch the full content of a skill including implementation patterns, code examples, and best practices. Use to get guidance on a specific topic.

Instructions

Fetch the full content of a specific skill. Skills contain implementation patterns, code examples, and best practices for a domain. Fetch skills on-demand when you need guidance on a specific topic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSkill ID from vibekit_list_skills (e.g., 'nextjs', 'trpc', 'auth')
Behavior3/5

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

No annotations provided, so description carries full burden. 'Fetch' indicates a read operation, but no details on side effects, authentication, or error handling. Adequate for a simple fetch.

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

Conciseness5/5

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

Two sentences: first states action, second adds context and usage. Front-loaded, no fluff.

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?

Describes action and usage adequately for a simple fetch with one parameter. Lacks output schema, but description implies full content; could specify return format for completeness.

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

Parameters3/5

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

Schema has 100% coverage with the parameter 'id' described including examples. The description adds no additional parameter meaning beyond schema.

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?

Uses specific verb 'Fetch' and resource 'full content of a specific skill', clearly distinguishing from sibling 'vibekit_list_skills' which lists skills.

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 'Fetch skills on-demand when you need guidance on a specific topic', providing clear context. Lacks explicit when-not-to-use or alternatives, but sibling list tool implies alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/609NFT/vibekit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server