Menu
Investment analysis workflow. Use for startup, token, stock, product, market, 투자 분석, 사업성 검토, 프로젝트 분석.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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-invest |
| description | Investment analysis workflow. Use for startup, token, stock, product, market, 투자 분석, 사업성 검토, 프로젝트 분석. |
| user_invocable | true |
| version | 1.0.0 |
프로젝트가 실제로 가치를 만들 수 있는 구조인지 본다. 가격 예측보다 구조 분석이 우선이다.
결론, 사업 구조, 강점, 리스크, 추가로 확인할 자료를 나눠 쓴다. 금융 조언처럼 단정하지 않고 자료의 한계를 밝힌다.
