Skip to main content
Glama
agentskill-sh

agentskill-mcp

Official

get_skill

Retrieve complete skill details including documentation, security information, and metadata from the agentskill-mcp server for AI agent skill management.

Instructions

Get full details for a specific skill including its SKILL.md content, security info, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSkill slug (e.g. 'seo-optimizer', 'react-best-practices')

Implementation Reference

  • src/index.ts:145-214 (registration)
    Complete registration of the get_skill tool using server.tool() with name, description, input schema, and handler function
    // Tool: get_skill
    server.tool(
      "get_skill",
      "Get full details for a specific skill including its SKILL.md content, security info, and metadata.",
      {
        slug: z
          .string()
          .describe("Skill slug (e.g. 'seo-optimizer', 'react-best-practices')"),
      },
      async ({ slug }) => {
        const data = await apiFetch<{
          data: {
            name: string;
            slug: string;
            description: string;
            owner: string;
            repositoryUrl: string;
            platforms: string[];
            installCount: number;
            score: number;
            ratingCount: number;
            skillMd: string;
            readme: string;
            tags: string[];
            skillTypes: string[];
            isVerified: boolean;
          };
        }>(`/skills/${encodeURIComponent(slug)}`);
    
        const s = data.data;
        if (!s) {
          return {
            content: [{ type: "text" as const, text: `Skill "${slug}" not found.` }],
          };
        }
    
        const rating = s.score
          ? `${s.score.toFixed(1)}/5 (${s.ratingCount} ratings)`
          : "No ratings yet";
        const sections = [
          `# ${s.name}`,
          "",
          s.description,
          "",
          "## Metadata",
          `- **Owner**: ${s.owner}`,
          `- **Repository**: ${s.repositoryUrl || "N/A"}`,
          `- **Platforms**: ${s.platforms?.join(", ") || "all"}`,
          `- **Types**: ${s.skillTypes?.join(", ") || "N/A"}`,
          `- **Tags**: ${s.tags?.join(", ") || "N/A"}`,
          `- **Installs**: ${s.installCount.toLocaleString()}`,
          `- **Rating**: ${rating}`,
          `- **Verified**: ${s.isVerified ? "Yes" : "No"}`,
        ];
    
        if (s.skillMd) {
          sections.push("", "## SKILL.md Content", "", s.skillMd);
        }
    
        sections.push(
          "",
          `Install: use the install_skill tool with slug "${s.slug}"`,
          `View on web: https://agentskill.sh/skills/${s.slug}`
        );
    
        return {
          content: [{ type: "text" as const, text: sections.join("\n") }],
        };
      }
    );
  • Handler function that fetches skill data from API using slug parameter, formats the response with metadata, SKILL.md content, and returns formatted text output
    async ({ slug }) => {
      const data = await apiFetch<{
        data: {
          name: string;
          slug: string;
          description: string;
          owner: string;
          repositoryUrl: string;
          platforms: string[];
          installCount: number;
          score: number;
          ratingCount: number;
          skillMd: string;
          readme: string;
          tags: string[];
          skillTypes: string[];
          isVerified: boolean;
        };
      }>(`/skills/${encodeURIComponent(slug)}`);
    
      const s = data.data;
      if (!s) {
        return {
          content: [{ type: "text" as const, text: `Skill "${slug}" not found.` }],
        };
      }
    
      const rating = s.score
        ? `${s.score.toFixed(1)}/5 (${s.ratingCount} ratings)`
        : "No ratings yet";
      const sections = [
        `# ${s.name}`,
        "",
        s.description,
        "",
        "## Metadata",
        `- **Owner**: ${s.owner}`,
        `- **Repository**: ${s.repositoryUrl || "N/A"}`,
        `- **Platforms**: ${s.platforms?.join(", ") || "all"}`,
        `- **Types**: ${s.skillTypes?.join(", ") || "N/A"}`,
        `- **Tags**: ${s.tags?.join(", ") || "N/A"}`,
        `- **Installs**: ${s.installCount.toLocaleString()}`,
        `- **Rating**: ${rating}`,
        `- **Verified**: ${s.isVerified ? "Yes" : "No"}`,
      ];
    
      if (s.skillMd) {
        sections.push("", "## SKILL.md Content", "", s.skillMd);
      }
    
      sections.push(
        "",
        `Install: use the install_skill tool with slug "${s.slug}"`,
        `View on web: https://agentskill.sh/skills/${s.slug}`
      );
    
      return {
        content: [{ type: "text" as const, text: sections.join("\n") }],
      };
    }
  • Input schema definition using zod for the slug parameter with description of expected format (e.g., 'seo-optimizer', 'react-best-practices')
    {
      slug: z
        .string()
        .describe("Skill slug (e.g. 'seo-optimizer', 'react-best-practices')"),
    },
  • apiFetch helper function used by the handler to make authenticated requests to the agentskill.sh API endpoint
    async function apiFetch<T>(path: string, options?: RequestInit): Promise<T> {
      const res = await fetch(`${API_BASE}${path}`, {
        ...options,
        headers: {
          "Content-Type": "application/json",
          "User-Agent": "agentskill-mcp/0.1.0",
          ...options?.headers,
        },
      });
      if (!res.ok) {
        throw new Error(`API error: ${res.status} ${res.statusText}`);
      }
      return res.json() as Promise<T>;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions retrieving 'full details' including specific components, but doesn't disclose behavioral traits such as error handling (e.g., what happens if the slug doesn't exist), authentication needs, rate limits, or response format. This leaves gaps for an agent to understand operational nuances.

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 a single, efficient sentence that front-loads the purpose and lists key details retrieved. It avoids redundancy and wastes no words, though it could be slightly more structured by separating usage context.

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

Completeness3/5

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

Given the tool's moderate complexity (retrieving detailed skill info), no annotations, and no output schema, the description is minimally adequate. It specifies what details are included, but lacks information on return values, error cases, or behavioral constraints, leaving the agent with incomplete context for reliable invocation.

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?

The input schema has 100% description coverage, with the 'slug' parameter well-documented in the schema. The description adds no additional parameter semantics beyond implying the slug identifies a 'specific skill', which is already clear from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the verb 'Get' and resource 'full details for a specific skill', specifying what information is retrieved (SKILL.md content, security info, metadata). It distinguishes from siblings like 'search_skills' (searching multiple) and 'install_skill' (installing), though not explicitly. However, it doesn't fully differentiate from 'get_trending' which might also retrieve skill details, keeping it at 4.

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

Usage Guidelines3/5

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

The description implies usage when you need detailed information for a specific skill, but provides no explicit guidance on when to use this tool versus alternatives like 'search_skills' for broader queries or 'get_trending' for trending skills. It lacks exclusions or prerequisites, relying on context from the tool name and parameters.

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/agentskill-sh/agentskill-mcp'

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