MCP HubMCP Hub
스킬 목록으로 돌아가기

learn

pjt222
업데이트됨 2 days ago
8 조회
17
2
17
GitHub에서 보기
메타aidesign

정보

`learn` 스킬은 Claude가 조사와 피드백 루프를 통해 구조화된 멘탈 모델을 구축함으로써 익숙하지 않은 분야의 지식을 체계적으로 습득할 수 있게 합니다. 이 스킬은 새로운 코드베이스 탐색, 상충되는 정보 해결, 복잡한 주제를 가르칠 준비와 같이 깊은 이해가 필요한 상황을 위해 설계되었습니다. 이 스킬은 향후 검색을 위해 지식을 통합하기 위해 개요 수립, 가설 설정, 탐색, 검증의 체계적인 프로세스를 활용합니다.

빠른 설치

Claude Code

추천
기본
npx skills add pjt222/agent-almanac -a claude-code
플러그인 명령대체
/plugin add https://github.com/pjt222/agent-almanac
Git 클론대체
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/learn

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Learn

Conduct a structured knowledge acquisition session — surveying unfamiliar territory, building initial models, testing them through deliberate exploration, integrating findings into coherent understanding, and consolidating for durable retrieval.

适用场景

  • Encountering an unfamiliar codebase, framework, or domain with no prior context
  • A user asks about a topic outside current working knowledge and the answer requires genuine investigation, not recall
  • Multiple conflicting sources or patterns exist and a coherent mental model needs to be built from scratch
  • After remote-viewing surfaces intuitive leads that need systematic validation
  • Preparing to teach a topic — the AI must first understand it deeply enough to explain it

输入

  • 必需: Learning target — a topic, codebase area, API, domain concept, or technology to understand
  • 可选: Scope boundary — how deep to go (surface survey vs. deep expertise)
  • 可选: User's purpose — why this knowledge matters (guides which aspects to prioritize)
  • 可选: Known starting points — files, docs, or concepts already familiar

步骤

第 1 步:Survey — Map the Territory

Before attempting to understand anything, map the landscape to identify what exists.

Learning Modality Selection:
┌──────────────────┬──────────────────────────┬──────────────────────────┐
│ Territory Type   │ Primary Modality         │ Tool Pattern             │
├──────────────────┼──────────────────────────┼──────────────────────────┤
│ Codebase         │ Structural mapping —     │ Glob for file tree,      │
│                  │ find entry points, core  │ Grep for exports/imports,│
│                  │ modules, boundaries      │ Read for key files       │
├──────────────────┼──────────────────────────┼──────────────────────────┤
│ API / Library    │ Interface mapping —      │ WebFetch for docs,       │
│                  │ find public surface,     │ Read for examples,       │
│                  │ types, configuration     │ Grep for usage patterns  │
├──────────────────┼──────────────────────────┼──────────────────────────┤
│ Domain concept   │ Ontology mapping —       │ WebSearch for overviews,  │
│                  │ find core terms,         │ WebFetch for definitions,│
│                  │ relationships, debates   │ Read for local notes     │
├──────────────────┼──────────────────────────┼──────────────────────────┤
│ User's context   │ Conversational mapping   │ Read conversation,       │
│                  │ — find stated goals,     │ Read MEMORY.md,          │
│                  │ preferences, constraints │ Read CLAUDE.md           │
└──────────────────┴──────────────────────────┴──────────────────────────┘
  1. Identify the territory type and select the primary modality
  2. Perform a broad scan — not reading deeply, but identifying landmarks (key files, entry points, core concepts)
  3. Note the boundaries: what is in scope, what is adjacent, what is out of scope
  4. Identify gaps: areas that look important but are opaque from the surface
  5. Create a rough map: list the major components and their apparent relationships

预期结果: A skeletal map of the territory with 5-15 landmarks identified. A sense of which areas are clear from the surface and which require deeper investigation. No understanding yet — just a map.

失败处理: If the territory is too large to survey, narrow scope immediately. Ask: "What is the minimum I need to understand to serve the user's purpose?" If the territory has no clear entry point, start from the output (what does this system produce?) and trace backward.

第 2 步:Hypothesize — Build Initial Models

From the survey, construct initial hypotheses about how the system works.

  1. Formulate 2-3 hypotheses about the territory's structure or behavior
  2. State each hypothesis clearly: "I believe X because I observed Y"
  3. For each hypothesis, identify what evidence would confirm it and what would refute it
  4. Rank hypotheses by confidence: which feels most supported, which is shakiest
  5. Identify the highest-value hypothesis to test first (the one that, if confirmed, would unlock the most understanding)

预期结果: Concrete, falsifiable hypotheses — not vague impressions. Each has a test that would confirm or refute it. The hypotheses collectively cover the most important aspects of the territory.

