Wos Search logo

Wos Search

Community
YuanyuanMa03
wos-search

Web of Science 全流程技能:主题/作者/标题/DOI/高级检索(内部 API,含 SID 回退)、论文详情解析、结果页解析(含离线快照模式)、翻页、DOM 结构参考。

Overview

PublisherYuanyuanMa03
Repositoryacademic-research-skills
Skill namewos-search
Stars
76
Forks
7
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by YuanyuanMa03 on GitHub. Read the source before you install it.

Installation

Install the Wos Search AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/YuanyuanMa03/academic-research-skills/tree/main/plugins/wos-search/skills/wos-search
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/YuanyuanMa03/academic-research-skills.git /tmp/academic-research-skills
mkdir -p .claude/skills
cp -r /tmp/academic-research-skills/plugins/wos-search/skills/wos-search .claude/skills/wos-search
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Wos Search in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Wos Search on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Wos Search is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

WoS Search — 全流程技能

一个技能覆盖 Web of Science 站内全部动作。检索在本文件;其余场景按路由表进入对应子流程文档。

场景路由

用户想做什么进入哪个流程
检索(本文件主流程:内部 API + no_session 回退)下文
打开/解析某篇论文详情页references/paper-detail.md
解析当前结果页(或已保存的页面快照,离线模式)references/parse-results.md
结果翻页references/navigate-pages.md
WoS 页面 DOM 结构参考(选择器速查)references/dom-reference.md
下载/导出/推送 Zotero条目交给 scansci-pdf 技能

Important: Browser Prerequisite

The browser must be on any webofscience.com page (logged in). The skill calls the WoS internal API directly via fetch, so no page navigation is needed.

Language Guidance

WoS databases (especially SCI/SSCI) primarily index English-language literature. If the user provides Chinese keywords, translate to English (e.g., "价值共创" → "value co-creation"). Inform the user about the translation.

Parameter Reference

Database (product)

User saysproductDescription
"core collection" / defaultWOSCCWoS Core Collection
"all databases"ALLDBAll databases combined
"medline"MEDLINEBiomedical literature
"preprint"PPRNPreprint Citation Index
"scielo"SCIELOSciELO Citation Index

Edition filtering (Core Collection only)

User sayseditions value
"SCI" / "science"WOS.SCI
"SSCI" / "social science"WOS.SSCI
"CPCI" / "conference"WOS.CPCI-S, WOS.CPCI-SSH
"all" / defaultomit editions field (or include all)

Multiple editions can be combined: ["WOS.SCI", "WOS.SSCI"]

Sort options

User sayssort value
"citations" / "most cited"times-cited-descending
"newest" / "latest"date-descending
"oldest"date-ascending
"relevance" / defaultrelevance
"usage"usage-count-last-180-days-descending

Field mapping (for query rows)

User saysrowField
topic / keyword / aboutTS
titleTI
authorAU
DOIDO
journal / sourceSO
yearPY
affiliation / institutionOG
abstractAB
fundingFO
countryCU

Steps

Step 1: Build API Request Body

json
{
  "product": "WOSCC",
  "searchMode": "general",
  "viewType": "search",
  "serviceMode": "summary",
  "search": {
    "mode": "general",
    "database": "WOSCC",
    "query": [
      {"rowField": "TS", "rowText": "USER_QUERY"}
    ],
    "editions": ["WOS.SSCI"]
  },
  "retrieve": {
    "count": 10,
    "history": true,
    "jcr": true,
    "sort": "times-cited-descending",
    "analyzes": [],
    "locale": "en"
  },
  "eventMode": null
}
  • query: array of {rowField, rowText} objects. For multiple conditions, add rowBoolean (AND/OR/NOT) to subsequent rows.
  • editions: optional, omit for all editions.
  • count: number of records to retrieve (default 10, max 50).
  • sort: default relevance.

Step 2: Execute API Call via evaluate_script

This is the only tool call needed — 1 call total.

