greenhouse
Skill4 starsChanged 17 days agoMITView on GitHub
Shared memory across the repositories of one platform (what each repo provides, depends on, and its key facts) kept in a base folder next to the repos. Use when a task touches an API, package, schema or convention shared with other repos, instead of opening those repos; publish this repo's card at task end.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- wolffe/three.js-skillstheir own version, first seen Nov 8, 2026
- apideck-libraries/api-skillstheir own version, first seen Aug 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- apideck-libraries/api-skills★ 4same name
- wolffe/three.js-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Files
greenhouse
!"${CLAUDE_SKILL_DIR}/bin/greenhouse" mode --banner
Agents that do not expand the line above (e.g. Codex): run
<this-skill-dir>/bin/greenhouse mode --banner first and follow it.
A base is a folder (usually <workspace>/.greenhouse/, beside the repos)
with one card per repo and platform-wide notes. Cards are harvested
deterministically: README summary, packages provided, dependencies,
entrypoints, layout, the repo's seedbank hot facts and mycelium notes.
Repos link automatically when one depends on a package another provides.
greenhouse is not on PATH: always run <this-skill-dir>/bin/greenhouse.
No base found (mode on, the session-start hook or any command says
so): never create one unasked. Ask the user with AskUserQuestion: create a
new base beside the repo (bin/greenhouse init), use an existing one or a
specific path (bin/greenhouse link <path> / init --at <path>), or this
repo is standalone (bin/greenhouse mode off). Then run their choice.
- Start (only if the task may cross a repo boundary):
bin/greenhouse brief "<task>". It lists this repo's upstream and downstream repos, matching platform notes and the relevant facts of other repos.bin/greenhouse show <slug>gives one full card. A card marked STALE must be verified before you rely on it. If a card does not settle the question, delegate one bounded question to theenvoyagent (read-only; give it the card and the checkout path) instead of reading the other repo yourself; record its platform note if it returns one. - End, after a change that others depend on, or when the brief said
this repo's card is missing or old:
bin/greenhouse sync [--summary "<what this repo is for>"] [--provides "<interface>"] [--consumes "<repo>: <what>"]--summary/--provides/--consumesare kept across syncs; give them once. - Platform facts that hold across repos (shared conventions, a
contract between two services, a migration in progress):
bin/greenhouse note "<topic>" "<fact>" [--repo <slug>]. Repo-local facts belong in the repo (seedbank), not here.
Discovery, layout, hook setup, sharing the base: references/guide.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.