mhistory

Generates a chronological research development-history article from database retrieval and web search.

75|7|Updated May 2, 2026
One-click install
npx skills add https://github.com/zjunlp/Mechanist --skill mhistory-zjunlp
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: mhistory
Source: https://github.com/zjunlp/Mechanist/tree/main/skills/mhistory
Command: npx skills add https://github.com/zjunlp/Mechanist --skill mhistory-zjunlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a rigorous, citation-backed history of a research field requires hours of literature searching across eras, and generic search often misses either foundational classics or the latest arXiv frontier work. ## Core Features & Use Cases - Two-track parallel retrieval: Runs the mechanic-db SEARCH service twice in parallel β€” one pass with temporal_mode=history for the long arc and one with temporal_mode=recent for the modern frontier. - Web supplementation: Uses WebSearch to fill gaps for pre-database classics and arXiv papers from the last 1–6 months that the database has not yet indexed. - Graceful degradation: If the database service is unavailable, the article is still produced from WebSearch and model knowledge, with an explicit availability note. - Use Case: Ask for a development history of mechanistic interpretability and receive a 2500–4500 word markdown article organized by eras, with verified citations, a frontier section, and a Tensions and Open Questions section saved to development_history.md. ## Quick Start Ask the agent to trace the development history of your research topic, for example by invoking /mhistory followed by the topic name.

Frequently Asked Questions about mhistory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a research development history for a topic?β–Ό

Invoke /mhistory followed by your topic in English or Chinese. The skill runs two parallel database retrieval passes plus WebSearch, then writes a 2500–4500 word markdown article to development_history.md.

How does the skill find both classic and recent papers?β–Ό

It queries the mechanic-db SEARCH service twice in parallel: once with temporal_mode=history for even coverage across eras, and once with temporal_mode=recent for recency-boosted frontier work. WebSearch fills gaps for pre-database classics and the last 1–6 months of arXiv papers.

What happens if the mechanic-db search service is unavailable?β–Ό

Both database passes degrade gracefully by writing a skipped flag to their output files. The article is then built from WebSearch results and the model's own knowledge, and the final markdown explicitly notes that mechanic-db was unavailable.

What is the structure of the generated history article?β–Ό

The markdown article is organized by chronological eras or thematic phases, includes a TL;DR, a contemporary landscape section, a frontier section tagged by source, a Tensions and Open Questions section, and a references list with DOI or arXiv URLs.

Can I use this skill for topics outside machine learning?β–Ό

Yes, the topic input is free text in Chinese or English and the pipeline is domain-agnostic. However, retrieval quality depends on the coverage of the mechanic-db corpus, which is oriented toward research literature.