القائمة
Use when the user says a paper, review, report, or LaTeX deliverable is final and wants it archived under published/ or exposed through the static published-paper site.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to install, configure, diagnose, or troubleshoot ScholarAIO, including setup check, dependency status, API keys, and bilingual setup flow.
Use when the user explicitly asks for Nature Skills, nature-skills, Nature style, Nature-style, Nature Communications, Nature-family, CNS, high-impact journal, or Springer Nature workflows, including Nature figure work, polishing, writing, reviewer critique, high-impact journal major revision response, Nature/CNS citations, Nature data-sharing workflows, paper readers, reviewer response, paper-to-PPT, submission checklist, or Nature-specific academic-search workflows.
Use when the user wants to rebuild or refresh ScholarAIO keyword, full-text, FTS5, FAISS, or semantic search indexes after data or metadata changes.
Use when the user wants to find academic papers, search the local library, run keyword or semantic search, search by author, explore topics, or federate across library, explore databases, and arXiv.
Use when the user wants to import papers from Endnote XML/RIS, Zotero Web API or local SQLite, attach PDFs, match PDFs to records, or supplement records with PDF content.
Use when the user wants to process new papers, patents, theses, documents, or proceedings from inbox queues into the knowledge base, run the ingest pipeline, or rebuild indexes.
| name | publish |
| description | Use when the user says a paper, review, report, or LaTeX deliverable is final and wants it archived under published/ or exposed through the static published-paper site. |
Use this skill only after the user clearly says the deliverable is final, audited, or ready to publish. Drafts should stay under workspace/.
The publishing workflow has three separate layers:
scholaraio/: upstream code and the scholaraio publish-site generatorpublished/: local audited deliverable archive, git-ignored by this repositoryDo not put user deliverables in the repository root except under published/, and do not commit published/ to the ScholarAIO repo.
Before creating or changing a published archive:
workspace/; publishing is a copy/archive step.Use one folder per final deliverable:
published/<YYYY-MM-DD>-<short-title>/
├── metadata.json
├── main.pdf
├── main.tex
├── images/
└── misc/
Recommended metadata.json:
{
"title": "Full title",
"date": "YYYY-MM-DD",
"keywords": ["keyword"],
"subject": "field or topic",
"pdf_filename": "main.pdf",
"tex_files": ["main.tex"],
"images_dir": "images",
"misc_dir": "misc",
"authors": ["Author", "Claude (AI Assistant)"],
"note": "Final audited deliverable."
}
The site generator reads published/*/metadata.json, builds a source ZIP beside each archive, and writes a static site.
Explicit output directory:
scholaraio publish-site --out-dir ~/generated-report
Configured output directory:
publish:
site_output_dir: ~/generated-report
Then:
scholaraio publish-site
Default mode copies PDFs and source ZIPs into assets/papers/, producing a self-contained site suitable for a separate GitHub Pages repository.
Local preview mode uses symlinks instead of copying assets:
scholaraio publish-site --out-dir ~/generated-report --symlink
scholaraio publish-site so the static site reflects the new item.--out-dir or help the user set publish.site_output_dir.