qveris-official

Discover API tools by capability and call them for structured JSON results.

21|3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/QVerisAI/open-qveris-skills --skill qveris-official-qverisai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qveris-official
Source: https://github.com/QVerisAI/open-qveris-skills/tree/main/qveris-official
Command: npx skills add https://github.com/QVerisAI/open-qveris-skills --skill qveris-official-qverisai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

QVeris provides a standardized workflow for AI agents to discover API tools by capability and then invoke them, returning structured results for downstream tasks.

Core Features & Use Cases

  • Discover API tools by capability type and retrieve tool metadata.
  • Call the selected tool to execute and receive structured JSON results suitable for agent workflows.
  • Two-step workflow: discover first, then call; supports deterministic tasks, error handling, and tiered fallbacks (native tools, HTTP API, script execution, and web search as a last resort).

Quick Start

Discover a weather forecast API for your city, then call it with the city parameter.

Frequently Asked Questions about qveris-official

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover and call API tools to return structured JSON for agent workflows?

To discover and call API tools, use a two-step workflow: first query tools by capability to retrieve metadata, then invoke the selected tool with parameters to receive structured JSON results suitable for agent workflows.

What is the two-step process for discovering APIs by capability before execution?

The two-step API discovery process involves first identifying and surfacing API tools by capability type to retrieve metadata, then calling the selected tool to execute the task and return structured JSON data.

Do I need Node.js 18+ to use this API discovery and tool-calling workflow?

Yes, Node.js 18+ is required to execute the API discovery and tool-calling workflow. The environment enforces API key usage and supports tiered fallbacks including native tools, HTTP API, and script execution.

Can I use tiered fallbacks for API tool execution when native tools fail?

Yes, tiered fallbacks are supported for API tool execution. If native tool execution fails, the workflow sequentially attempts HTTP API calls, script execution, and web search as a last resort to ensure task completion.

What types of workflows are supported by discovering API tools by capability?

Discovering API tools by capability supports real-time data retrieval, historical data queries, report generation, and media generation workflows, returning structured JSON results for downstream agent tasks.

How do I handle API key enforcement when calling external tools via CLI?

API key enforcement is built into the tool-calling workflow. When discovering and invoking CLI tools or HTTP APIs, the system automatically manages API key usage to ensure secure execution and structured JSON output.