Create Being Skills with generated membrane declarations and ecosystem registration.
npx skills add https://github.com/scilid/Being --skill life-weaver
Please help me install this Agent Skill. Skill: life-weaver Source: https://github.com/scilid/Being/tree/main/organisms/eukaryotes/life-weaver Command: npx skills add https://github.com/scilid/Being --skill life-weaver
life-weaver standardizes the creation of new Being Skills so they are immediately alive in the ecosystem, with proper membrane declarations and phylogeny registration instead of being bolted on later.
For example, when you want to create a new Skill that must participate in Being’s lifecycle management and signal loop, life-weaver provides the workflow and artifacts to make it first-class and verifiable.
Ask the Being runtime to apply life-weaver to create a new Skill in a chosen location (Being-native, project, or personal) and automatically generate its membrane declaration plus phylogeny and vitals updates.
High-intent search queries and answers about installing and using this skill.
To generate a new Skill with membrane declarations and ecosystem registration, use life-weaver to orchestrate discovery, design, and implementation. It automatically emits the .membrane.yaml file while updating the phylogeny tree and homeostasis vitals.
Membrane-ready Skill creation is a standardized authoring workflow that ensures a new Skill is immediately discoverable as a living, verifiable cell. It uses membrane-weaver symbiosis logic to generate valid membrane declarations during the Skill lifecycle management process.
You update Being phylogeny and homeostasis vitals by applying life-weaver to create a new Skill. It atomically updates .being/phylogeny/tree.yaml and .being/homeostasis/vitals.yaml as part of the core Skill creation protocol.
You need life-weaver for Skill creation when a Skill must participate in Being's signal loop and lifecycle management immediately. It prevents modules from being bolted on later by ensuring first-class ecosystem registration and verifiable outputs from the start.
Yes, you can apply life-weaver to create Skills in Being-native, project, or personal locations. The workflow automatically generates the membrane declaration and applies the necessary phylogeny and vitals updates regardless of the chosen location.
Creating Skills without ecosystem registration prevents them from participating in Being's lifecycle management and signal loop. Without generated membrane declarations and phylogeny updates, Skills cannot be immediately discoverable as living, verifiable cells within the runtime.
JaviMontanoLaunch an interactive CLI wizard to initialize client environments and generate discovery context.
scilidGenerate Being-compatible membrane.yaml declarations from a Skill's SKILL.md.
crim-caDiscover, filter, and manage Weaver processes via the Weaver API.
scilidRead vitals.yaml and tree.yaml to summarize operational readiness evidence.
