onboard-omnigrid

Detects repository stack and generates a staged omnigrid.yaml configuration via a describe-propose-confirm flow.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill onboard-omnigrid-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: onboard-omnigrid
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/onboard-omnigrid
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill onboard-omnigrid-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adopting an agentic workflow framework into an existing repository normally requires manually inspecting the stack, deciding which agent roles apply, and hand-writing configuration. This Skill automates that one-time per-project setup by detecting the stack deterministically and producing a reviewed, staged config file. ## Core Features & Use Cases - Deterministic stack detection: Runs omnigrid onboard to detect languages, framework, backend, test runner, and package manager from the live repo rather than interviewing the user. - Harnessability scoring: Scores the repo across five dimensions (type safety, module boundaries, framework opinionation, test coverage, lint baseline) and derives the enforcement default (blocking or advisory). - Role derivation and Handbook seeding: Derives active conditional Roles (e.g. frontend-engineer, platform-engineer, penetration-tester) and scaffolds the omnigrid/handbooks/ directories. - Use Case: A developer adopting OMNIGRID into an existing web service runs this Skill once; it proposes a complete omnigrid.yaml, and on confirmation writes and git adds the file, leaving the commit to the user. ## Quick Start Ask the assistant to onboard this repository into OMNIGRID and describe your project in one or two sentences when prompted.

Frequently Asked Questions about onboard-omnigrid

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

FAQPage Schema
How do I onboard an existing repository into OMNIGRID?▼

Run the onboard-omnigrid Skill once per project. It asks one open-ended question about the project, runs `omnigrid onboard --desc` to propose a config, and on your confirmation runs with `--write` to write and stage omnigrid.yaml.

What does the OMNIGRID onboarding detector detect in a repo?▼

The detector identifies languages, framework, backend, test runner, and package manager from the live repository. It also scores Harnessability across type safety, module boundaries, framework opinionation, test coverage, and lint baseline.

Does omnigrid onboard commit the configuration file automatically?▼

No. The `--write` flag writes omnigrid.yaml and runs `git add` to stage it, but never commits. The user reviews the staged file and owns the commit.

Can I override values in the proposed omnigrid.yaml?▼

Yes. You can re-run the proposal without `--write` using flags like `--name`, `--source <git-url>`, and `--dist-version <semver>` to correct fields the detector cannot infer, iterating until the proposal looks right.

When should I re-run OMNIGRID onboarding?▼

Re-run it after a significant stack change, because the Harnessability score is a dated snapshot stored in `harnessability.scored_on`, not a live value. Onboarding is otherwise a one-time per-project step.