arcanum-bootstrap

Generate native runtime skill packages and observability state for Arcanum repositories.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill arcanum-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arcanum-bootstrap
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/arcanum-bootstrap
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill arcanum-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the integration of Arcanum into a consuming repository by provisioning native runtime skill packages, observability scaffolding, and optional Necronomicon harness state.

Core Features & Use Cases

  • Generates native runtime packages for chosen sigils and spells.
  • Sets up observability storage and optional Necronomicon harness state for memory and routing.
  • Supports installation postures to target specific capabilities or all included components.

Quick Start

Run the bootstrap to install Arcanum into your repository and generate the runtime packages and observability state.

Frequently Asked Questions about arcanum-bootstrap

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

FAQPage Schema
How do I install runtime packages and observability state into my repository?

To install runtime packages and observability state, run the bootstrap to generate native runtime skill packages for your chosen sigils and spells along with the required observability scaffolding.

What is the best way to generate native runtime skill packages for specific capabilities?

Generating native runtime skill packages for specific capabilities is done by setting an installation posture that targets a selected set of sigils and spells rather than provisioning all included components.

Can I set up Necronomicon harness state and legacy Codex adapters during installation?

Yes, you can set up Necronomicon harness state for memory and routing alongside legacy Codex adapters by enabling these optional features during the repository bootstrap process.

What do I need to provide before generating runtime packages and observability hooks?

Before generating runtime packages and observability hooks, you need to provide a known target repository root, an installation posture, and a default runtime adapter.

Does the bootstrap process support targeting only a selected set of sigils and spells?

Yes, the bootstrap process supports targeting a selected set of sigils and spells by configuring the installation posture to generate packages for specific capabilities instead of all components.