MCP HubMCP Hub
SKILL·ED9F6E

read-garden

pjt222
Actualizado 1 month ago
9 vistas
26
3
26
Ver en GitHub
Otrogeneral

Acerca de

Esta habilidad proporciona un protocolo sensorial estructurado para observar y evaluar sistemáticamente la salud de un jardín antes de cualquier intervención. Guía al usuario a través de etapas de despeje, observación gestáltica, comprobaciones sensoriales detalladas y análisis de patrones para diagnosticar problemas. Úsela al evaluar el estrés de las plantas, los cambios estacionales o durante el monitoreo regular para fundamentar decisiones de jardinería basadas en datos.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/read-garden

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

Read Garden

Observe + assess garden via structured sensory protocol → before any intervention decision.

Use When

  • Before any intervention → read first, act second
  • Plant stress (yellow, wilt, curl, spots)
  • Seasonal trans (spring wake, autumn decline)
  • New site eval before plant
  • Regular weekly/biweekly monitor
  • After extreme weather (frost, heat, heavy rain)

In

  • Required: Physical access garden
  • Required: Journal/notebook → record obs
  • Optional: Prev records → compare
  • Optional: Soil thermometer, pH strips, moisture meter
  • Optional: Hand lens (pest/disease ID)

Do

Step 1: Meditate Check — Pre-Entry Clear

Before enter for assess, 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.

→ Calm, receptive, no preconceptions.

If err: can't release expectations (anxiety, frustration) → ack emotion, write "AOL: [concern]", proceed. Naming reduces influence.

Step 2: Stage I — Gestalt

Walk 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)

→ Brief holistic record, no analysis or diagnosis.

If err: start diagnose ("squash wilts because...") → write "AOL: [diagnosis]" → return to obs. Analysis = Stage III.

Step 3: Stage II — Sensory

Move bed by bed. Engage all senses 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"

→ Detailed sensory record per bed/zone, descriptive only.

If err: catch self diagnosing (name disease, blame pest) → "AOL: [diagnosis]" → return raw obs. Name later, data first.

Step 4: Stage III — Pattern

Now, only now, connect obs 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

→ One+ tentative diagnoses backed by multi indep obs.

If err: no clear pattern → garden may be healthy (not all = problem) or signals too early. Record + reassess 1 week. Time clarifies what single visit can't.

Step 5: Heal Check — Triage

Convert obs → 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)

→ Triaged action list w/ clear priority + timeline.

If err: all feels red → may be anxiety mode not obs. Return Step 1, re-enter. True emergencies rare → most problems develop slow, can wait day.

Step 6: Record + Track

Complete session w/ 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: ___________

→ Complete dated record → comparable to prev visits.

If err: journal feels burden → minimum: date, weather, triage, one obs/bed. Consistency > detail.

Check

  • Meditate done before enter
  • Gestalt recorded before exam plants
  • Stage II sensory uses descriptive lang (no diagnosis)
  • AOLs ID'd + set aside (no premature act)
  • Pattern → spatial, temporal, population
  • Triage matrix done w/ clear priority
  • Record dated + filed
  • Actions proportional to triage (no over-treat green)

Traps

  1. Confirmation bias: Enter looking for problem → find it. Meditate prevents.
  2. Diagnose Stage II: Naming disease during sensory biases data. Stay descriptive til Stage III.
  3. Green as amber: Most "problems" resolve. Spray/prune first sign → more harm than symptom.
  4. Skip record: No journal → every visit fresh. Patterns need time + records.
  5. AOL suppress vs mgmt: Goal ≠ no analytic thoughts (impossible). Goal = notice, name, set aside til data supports/refutes.
  6. Over-intervention: Protocol → increase confidence + reduce actions. Doing more after reading → treating anxiety not garden.

  • meditate — pre-entry clear protocol
  • heal — triage pattern in checkpoint
  • prepare-soil — soil assess overlaps soil obs layer
  • cultivate-bonsai — bonsai health assess same staged obs
  • plan-garden-calendar — records inform calendar mid-season
  • remote-viewing — CRV-adapted staging origins

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/caveman-ultra/skills/read-garden
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams
FAQ

Frequently asked questions

What is the read-garden skill?

read-garden is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform read-garden-related tasks without extra prompting.

How do I install read-garden?

Use the install commands on this page: add read-garden to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does read-garden belong to?

read-garden is in the Other category, tagged general.

Is read-garden free to use?

Yes. read-garden is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.

Habilidades relacionadas

llamaguard
Otro

LlamaGuard es el modelo de Meta de 7-8B parámetros para moderar las entradas y salidas de LLM en seis categorías de seguridad como violencia y discurso de odio. Ofrece una precisión del 94-95% y puede implementarse usando vLLM, Hugging Face o Amazon SageMaker. Utiliza esta skill para integrar fácilmente filtrado de contenido y barreras de seguridad en tus aplicaciones de IA.

Ver habilidad
cost-optimization
Otro

Esta Skill de Claude ayuda a los desarrolladores a optimizar los costes en la nube mediante el ajuste de tamaño de recursos, estrategias de etiquetado y análisis de gastos. Proporciona un marco para reducir los gastos en la nube e implementar una gobernanza de costes en AWS, Azure y GCP. Úsala cuando necesites analizar los costes de infraestructura, ajustar el tamaño de los recursos o cumplir con restricciones presupuestarias.

Ver habilidad
sports-betting-analyzer
Otro

Esta habilidad de Claude analiza los mercados de apuestas deportivas, incluyendo spreads, over/unders y apuestas de propuestas, mediante el examen de tendencias históricas y estadísticas situacionales para identificar apuestas de valor. Proporciona una salida en markdown estructurado con recomendaciones accionables con fines educativos. Los desarrolladores deben utilizar esto para herramientas de análisis de apuestas deportivas, teniendo en cuenta que está diseñado únicamente para entretenimiento/educación.

Ver habilidad
quantizing-models-bitsandbytes
Otro

Esta habilidad cuantiza LLMs a precisión de 8 o 4 bits utilizando bitsandbytes, logrando una reducción de memoria del 50-75% con pérdida mínima de precisión. Es ideal para ejecutar modelos más grandes en memoria GPU limitada o para acelerar la inferencia, admitiendo formatos como INT8, NF4 y FP4. La habilidad se integra con HuggingFace Transformers y permite entrenamiento QLoRA y optimizadores de 8 bits.

Ver habilidad