AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

S4ag Permaculture

skill-human-avatar-skills-for-agriculture-s4ag-permaculture · by human-avatar

Permaculture design for farms, gardens, and land decisions. Use when the user mentions zones, guilds, swales, food forests, companion planting design, sector analysis, or says 'permaculture design', 'how do I lay out my land', 'design my garden', or 'integrate trees'.

No reviews yet
0 installs
24 views
0.0% view→install

Install

$ agentstack add skill-human-avatar-skills-for-agriculture-s4ag-permaculture

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-human-avatar-skills-for-agriculture-s4ag-permaculture)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of S4ag Permaculture? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Permaculture

Permaculture is a design system, not a philosophy. It gives you a repeatable method for laying out a farm or garden so that every element — water, sun, wind, plants, animals — does multiple jobs and the whole system requires less energy to maintain over time. The central principle is that the right element in the right place, doing the right number of things, is more productive than any single high-input intervention. You are here because you want to make better land decisions — this skill structures that design process.

How this skill works: Each sub-tool pauses at a Checkpoint to confirm the assumptions it is about to build on before producing output. A design built on a wrong assumption wastes time and money — confirm the checkpoint before acting. Each sub-tool ends with Next steps — the skills worth running once you have acted on this one.


Expert Lineage

The thinkers whose frameworks underpin this skill — and what they specifically discovered that changes how you farm.

Bill Mollison — Permaculture: A Designers' Manual Mollison co-developed permaculture in Australia in the 1970s from observations of natural forest systems. His most actionable discovery: productive natural systems succeed because every element is connected to multiple others by energy, nutrient, and water flows — no waste exits the system. On a designed farm, you replicate this by asking, for every element: what does it need, what does it produce, and what else in the system can supply its needs or use its outputs? Any element that needs to be serviced entirely from outside the system is a design failure.

David Holmgren — Twelve Design Principles Holmgren refined Mollison's work into twelve explicit design principles, the most useful of which for practical farm design are: observe and interact before acting; use edges and value the marginal; design from patterns to details; and integrate rather than segregate. His specific contribution is making explicit that the design process has a sequence — observation must precede intervention, and large-scale pattern planning (zone and sector) must precede detail (species selection). Starting with species selection is the most common permaculture design mistake.

Toby Hemenway — Guild and Polyculture Design Hemenway's Gaia's Garden translated permaculture into actionable small-scale farm and homestead design. His specific contribution is the guild — a functional plant community designed around a central tree or productive plant, where each surrounding species performs a defined ecological service (nitrogen fixation, dynamic accumulation, pollinator support, ground cover, pest confusion). Guilds replace the companion planting guess with a structured functional logic: design for services, not species.

Masanobu Fukuoka — Non-Action as a Design Principle Fukuoka farmed 1,200 square metres of Japanese hillside for over sixty years, producing yields that matched or exceeded local conventional farms with no ploughing, no fertilisers, no weeding, and no pruning. His provable finding: a natural system in balance does not need constant intervention — most farm labour inputs are remedial actions compensating for earlier disturbances. The design implication is direct: reduce disturbance, increase diversity, and the system tends toward stability. The first question before any intervention should be: what would happen if I did nothing?

P.A. Yeomans — Sector and Water Pattern Analysis Yeomans' keyline design, while not labelled permaculture, underpins Mollison's sector analysis and water element design. His specific discovery: the keyline — the inflection point on a valley slope where gradient changes from convex to concave — is the natural distribution point for water across a landscape. By reading this line and designing earthworks along it, a farmer can move water from valleys to ridges, transforming a farm's hydrology without pumping. Permaculture sector analysis for water is Yeomans' methodology applied at farm design scale.

Christine Jones — Living Roots and Soil Biology Jones' research on the liquid carbon pathway establishes why permanent ground cover and perennial root systems are the most powerful soil biology tools available. Specifically: plants allocate 30–40% of photosynthetic output through roots to mycorrhizal networks when those networks are intact. Permaculture's emphasis on perennial polycultures, permanent ground cover, and minimal disturbance is — in Ingham/Jones terms — the design system that maximises this biological carbon and nutrient pipeline. Every zone and guild decision has a soil food web consequence.


Which tool fits

| You need to... | Tool | |---|---| | Map zones 0–5 and plan what goes where | zone-design | | Analyse sun, wind, water, fire, pest flows across the site | sector-analysis | | Design a plant community around a tree or crop | guild-design | | Apply natural patterns (edge, keyhole, spiral) to layout decisions | pattern-language | | Run a farm or land decision through the three permaculture ethics | ethics-check |

Routing Decision

  • Starting a new design or redesigning an existing space → zone-design first, then sector-analysis
  • Have zones mapped, need to decide what to plant where and with what → guild-design
  • Have a layout in mind, want to improve the shape or edge of beds and paths → pattern-language
  • Facing a land, purchase, or investment decision and want an ethics filter → ethics-check
  • Unclear where to start → zone-design first; it reveals what else you need

