Journal Impact Factor Trend
name: journal-impact-factor-trend
by aipoch-ai · published 2026-04-01
$ claw add gh:aipoch-ai/aipoch-ai-journal-impact-factor-trend---
name: journal-impact-factor-trend
description: Show journal impact factor and quartile trends over 5 years.
license: MIT
skill-author: AIPOCH
---
# Journal Impact Factor Trend
Display 5-year impact factor and quartile trends for target journals to identify rising or declining journals.
When to Use
Key Features
Dependencies
See `## Prerequisites` above for related details.
Example Usage
See `## Usage` above for related details.
cd "20260318/scientific-skills/Evidence Insight/journal-impact-factor-trend"
python -m py_compile scripts/main.py
python scripts/main.py --help
Example run plan:
1. Confirm the user input, output path, and any required config values.
2. Edit the in-file `CONFIG` block or documented parameters if the script uses fixed settings.
3. Run `python scripts/main.py` with the validated inputs.
4. Review the generated output and return the final artifact with any assumptions called out.
Implementation Details
See `## Workflow` above for related details.
Quick Check
Use this command to verify that the packaged script entry point can be parsed before deeper execution.
python -m py_compile scripts/main.py
Audit-Ready Commands
Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.
python -m py_compile scripts/main.py
python scripts/main.py --help
Workflow
1. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
2. Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
3. Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
4. Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
5. If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.
Usage
python scripts/main.py --journal "Nature Medicine"
python scripts/main.py --journal-list journals.txt
Parameters
| Parameter | Type | Default | Required | Description |
|-----------|------|---------|----------|-------------|
| `--journal` | string | - | No | Journal name (single journal) |
| `--journal-list` | string | - | No | Path to file with journal names |
| `--years` | int | 5 | No | Number of years to analyze |
| `--output` | string | table | No | Output format (table, plot) |
Output
Risk Assessment
| Risk Indicator | Assessment | Level |
|----------------|------------|-------|
| Code Execution | Python/R scripts executed locally | Medium |
| Network Access | No external API calls | Low |
| File System Access | Read input files, write output files | Medium |
| Instruction Tampering | Standard prompt guidelines | Low |
| Data Exposure | Output files saved to workspace | Low |
Security Checklist
Prerequisites
No additional Python packages required.
Evaluation Criteria
Success Metrics
Test Cases
1. **Basic Functionality**: Standard input → Expected output
2. **Edge Case**: Invalid input → Graceful error handling
3. **Performance**: Large dataset → Acceptable processing time
Lifecycle Status
- Performance optimization
- Additional feature support
Output Requirements
Every final response should make these items explicit when they are relevant:
Error Handling
Input Validation
This skill accepts requests that match the documented purpose of `journal-impact-factor-trend` and include enough context to complete the workflow safely.
Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:
> `journal-impact-factor-trend` only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.
References
Response Template
Use the following fixed structure for non-trivial requests:
1. Objective
2. Inputs Received
3. Assumptions
4. Workflow
5. Deliverable
6. Risks and Limits
7. Next Checks
If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...