Menu
Paper lineage and related work tracing workflow. Use for citation trail, prior work, follow-up research, 논문 계보, 관련 연구.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run iterative agent evaluation and improvement loops (judge, improve, scenarios, playbooks) via pi-autocontext or autoctx CLI. Use when improving repeatable agent workflows (review rubrics, skill quality, scenario-based feedback), checking run status, or accumulating knowledge—not for one-off code edits or repo pattern drift (use continuity) or single PR review (use zereight-review).
Pi-native evaluate→improve→persist harness. Provides a systematic loop for generating candidates, judging them against rubrics, and accumulating knowledge as playbooks. Use for iterative output improvement, not for one-off edits (use continuity) or single PR review (use zereight-review).
Audit agent skills — token cost, duplicates, outdated plugin versions, unused skills, and overly long descriptions. Use when trimming skill prompt budget, finding duplicate or unused skills, auditing plugin versions, or deciding which skills to remove.
Diagnose why a skill is missing from Pi /skill or Cursor lists. Use when a skill exists on disk but does not appear, Pi shows only project or extension skills, or after adding a repo skill under .agents/skills/.
Comprehensive code review skill for practical PR feedback. Use for feature, bugfix, and refactor reviews. Prioritizes correctness, edge cases, logic invariants, fallback-chain safety, async state transitions, architecture analysis, OWASP security, and clear actionable feedback.
Skill map and inventory workflow. Use for scanning installed skills, skill overview, 스킬 목록, skill map.
| name | ljg-paper-river |
| description | Paper lineage and related work tracing workflow. Use for citation trail, prior work, follow-up research, 논문 계보, 관련 연구. |
| user_invocable | true |
| version | 1.0.0 |
논문 하나를 기준으로 앞뒤 연구 흐름을 잡는다. 단순 관련 논문 목록이 아니라 문제가 어떻게 이어졌는지 설명한다.
확인한 자료와 추정한 연결을 구분해서 쓴다.
