Portable agent skills for Lattice Chat

When helpers nest, someone has to tell each child which room they are in — without pasting the entire site into every prompt. FractiSkills files portable, page-scoped skill packs as short SKILL.md packages under the AI catalog layer: pointer-first into Lattice Chat, local monorepo corpus on the order of hundreds of skills. This note is the kitchen-table reason CEOs and guests should care before the math lesson: portable skills keep doors clear, burn fewer tokens, and stop dialect islands that confuse real people.

Everyday stakes are cost, clarity, and livelihoods. When every child reinvents the room, briefs get mushy, demos slip, and the humans who were supposed to ship lose hours — then households feel it as overtime, delayed pay, or a quieter job board. Portability is not a toy. It is how nested work stays hospitable.

What “portable” means when agents nest

Portable means a skill pack can move with the surface: which paper, which ship-blog, which protocol — without embedding a whole foreign corpus as production proof. It does not embed Skillarum. It does not treat a live public crawl page-count as production proof. It does not pin into the Infinite Octaves engine shelf. About 1.618 is nesting grammar. Keep those seatbelts near design reviews so marketing fog does not steal a Tuesday.

Why CEOs care before the math lesson

CEOs feel token burn as budget. They feel dialect islands as support tickets. They feel unclear doors as stalled hires. Portable skills are an operations story first: less paste, more pointer, shared nouns across children. Parents summarizing for boards should refuse “infinite GPU-free scaling proved” compression. Flat summaries invite myth. Banded briefs invite re-runs. Myth is expensive for people who still have rent due.

What a skill pack actually contains

A skill pack is a short package plus index: enough to orient a child to a surface, not enough to pretend the child swallowed the library. Generated from registries — papers, ship-blog, protocols — so the corpus stays resonant with what the ship actually publishes. Guests should try it by opening Lattice Chat, loading a surface, and noticing whether the helper still knows which room it is in after a nested handoff.

Tuesday work for operators

Regenerate when registries change. Prefer pointer-first prompts. Reject vanity heat that loads every skill “just in case.” Scale-to-zero when a child’s drift is done. Keep wallets and keys on lite edges. Tip under Fair Exchange if the framing cleared a real argument about agent cost and clarity. Ignore the tip if you only needed a raw file tree.

What fails when skills are not portable

Each nest invents a private handbook. Guests get contradictory answers. Token meters climb while job boards thin for the humans who clean up the mess. School projects and small businesses that wanted a helper get a fog machine instead. Portability is how the ship refuses that failure mode without refusing nested work.

Guests should try a simple path. Open Lattice Chat. Pick a surface you care about — a paper, a ship-blog, a protocol. Watch whether the helper still knows the room after a handoff. If it starts inventing a private handbook, the skill pack failed the hospitality test. If it points and stays scoped, the corpus is doing its job. People teaching kids already know the difference between a study guide and a suitcase of every textbook. Portable skills are study guides for nested work.

Tuesday work continues after regenerate. Audit a sample of packs for honesty leakage into guest screens — park honesty at the end rail. Prefer shared nouns. Reject vanity heat. When a CEO asks whether this reduces spend, answer with doors and tickets, not mysticism: fewer contradictory answers, fewer cleanup loops, fewer humans losing hours to fog. Those hours are paychecks. Those paychecks are rent.

Along the Truckee, warehouse GPU heat and river cool air argue all summer. Ambition wants every skill loaded. Restraint loads what the story needs. Keep both. Tip under Fair Exchange if the framing cleared a real argument about agent cost and clarity. Ignore the tip if you only needed a raw file tree. Nevada’s holographic AI valley will keep printing hospitality before prophecy — pointer-first, room-scoped, human emergency above every clever map.

The pier close is practical. Keep skills short, scoped, and honest. Keep engine pins separate from application companions. Keep human emergency above every clever map. When nested helpers share rooms without pasting the whole town into every prompt, people get hours back — and hours back are how craft, school, and rent get easier in the same week the tools get smarter.

Closing pier

Keep skills short, scoped, and honest. Keep engine pins separate from application companions. Keep human emergency above every clever map. Open the whitepaper after this human article if you want the filing. Walk Lattice Chat if you want the live floor. Nevada’s holographic AI valley will keep printing hospitality before prophecy. That order is how SuperAI stays Goldilocks on a ship that still believes nested helpers can share rooms without pasting the whole town into every prompt — and without forgetting that people still need clear doors to earn a living.

Honesty boundary: Soft Story / catalog. application companion under the AI catalog layer — local monorepo SKILL.md corpus (~421 skills), pointer-first into Lattice Chat. Does not embed Skillarum, does not treat a live 405-page public crawl as production proof, does not pin into the Infinite Octaves engine shelf, and does not prove infinite GPU-free scaling. Φ ≈ 1.618 is nesting grammar.

Fair Exchange: a portion of transaction value remains subject to refund or adjustment depending on resonance, utility, and depth of delivery.