node-wizard-expert

Coordinate Cogni node formation design, debugging, and launch handoffs to the node-wizard-scorecard.

4|5|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/cogni-dao/cogni --skill node-wizard-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-wizard-expert
Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/node-wizard-expert
Command: npx skills add https://github.com/cogni-dao/cogni --skill node-wizard-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the design, debugging, and operation of Cogni node formations, PRs, submodule-pinned repos, and AI-assistant handoffs, routing launch execution and end-to-end proof to the node-wizard-scorecard.

Core Features & Use Cases

  • Orientation layer for node-wizard launches and handoffs to the scorecard.
  • Guidance for throwaway-node formation planning, PR reviews, and submodule pin alignment.
  • Reference patterns and rules to ensure consistent, auditable launches.

Quick Start

Provide a live node-wizard launch objective and redirect execution to the node-wizard-scorecard for end-to-end proof and handoff.

Frequently Asked Questions about node-wizard-expert

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

FAQPage Schema
How do I orchestrate a node formation and handle off launch execution to a scorecard?

Node formation orchestration is managed by providing a live launch objective and explicitly redirecting execution and end-to-end proof to the node-wizard-scorecard for auditable handoffs.

What is the best way to align submodule-pinned repos during a node launch PR workflow?

Submodule-pinned repo alignment during PR workflows is guided by reference patterns and rules that enforce consistent orientation, ensuring auditable launches and proper submodule pin alignment.

Can I use this node orchestration approach for throwaway-node formation planning?

Throwaway-node formation planning is fully supported, providing design guidance, debugging rules, and explicit handoff contracts to route execution proof directly to the scorecard.

Why do I need an orientation layer for AI-assistant handoffs in node launches?

An orientation layer for AI-assistant handoffs is required to enforce reference patterns to the scorecard, ensuring consistent, auditable node launches and explicit execution contracts.

Does this node launch workflow support live debugging of formation processes?

Live debugging of node formation processes is supported throughout the flight process, coordinating design and operation while routing end-to-end proof to the scorecard.