| name | journal-if |
| description | Use when looking up journal impact factors (JCR IF), checking a journal's impact factor by name, comparing IF across journals, or answering questions about "影响因子" / "impact factor" / "IF". Triggers on "impact factor", "journal IF", "影响因子", "JCR", "IF score", "journal rank", "which journal has higher IF", "what is the IF of". PROACTIVELY USE when user mentions journal prestige, publication venue quality, or manuscript submission target evaluation. |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep |
| author | Agents365-ai |
| category | Academic Research |
| version | 1.0.0 |
| created | 2026-07-14T00:00:00.000Z |
| updated | 2026-07-14T00:00:00.000Z |
| github | https://github.com/Agents365-ai/journal-if |
| homepage | https://github.com/Agents365-ai/journal-if |
| metadata | {"version":"1.0.0","openclaw":{"requires":{"bins":"[Truncated]"},"emoji":"📊","homepage":"https://github.com/Agents365-ai/journal-if","os":["macos","linux","windows"]}} |
Journal Impact Factor Lookup
Look up journal impact factors using a two-source cascade: bundled CSV cache (~200 common journals) → OpenAlex API (approximate 2-year IF for any journal).
Critical rule: Always use journal_if.py for lookups. Never guess impact factors — they change yearly and vary by edition.
Quick Reference
| User wants... | Tier | Command |
|---|
| Look up IF of a journal | read | python3 journal_if.py lookup "Nature Medicine" |
| Search for a journal | read | python3 journal_if.py search "cancer immunology" |
| Process a list of journals | read | python3 journal_if.py batch journals.txt |
| Cache-only (no network) | read | python3 journal_if.py --offline lookup "Cell" |
| Inspect cache state | read | python3 journal_if.py cache status |
| Refresh upstream CSV | write | python3 journal_if.py cache update |
| Machine-readable CLI contract | read | python3 journal_if.py schema |
| Schema for one subcommand | read | python3 journal_if.py schema lookup |
Output format
Stdout is a stable JSON envelope when the CLI is not attached to a terminal
(piped or captured by an agent), and a human-readable view when run on a TTY.
To force a format: --format json|table|human|auto. --json is a back-compat
alias for --format json.
Envelope shape:
- Success:
{ "ok": true, "data": {...}, "meta": { "schema_version", "cli_version", "latency_ms" } }
- Partial success (batch):
{ "ok": "partial", "data": { "succeeded": [...], "failed": [...] }, "meta": {...} }
- Error:
{ "ok": false, "error": { "code", "message", "retryable", ... }, "meta": {...} }
Exit codes
