membrane-weaver

Generate Being-compatible membrane.yaml declarations from a Skill's SKILL.md.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/scilid/Being --skill membrane-weaver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: membrane-weaver
Source: https://github.com/scilid/Being/tree/main/organisms/prokaryotes/membrane-weaver
Command: npx skills add https://github.com/scilid/Being --skill membrane-weaver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes how Being Skills describe their boundaries, inputs, outputs, side effects, and compatibility so they can be safely integrated into the ecosystem.

Core Features & Use Cases

  • Membrane Declaration Generation: Reads a target Skill's SKILL.md (frontmatter + body) and produces a Being-compatible .membrane.yaml declaration.
  • Ingress/Egress/Side-Effect Inference: Infers required inputs, emitted outputs, file/environment mutations, and signal interactions from the Skill’s operational text.
  • Optional Compatibility Analysis: When provided a second Skill membrane, checks egress→ingress type matching and signal compatibility to classify symbiosis potential.
  • Phylogeny Registration: Records the resulting membrane declaration into the Being phylogeny tree with appropriate biogenesis/evolution updates.

Quick Start

Use membrane-weaver to analyze a target Skill's SKILL.md and generate its standardized .membrane.yaml membrane declaration for Being integration.

Frequently Asked Questions about membrane-weaver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a membrane YAML declaration from a SKILL.md file?

To generate a membrane YAML declaration, you analyze the target Skill's SKILL.md frontmatter and body to infer ingress, egress, side effects, and signals, producing a standardized .membrane.yaml file without modifying the original document.

What is a standardized membrane protocol for Skill integration?

A standardized membrane protocol defines how Skills describe their boundaries, inputs, outputs, and side effects so they can be safely integrated and checked for compatibility within the Being ecosystem.

How do I check compatibility and symbiosis between two Skills?

You check symbiosis potential by comparing a second Skill's membrane against the first, matching egress to ingress types and signal compatibility to classify how well the two Skills integrate.

Can I infer side effects and signal interactions from an existing Skill's metadata?

Yes, you can infer side effects, signal receives, signal emits, niche context triggers, and affinity relations directly from the operational text found in a Skill's SKILL.md file.

Does generating a .membrane.yaml file modify the original SKILL.md?

No, generating a .membrane.yaml file does not modify the original SKILL.md; it reads the content to infer interface declarations and writes the output to a separate standardized membrane file.

How do I register a Skill membrane declaration into a phylogeny tree?

You register a Skill membrane declaration into the phylogeny tree by recording the generated .membrane.yaml file with appropriate biogenesis and evolution updates to track its integration lineage.