blue-org-context

Name: blue-org-context
Availability: InStock
Author: superviber

Read org.yaml and domain.yaml to display organization context.

1|1|Updated Mar 11, 2026

Search Tags:#jira #hook #session-start #repos #org-context #org.yaml #domain.yaml

Ready to run

npx skills add https://github.com/superviber/blue --skill blue-org-context

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blue-org-context
Source: https://github.com/superviber/blue/tree/main/skills/blue-org-context
Command: npx skills add https://github.com/superviber/blue --skill blue-org-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill exposes the current organizational context to guide decisions and ensure alignment across repos and projects by reading org.yaml and domain.yaml.

Core Features & Use Cases

Display org name and PM repository location to orient new contributors.
List all repos with clone status and domain areas and component mappings for quick assessment.
Show Jira project configuration and indicate where to create RFCs (org-wide vs repo-specific) for governance.
Automatically activates during session-start to provide context at the start of work.

Quick Start

Run blue hook session-start to display the current org context.

Frequently Asked Questions about blue-org-context

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

FAQPage Schema

How do I display organization context from org.yaml during a session start?▼

To display organization context, run the session-start hook to read org.yaml and domain.yaml from your repository root, outputting org name, repository clone status, Jira configuration, and domain mappings for immediate workspace orientation.

What is the purpose of an org.yaml file in a repository?▼

An org.yaml file defines organization-wide context for a repository, specifying the org name, PM repository location, and Jira project configuration to orient contributors and guide governance decisions like RFC placement.

How do I check Jira project configuration and RFC placement rules for my repos?▼

You can check Jira project configuration and RFC placement by reading org.yaml from the repository root, which indicates where to create org-wide versus repo-specific RFCs for governance and alignment.

Do I need a domain.yaml file to view complete organization context mappings?▼

You need domain.yaml optionally to view complete organization context mappings, while org.yaml at the repository root is required to expose basic org context including repos and component mappings.

Can I list all repos with clone status and domain areas automatically?▼

Yes, you can list all repos with clone status and domain areas automatically by triggering the session-start hook, which reads org.yaml and domain.yaml to provide quick assessment of repository mappings.

What are the limitations of using org.yaml for organizational context?▼

Using org.yaml for organizational context requires the file to exist at the repository root, and without the optional domain.yaml file, complete domain mappings will not be displayed during the session-start hook.