knowledge-gardening
Keep a team knowledge base alive — the gardener role and its weekly half-hour, the rot signals (stale pages, orphans, duplicates) and their fixes, the capture funnels that feed the garden, and the pruning that keeps search useful. Use when asked our wiki is a graveyard, who maintains the knowledge base, set up knowledge management that lasts, or people can't find anything anymore. Produces the gardener rotation, the weekly tending routine, the rot triage, and the capture funnels.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill knowledge-gardening --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Knowledge Gardening Skill Knowledge bases don't die of bad writing — they die of no gardener: pages rot silently, duplicates sprout (because the original wasn't findable), orphans accumulate, and within two years search returns three contradictory versions of everything, teaching everyone to ask humans again. The fix isn't a heroic cleanup (that's the [shared-drive-cleanup](../shared-drive-cleanup/SKILL.md) move, needed once) — it's *gardening*: a named rotating role, a weekly half-hour routine, rot signals with standard fixes, and capture funnels that turn the team's answered-questions and decisions into pages while they're fresh. ## What This Skill Produces - **The gardener role** — rotating (monthly), scoped (a half-hour weekly), with the routine written - **The weekly tending routine** — the four moves: triage new, fix flagged, prune one, merge duplicates - **The rot triage** — the signals (stale-flag, orphan, duplicate, contradicting) and each one's standard fix - **The capture funnels** — the answered-twice rule, decision-log links, and the offboarding harvest ## Required Inputs Ask for these if not provided: - **The garden's state** — page count, the known-rotten zones, wh
- What This Skill Produces
- Required Inputs
- Framework: The Gardening Rules
- Output Format
- The Role
- The Weekly Routine
- Rot Triage
- The Funnels
- Quality Checks
- Anti-Patterns
What does the knowledge-gardening skill do?
Keep a team knowledge base alive — the gardener role and its weekly half-hour, the rot signals (stale pages, orphans, duplicates) and their fixes, the capture funnels that feed the garden, and the pruning that keeps search useful. Use when asked our wiki is a graveyard, who maintains the knowledge base, set up knowledge management that lasts, or people can't find anything anymore. Produces the gardener rotation, the weekly tending routine, the rot triage, and the capture funnels.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill knowledge-gardening --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.