Zone Design

Maps the farm or garden into zones of use intensity and assigns elements to the zone that matches their management frequency.

Zone design is the first layer of any permaculture design. It is not about what you grow — it is about where you grow it, determined by how often you need to visit it. High-maintenance, daily-attention elements go closest to the house. Wild or unmanaged elements go furthest away. The logic is energy efficiency: every unnecessary trip across the farm is time and fuel the system cannot recover.

The five zones:

| Zone | Distance from house | Use frequency | Typical elements | |---|---|---|---| | 0 | The house itself | Constant | Kitchen, fermentation, storage, sprouting | | 1 | Within easy reach — 10–30m | Daily | Salad leaves, herbs, chillies, eggs, compost, cold frames | | 2 | Regular access — 30–100m | Every few days | Main vegetable beds, small fruits, beehives, chicken tractors | | 3 | Infrequent management — 100m–300m | Weekly or less | Orchards, grain crops, fodder crops, larger stock | | 4 | Extensive management — 300m+ | Seasonal | Managed woodland, silvopasture, grazing paddocks | | 5 | No management | Never | Wild reference area, wildlife habitat, observation zone |

Common placement errors to correct:

  • Eggs at Zone 4 (chickens belong at Zone 2 on a small farm — daily collection).
  • Salad leaves at Zone 3 (they bolt or fail between visits — Zone 1 always).
  • Compost at Zone 1 edge — input materials from the whole farm need to reach it; place at Zone 1/2 boundary.
  • Fruit trees scattered at Zone 1 — pruning and harvest demand is manageable but the shade impact on vegetable beds is often overlooked.

Process:

  1. Draw a rough overhead sketch of the property — house, access points, existing structures, roads.
  2. Mark distance rings at roughly 30m, 100m, and 300m from the main entry point and house.
  3. List every element currently on the farm (crops, animals, infrastructure).
  4. List every element you plan to add.
  5. Assign each to a zone based on management frequency, not preference.
  6. Identify zone conflicts — anything placed in a zone that does not match its management needs.
  7. Adjust the layout to resolve conflicts before building or planting anything.

Zone boundary flexibility: Real terrain — slopes, water, existing trees, access tracks — modifies zone boundaries. A greenhouse at 80m accessed by a direct path is effectively Zone 1. A vegetable bed at 30m at the far end of a barn with no direct access is effectively Zone 3. Design with movement patterns, not just distance.

Soil food web note: Zone placement is also compaction management. Routing foot and vehicle traffic away from productive beds preserves the fungal networks Ingham documents. Zone 1 should have hard paths or stepping stones — the beds themselves should never take foot traffic. Zone 4 and 5, where traffic is rare, are where undisturbed mycorrhizal networks develop deepest.

Checkpoint — confirm before finalising:

  • How large is the property and where is the main dwelling or working base that determines zone centre?
  • Which elements are fixed (existing buildings, roads, large trees) that cannot move regardless of zone logic?
  • Who manages the farm — one person full-time, or a family with part-time attention? Access frequency assumptions change with labour.

Designing zones around an imagined version of the farm rather than the actual land and labour available produces a beautiful plan that does not survive contact with reality.

Output:

ZONE DESIGN — [Property Name / Date]

PROPERTY: [area in ha/acres] / [main access point]

ZONE 0 — [house / processing area elements]

ZONE 1 — [within [distance]m]
Elements: [list]
Justification: [why daily access needed]

ZONE 2 — [within [distance]m]
Elements: [list]
Justification: [why regular access needed]

ZONE 3 — [within [distance]m]
Elements: [list]
Justification: [infrequent management description]

ZONE 4 — [beyond [distance]m]
Elements: [list]
Management: [seasonal tasks only]

ZONE 5 — [location]
Purpose: [wild/observation/wildlife]

PLACEMENT CONFLICTS TO RESOLVE:
- [element currently misplaced]: move from Zone [x] to Zone [y] — reason

NEXT DESIGN STEP: sector-analysis

Next steps:

  • Run sector-analysis (within this skill) — once zones are placed, map energy sectors (sun, wind, water) across them to refine placement.
  • Run guild-design (within this skill) — use zone placement to determine which guilds belong at which zone.
  • /s4ag-earthworks — if Zone 4 or 5 contains water management opportunities, design earthworks before permanent planting.

Sector Analysis

Maps the energy flows crossing the site — sun, wind, water, fire, pest, noise — and uses them to place, orient, and protect elements correctly.

Sectors are the forces that come from outside the farm and flow through it. You cannot change them. You can design with them or against them. Designing with them means placing elements where the sectors support rather than damage them; designing against them means spending permanent energy on shelter belts, irrigation, or pest control that the sector analysis would have made unnecessary.

The six sectors to map:

