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

read-garden

pjt222
업데이트됨 Yesterday
3 조회
17
2
17
GitHub에서 보기
기타general

정보

`read-garden` 스킬은 정원 건강 상태를 프로그래밍 방식으로 평가하기 위한 구조화된 프로토콜을 제공하며, 식물과 토양을 체계적으로 관찰하기 위해 좌표 원격 투시(Coordinate Remote Viewing)의 단계를 적용합니다. 이 스킬은 식물 스트레스, 계절적 변화 또는 정기적인 모니터링에 의해 트리거되어 감각 데이터 수집, 패턴 인식 및 건강 상태 분류 매트릭스를 안내합니다. 이 도구는 데이터 기반의 정원 관리 결정을 내리기 위해, 어떠한 개입보다 먼저 사용하도록 설계되었습니다.

빠른 설치

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에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Read Garden

Observe and assess garden with structured sensory protocol before any intervention decision.

When Use

  • Before intervention — read garden first, act second
  • Plants show stress (yellow, wilt, curl, spots)
  • Seasonal transitions (spring wakeup, autumn decline) need check
  • New garden site eval before plant
  • Regular (weekly or biweekly) garden health monitoring
  • After extreme weather (frost, heat wave, heavy rain)

Inputs

  • Required: Physical access to garden
  • Required: Garden journal or notebook for record
  • Optional: Prior observation records for compare
  • Optional: Soil thermometer, pH strips, moisture meter
  • Optional: Hand lens or magnifier (pest/disease ID)

Steps

Step 1: Meditate Checkpoint — Pre-Entry Clearing

Before enter garden, clear preconceptions.

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.

Got: Calm, receptive state. No preconceptions about what you find.

If fail: Cannot release expectations (strong worry over specific plant, frustration from recent loss)? Acknowledge emotion, write as "AOL: [concern]", proceed. Naming reduces influence.

Step 2: Stage I — Gestalt Impression

Walk garden perimeter. Record first unfiltered impression.

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)

Got: Brief holistic record of garden state. No analysis or diagnosis.

If fail: Start diagnose right away (e.g., "the squash wilts because...")? Write "AOL: [diagnosis]". Return to pure observation. Analysis comes in Stage III.

Step 3: Stage II — Sensory Layer

Move through garden bed by bed. Engage all senses for each area.

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"

Got: Detailed sensory record per bed or zone. Descriptive language only.

If fail: Catch self diagnose (name disease, blame pest)? Write "AOL: [diagnosis]". Return to raw observation. Name comes later — data first.

Step 4: Stage III — Pattern Recognition

Now, and only now, start connect observations to patterns.

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

Got: One or more tentative diagnoses backed by multiple independent observations.

If fail: No clear pattern? Garden may be healthy (not all is problem) or signals too early to read. Record observations. Reassess in one week. Time clarifies what one visit cannot.

Step 5: Heal Checkpoint — Garden Health Triage

Convert observations into prioritized action plan.

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)

Got: Triaged action list. Clear priorities and timeline.

If fail: All feels like red? You may be in anxiety mode, not observation mode. Return to meditate checkpoint (Step 1). Re-enter. True emergencies rare — most garden problems develop slow, can wait a day.

Step 6: Record and Track

Close observation session with journal entry.

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: ___________

Got: Complete dated observation record. Comparable to prior visits.

If fail: Journaling burdensome? Cut to minimum: date, weather, triage summary, one observation per bed. Consistency beats detail.

Checks

  • Meditate checkpoint done before enter garden
  • Gestalt impression recorded before examine individual plants
  • Sensory observations use descriptive language (no diagnosis in Stage II)
  • AOLs identified, set aside (not acted on premature)
  • Pattern analysis covers spatial, temporal, population factors
  • Triage matrix done with clear priority levels
  • Observation record dated, filed in garden journal
  • Actions match triage level (no over-treat green items)

Pitfalls

  1. Confirmation bias: Enter garden looking for specific problem = guarantee you find it (or look-alike). Meditate checkpoint prevents this
  2. Diagnose in Stage II: Name disease during sensory observation biases all next data. Stay with descriptors until Stage III
  3. Treat green as amber: Most garden "problems" resolve themselves. Spray or prune at first sign often causes more harm than original symptom
  4. Skip record: No journal = every visit starts from scratch. Patterns emerge only over time — time needs records
  5. AOL suppress vs manage: Goal is not zero analytical thoughts — impossible. Goal: notice, name, set aside until data supports or refutes
  6. Over-intervention: Reading protocol should boost confidence, cut number of actions. Doing more after reading? Maybe treating anxiety, not garden

See Also

  • meditate — Pre-entry clearing protocol (full meditation procedure)
  • heal — Health triage pattern used in checkpoint
  • prepare-soil — Soil assessment overlaps with soil observation layer
  • cultivate-bonsai — Bonsai health assessment follows same staged observation
  • plan-garden-calendar — Observation records inform calendar tweaks mid-season
  • remote-viewing — CRV-adapted staging protocol originates from this skill

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman/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개 이상의 독립적인 문제를 동시에 조사하고 해결하기 위해 다중 에이전트를 배치합니다. 공유 상태나 의존성 없이 해결 가능한 무관련 장애 시나리오에 맞게 설계되었습니다. 핵심 기능은 병렬 문제 해결로, 각 독립 문제 영역마다 하나의 에이전트를 할당하여 효율성을 극대화합니다.

스킬 보기