Skip to main content
Glama

generate_skills

Generate ranked skill packages from any URL (video, article, PDF, image). Outputs skill files ready to save and reuse with Claude Code.

Instructions

Extract structured skill packages from any content source.

Analyzes a YouTube video, article, PDF, or image URL and returns ranked skill packages — each with a SKILL.md (principles, failure modes, implementation steps), README.md, reference files, and a test script.

Skill files are ready to save to .claude/skills/ so Claude Code can apply them directly on future tasks, reducing token usage on repeated patterns.

Billing: this tool calls /api/v1/skills/generate with the LORETO_API_KEY from the environment. For pay-per-call without a key, use the x402 endpoint /api/v1/skills/x402/generate directly via the x402 Python SDK (flat $0.75/call in USDC on Base mainnet — see https://loreto.io/docs-x402). The response shape is identical; both paths return a generation_id you can pass to verify_artifacts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesURL to analyze — YouTube video, article, public PDF, or image URL.
source_typeNoContent type. Use "auto" to detect automatically, or specify "youtube", "article", "pdf", or "image".auto
test_languageNoLanguage for the generated test script. One of "python" (default), "typescript", or "javascript".python
include_visualsNoWhen True (default), embeds Mermaid diagrams in SKILL.md.
contextNoOptional 1–3 sentence hint to guide what kind of skill to extract (max 500 characters). Does not override extraction — used to disambiguate framing only.
themes_to_processNoFor follow-up calls only. Pass skill_name values from a previous response's queued themes (max 3 names).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully discloses it calls /api/v1/skills/generate with LORETO_API_KEY, mentions alternative x402 endpoint, and describes output artifacts. It does not mention side effects or rate limits but is transparent about its operation.

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 four paragraphs, each adding value: purpose, output, billing, and follow-up. It is well-structured but could be slightly more concise.

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

Completeness5/5

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

Given the tool has an output schema, the description appropriately focuses on input, behavior, and billing. It covers source types, follow-up themes, and billing alternatives, making it complete for the complexity.

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 description coverage is 100%, so baseline is 3. The description adds context about the overall tool but does not significantly enhance individual parameter meanings beyond what the schema already provides.

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 the tool extracts structured skill packages from any content source, with a specific verb and resource. It distinguishes from siblings like list_skills or verify_artifacts by focusing on generation from diverse inputs.

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?

It specifies when to use (analyze video, article, PDF, or image) and provides billing alternatives (API key vs x402 endpoint). However, it lacks explicit when-not-to-use guidance.

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/kopias/loreto-mcp'

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