메뉴
GPT expert delegation via Codex MCP. Use when user says "ask GPT", "consult GPT", "GPT review", or explicitly requests delegation to an external expert for architecture, plan review, scope analysis, code review, or security analysis.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Design, implement, and analyze conjoint experiments for studying multidimensional preferences and choices using causal inference methods (AMCE, ACIE)
Comprehensive econometrics reference covering OLS, IV, MLE, GMM, panel data, limited dependent variables, treatment evaluation, and advanced topics. Use when advising on empirical methodology, interpreting regression output, explaining identification strategies, or selecting appropriate estimators.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Semantic search over Zotero library (~441 economics/social science papers). Use when user needs to find papers, passages, or evidence on a topic.
Use when scraping Indian government portals, property tax systems, land records, ArcGIS services, ASP.NET WebForms sites, or any large-scale web data collection. Covers requests, Playwright, aiohttp, CAPTCHA solving, proxy rotation, resumable pipelines, and anti-detection. Triggers on: scrape, crawl, download portal data, extract records, bulk download, government website, CAPTCHA, ViewState, ArcGIS REST.
| name | delegator |
| description | GPT expert delegation via Codex MCP. Use when user says "ask GPT", "consult GPT", "GPT review", or explicitly requests delegation to an external expert for architecture, plan review, scope analysis, code review, or security analysis. |
Delegate to GPT experts via mcp__codex__codex. Each call is stateless (include full context every time). Always use config: { "model_reasoning_effort": "xhigh" }.
| Expert | Prompt File | Triggers |
|---|---|---|
| Architect | ${CLAUDE_PLUGIN_ROOT}/prompts/architect.md | Architecture/design decisions, tradeoffs, "should I use A or B", after 2+ failed fixes |
| Plan Reviewer | ${CLAUDE_PLUGIN_ROOT}/prompts/plan-reviewer.md | "review this plan", "validate approach", before significant work |
| Scope Analyst | ${CLAUDE_PLUGIN_ROOT}/prompts/scope-analyst.md | Vague requirements, "what am I missing", "clarify scope" |
| Code Reviewer | ${CLAUDE_PLUGIN_ROOT}/prompts/code-reviewer.md | "review this code", "find issues", after implementing features |
| Security Analyst | ${CLAUDE_PLUGIN_ROOT}/prompts/security-analyst.md | "is this secure", "vulnerabilities in", auth/data changes, "threat model" |
Explicit requests ("ask GPT", "consult GPT", "GPT review") always trigger delegation. Route by context.
| Mode | Sandbox | Use When |
|---|---|---|
| Advisory | read-only | Analysis, reviews, recommendations |
| Implementation | workspace-write | Making changes, fixing issues |
Mode is determined by the task, not the expert.
${CLAUDE_PLUGIN_ROOT}/prompts/[expert].mdmcp__codex__codex with prompt, developer-instructions (expert prompt contents), config, sandbox, cwd1. TASK: [One sentence, atomic goal]
2. EXPECTED OUTCOME: [What success looks like]
3. CONTEXT: Current state, relevant code paths/snippets, background
4. CONSTRAINTS: Technical limits, patterns to follow, what cannot change
5. MUST DO: [Requirements]
6. MUST NOT DO: [Forbidden actions]
7. OUTPUT FORMAT: [Structure for response]
Each retry is a fresh call. Include: original task + what was tried + exact error + files modified. Escalate to user after 3 failures.