
- Installs
- 54
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/cookjohn/wos-skills --skill wos-export- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads wos-export automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
WoS Export
Export WoS paper records. Two modes: direct Zotero push (preferred) or file export via UI.
Mode A: Push to Zotero (preferred, no UI interaction)
Collect paper metadata (from prior search/detail results) and push to Zotero via the push_to_zotero.py script.
Step 1: Prepare Paper Data
Build a JSON object from data already available in the conversation (from wos-search API results or wos-paper-detail extraction). The script accepts WoS paper fields directly:
{
"title": "Value co-creation in service logic",
"authors": "Grönroos, C",
"source": "MARKETING THEORY",
"year": 2011,
"volume": "11",
"issue": "3",
"pages": "279-301",
"doi": "10.1177/1470593111408177",
"issn": "1470-5931",
"abstract": "The underpinning logic of...",
"language": "English",
"accessionNumber": "WOS:000295471900004",
"authorKeywords": ["value co-creation", "service logic"],
"keywordsPlus": ["DOMINANT LOGIC"],
"citedCount": "992",
"alldbCited": "1,254",
"jif": "2.8",
"jifYear": "2024",
"jcrQuartile": "Q3",
"researchAreas": "Business & Economics",
"wosCategories": "Business",
"docType": "Article"
}
For multiple papers, wrap in an array or {"items": [...]}.
Step 2: Push via Script
echo '{JSON_DATA}' | python "e:\wos-skills\.claude\skills\wos-export\scripts\push_to_zotero.py"
Or save to temp file first (recommended for large data or Chinese characters):
python "e:\wos-skills\.claude\skills\wos-export\scripts\push_to_zotero.py" /tmp/wos_export.json
Step 3: Report Result
OK: Saved (session: xxx)→ successOK: Already saved (session: xxx)→ idempotent, no duplicatesError: Zotero not running→ tell user to start Zotero desktop
The script auto-detects Zotero's currently selected collection. User can change target by selecting a different folder in Zotero before exporting.
To list collections: python push_to_zotero.py --list
Mode B: File Export via UI (fallback)
When Zotero is not available or user specifically wants a file.
Prerequisites
Browser must be on a WoS results page (/summary/...) or full record page (/full-record/...).
Supported Formats
| Format | Menu Item | File |
|---|---|---|
| RIS | "RIS (other reference software)" | .ris |
| BibTeX | "BibTeX" | .bib |
| Excel | "Excel" | .xlsx |
| Plain Text | "Plain text file" | .txt |
| Fast 5000 | "Fast 5000" | Quick export |
Steps
take_snapshot→ find Export button (buttonwithhaspopup="menu"containing "Export") →clicktake_snapshot→ find format menuitem →click- Handle export dialog (record range, content options) → click download button
Notes on UI Export
- Uses 3-4 tool calls: snapshot + click Export + snapshot + click format + dialog
- "Fast 5000" exports up to 5000 records with basic fields
- On full-record page, exports only the current record
Zotero Script Features
- Deterministic session ID: Same papers always produce the same session ID (content hash). Prevents duplicates on retry (409 → treated as success).
- WoS metadata mapping: Automatically maps WoS fields to Zotero's journalArticle schema.
- Extra field: Stores WoS-specific data (WoS ID, citation counts, JIF, JCR quartile, research areas) in Zotero's Extra field.
- Author parsing: Handles WoS standard format "LastName, Initials" → Zotero firstName/lastName.
- Keywords: Both Author Keywords and Keywords Plus are added as Zotero tags.
Notes
- Mode A (Zotero push) requires no browser interaction — uses data from prior API calls
- Mode A works even when browser is not on a WoS page
- Script path:
e:\wos-skills\.claude\skills\wos-export\scripts\push_to_zotero.py - Zotero must be running on localhost:23119
FAQ
What does the wos-export skill do?
Export WoS records to Zotero, RIS, BibTeX, or Excel.
How do I install wos-export?
Run npx skills add https://github.com/cookjohn/wos-skills --skill wos-export in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/wos-export/ (personal) or .claude/skills/wos-export/ (project).
Which AI agents can use wos-export?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is wos-export safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains wos-export?
It is published by cookjohn in cookjohn/wos-skills. It has 54 recorded installs.
More from cookjohn/wos-skills
wos-download
cookjohn/wos-skills
Download PDF full text for a WoS paper via publisher links.
wos-paper-detail
cookjohn/wos-skills
Get detailed information for a paper by WoS ID (e.g., WOS:000779183600001).
wos-parse-results
cookjohn/wos-skills
Parse search results from the current WoS results page or API response. Internal skill used by other skills.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.