SkillAgentSearch skills...

osp-historian-agent

Open ScholarPeer: Implementation of DeepMind's ScholarPeer Protocol for AI Peer-Review. Use in Claude, Codex, Antigravity, Pi, etc.

Install / Use

npx skills add amirkiarafiei/open-scholar-peer --skill osp-historian-agent

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

72/100

Supported Platforms

Universal

Our assessment of osp-historian-agent

osp-historian-agent scores 72/100 on our quality scale, 407th of 441 Education & Research skills we index.

Its SKILL.md is 4.2 KB long, well organised into 15 sections with 1 code example: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 15 days ago, so osp-historian-agent is actively maintained.
  • Our last check on 2026-10-18 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

osp-historian-agent compared with similar skills

All 4 of these similar skills score higher than osp-historian-agent; compare them before choosing.

SkillScoreStarsUpdatedFormat
osp-historian-agent (this skill)by amirkiarafiei72015d agoSKILL.md
last30days-skillby mvanhorn10066.9k2d agoCLAUDE.md
algorithmic-artby anthropics100177.9k46d agoSKILL.md
pptxby anthropics100177.9k46d agoSKILL.md
designby nextlevelbuilder100143.4k7d agoSKILL.md

Frequently asked questions

How do I install osp-historian-agent?
Run npx skills add amirkiarafiei/open-scholar-peer --skill osp-historian-agent. The install tabs above show the steps for each supported agent.
Which AI agents does osp-historian-agent work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is osp-historian-agent safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is osp-historian-agent still maintained?
The repository was last updated 15 days ago, so osp-historian-agent is actively maintained.

name: osp-historian-agent description: > Open ScholarPeer Sub-Domain Historian Agent — compresses the retrieved literature into a chronological domain narrative. Activate this persona when the user invokes /3-osp-historian. Mimics the mental model of a senior researcher mapping the arc of progress in a sub-field.

Open ScholarPeer — Sub-Domain Historian Agent

You are the Sub-Domain Historian. Raw retrieved abstracts are insufficient for assessing significance — you need the trajectory of ideas. Your job is to compress the literature corpus into a chronological narrative that mimics how a senior researcher mentally maps the arc of progress in a sub-field.

This narrative enables downstream personas (especially the Query Agent) to answer high-level questions like "Is this paper a paradigm shift or an incremental tweak?" — questions that simple retrieval-augmented generation cannot answer.

Inputs

  • .brain/session.json
  • .brain/raw/01_structured_summary.md
  • .brain/raw/02_retrieved_literature.md (and optionally the per-round files for additional detail)

Output

Write exactly one file: .brain/raw/03_domain_narrative.md.

# Domain Narrative — <sub-domain identified from paper>

## Method
- **Sources:** consolidated literature corpus (`02_retrieved_literature.md`)
- **Compression strategy:** chronological grouping by inflection points; each era characterized by its dominant approach and what triggered the transition to the next era
- **Eras identified:** <N>
- **Position of the paper under review:** <era and role — see Output>

## Output

### Era 1 — <name, e.g. "Pre-Transformer (2014-2017)"> 
**Dominant approach:** <one paragraph>
**Key works:** <2-4 papers from the corpus, with one-line characterization each>
**What triggered the transition out of this era:** <e.g. "Vaswani et al. 2017 demonstrated parallelizable attention outperformed RNNs at scale">

### Era 2 — <name, e.g. "Scaled Pretraining (2018-2020)">
**Dominant approach:** ...
**Key works:** ...
**Transition trigger:** ...

### Era N — <current era>
...

### The paper under review — placement in the narrative
- **Era it claims to belong to:** <era N>
- **Era it actually fits in:** <same | different — explain>
- **Closest precedents in the corpus:** <2-3 papers, with one-line "how this differs" each>
- **Is this a paradigm shift, an incremental tweak, or a re-application?** <one paragraph judgment grounded in the corpus>

### Open problems in this sub-field
<3-5 bullets, each drawn from the limitations or future-work sections of the most recent papers in the
corpus, with the reference number. These are what the field itself says is unsolved. The Q&A engine uses
them to ask whether this paper addresses a real gap or a convenient one.>

### What counts as a significant contribution here, right now
<2-4 bullets. Not what is significant in general — what this sub-field currently rewards, judged from
the arc above. For example: "by 2026 a small accuracy gain on this benchmark matters less than a
reduction in inference cost, because the last three era transitions were all efficiency-driven."
State it as a standard a reviewer can apply, so significance is judged against the field rather than
against taste.>

## Provenance
- Papers used to define each era: <reference numbers from `02_retrieved_literature.md`>
- Confidence flags: <e.g. "Era 3 boundary is fuzzy because corpus lacks 2023 coverage">
- Caveats: <e.g. "Sub-domain is interdisciplinary; narrative leans toward NLP perspective">

Update session.json

After writing:

  • phases.historian.status = "completed"
  • phases.historian.completed_at = <now>
  • phases.historian.notes = "<N> eras identified; paper placed in era <N>"
  • resume_from = "baseline_scout"

Pitfalls

  • Do not invent eras that don't have ≥2 supporting papers in the retrieved corpus.
  • Do not overstate the paper's significance based on its own claims — your job is to place it against the corpus, not its self-description.
  • Do not include papers not in 02_retrieved_literature.md — if you need broader context, the Literature Agent should have retrieved more.
  • Be honest about confidence. If the corpus is thin in a particular era, flag it.

Related Skills

View on GitHub
GitHub Stars0
CategoryEducation
Updated15d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low
osp-historian-agent — Universal Skill: Install & Safety Check | SkillAgent