om-setup-agent-pipeline

Configures the shared agentic pipeline config, tracker descriptors, and project docs for a repository.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill om-setup-agent-pipeline-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-setup-agent-pipeline
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/om-setup-agent-pipeline
Command: npx skills add https://github.com/tkogut/agents-os-core --skill om-setup-agent-pipeline-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent skills in a repository need a single, committed source of truth for validation commands, tracker integration, label taxonomy, and QA gates. Without it, every skill fails or improvises its own settings. This Skill inspects the repository, asks a few questions, and writes .ai/agentic.config.json plus the supporting docs every other skill reads. ## Core Features & Use Cases - Auto-detected configuration: Resolves the default branch, detects validation commands from package.json scripts, Makefiles, or language conventions (Cargo, Go, Python), and writes the committed .ai/agentic.config.json schema. - Tracker and browser descriptor installation: Installs shipped descriptors for GitHub, Linear, or Jira trackers and agent-browser or Playwright browser providers, with refresh/merge/keep protection for existing files. - Project doc generation: Generates missing SDLC.md, AGENTS.md (with a task-routing table), CODE_REVIEW.md, and BACKWARD_COMPATIBILITY.md, each derived from the actual repository and never overwriting existing files. - Use Case: After installing a collection of agent workflow skills into a fresh repository, run this Skill once so every other skill can load its config, tracker operations, and label taxonomy instead of stopping with a missing-config error. ## Quick Start Ask the agent to run the setup-agent-pipeline skill to configure this repository's agentic pipeline, or pass --defaults to write the auto-detected config without questions.

Frequently Asked Questions about om-setup-agent-pipeline

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

FAQPage Schema
How do I configure agent skills for a new repository?▼

Run the om-setup-agent-pipeline skill first. It inspects the repo, asks about tracker, labels, and QA gate preferences, then writes .ai/agentic.config.json, which every other skill in the collection loads before doing any work.

What is .ai/agentic.config.json used for?▼

It is the committed, team-shared configuration file that stores the base branch, tracker provider, validation commands, label taxonomy, QA gate setting, and directory paths. Every skill in the collection reads it at startup and stops with a setup pointer when it is missing.

Does the setup skill support Linear or Jira instead of GitHub issues?▼

Yes. The tracker field selects a descriptor: github, linear, or jira ship with the collection. Linear and Jira own issues but delegate PR, review, and CI operations to a required github.md companion descriptor, which setup installs alongside.

Will running setup overwrite my existing AGENTS.md or SDLC.md?▼

No. The skill generates SDLC.md, AGENTS.md, CODE_REVIEW.md, and BACKWARD_COMPATIBILITY.md only when they are missing, and shows each generated document before writing. Existing process docs are never touched and are used as-is.

Can I run the setup non-interactively in an autonomous workflow?▼

Yes. Pass --defaults to skip all questions and write the auto-detected config without confirmation. Other skills auto-invoke setup this way during unattended runs when they find the config missing.

What happens when a referenced skill is not installed?▼

Setup runs a cross-skill coverage check that scans installed skills for name and file references to other collection skills. It prints a paste-ready npx skills add command for anything missing and re-checks after installation.