메뉴
Use when work needs persistent multi-step execution, independent review, resumable project state, or long-running research and engineering coordination through Argus.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/lbx154/Argus --skill argus-run명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Plan and execute multi-step research, surveys, feasibility studies, and evidence-heavy analyses with adaptive planning, source verification, critic review, and cross-task learning. Use when a request needs multiple dependent investigations or a durable evidence trail; do not use for simple factual questions or small one-step edits.
Use when checking an Argus project's progress, pending questions, active role, diagnostics, selected artifacts, intervention state, recovery options, or graceful stop status.
Use when researching a biomedical target and disease relationship, mechanism, human evidence, clinical translation, safety, failed programs, competitive trials, or an auditable pharmaceutical decision dossier.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | argus-run |
| description | Use when work needs persistent multi-step execution, independent review, resumable project state, or long-running research and engineering coordination through Argus. |
Use the installed Argus MCP tools. Do not imitate the Argus roles in the host session and do not write Argus state files directly.
argus_project_list with the exact current work directory.argus_project_create with that directory and a concise name.argus_message with the user's complete objective. Manager owns chat
versus task routing, lifetime, workflow, domain, and execution handoff.argus-status Skill when status is requested.If the MCP server is unavailable, run argus --doctor and report the exact
installation or backend failure. Do not silently replace Argus with an ad hoc
single-agent workflow.
Never claim completion from dispatch, daemon activity, loss, or intermediate artifacts. Argus completion comes from its persisted Reviewer/Manager state.