paper-learning
starsforks
How to install paper-learning?
rlaope/oh-my-hermes/paper-learning
$npx -y skills add rlaope/oh-my-hermes --skill paper-learning[omh] Hermes Paper Learning workflow: explain a supplied paper or paper/PDF at a selected level while preserving full section coverage and source evidence boundaries.
SKILL.md
| 1 | # Paper Learning |
| 2 | |
| 3 | This is a Hermes-native `paper-learning` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `paper-learning` exists so Hermes can act like a strong human tutor for papers: choose the right explanation level, walk through the full paper section by section, and keep PDF extraction and validation evidence honest. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request asks to export, convert, render, or package a file; use `materials-package`. |
| 12 | - The request asks for daily/weekly paper monitoring, digest, source inbox, or Scout/Analyst/Briefer operations; use `research-department`. |
| 13 | - The request asks to find current papers or sources when no supplied paper exists; use `web-research`. |
| 14 | - The request asks for a visual/image card; use `img-summary`. |
| 15 | - The request asks to implement or reproduce the paper's code; prepare a coding handoff only after a paper learning or reproduction plan is accepted. |
| 16 | |
| 17 | ## Examples |
| 18 | |
| 19 | Good example: |
| 20 | |
| 21 | - Prompt: paper-learning 이 논문 PDF를 아주 쉽게 설명해줘. 내용은 줄이지 말고 섹션별로. |
| 22 | - Expected behavior: Prepare paper_learning_card/v1, ask or record level=very_easy, mark PDF extraction/source_state evidence, then explain section-by-section with a coverage ledger. |
| 23 | - Why: The user supplied a paper/PDF explanation intent with an explicit level and coverage-preserving constraint. |
| 24 | |
| 25 | Bad example: |
| 26 | |
| 27 | - Prompt: paper-learning 이 PDF를 PPT로 변환해서 공유용 파일 만들어줘. |
| 28 | - Expected behavior: Route to `materials-package` because the user wants file conversion/export, not conceptual paper explanation. |
| 29 | - Why: PDF file output and render QA are material packaging work, not paper learning evidence. |
| 30 | |
| 31 | ## Completion Checklist |
| 32 | |
| 33 | - The selected explanation level is one of: very_easy, moderate, expert, choose. |
| 34 | - The source_state is recorded and scoped to observed text or extraction evidence. |
| 35 | - The coverage ledger lists observed, missing, or prepared sections before claiming completion. |
| 36 | - The explanation is section-aware and does not compress away claims, equations, figures, limitations, or reproducibility notes. |
| 37 | - Not-observed boundaries remain visible: full_pdf_extraction, figure_ocr, external_citation_check, math_proof_validation, code_or_benchmark_reproduction, peer_review_or_claim_correctness. |
| 38 | |
| 39 | ## Recovery Notes |
| 40 | |
| 41 | - If no paper text is observed, prepare the learning card from metadata only and ask for an attachment, excerpt, or extraction evidence. |
| 42 | - If only an abstract or excerpt is supplied, label the result as excerpt explanation and list missing sections. |
| 43 | - If context is too long, continue section-by-section and keep covered / next / missing state in the ledger. |
| 44 | - If the user asks for validation, citation checking, math proof review, or reproduction, create a separate observed-evidence or coding handoff path. |
| 45 | |
| 46 | ## OMH Context Rail |
| 47 | |
| 48 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 49 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 50 | - Current lane: **Research and company ops** (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings. |
| 51 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 52 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 53 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 54 | - Coverage: Every generated workflow skill carries this rail. |
| 55 | - Normal users talk to Hermes; OMH CLI is infra. |
| 56 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 57 | |
| 58 | ## Use When |
| 59 | |
| 60 | Use when Hermes should explain a supplied paper, arXiv entry, paper PDF, pasted excerpt, or extracted paper text at a selected level while keeping a coverage ledger instead of shrinking the paper into a lossy summary. |
| 61 | |
| 62 | Strong routing signals: `paper-learning`, `paper learning`, `paper-explainer`, `paper explainer`, `paper explanation`, `explain this paper`, `explain this arxiv paper`, `paper walkthrough`, `research paper explanation`, `arxiv paper explain`, `pdf paper explain`, `paper pdf explanati |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
