Back to Skills

read-garden

pjt222
Updated Yesterday
5 views
17
2
17
View on GitHub
Othergeneral

About

The `read-garden` skill provides a structured protocol for observing and assessing garden health, adapted from Coordinate Remote Viewing. It guides users through sensory stages—from initial impressions to detailed analysis of plant parts and soil—and includes a health triage matrix. Developers should use it for diagnostic monitoring before interventions, during plant stress, at seasonal changes, or after extreme weather events.

Quick Install

Claude Code

Recommended
Primary
npx skills add pjt222/agent-almanac -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternative
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/read-garden

Copy and paste this command in Claude Code to install this skill

Documentation

讀園

於任何介入之前,以結構化感官程序觀察並評估庭園。

適用時機

  • 任何介入之前——先讀園,後行事
  • 植物呈現壓力徵兆(黃化、萎蔫、捲曲、斑點)
  • 換季過渡(春甦、秋衰)需作評估
  • 種植前對新園址之評估
  • 例行(每週或隔週)之健康監測
  • 極端天氣事件之後(霜害、熱浪、暴雨)

輸入

  • 必要:得親臨庭園
  • 必要:庭園日誌或筆記本以記錄觀察
  • 選擇性:往昔觀察記錄以資比對
  • 選擇性:土溫計、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 Repository

pjt222/agent-almanac
Path: i18n/wenyan-lite/skills/read-garden
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Related Skills

llamaguard

Other

LlamaGuard is Meta's 7-8B parameter model for moderating LLM inputs and outputs across six safety categories like violence and hate speech. It offers 94-95% accuracy and can be deployed using vLLM, Hugging Face, or Amazon SageMaker. Use this skill to easily integrate content filtering and safety guardrails into your AI applications.

View skill

cost-optimization

Other

This Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.

View skill

quantizing-models-bitsandbytes

Other

This skill quantizes LLMs to 8-bit or 4-bit precision using bitsandbytes, achieving 50-75% memory reduction with minimal accuracy loss. It's ideal for running larger models on limited GPU memory or accelerating inference, supporting formats like INT8, NF4, and FP4. The skill integrates with HuggingFace Transformers and enables QLoRA training and 8-bit optimizers.

View skill

dispatching-parallel-agents

Other

This Claude Skill dispatches multiple agents to investigate and fix 3+ independent problems concurrently. It is designed for scenarios involving unrelated failures that can be resolved without shared state or dependencies. The core capability is parallel problem-solving, assigning one agent per independent problem domain to maximize efficiency.

View skill