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

read-garden

pjt222
업데이트됨 6 days ago
14 조회
17
2
17
GitHub에서 보기
기타general

정보

이 스킬은 좌표 원격관찰 기법을 응용하여 정원 건강 상태를 관찰하고 평가하는 구조화된 프로토콜을 제공합니다. 식물 스트레스를 진단하기 위해 감각적 인상, 세부적인 층위 분석, 패턴 인식 단계를 사용자에게 안내합니다. 정원 관리 결정을 내리기 전, 정기적 모니터링 중, 혹은 극한 기상 현상 이후에 활용하십시오.

빠른 설치

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/read-garden

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

문서

讀園

入結構感察、後決動。

  • 動前——先讀後行
  • 草現受脅(黃、萎、卷、斑)
  • 季變(春醒、秋衰)需察
  • 新園地、植前估
  • 常(週、雙週)健察
  • 極端氣後(霜、熱浪、暴雨)

  • :能臨園
  • :園誌或筆記
  • :前察錄供較
  • :土溫計、pH 試紙、濕計
  • :手鏡(蟲、病識)

一:禪檢——入前清

入察前,清成見。

Pre-Garden Clearing (3-5 minutes):
1. Stand at the garden's edge — do not enter yet
2. Take three slow breaths (inhale 4 counts, exhale 6 counts)
3. Set aside what you expect to find:
   - "I think the tomatoes need water" → Set aside
   - "That pest spray probably didn't work" → Set aside
   - "The lettuce should be ready by now" → Set aside
4. Adopt the observer's stance: you are here to receive information,
   not confirm hypotheses
5. Let your eyes soften — peripheral vision, not focused scanning
6. When you feel neutral and receptive, enter the garden

Why this matters:
Gardeners who enter with a diagnosis in mind see confirmation
everywhere and miss what the garden is actually showing them.
Observation before interpretation is the foundation of good practice.

得:靜納、無成見。

敗:難釋期(強憂某株、近損之恚)→認情、書「AOL: [concern]」、續行。命名減其勢。

二:階一——統印

繞園周。記首、未濾印。

Gestalt Protocol:
1. Walk slowly around the entire garden boundary
2. Do NOT examine individual plants yet — take in the whole
3. Record your impression using only these categories:
   - Overall vigour: thriving / stable / declining
   - Dominant colour tone: deep green / pale / mixed / yellowing
   - Density: lush / adequate / sparse / bare patches
   - Energy: (subjective) vibrant / calm / tired / distressed
4. Note what draws your eye first — this is often the loudest signal
5. Record ambient conditions: temperature, wind, sky, soil moisture
   (visual), recent weather

Example Gestalt Record:
  Date: 2026-04-15, 9:30am, 14°C, overcast, light rain yesterday
  Overall: Stable, but northeast corner looks depleted
  Colour: Mixed — good green on brassicas, pale on tomato starts
  Density: Adequate except herb bed (sparse)
  Energy: Calm, not vibrant — spring is slow this year
  Eye drawn to: Wilting squash transplants (row 3)

得:簡、整錄、無析無診。

敗:立析(如「瓜萎因…」)→書「AOL: [diagnosis]」、回純察。析在階三。

三:階二——感層

逐床移。各區皆動五感。

Sensory Observation Protocol (per bed or zone):

LEAF LANGUAGE:
- Colour: Deep green, pale green, yellowing, purpling, browning
  - Yellowing (chlorosis): general = nitrogen, interveinal = iron/manganese
  - Purpling: phosphorus deficiency or cold stress
  - Browning: tip burn = salt/fertilizer, edge burn = potassium
- Curl direction:
  - Upward: heat stress, drought, herbicide exposure
  - Downward: overwatering, root damage
  - Inward (cupping): virus, mite damage
- Surface: Smooth, rough, sticky (aphid honeydew), powdery (mildew), spotted
- Underside: Check for eggs, mites (tiny dots), early mildew

STEM AND STRUCTURE:
- Strength: Upright and sturdy vs. leaning or lodged
- Colour: Normal woody/green vs. blackening (rot) or pale (etiolation)
- Flexibility: Supple (healthy) vs. brittle (dehydrated) vs. mushy (disease)
- Growth pattern: Normal internodes vs. elongated (light-seeking)

ROOT SIGNALS (check at soil line and during transplant):
- Colour: White/cream (healthy), brown/black (rot), orange (rust fungus)
- Smell: Earthy (healthy), sour/sulphurous (anaerobic rot)
- Structure: Fibrous network (good) vs. circling (pot-bound) vs. sparse (stress)