1. Sun

  • Track sun angle by season: summer arc vs winter arc are very different at latitudes above 35°.
  • Shade sectors: identify what the existing house, trees, and structures shade at each season.
  • Warm wall effect: south-facing walls (north in southern hemisphere) create a microclimate 2–4°C warmer — valuable for tender crops or early propagation.
  • Practical rule: Zone 1 food production should be placed in full sun; trees should not shade it from the south.

2. Wind

  • Identify prevailing wind direction (check local met data or ask a long-term neighbour).
  • Identify secondary problem winds — cold northerlies in winter, hot desiccating summer winds.
  • Wind solutions: hedgerow or windbreak at 2–5x its height on the windward side of the zone being protected. Dense coniferous windbreak stops wind; permeable mixed hedgerow reduces it — the latter is usually more appropriate.
  • Wind danger: unsheltered polytunnels lose covers; tender crops die in frost pockets that form downslope of a solid windbreak.

3. Water

  • Map where water flows in heavy rain — paths from high points to low, runoff channels, flood zones.
  • Identify waterlogging areas and note their seasonal pattern.
  • Mark high water harvesting potential — roof runoff, natural catchment points.
  • The water sector determines earthworks priority and constrains where annual beds can go (waterlogged soil kills plant roots and destroys soil biology).

4. Fire

  • In fire-prone climates (Mediterranean, Australian, Californian): identify the upslope and upwind fire approach direction.
  • Fire sector design: low-water, low-fuel species on the fire approach side; no dry-grass clearings adjacent to structures; fire break design before permanent planting.
  • In non-fire climates: this sector can be noted but deprioritised.

5. Pest and wildlife

  • Identify where animal pressure enters the property — rabbit warrens, deer approaches, badger sets, neighbour's poultry.
  • Map crop predation pressure by direction.
  • Zone 1 should be easiest to protect; Zone 4 and 5 accept wildlife as part of the system.

6. Noise and views

  • Less critical for most farmers; relevant for agritourism (→ /s4ag-agritourism) and residential integration.
  • Dense planting between a road noise source and the living/working area can reduce noise significantly.

How to map sectors:

  1. On the same base sketch used for zone design, draw arrows or shaded wedges indicating the direction and strength of each sector.
  2. Mark positive sectors (beneficial flows — morning sun, gentle prevailing rain) differently from negative (cold wind, fire risk, pest entry).
  3. Overlay the zones. Look for conflicts — where a negative sector crosses a Zone 1 area.
  4. Design interventions: windbreaks, hedgerows, swales, or simply repositioning zone elements to avoid or harness the sector flow.

Common sector mistakes:

  • Placing a polytunnel in a frost pocket (identified by the cold air drainage sector — cold air flows downslope and pools in hollows).
  • Putting the vegetable garden on the shaded side of the house.
  • Ignoring the water sector entirely until a flood event damages beds or undermines pathways.

Soil food web note: Sectors affect soil biology directly. Cold wind over bare soil desiccates the biological zone. Frost pockets kill soil organisms in shallow soils. Waterlogging causes anaerobic conditions that crash the aerobic food web. Sector analysis is a map of where the food web is most vulnerable — design permanent cover and protection accordingly.

Checkpoint — confirm before finalising:

  • What is the climate — temperate maritime, continental, Mediterranean, subtropical, arid? Wind, sun, and fire sector priorities differ significantly.
  • Is fire a realistic risk in this location? If yes, it becomes a primary sector, not a footnote.
  • Has the user observed the site across seasons, or only recently? Sectors observed for one season are incomplete.

Acting on a single-season observation — placing beds based on one summer's sun pattern — misses winter shade, spring frost pockets, and autumn wind exposure.

Output:

SECTOR ANALYSIS — [Property Name / Date]

SUN SECTOR
Summer arc: [direction, hours of direct sun in key zones]
Winter arc: [direction, hours, key shade impacts]
Warm wall opportunities: [location and aspect]

WIND SECTOR
Prevailing direction: [compass direction]
Problem winds: [secondary winds, seasonal cold or hot winds]
Current shelter: [existing shelterbelts, hedges, structures]
Shelter needed: [where and what type]

WATER SECTOR
Runoff pathways: [describe high-to-low flow paths]
Waterlogging areas: [location, seasonal pattern]
Harvesting opportunities: [roof area, catchment points]

FIRE SECTOR
Risk level: [low / moderate / high]
Approach direction: [if applicable]
Priority actions: [if applicable]

PEST/WILDLIFE SECTOR
Entry points: [species and approach direction]
Most vulnerable zones: [Zone 1 or 2 elements at risk]
Protection needed: [fencing, netting, plant deterrents]

SECTOR CONFLICTS WITH ZONES
- [Zone 1 element] is in the path of [sector] — resolve by [action]
- [Zone 2 element] is

…

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [human-avatar](https://github.com/human-avatar)
- **Source:** [human-avatar/skills-for-agriculture](https://github.com/human-avatar/skills-for-agriculture)
- **License:** MIT
- **Homepage:** https://www.npmjs.com/package/@human-avatar/skills-for-agriculture

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.