omk-research-verify

Name: omk-research-verify
Availability: InStock
Author: dmae97

Research current web sources and produce cited confirmation summaries for technical facts.

130|14|Updated Apr 30, 2026

Search Tags:#versioning #web research #technical documentation #fact verification #api pricing #source citation

Ready to run

npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-research-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: omk-research-verify
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/agents/omk-research-verify
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-research-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wrong or outdated technical claims by guiding research that confirms current facts, versions, APIs, pricing, and policy details from reliable references.

Core Features & Use Cases

Evidence-first verification: Prioritizes official documentation, checks dates and versions, and separates confirmed facts from inference.
Multi-source corroboration: Compares at least two reliable sources when possible to reduce the risk of errors.
Source-cited outputs: Requires citing sources in the final answer and avoiding stale memory for version-sensitive information.
Use Case: When evaluating whether a library endpoint, SDK method, or pricing policy has changed for a specific release, gather current evidence and produce a clear “confirmed vs uncertain” summary.

Quick Start

Use omk-research-verify to research a specific technical question for the current version and return a “Confirmed / Uncertain / Sources” result with cited evidence.

Frequently Asked Questions about omk-research-verify

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

FAQPage Schema

How do I verify if technical documentation or API pricing has changed for a recent release?▼

You can verify API pricing changes by researching current web sources, prioritizing official documentation, checking version dates, and comparing multiple reliable references to produce a source-cited confirmation summary.

What is the best way to check current API pricing without relying on stale memory?▼

The best way to check current API pricing without stale memory is to gather current evidence from official documentation and multiple reliable references, separating confirmed facts from inference while outputting explicit sources.

How do I confirm version-sensitive library endpoints and SDK methods from reliable references?▼

You confirm version-sensitive library endpoints and SDK methods by researching web sources, prioritizing official documentation, checking dates and versions, and comparing at least two reliable sources to reduce the risk of errors.

Can I get a confirmed versus uncertain summary for fast-changing tech facts and policies?▼

Yes, you can get a confirmed versus uncertain summary for fast-changing tech facts by gathering current evidence from official documentation and returning a clear result with cited sources for version-sensitive details.

Does fact verification for technical documentation require multi-source corroboration?▼

Fact verification for technical documentation requires multi-source corroboration by comparing at least two reliable sources when possible, reducing the risk of errors and separating confirmed facts from inference in the output.

When do I need source citation for verifying version-sensitive technical facts?▼

You need source citation for verifying version-sensitive technical facts when built-in knowledge may be stale, requiring you to output explicit sources and produce a source-cited confirmation summary for libraries, APIs, pricing, and policies.