Agent skill

Research

by katipally in katipally/openlive

A skill your agent uses when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources.

Apache-2.0Auto-check passedMedia & Creative

Install Research

skills CLI
$ npx skills add katipally/openlive --skill research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install katipally/openlive research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/katipally/openlive.git skills-src && mkdir -p .claude/skills && cp -r skills-src/services/agent/skills/research .claude/skills/research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
research
GitHub stars
336
Token cost
~827 tokens
SKILL.md length
535 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources.

  • Works in 6 steps: Plan the questions → Ask for sources, every time → Prefer primary sources → …
  • The user asks you to research
  • SKILL.md covers Your tools, 1. Plan the questions, 2. Ask for sources, every time and 3. Prefer primary sources, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Research is an agent skill from katipally/openlive. Use when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Media & Creative, covering Fact-checking and source verification and Text to speech and voice. The repository describes itself as: Opensource, on-device voice + vision layer for AI agents. Bring any model or coding agent; the whole speech loop (VAD, STT, TTS, barge-in) runs locally. An open alternative to… The licence is Apache-2.0.

When your agent uses it

  • The user asks you to research
  • Find current information
  • The answer should come with sources

Example prompts

  • “/research”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Plan the questions
  2. Ask for sources, every time
  3. Prefer primary sources
  4. Cross-check
  5. Answer and cite
  6. Say what is uncertain

What it can do on your machine

Read from SKILL.md and the folder at commit c9121eb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • frame.work

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Research loads about 827 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 535 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~827

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from katipally/openlive at commit c9121eb, republished under its Apache-2.0 licence (© katipally). 535 words, ~827 tokens.

