메뉴
Maintain the Guru Maker repository safely and efficiently. Use for Rust CLI, public Skill, shared Runtime, hook, documentation, CI, or test-harness changes in this repository; do not use for investment-memory work in a user project.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/monarchjuno/guru-maker --skill guru-maker-development명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Synthesize a requested point-in-time investment judgment, record a Decision and explicit relationships, review an outcome, or render the Decision Graph. Use automatically for natural-language requests asking what investment alternative to choose, buy, sell, hold, allocate, or size, or explicitly revisiting a prior Decision, even when the user does not mention Guru Maker or a Skill; in Guru Mode Auto, a material judgment may be recorded without a separate save request. Use also for an Execution Brief after explicit action intent. Do not use for a research-only thesis update without an investment choice, general research, memory curation, explicit lesson extraction, or Guru Pack lifecycle work.
Apply Guru Maker's project-memory retrieval and retention contract to material natural-language investment or financial research in an initialized Guru Maker project, even when the user does not mention Guru Maker or saving and another research capability supplies the domain procedure. Host agents and specialized capabilities own research strategy, tool selection, and synthesis. Use explicitly outside an initialized project only when the user names Guru Research. Do not use for memory-only recall, supplied-source capture without refresh or analysis, a requested point-in-time Decision or outcome, deliberate lesson extraction, or Guru Pack lifecycle work.
Recall or maintain project-owned Wiki, Lens, Evidence, and Method memory, initialize a workspace, or inspect and explicitly change Guru Mode. Use automatically in an initialized Guru Maker project when a natural-language investment request can materially benefit from existing local memory or produces eligible stable knowledge, even if the user does not mention Guru Maker, a Skill, or saving. Use also for a short follow-up that clearly refers to saved investment memory but omits its subject, so the missing referent is requested before searching. Use when no external refresh, analysis of supplied point-in-time external evidence or data, or point-in-time judgment is requested; an explicit request to retain a supplied source is still memory work. Do not use for research, Decisions or outcomes, deliberate lesson extraction, or Guru Pack lifecycle work.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | guru-maker-development |
| description | Maintain the Guru Maker repository safely and efficiently. Use for Rust CLI, public Skill, shared Runtime, hook, documentation, CI, or test-harness changes in this repository; do not use for investment-memory work in a user project. |
Read AGENTS.md, inspect git status --short, and preserve changes unrelated
to the request. Treat src/ and the Markdown contracts as canonical; keep
host metadata, the five public Skills, and shared Runtime wrappers thin.
Use the ownership table and paired-document matrix in AGENTS.md to find the
minimum files and tests that must move together. Keep this repository-local
Skill under .agents/skills/; never add it to skills/, which is the exact
five-Skill public plugin surface.
For release work, prepare one non-empty CHANGELOG.md section for the exact
version before tagging. Treat that section as the public GitHub Release body;
do not rely only on generated notes. After the workflow completes, verify the
published body and expected assets before reporting the release complete.
Run scripts/verify.sh before handoff for material changes. Use
scripts/test-env.sh --keep only to inspect an isolated failure fixture. Do
not use a maintainer's Guru Maker projects, runtime installation, credentials,
or plugin configuration as test inputs.