If the browser was previously on a non-WoS page (e.g., after following a publisher link), SID will be lost. In that case, first navigate back to any WoS page (navigate_page to https://www.webofscience.com/wos/woscc/basic-search) to re-establish the session, then run the API call. This adds 1 extra tool call (2 total).

Alternatively, use the URL-based fallback (Step 2B below) which always works regardless of SID state.

javascript
async () => {
  // Extract SID from network history
  const sid = performance.getEntriesByType('resource')
    .filter(r => r.name.includes('SID='))
    .map(r => r.name.match(/SID=([^&]+)/)?.[1])
    .filter(Boolean)[0] || '';

  if (!sid) return { status: 'no_session', message: 'SID lost (likely navigated to external site). Use Step 2B or navigate to any WoS page first.' };

  const response = await fetch(`/api/wosnx/core/runQuerySearch?SID=${sid}`, {
    method: 'POST',
    headers: { 'Content-Type': 'text/plain;charset=UTF-8', 'Accept': 'application/x-ndjson' },
    body: JSON.stringify({
      "product": "{PRODUCT}",
      "searchMode": "general",
      "viewType": "search",
      "serviceMode": "summary",
      "search": {
        "mode": "general",
        "database": "{PRODUCT}",
        "query": [{QUERY_ROWS}],
        "editions": [{EDITIONS}]
      },
      "retrieve": {
        "count": {COUNT},
        "history": true,
        "jcr": true,
        "sort": "{SORT}",
        "analyzes": [],
        "locale": "en"
      },
      "eventMode": null
    })
  });

  const text = await response.text();
  const lines = text.trim().split('\n').map(line => {
    try { return JSON.parse(line); } catch(e) { return null; }
  }).filter(Boolean);

  const searchInfo = lines.find(l => l.key === 'searchInfo')?.payload;
  const recordsData = lines.find(l => l.key === 'records')?.payload;

  let records = [];
  if (recordsData) {
    records = Object.entries(recordsData).map(([idx, rec]) => ({
      idx: parseInt(idx),
      wosId: rec.colluid,
      title: rec.titles?.item?.en?.[0]?.title || '',
      authors: rec.names?.author?.en?.filter(Boolean).map(a => a.wos_standard).join('; ') || '',
      source: rec.titles?.source?.en?.[0]?.title || '',
      year: rec.pub_info?.pubyear || '',
      vol: rec.pub_info?.vol || '',
      issue: rec.pub_info?.issue || '',
      pages: rec.pub_info?.page_no || '',
      doi: rec.doi || '',
      citations: rec.citation_related?.counts?.WOSCC || 0,
      citationsAll: rec.citation_related?.counts?.ALLDB || 0,
      refCount: rec.ref_count || 0,
      abstract: rec.abstract?.basic?.en?.abstract?.replace(/<[^>]*>/g, '')?.substring(0, 300) || '',
      docType: rec.doctypes?.[0] || '',
      oa: rec.oa || false
    }));
  }

  return {
    status: 'ok',
    totalResults: searchInfo?.RecordsFound || 0,
    recordsSearched: searchInfo?.RecordsSearched || 0,
    queryId: searchInfo?.QueryID || '',
    records
  };
}

Step 3: Present Results

Display as a table:

Found **{totalResults}** results in {database} ({edition}).
Sorted by: {sort}.

| # | Title | Authors | Source | Year | Cited | WoS ID |
|---|-------|---------|--------|------|-------|--------|
| 1 | {title} | {authors} | {source} | {year} | {citations} | {wosId} |
| ... |

Offer next actions:

  • "Use /wos-paper-detail {WoS ID} for detailed information"
  • "Export results: collect entries, then use the scansci-pdf skill (scansci_pdf_citation / scansci_pdf_zotero_push)"
  • To see more results, re-run with higher count or use /wos-navigate-pages

Step 2B: URL-based Fallback (when SID is lost)

If API returns no_session (e.g., after navigating to an external publisher site), fall back to URL navigation:

navigate_page({
  url: "https://www.webofscience.com/wos/{db}/general-summary?queryJson={ENCODED_QUERY_JSON}",
  initScript: "Object.defineProperty(navigator, 'webdriver', {get: () => undefined})"
})

Then extract results via evaluate_script with DOM selectors (see wos-parse-results Mode B), or re-attempt the API call (SID will be re-established after the navigation).

When to use: After the browser visited an external site (publisher, DOI link, etc.) and performance.getEntriesByType('resource') no longer contains WoS SID entries.

Notes

  • 1 tool call (API) or 2 tool calls (navigate + API/DOM) if SID is lost
  • API returns NDJSON (newline-delimited JSON); parse line by line
  • SID is extracted from browser's performance resource entries
  • SID loss: Navigating to external sites clears performance entries. Recover by navigating to any WoS page first, or use URL-based fallback (Step 2B)
  • editions field uses format WOS.SCI, WOS.SSCI, WOS.CPCI-S, etc.
  • For Chinese keywords in SCI/SSCI, translate to English first
  • Max 50 records per request; use retrieve.count to control
  • history: true saves the search to WoS session history

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Wos Search AI skill do?

Web of Science 全流程技能:主题/作者/标题/DOI/高级检索(内部 API,含 SID 回退)、论文详情解析、结果页解析(含离线快照模式)、翻页、DOM 结构参考。

Why use Wos Search on TypingMind?

Because you install it once and use it with any model. Wos Search is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Wos Search in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/YuanyuanMa03/academic-research-skills/tree/main/plugins/wos-search/skills/wos-search. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Wos Search?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Wos Search?

As many as you like. As long as a model supports skills, you can use Wos Search with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Wos Search AI skill free?

Yes. It is published on GitHub by YuanyuanMa03 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