Download SKILL.mdSave it as .claude/skills/research/SKILL.md (or your agent's skills folder).
name
research
description
Use when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources.

Researching well

Good research answers the question asked, from sources that can be checked, and says plainly what is still uncertain.

Your tools

  • delegate(task): hands one task to OpenLive's research assistant, who has web_search and fetch_url and reports back a short summary. It works while you keep talking and takes a few search steps at most, so give it one focused question per call.
  • web_search and fetch_url: if these are in your own tool list, call them directly instead of delegating. A coding agent may also have its own web tools; use whichever you have.

If you have none of these, say you cannot look it up right now and answer only from what you are sure of, marked as such.

1. Plan the questions

Before searching, break the request into the few facts that decide the answer. "Which laptop should I buy" becomes: the models in their budget, battery life measured by reviewers, current prices. Two to four focused questions beat one vague one.

Tell the user in one short line what you are checking, then start.

2. Ask for sources, every time

The assistant returns plain sentences and leaves links out unless asked. So write each delegated task to ask for them:

Find the current price of the Framework Laptop 13 in the US, from the official store, with the source URL.

Good task lines name: the exact fact, the time frame ("as of this month"), the kind of source you want (official site, the paper, the filing, a named outlet), and "with source URLs".

With web_search yourself: search, pick the most authoritative results, then fetch_url them to read the page itself. Search highlights are a lead, not a source.

3. Prefer primary sources

In order:

  1. The original: the official page, the paper, the dataset, the changelog, the court filing, the company's own announcement.
  2. A reputable outlet reporting on it, with a date.
  3. Everything else, only to find 1 or 2.

Check the date. For anything that changes (prices, versions, schedules, office holders, scores), an old page is a wrong answer.

Show full SKILL.md (189 more words)Show less

4. Cross-check

  • A fact that decides the answer needs two independent sources, or one primary source.
  • When sources disagree, say so, give both, and say which you trust and why.
  • A number with no source stays out of the answer.

If a step comes back empty or vague, rephrase once (other words, a narrower question, the official site's name). Do not repeat the same task.

5. Answer and cite

  • Lead with the answer in a sentence or two. Then the supporting facts.
  • Cite inline, right after the claim, with the URL: "The base model is $999 (https://frame.work/...)". In a spoken reply, name the source out loud ("per the official store") and keep the URLs for the written reply.
  • Keep it short. The user asked a question, not for a report, unless they asked for a report.

6. Say what is uncertain

End with what you could not confirm, if anything: "I could not find a 2026 figure; the latest is from March 2025." Never fill a gap with a guess dressed as a fact. "I don't know yet" is a fine answer, and better than a confident wrong one.

© katipally, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in services/agent/skills/research of katipally/openlive.

Open the folder on GitHubat commit c9121eb

Compare with similar skills

Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Research this skillkatipally/openlive336—~827Automated safety check: PassApache-2.0
Press Conference Revision Evidence Boundlensback940701/Evidence-Bound-Press-Conference-Revision-Skill255—~2.2kAutomated safety check: PassMIT
Podcast Generationbytedance/deer-flow83k2 repos~2.2kAutomated safety check: PassMIT
Blog AudioAgriciDaniel/claude-blog2.3k1 repos~2.2kAutomated safety check: NotesMIT
Video Translatorshang-zhu/violin1.1k—~1kAutomated safety check: NotesMIT
Adaptationdanjdewhurst/story-skills2792 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • Press Conference Revision Evidence Bound

    lensback940701/Evidence-Bound-Press-Conference-Revision-Skill

    Diagnose and revise defensive academic writing while preserving claim ceilings, evidence status, scope conditions, rival explanations, and conceptual hierarchy.

    255 GitHub stars~2.2k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Podcast Generation

    bytedance/deer-flow

    Turns written content into a two-host conversational podcast MP3 with a transcript, by drafting a JSON script and running a text-to-speech script.

    83k GitHub starsUsed in 2 repos~2.2k tokens
    Media & CreativeAuto-check passed
  • Blog Audio

    AgriciDaniel/claude-blog

    Generate audio narration of blog posts using Google Gemini TTS.

    2.3k GitHub starsUsed in 1 repo~2.2k tokens
    Media & CreativeAuto-check: notes
  • Video Translator

    shang-zhu/violin

    Dub a video into another language and generate subtitles using the default Together + Cartesia stack.

    1.1k GitHub stars~1k tokensUpdated 1 mo ago
    Media & CreativeAuto-check: notes
  • Adaptation

    danjdewhurst/story-skills

    This skill should be used when the user asks to "make an audiobook", "narration script", "narrator", "ACX", "Findaway", "pronunciation guide", "how long is the audiobook", "adapt to a screenplay"…

    279 GitHub starsUsed in 2 repos~3.5k tokens
    Media & CreativeAuto-check: notes
  • Grounded Citations

    NousResearch/hermes-agent

    Attaches a numbered, URL-backed citation to every outside fact in an answer or document, rejecting quotes that aren't real.

    252k GitHub stars~3.1k tokensUpdated yesterday
    Research & ScienceAuto-check passed

More from katipally/openlive

  • Connector Setup

    katipally/openlive

    A skill your agent uses when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion).

    336 GitHub stars~860 tokensUpdated yesterday
    Auto-check passed
  • Skill Creator

    katipally/openlive

    A skill your agent uses when the user wants to teach you a workflow, save how they like something done, or make a new skill.

    336 GitHub stars~657 tokensUpdated yesterday
    Auto-check passed
  • Computer Use

    katipally/openlive

    Use before operating an app on the user's computer, such as clicking, filling a field, reading a window or moving through a website in their browser.

    336 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Questions about Research

What does Research do?

A skill your agent uses when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources. Research is an agent skill from katipally/openlive. Use when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources.

When should I use Research?

Research fits situations like: the user asks you to research; find current information; the answer should come with sources.

How do I install Research in Claude Code?

Run `npx skills add katipally/openlive --skill research -a claude-code`. Or copy the skill folder (services/agent/skills/research in katipally/openlive) into .claude/skills/research in your project. Claude Code loads it when a task matches its description.

How do I install Research in Codex?

Run `npx skills add katipally/openlive --skill research -a codex`. Or copy the skill folder (services/agent/skills/research in katipally/openlive) into .agents/skills/research in your project. Codex loads it when a task matches its description.

Can I use Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add katipally/openlive --skill research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/research, .gemini/skills/research, .github/skills/research and .opencode/skills/research in your project.

What does Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Research is instructions for the agent only.

Does Research access the network?

SKILL.md names 1 domain. As links in the text: frame.work. This is read from the text; nothing was executed.

Is Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Research use?

Research is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Research use?

About 827 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Research?

Skills that share tags, products or a category with Research: Press Conference Revision Evidence Bound (lensback940701/Evidence-Bound-Press-Conference-Revision-Skill, 255 stars), Podcast Generation (bytedance/deer-flow, 83k stars), Blog Audio (AgriciDaniel/claude-blog, 2.3k stars) and Video Translator (shang-zhu/violin, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Research?

katipally (a GitHub user) maintains it in katipally/openlive, which has 336 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.

Source: katipally/openlive on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.