orchestration/gencreator-stack

Audit AI stacks across repos and emit constellation files, scaffolds, drift reports from inventory.json and STACK.md files.

6|2|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill orchestration-gencreator-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestration/gencreator-stack
Source: https://github.com/frankxai/Starlight-Intelligence-System/tree/main/skills/orchestration/gencreator-stack
Command: npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill orchestration-gencreator-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill maintains a canonical per-repo STACK.md manifest that catalogs the AI surfaces, tooling, and MCP bindings across brands to enable governance, drift detection, and cross-repo planning.

Core Features & Use Cases

  • Audit across all repos to emit a unified constellation file that reflects current stacks and bindings.
  • Scaffold STACK.md templates into target repos, including default tier bindings and change logs.
  • Diff and surface drift between declared STACK.md intent and the actual filesystem state and installed tooling.

Quick Start

Run the audit to generate context/stack-constellation.md and scaffold STACK.md into a target repo as the first step.

Frequently Asked Questions about orchestration/gencreator-stack

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

FAQPage Schema
How do I audit multiple repos for tech stack inventory and MCP bindings?

To audit tech stack inventory, the skill reads an inventory.json file and parses STACK.md manifests across repos to emit a unified stack-constellation.md reflecting current stacks and MCP bindings.

What is STACK.md used for in multi-repo governance?

STACK.md serves as a canonical per-repo manifest cataloging AI surfaces, tooling, and MCP bindings to enable governance, drift detection, and cross-repo planning across multiple brands.

How do I detect drift between declared stack manifests and actual repo state?

To detect stack drift, the skill diffs the declared STACK.md intent against the actual filesystem state and installed tooling, generating a report that surfaces inconsistencies.

Can I scaffold a STACK.md template into a target repository?

Yes, you can scaffold STACK.md templates into target repos, which includes populating default tier bindings and initializing change logs for per-repo stack tracking.

Does this stack inventory tool require any external dependencies?

No, this stack inventory and audit tool has no external dependencies, operating directly on local assets like inventory.json and repository filesystems to generate constellation files and drift reports.

What's the best way to track per-repo AI tooling assignments across brands?

The best way to track per-repo AI tooling is maintaining a canonical STACK.md manifest for each repository and aggregating them into a unified constellation file for cross-brand governance.