QVerisAI

Search and execute dynamic tools via QVeris API. Use when needing to find and call external APIs/tools dynamically — covers weather, search, stocks, finance, economics, geolocation, AIGC, news, social media, health data, and thousands more. Requires QVERIS_API_KEY environment variable.

Security Scan

The skill is internally consistent with its stated purpose (it needs a QVERIS_API_KEY and contacts qveris.ai to search/execute external tools), with only minor metadata inconsistencies and standard privacy considerations when using an aggregator service.

Purpose & Capability

The skill's name/description (dynamic tool discovery & execution) matches what it requires and does: it asks for a QVERIS_API_KEY and calls https://qveris.ai/api/v1 to search and execute tools. There are no unrelated credentials or unexpected binaries. Note: registry metadata in the header incorrectly listed no required env vars/primary credential while the SKILL.md and script both require QVERIS_API_KEY — this mismatch should be reconciled.

Instruction Scope

SKILL.md and the included script only read QVERIS_API_KEY, POST to qveris.ai, and print results; they do not read other env vars or local files. However, executing a discovered tool means QVeris (the remote service) may in turn call many third-party APIs (weather, health, finance, etc.). That is expected for an aggregator but means user-provided parameters (which may contain sensitive data) will be sent to the remote service.

Install Mechanism

No install spec; this is instruction-only with a small Node.js script included. No downloads, package managers, or extraction from arbitrary URLs are used. Risk from installation is low.

Credentials

Only one credential (QVERIS_API_KEY) is required, which is proportionate to a remote API aggregator. The SKILL.md declares the key as primary and read-only. Double-check that your API key can be scoped/revoked; avoid sending secrets in tool parameters because those parameters are forwarded to the aggregator and its downstream APIs. Also note the registry header omission of the required env var — ensure the platform will request/store the API key properly.

Persistence & Privilege

The skill is not always-enabled and does not request elevated system privileges or modify other skills. It does not persist credentials to disk in included code. Autonomous invocation is allowed (platform default) but is not combined with other concerning privileges.

Assessment

This skill appears to do what it says: it needs a QVERIS_API_KEY and calls qveris.ai to discover and run external APIs. Before installing: 1) Confirm you trust qveris.ai (the service will receive your API key and any parameters you pass). 2) Use a scoped, revocable API key and monitor its usage. 3) Do not pass secrets or sensitive PHI/PII as tool parameters unless you are sure the downstream API and QVeris policy permit it. 4) Note a small metadata inconsistency: registry metadata omitted the required env var while SKILL.md and the script require QVERIS_API_KEY — ensure the platform prompts for the key appropriately.

QVeris Tool Search & Execution

QVeris provides dynamic tool discovery and execution - search for tools by capability, then execute them with parameters.

Setup

Requires environment variable:

• QVERIS_API_KEY - Get from https://qveris.ai

No additional dependencies — uses Node.js built-in fetch.

Security

• Credential: Only QVERIS_API_KEY is accessed. No other env vars or secrets are read.
• Network: API key is sent only to https://qveris.ai/api/v1 over HTTPS. No other endpoints are contacted.
• Storage: The key is never logged, cached, or written to disk.
• Recommendation: Use a scoped, revocable API key. Monitor usage at https://qveris.ai.

Quick Start

Search for tools

node scripts/qveris_tool.mjs search "weather forecast API"

Execute a tool

node scripts/qveris_tool.mjs execute openweathermap_current_weather --search-id <id> --params '{"city": "London", "units": "metric"}'

Script Usage

node scripts/qveris_tool.mjs <command> [options]

Commands:
  search <query>     Search for tools matching a capability description
  execute <tool_id>  Execute a specific tool with parameters

Options:
  --limit N          Max results for search (default: 10)
  --search-id ID     Search ID from previous search (required for execute)
  --params JSON      Tool parameters as JSON string
  --max-size N       Max response size in bytes (default: 20480)
  --timeout N        Request timeout in seconds (default: 30 for search, 60 for execute)
  --json             Output raw JSON instead of formatted display

Workflow

1. Search: Describe the capability needed (not specific parameters)

   • Good: "weather forecast API"
   • Bad: "get weather for London"

2. Select: Review tools by success_rate and avg_execution_time

3. Execute: Call tool with tool_id, search_id, and parameters

Example Session

# Find weather tools
node scripts/qveris_tool.mjs search "current weather data"

# Execute with returned tool_id and search_id
node scripts/qveris_tool.mjs execute openweathermap_current_weather \
  --search-id abc123 \
  --params '{"city": "Tokyo", "units": "metric"}'

Use Cases

• Weather: Get current weather, forecasts for any location
• Search: Web search, information retrieval
• Stocks & Finance: Query stock prices, historical data, earnings calendars
• Economics: GDP, inflation rates, economic indicators
• Geolocation: IP lookup, geocoding, reverse geocoding
• AIGC: Image generation, text-to-speech, AI content creation
• News: Headlines, article search, trending topics
• Social Media: Trending topics, post analytics, engagement data
• Health Data: Clinical trials, drug info, health statistics
• And more: QVeris aggregates thousands of API tools