scopus-wos-coverage-auditor
Use when comparing Scopus, Web of Science, Dimensions, or related indexing outputs and the user needs a disciplined explanation of differences.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- scopus-wos-coverage-auditor
- description
- Use when comparing Scopus, Web of Science, Dimensions, or related indexing outputs and the user needs a disciplined explanation of differences.
02 资源文件 1
- 参考文档references/acceptance-criteria.md4.1 KB
03 SKILL.md 正文
scopus-wos-coverage-auditor
This skill audits database-coverage disagreements. It is for explaining why one index finds a paper, citation count, or journal signal that another one does not.
When to use
- Citation counts, h-index signals, journal coverage, or affiliation metrics differ across platforms.
- The user needs a defensible explanation before reporting metrics.
Workflow
- Identify the entity being compared: paper, author, journal, institution, or subject slice.
- Normalize identifiers first: DOI, ORCID, ISSN, affiliation variant, or journal title.
- Compare coverage assumptions, document types, update lag, and data-cleaning differences.
- Summarize what is a real disagreement versus a platform-scope difference.
- Recommend the least misleading metric to report.
Configuration and access
- Save only identifiers, report paths, and platform labels.
- Keep account access user-controlled.
Output standard
- Explain differences mechanistically, not as mysterious platform failure.
- State the reporting caveat that should travel with the metric.
Guardrails
- Do not average incompatible metrics into one number.
- Do not report comparative counts without naming the source platform and date.
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files