SOIL AT THE PLANT:
- Moisture: Dry and cracked / moist and dark / waterlogged and gleaming
- Surface: Mulched / bare / crusted / mossy / algae-covered
- Smell: Sweet and earthy (good) / sour (anaerobic) / musty (fungal)
- Inhabitants: Earthworms, beetles, spiders (good) / slugs, ants farming aphids (concerning)

Record each observation as a sensory descriptor — no analysis yet.
Wrong: "The tomatoes have early blight"
Right: "Tomato lower leaves: brown spots, concentric rings, yellowing around spots"

得:各床、各區詳感錄、唯描非析。

敗:察自診(命病、咎蟲)→書「AOL: [diagnosis]」、回原察。名後至——數據先行。

四:階三——識模

至此乃連察與模。

Pattern Analysis Protocol:
1. Review your Stage II notes for each bed
2. Ask these structured questions:

   SPATIAL:
   - Are symptoms localized (one plant, one bed) or systemic (whole garden)?
   - Is there a gradient? (Worse near a fence = shade; worse near path = compaction)
   - Are only certain species affected? (Host-specific = disease; all species = environmental)

   TEMPORAL:
   - Is this new growth or old growth?
     - New growth affected: nutrient deficiency (can't build new tissue)
     - Old growth affected: mobile nutrient being relocated, or infection spreading
   - Did symptoms appear suddenly (weather event, application) or gradually (chronic condition)?

   POPULATION:
   - One plant: likely individual issue (root damage, transplant shock)
   - One species: likely species-specific (disease, pest preference)
   - All plants: likely environmental (soil, water, weather)

3. Cross-reference with Five Indicators (leaf, stem, root, soil, phenology):
   - Do multiple indicators point to the same cause?
   - Convergent signals = higher confidence diagnosis
   - Contradictory signals = more observation needed

AOL Management:
If your mind jumps to a conclusion before the pattern analysis is complete:
- Write "AOL: [conclusion]" on a separate line
- Do NOT act on it yet
- Return to the data
- If the same conclusion re-emerges from multiple independent observations,
  it graduates from AOL to tentative diagnosis
- A tentative diagnosis is still not action — it's a hypothesis to test

Distinguish:
- Premature label (low evidence, high confidence) → dangerous
- Convergent conclusion (high evidence, proportional confidence) → actionable

得:一或諸試診,由眾獨察支持。

敗:無顯模→園或健(非皆問),或號太早。錄之,週後再察。時常明一訪未明。

五:癒檢——園健分流

化察為序動計。

Garden Health Triage Matrix:
┌──────────┬──────────────────────────┬─────────────────────────────┐
│ Priority │ Criteria                 │ Example Actions             │
├──────────┼──────────────────────────┼─────────────────────────────┤
│ TODAY    │ Actively dying, wilting  │ Deep water. Emergency shade.│
│ (Red)    │ severely, pest           │ Hand-remove pests. Support  │
│          │ infestation visible      │ lodged stems.               │
├──────────┼──────────────────────────┼─────────────────────────────┤
│ THIS     │ Declining but stable,    │ Feed (compost tea or foliar │
│ WEEK     │ nutrient deficiency      │ seaweed). Mulch bare soil.  │
│ (Amber)  │ symptoms, early disease  │ Improve drainage. Prune     │
│          │ signs                    │ affected foliage.           │
├──────────┼──────────────────────────┼─────────────────────────────┤
│ WATCH    │ Subtle changes, early    │ Record in journal. Reassess │
│ (Green)  │ signs that may resolve   │ in 1 week. Take photos for  │
│          │ naturally, seasonal      │ comparison. Do NOT          │
│          │ transitions              │ intervene yet.              │
├──────────┼──────────────────────────┼─────────────────────────────┤
│ HEALTHY  │ No issues observed,      │ Appreciate. Continue        │
│ (Blue)   │ vigorous growth, good    │ current care. Note what's   │
│          │ colour, active biology   │ working for future seasons. │
└──────────┴──────────────────────────┴─────────────────────────────┘

Triage Rules:
1. Address RED items immediately — everything else can wait
2. Address AMBER items this week — schedule specific days
3. GREEN items: observe only. Most "watch" items resolve themselves.
   The most common gardener error is treating green items as amber
4. BLUE items: actively note what's working — these are your successes
5. Never address more than 2 priorities per garden visit
   (doing too many things at once means doing nothing well)

得:分流動表,序與時皆明。

敗:皆覺紅→在憂模非察模。回禪檢(一)、再入。真急罕——多園問緩生、可待日。

六:錄追

以誌成察。

Garden Observation Record Template:
Date: ___________  Time: ___________
Weather: ___________  Recent weather: ___________

GESTALT: (1-2 sentences from Stage I)

BED-BY-BED OBSERVATIONS: (Stage II data)
  Bed 1: ___________
  Bed 2: ___________
  [...]

PATTERNS NOTED: (Stage III analysis)
  ___________

TRIAGE:
  RED (today): ___________
  AMBER (this week): ___________
  GREEN (watch): ___________
  BLUE (healthy): ___________

AOLs RECORDED: (list any premature conclusions that arose)
  ___________

ACTIONS TAKEN:
  ___________

COMPARE TO LAST VISIT:
  Improving: ___________
  Worsening: ___________
  Unchanged: ___________

得:完日察錄,可較前訪。

敗:書誌煩→減至最少:日、氣、流摘、各床一察。恆勝詳。

  • 入前禪檢已畢
  • 統印於察株前已錄
  • 感察用描語(階二無診)
  • AOL 已識且擱(未早動)
  • 模析顧空、時、群
  • 流陣已成、序明
  • 察錄日記入園誌
  • 動稱流級(綠不過治)

  1. 確認偏:入園尋特問→必見之(或似之)。禪檢防之
  2. 階二診:感察時命病→偏後採。守描至階三
  3. 綠當琥:多園「問」自解。一見即噴或剪→害過原症
  4. 略錄:無誌、每訪重起。模唯時生——時需錄
  5. AOL 抑非管:旨非無析想——無能。旨在察、命、擱,待數支或駁
  6. 過度動:讀園應增信、減動,非反。讀後動增→或治憂、非治園

  • meditate — 入前清法(全禪程)
  • heal — 檢用之健流模
  • prepare-soil — 土估與土察層相疊
  • cultivate-bonsai — 盆健察循同階法
  • plan-garden-calendar — 察錄導季中歷調
  • remote-viewing — CRV 階法源此技

GitHub 저장소

pjt222/agent-almanac
경로: i18n/wenyan-ultra/skills/read-garden
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

llamaguard

기타

LlamaGuard는 폭력 및 혐오 발언 등 6가지 안전 범주에서 LLM 입력과 출력을 조정하기 위한 Meta의 70-80억 파라미터 모델입니다. 94-95% 정확도를 제공하며 vLLM, Hugging Face 또는 Amazon SageMaker를 사용해 배포할 수 있습니다. 이 기술을 사용하여 AI 애플리케이션에 콘텐츠 필터링 및 안전 가드레일을 손쉽게 통합하세요.

스킬 보기

cost-optimization

기타

이 Claude Skill은 리소스 적정화, 태깅 전략, 지출 분석을 통해 개발자들이 클라우드 비용을 최적화할 수 있도록 지원합니다. AWS, Azure, GCP에서 클라우드 비용을 절감하고 비용 거버넌스를 구현하기 위한 프레임워크를 제공합니다. 인프라 비용을 분석하거나, 리소스를 적정화하거나, 예산 제약을 충족해야 할 때 사용하세요.

스킬 보기

quantizing-models-bitsandbytes

기타

이 스킬은 bitsandbytes를 사용하여 LLM을 8비트 또는 4비트 정밀도로 양자화하며, 최소한의 정확도 손실로 50-75%의 메모리 감소를 달성합니다. 제한된 GPU 메모리에서 더 큰 모델을 실행하거나 추론을 가속화하는 데 이상적이며, INT8, NF4, FP4와 같은 형식을 지원합니다. 이 스킬은 HuggingFace Transformers와 통합되어 QLoRA 학습 및 8비트 옵티마이저를 가능하게 합니다.

스킬 보기

dispatching-parallel-agents

기타

이 Claude Skill은 3개 이상의 독립적인 문제를 동시에 조사하고 해결하기 위해 다중 에이전트를 배치합니다. 공유 상태나 의존성 없이 해결 가능한 무관련 장애 시나리오에 맞게 설계되었습니다. 핵심 기능은 병렬 문제 해결로, 각 독립 문제 영역마다 하나의 에이전트를 할당하여 효율성을 극대화합니다.

스킬 보기