AI 코딩 에이전트에 대한 높은 수준의 연구 방법론 기술.

다른 도구 목록이 없습니다. research 워크플로우를 인코딩하는 각 기술 — 달이 개발하는 도메인 전문 지식의 종류. Skills are written for AI Agent to read and follow; 이 README is written for humans to configuration and choose.

한국어 (Korean)

빠른 시작

AI 에이전트

사용자가 이 재포 링크를 보낼 경우, 이 온보딩 흐름을 따르십시오. ** 포스트 설치 구성 단계를 건너 뛰지 마십시오 ** - 많은 기술은 API 키없이 비 기능이며, 조용히 설치된 기술은 제거되지 않는 것보다 더 나아집니다.

Step 1 - 기술 도입

이 README를 읽고, 각 기술의 이름을 제시하고 사용자에 대한 한 줄 설명. 카테고리별로 그룹(Tool-integrated vs vs methodology-only) 그래서 사용자가 구성을 필요로 하는 것을 이해합니다.

Step 2 — 설치해야 하는 것을 확인합니다

질문 : * “어떤 기술은 설치하시겠습니까? (모든 / 특정 하나를 선택)”*

단계 3 - 설치

선택한 기술 폴더를 플랫폼에 적합한 위치로 복사하십시오.

• **OpenClaw **: ~/.openclaw/skills/
• Claude Code: ~/.claude/skills/ (사용자 레벨) 또는 .claude/skills/ (프로젝트 레벨)

🔬 Scientific Research Skills

High-level research methodology skills for AI coding agents.

Not another tool list. Each skill encodes a research workflow — the kind of domain expertise that takes months to develop. Skills are written for AI agents to read and follow; this README is written for humans to configure and choose.

中文版本 (Chinese)

Quick Start

For AI Agents

If a user sends you this repo link, follow this onboarding flow. Do not skip the post-install configuration step — many skills are non-functional without API keys, and silently installed skills are worse than uninstalled ones.

Step 1 — Introduce the skills

Read this README, then present each skill’s name and one-line description to the user. Group them by category (🔧 tool-integrated vs 📋 methodology-only) so the user understands which ones will require configuration.

Step 2 — Confirm what to install

Ask: “Which skills would you like to install? (all / select specific ones)”

Step 3 — Install

Copy the selected skill folders to the appropriate location for your platform:

• OpenClaw: ~/.openclaw/skills/
• Claude Code: ~/.claude/skills/ (user-level) or .claude/skills/ (project-level)
• Codex: ~/.agents/skills/ (user-level) or .agents/skills/ (project-level)

Step 4 — ⚠️ Post-install configuration (do not skip)

After installation, explicitly notify the user which installed skills require configuration before they will work. Use this template:

✅ Installed: skill-a, skill-b, skill-c

⚠️ Heads up — the following skills need configuration before use:

• skill-a requires: TAVILY_API_KEY (free tier available)
• skill-c requires: Zotero API key + User ID

Want me to walk you through setting these up now? I can do them one by one.

Then, for each skill the user agrees to configure, walk them through it interactively:

1. Check existing config first — Run echo $TAVILY_API_KEY (or equivalent) to see if it’s already set. If yes, skip to verification.
2. Explain what the key is for — One sentence on what the skill will use it for.
3. Provide the signup link — Give the direct URL (see Dependencies below). Wait for the user to obtain the key.
4. Help them set it persistently — Append the export line to their shell profile (~/.zshrc for zsh, ~/.bashrc for bash). Don’t just export in the current shell — that won’t survive a restart.
5. Verify — Run a quick test (e.g., a 1-result search) to confirm the key works. If it fails, debug before moving on.
6. Move to the next skill — Repeat until all configurable skills are set up.

Per-skill configuration cheat sheet: