cb.fabric-cell-onboarding

Name: cb.fabric-cell-onboarding
Availability: InStock
Author: Softmax

Onboard new Cortical Fabric cell families by aligning registration patterns and tests.

Updated Aug 27, 2026

Search Tags:#workflow #testing #onboarding #fabric #registration #cortical

Ready to run

npx skills add https://github.com/Metta-AI/cortical --skill cb-fabric-cell-onboarding

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cb.fabric-cell-onboarding
Source: https://github.com/Metta-AI/cortical/tree/main/skills/cb.fabric-cell-onboarding
Command: npx skills add https://github.com/Metta-AI/cortical --skill cb-fabric-cell-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through the concrete workflow of onboarding a new Cortical Fabric cell, ensuring proper registration, parity checks, and test coverage to maintain engine consistency.

Core Features & Use Cases

Structured onboarding: Establish a repeatable process for adding a new Fabric cell family, including registration export and test scaffolding.
Boundary-awareness: Enforces interfaces and integration with existing cell patterns and boundary rules.
Use Case: When adding a new cell type, use this skill to align API surface, tests, and documentation with current Fabric conventions.

Quick Start

Begin by reviewing the live Fabric cell API and copy the current registration pattern to implement the new cell.

Frequently Asked Questions about cb.fabric-cell-onboarding

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

FAQPage Schema

How do I onboard a new Cortical Fabric cell family safely?▼

To onboard a new Cortical Fabric cell, align with existing registration patterns, run boundary checks, inspect cell APIs, and perform parity validation across tests and documentation to ensure safe integration.

What is Fabric cell parity validation and when do I need it?▼

Fabric cell parity validation checks consistency across registration exports, test suites, and documentation. You need it when adding a new cell type to maintain engine consistency and enforce canonical backend contracts.

How do I add test scaffolding for a new Fabric cell registration?▼

Add test scaffolding by copying current registration patterns from the live Fabric cell API, then apply boundary rules to validate the new cell's API surface and integration with existing conventions.

Does Fabric cell onboarding require reviewing existing boundary rules?▼

Yes, Fabric cell onboarding requires consulting current boundary rules and test suites to enforce interfaces and ensure the new cell family integrates safely with existing patterns.

What's the best way to align a new Fabric cell API with existing conventions?▼

The best way to align a new Fabric cell API is to review live documentation, copy current registration patterns, and validate parity across registration, tests, and documentation to match conventions.

Why does my new Fabric cell fail boundary checks during onboarding?▼

Fabric cell boundary checks fail when the new cell violates existing interface contracts or registration patterns. Consult current boundary rules and test suites to identify and correct integration mismatches.