失败处理: If no hypotheses form, the survey was too shallow — return to Step 1 and read 2-3 landmarks in depth. If all hypotheses feel equally uncertain, start with the simplest one (Occam's razor) and build from there.

第 3 步:Explore — Probe and Test

Systematically test each hypothesis through targeted investigation.

  1. Select the highest-priority hypothesis
  2. Design a minimal probe: what is the smallest investigation that would confirm or refute it?
  3. Execute the probe (read a file, search for a pattern, test an assumption)
  4. Record the result: confirmed, refuted, or modified
  5. If refuted, update the hypothesis based on the new evidence
  6. If confirmed, probe deeper: does the hypothesis hold at the edges, or only in the center?
  7. Move to the next hypothesis and repeat

预期结果: At least one hypothesis tested to conclusion. The mental model is beginning to take shape — some parts confirmed, some revised. Surprises are noted as particularly valuable data.

失败处理: If probes consistently produce ambiguous results, the hypotheses may be testing the wrong things. Step back and ask: "What would someone who understands this system consider the most important fact?" Probe for that instead.

第 4 步:Integrate — Build Mental Model

Synthesize findings into a coherent model that connects the pieces.

  1. Review all confirmed hypotheses and revised models
  2. Identify the central organizing principle: what is the "spine" that everything connects to?
  3. Map relationships: which components depend on which? What flows where?
  4. Identify the surprising findings — these often contain the deepest insight
  5. Look for patterns that repeat across different parts of the territory
  6. Build a mental model that can predict behavior: "Given input X, I expect Y because Z"

预期结果: A coherent mental model that explains the territory's structure and predicts its behavior. The model should be expressible in 3-5 sentences and should make specific claims, not vague generalizations.

失败处理: If the pieces do not integrate into a coherent model, there may be a fundamental misunderstanding in one of the earlier hypotheses. Identify the piece that does not fit and re-test it. Alternatively, the territory may genuinely be incoherent (poorly designed systems exist) — note this as a finding rather than forcing coherence.

第 5 步:Verify — Challenge Understanding

Test the mental model by making predictions and checking them.

  1. Use the model to make 3 specific predictions about the territory
  2. Test each prediction through investigation (not by assuming it is true)
  3. For each confirmed prediction, confidence increases
  4. For each refuted prediction, identify where the model is wrong and correct it
  5. Identify edge cases: does the model hold at the boundaries, or does it break down?
  6. Ask: "What would surprise me?" — then check if that surprise is possible

预期结果: The mental model survives at least 2 of 3 prediction tests. Where it breaks, the failure is understood and the model is corrected. The model now has both confirmed strengths and known limitations.

失败处理: If most predictions fail, the mental model has a fundamental flaw. This is actually valuable information — it means the territory works differently than expected. Return to Step 2 with the new evidence and rebuild the hypotheses from scratch. The second attempt will be much faster because the wrong models have been eliminated.

第 6 步:Consolidate — Store for Retrieval

Capture the learning in a form that supports future retrieval and application.

  1. Summarize the mental model in 3-5 sentences
  2. Note the key landmarks — the 3-5 most important things to remember
  3. Record any counterintuitive findings that might be forgotten
  4. Identify related topics that this learning connects to
  5. If the learning is durable (will be needed across sessions), update MEMORY.md
  6. If the learning is session-specific, note it as context for the current conversation
  7. State what remains unknown — honest gaps are more useful than false confidence

预期结果: A concise, retrievable summary that captures the essential understanding. Future references to this topic can start from this summary rather than re-learning from scratch.

失败处理: If the learning resists summarization, it may not yet be fully integrated — return to Step 4. If the learning seems too obvious to be worth storing, consider that what feels obvious now may not feel obvious in a fresh context. Store the non-obvious parts.

验证清单

  • A survey was conducted before any deep investigation (map before dive)
  • Hypotheses were explicitly stated and tested, not assumed
  • At least one hypothesis was revised based on evidence (indicates genuine learning)
  • The mental model makes specific, testable predictions about the territory
  • Known unknowns are identified alongside known knowns
  • The consolidated summary is concise enough to be useful for future retrieval

常见问题

  • Skipping the survey: Diving into detail before understanding the landscape wastes time on unimportant areas and misses the big picture
  • Unfalsifiable hypotheses: "This is probably complex" cannot be tested. "This module handles authentication because it imports crypto" can be
  • Confirmation bias during exploration: Seeking only evidence that supports the initial hypothesis while ignoring contradictions
  • Premature consolidation: Storing a model before it has been tested leads to confidently wrong future predictions
  • Perfectionism: Attempting to learn everything before applying any knowledge. Learning is iterative — use partial understanding, then refine
  • Learning without purpose: Acquiring knowledge with no application in mind produces unfocused, shallow understanding

相关技能

  • learn-guidance — the human-guidance variant for coaching a person through structured learning
  • teach — knowledge transfer calibrated to a learner; builds on the model constructed here
  • remote-viewing — intuitive exploration that surfaces leads for systematic learning to validate
  • meditate — clearing prior context noise before entering a new learning territory
  • observe — sustained neutral pattern recognition that feeds learning with raw data

GitHub 저장소

pjt222/agent-almanac
경로: i18n/zh-CN/skills/learn
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

content-collections

메타

이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.

스킬 보기

polymarket

메타

이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.

스킬 보기

creating-opencode-plugins

메타

이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.

스킬 보기

sglang

메타

SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.

스킬 보기