Agent skill

Research

by EliasOulkadi in EliasOulkadi/shokunin

Deep research with web search, source verification, and fact-checking.

MITAuto-check passedResearch & Science

Install Research

skills CLI
$ npx skills add EliasOulkadi/shokunin --skill research -a claude-code

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

GitHub CLI
$ gh skill install EliasOulkadi/shokunin 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/EliasOulkadi/shokunin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pack/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
114
Token cost
~3.4k tokens
SKILL.md length
1,594 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
MIT

At a glance

Deep research with web search, source verification, and fact-checking.

  • Works in 4 steps: The direct knowledge test (before citing) → Triangulation (Princeton method) → Bias and agenda assessment (NPR) → …
  • User asks to research a topic
  • SKILL.md covers Core principle, Evidence hierarchy (adapted…, Source verification protocol… and Verification tiers (adapted…, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Research is an agent skill from EliasOulkadi/shokunin. Deep research with web search, source verification, and fact-checking. Runs before humanize + kami in the document pipeline. Use when user asks to research a topic, verify facts, gather sources, or do deep web investigation. Covers source validation, citation, and evidence hierarchy.

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: opencode

It sits in Research & Science, covering Fact-checking and source verification, Humanizing AI text and Deep research. The repository describes itself as: 職人 Shokunin 62 AI agent skills for OpenCode, Claude Code, Cursor, Windsurf. ChromaDB memory, MCP servers, declarative self-updates. Multi-model, open source, zero cost. The licence is MIT.

When your agent uses it

  • User asks to research a topic
  • Do deep web investigation

Example prompts

  • “/research”

Requirements

  • Compatibility (from SKILL.md): opencode

Workflow steps

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

  1. The direct knowledge test (before citing)
  2. Triangulation (Princeton method)
  3. Bias and agenda assessment (NPR)
  4. The five-minute background check (NPR)

What it can do on your machine

Read from SKILL.md and the folder at commit 4c68e5b. 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

    No URLs in SKILL.md.

    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.

  • Compatibility

    opencode

    From compatibility in the SKILL.md frontmatter.

Context cost

Research loads about 3.4k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 1,594 words of instructions outside code blocks.

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

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 EliasOulkadi/shokunin at commit 4c68e5b, republished under its MIT licence (© EliasOulkadi). 1,594 words, ~3,396 tokens.

Download SKILL.mdSave it as .claude/skills/research/SKILL.md (or your agent's skills folder).
name
research
description
Deep research with web search, source verification, and fact-checking. Runs before humanize + kami in the document pipeline. Use when user asks to research a topic, verify facts, gather sources, or do deep web investigation. Covers source validation, citation, and evidence hierarchy.
compatibility
opencode
triggers
research, research this, find information about, search the web, verify facts, fact check, gather sources, deep investigation, web research, look up…
negatives
memory search, ChromaDB, vector search, code search, git history
license
MIT
metadata.version
1.0.0
metadata.workflow
ai-agents
metadata.audience
general

research · 調査

調査 · ちょうさ — "investigation". Source verification and fact-checking for document generation.

Pre-loads facts before writing. Runs BEFORE humanize + kami + kagen in the document pipeline. Prevents hallucinated data, fake citations, unverified claims.

Based on: CIA Structured Analytic Techniques (Heuer & Pherson), US Government Tradecraft Primer, NPR Training verification guide, Princeton triangulation methodology, OSINT verification tiers (War Intel Hub), journalistic cross-verification research (Godler & Reich), AI hallucination benchmarks (Vectara HHEM 2026), and evidence hierarchy frameworks (NHMRC).


Core principle

Sources before phrasing. Do not write a claim without verifying it first. Every number, date, name, version, and citation must be traced to a primary or reputable secondary source.


Evidence hierarchy (adapted from NHMRC + intelligence community)

Use this hierarchy to determine the weight of each source:

LevelTypeExample
1 — Direct primaryOfficial document, direct capture, observed dataReal HTTP response, source code, DB dump, screenshot
2 — Official primaryOfficial statement, public documentation, filingSEC filing, CVE entry, official changelog, press release
3 — Reputable secondaryEstablished outlet, peer-reviewed paper, curated databaseNVD, Wordfence, OWASP, Reuters, arXiv
4 — Multiple independent sources3+ unrelated sources report the sameCross-reference across tech blogs + forums + docs
5 — Single source with evidenceOne verifiable source but no corroborationResearcher blog with reproducible evidence
6 — UnverifiedUnsupported claim, rumor, speculationDo NOT use as fact in a document

Rule: a professional document only uses levels 1–4 for factual claims. Level 5 for context or direct quotes, marked as such. Level 6 is not published.


Source verification protocol (NPR + Princeton triangulation)

Step 1: The direct knowledge test (before citing)

Ask about each source:

  • First-hand: Did the source witness the event, participate directly, or have documentation? → Strong, but requires corroboration
  • Second-hand: Did the source hear it from someone else? → Useful for leads, insufficient to publish
  • Third-hand+: Rumor, hearsay, speculation? → Not publishable as fact
Step 2: Triangulation (Princeton method)

Cross-check each claim against multiple independent sources:

Claim: "WordPress 6.7 has vulnerability X"
  → Source A: official WordPress advisory
  → Source B: entry in NVD/CVE
  → Source C: Wordfence or similar analysis
  → Do they agree? → VERIFIED
  → Only one source? → NOT VERIFIED
Step 3: Bias and agenda assessment (NPR)

For each source, identify:

  • Financial interest: Does the source benefit financially from a particular narrative?
  • Professional interest: Does their reputation/career depend on a certain outcome?
  • Personal relationships: Friends, family, enemies of the subject?
  • Funding: Who funds the source? What interests does that funder have?
Step 4: The five-minute background check (NPR)

When time is short:

  1. Read the source's bio and "About" page
  2. Identify who funds or backs them
  3. Look for behavior patterns or prior claims
  4. Verify if there are visible conflicts of interest

Verification tiers (adapted from OSINT + War Intel Hub)

Every claim in the document must have an assigned tier:

TierLabelRequirementColor in document
✓VERIFIED2+ primary sources or 1 primary + direct evidenceNormal (no mark)
oCORROBORATEDMultiple independent sources report the same, without direct primary sourceNormal (no mark)
XUNVERIFIEDSingle source or unconfirmableExplicitly mark "unverified" or don't include

Rule: in professional documents, everything published without a mark must be VERIFIED or CORROBORATED. UNVERIFIED is omitted or declared as such.


Anti-hallucination checklist (based on Vectara HHEM benchmarks 2026)

LLMs hallucinate 15-20% of the time on factual queries (source: Prompt Guardrails, Vectara benchmark March 2026). Reasoning models hallucinate more than standard ones in summarization (DeepSeek-R1: 14.3% vs V3: 6.1%).

Before writing any claim, run it through this filter:

QuestionCheck
Does this number have a verifiable source?
Is this date confirmed by a primary source?
Does this name/version actually exist?
Is this quote verbatim and verifiable?
Is this CVE/ID real and does it match what I'm saying?
Does this statistic come from a real study?
Am I making up a "study shows" to add weight?
Is this claim about the model/framework true today?

Common categories of AI-invented data (research flags)

CategoryRed flagWhat to do
Versions"WordPress 6.8 has..." with no advisoryCheck wordpress.org/news/releases
CVEsCVE-2026-XXXX with no NVD entrySearch nvd.nist.gov
Statistics"80% of sites..." with no studyDon't use without a source
DatesPatch dates, release datesVerify in official changelog
Quotes"As X said: '...'"Confirm X actually said that
Security metricsExploit times, ratesSearch real reports (Veracode, Splunk, etc.)
Tool namesNon-existent tools or wrong versionsVerify official homepage or repository

Context adaptation by document type

Not all documents need the same verification level. Adjust by type:

Document typeVerification priorityCritical fieldsTolerance
Pentest / SecurityMaximumCVEs, versions, dates, screenshots, exploitsZero. A fake CVE invalidates the report
White paper / TechnicalHighStatistics, quotes, dates, versions, tool namesLow. Made-up quotes destroy credibility
One-pager / ExecutiveMediumCore metrics, client names, key datesMedium. Minor errors tolerable if the central message is correct
Resume / CVMaximum in personal dataEmployment dates, titles, companies, quantifiable achievementsZero in personal data. Achievement claims can be contextual
LetterLowNames, titles, datesHigh. Tone matters more than factual precision
Slides / DeckMediumKey statistics, verbatim quotes, namesMedium. Visual context takes priority over detail

Rule: if the document goes to an external client or has legal/security implications, always use maximum verification.

Document pipeline integration

  • A specific software version → check official changelog
  • A CVE or vulnerability → search NVD + official advisory
  • A statistic or metric → find primary source or don't include
  • A verbatim quote → confirm it exists
  • An event date → verify in official source
  • A person/tool/company name → verify it exists and is spelled correctly

Sources

  • Heuer & Pherson, Structured Analytic Techniques for Intelligence Analysis (CIA Sherman Kent School)
  • US Government, A Tradecraft Primer: Structured Analytic Techniques for Improving Intelligence Analysis (2009)
  • NPR Training, "Don't just check the facts, check the source: a guide to verification" (March 2026)
  • Princeton University Library, guide "Triangulation and Media Literacy" (2025)
  • War Intel Hub, "OSINT Verification Methodology"
  • Vectara HHEM hallucination benchmark leaderboard (March 2026)
  • Prompt Guardrails, "AI Hallucination Detection and Prevention Guide" (2026)
  • News Factory, "News Fact-Checking in 2026: Hallucination Benchmarks, RAG, and Verification Tools"
  • Reuters / AP sourcing standards
  • GlobalX Publications, "Fact-Checking, Triangulation, and Evidence Reliability in Research"
  • NHMRC evidence hierarchy framework

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

Workflow

  1. Define research scope — identify exactly what claims need verification: numbers, dates, versions, names, quotes, CVE IDs, statistics.
  2. Search primary sources first — official changelogs, CVE entries (nvd.nist.gov), SEC filings, source code repositories, direct HTTP responses.
  3. Triangulate across independent sources — cross-check each claim against 3+ unrelated sources. Do they independently agree? If only one source, mark as UNVERIFIED.
  4. Assess source credibility — financial interest, professional stake, funding bias, personal relationships. Apply the five-minute background check from NPR methodology.
  5. Assign verification tiers — VERIFIED (2+ primary sources), CORROBORATED (multiple sources, no primary), UNVERIFIED (single source). Tag every claim.
  6. Run anti-hallucination filter — verify every number, date, version, and quote against the Vectara HHEM checklist before writing.
  7. Adapt verification level to document type — maximum for pentest/security reports and CVs. Medium for white papers and exec summaries. Lower for personal letters.

Error Handling

CauseFix
CVE ID returned no results from NVDSearch official vendor advisory directly. Check if it's a reserved but unpublished CVE. Mark as CORROBORATED if vendor confirms.
Official changelog disagrees with secondary sourcesTrust the primary source. Note the discrepancy. Re-check secondary sources for outdated or misinterpreted data.
Statistics claim with no identifiable studyReject the claim. Do not publish. Replace with qualified language ("commonly observed", "widely reported") or omit entirely.
Source behind paywall or login gateSearch for preprint, open-access version, or web archive. If unavailable, mark as "source not independently verified."
Direct quote cannot be confirmed to existDo not publish as verbatim. If essential, paraphrase with attribution like "as characterized by..." or "according to reporting by..."
Multiple sources conflict on a key date or numberGo with the primary source. Note the conflict if it matters (e.g., "Sources differ on exact date; official changelog lists [date]").
AI hallucination detected in generated text during verificationStrip the hallucinated claim immediately. Replace with verified data or omit. Re-check surrounding context for contamination.
Research timed out before all claims verifiedPrioritize critical claims (CVEs, versions, names). Mark unverified claims explicitly. Ship with "preliminary" designation if necessary.

Anti-Patterns

PatternProblemFix
"Studies show..." with no citationHallucinated authority. Undermines entire document credibility.Never state a study exists without a verifiable citation. Use real sources or don't claim one.
Accepting the first Google result as factSingle-source bias. SEO ranking ≠ accuracy.Always triangulate. Minimum 3 independent sources for factual claims.
Citing Wikipedia as a primary sourceWikipedia is a tertiary source. Editing wars and vandalism skew content.Trace Wikipedia citations to their original primary sources. Use Wikipedia as a launch point, not an endpoint.
Publishing numbers without checking if they're from a real studyLLMs invent plausible-sounding statistics 15-20% of the time.Verify every number against its original study. If the study doesn't exist, the number doesn't either.
Using LLM training data as "verification" without web searchTraining data is frozen, outdated, and hallucination-prone.Always run live web searches. Cross-check against current official sources.
Including level 5 (single source) claims without marking themReader assumes verified when it's actually unconfirmed.Explicitly mark any level 5 claim: "[Source: single report, not independently confirmed]".
Treating all sources as equally credibleA Reddit comment ≠ a peer-reviewed paper ≠ an NVD entry.Apply evidence hierarchy. Weight sources by type, not by what supports the desired narrative.
Skipping verification because the claim "sounds right"Confirmation bias. LLMs are confident and wrong simultaneously.Verify every factual claim. "Sounds right" is how hallucinations reach production documents.

Checklist

  • Skill loads without errors in the AI agent
  • YAML frontmatter is valid (description, compatibility, audience)
  • Workflow section provides clear step-by-step instructions
  • Error handling section covers common failure modes
  • All referenced files (references/, scripts/, assets/) exist
  • Skill triggers correctly for intended use cases
  • No broken links or missing resources

© EliasOulkadi, MIT. 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 .pack/skills/research of EliasOulkadi/shokunin.

Open the folder on GitHubat commit 4c68e5b

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 skillEliasOulkadi/shokunin114—~3.4kAutomated safety check: PassMIT
Parallel WebLeonChaoX/qinyan-academic-skills9441 repos~2.9kAutomated safety check: NotesMIT
Ray Trend Searchimraywang/rayskills159—~2.1kAutomated safety check: PassCustom licence
Argo Search and Verificationtaxueseek/argo188—~1.2kAutomated safety check: PassMIT
Live Researchbrightdata/skills264—~1.8kAutomated safety check: PassMIT
Researchzhongkaifu/TensorSharp568—~2.3kAutomated safety check: WarnBSD-3-Clause

Similar skills

  • Parallel Web

    LeonChaoX/qinyan-academic-skills

    Search the web, extract URL content, and run deep research using the Parallel Chat API and Extract API.

    944 GitHub starsUsed in 1 repo~2.9k tokens
    Research & ScienceAuto-check: notes
  • Ray Trend Search

    imraywang/rayskills

    Researches what people are saying about a topic over a recent window across X, Reddit, YouTube and the public web, reporting each source's status with links.

    159 GitHub stars~2.1k tokensUpdated 18 days ago
    Research & ScienceAuto-check passed
  • Unified web search, page fetching and evidence checking across hundreds of sources, with result verification, a research-dossier mode and vertical search engines.

    188 GitHub stars~1.2k tokensUpdated 5 days ago
    Research & ScienceAuto-check passed
  • Live Research

    brightdata/skills

    Produce a deep, multi-source, cited research brief on a topic from live web data using Bright Data's Discover API (intent-ranked web search + parsed page content).

    264 GitHub stars~1.8k tokensUpdated 4 days ago
    Research & ScienceAuto-check passed
  • Research

    zhongkaifu/TensorSharp

    A skill your agent uses for web searches and current information lookups, finding sources, fact-checking, researching questions, comparing sources, or summarising web pages.

    568 GitHub stars~2.3k tokensUpdated today
    Research & ScienceAuto-check: warnings
  • Deep Research Methodology

    RightNow-AI/openfang

    Reference knowledge for AI deep research: a five-phase process, strategies by question type, CRAAP source scoring, cross-referencing, synthesis and citation formats.

    18k GitHub stars~2.6k tokensUpdated 3 mo ago
    Research & ScienceAuto-check passed

More from EliasOulkadi/shokunin

All 49 skills in this repo
  • CI CD

    EliasOulkadi/shokunin

    Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…

    114 GitHub stars~3.4k tokensUpdated 6 days ago
    Auto-check: notes
  • Component Forge

    EliasOulkadi/shokunin

    Build production-grade components for React, Vue 3, and Svelte 5 with all states (loading, empty, error, success, idle), TypeScript strict, WCAG 2.2 accessibility, server components (RSC), and…

    114 GitHub stars~3.6k tokensUpdated 6 days ago
    Auto-check: notes
  • DB Admin

    EliasOulkadi/shokunin

    PostgreSQL database administration — backup/restore (pgdump, PITR, WAL archiving), health monitoring (connections, bloat, cache hit ratio, dead tuples), connection pooling (PgBouncer), replication…

    114 GitHub stars~2k tokensUpdated 6 days ago
    Auto-check: notes
  • DB Sculptor

    EliasOulkadi/shokunin

    Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and…

    114 GitHub stars~3.1k tokensUpdated 6 days ago
    Auto-check: notes
  • Docker

    EliasOulkadi/shokunin

    Optimize Docker images with multi-stage builds, distroless bases, BuildKit cache mounts, multi-arch builds, compose watch, security hardening (non-root, seccomp, capabilities drop), and…

    114 GitHub stars~3.8k tokensUpdated 6 days ago
    Auto-check: notes
  • Error Handler

    EliasOulkadi/shokunin

    Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…

    114 GitHub stars~3.6k tokensUpdated 6 days ago
    Auto-check: notes

Questions about Research

What does Research do?

Deep research with web search, source verification, and fact-checking. Research is an agent skill from EliasOulkadi/shokunin. Deep research with web search, source verification, and fact-checking.

When should I use Research?

Research fits situations like: user asks to research a topic; do deep web investigation.

How do I install Research in Claude Code?

Run `npx skills add EliasOulkadi/shokunin --skill research -a claude-code`. Or copy the skill folder (.pack/skills/research in EliasOulkadi/shokunin) 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 EliasOulkadi/shokunin --skill research -a codex`. Or copy the skill folder (.pack/skills/research in EliasOulkadi/shokunin) 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 EliasOulkadi/shokunin --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. Compatibility (from SKILL.md): opencode.

Does Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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 MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Research use?

About 3.4k tokens (SKILL.md is roughly 14k 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: Parallel Web (LeonChaoX/qinyan-academic-skills, 944 stars), Ray Trend Search (imraywang/rayskills, 159 stars), Argo Search and Verification (taxueseek/argo, 188 stars) and Live Research (brightdata/skills, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Research?

EliasOulkadi (a GitHub user) maintains it in EliasOulkadi/shokunin, which has 114 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 5, 2026.

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