org-config

Configure Topia organization policy files from structured team interview inputs.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill org-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: org-config
Source: https://github.com/linenoize/topia/tree/main/skills/org-config
Command: npx skills add https://github.com/linenoize/topia --skill org-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a generic Topia organization template into a real, team-specific policy file so guardian and readiness enforce the rules your group actually uses.

Core Features & Use Cases

  • Policy Interview and Setup: Collects org name, team shape, governance level, review rules, and deployment preferences.
  • Safe Policy Authoring: Updates the project .topia/org/org.md file while preserving the required parser sections and frontmatter.
  • Team and Solo Workflows: Supports both solo developers and multi-team organizations that need consistent review, security, and release governance across repositories.

Quick Start

Use the org-config skill to interview the team and write a customized .topia/org/org.md policy file for Topia.

Frequently Asked Questions about org-config

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

FAQPage Schema
How do I set up a Topia organization policy file for my team?

To set up a Topia organization policy file, you provide structured team interview inputs detailing your org name, governance level, and review rules to automatically generate a customized .topia/org/org.md file.

How does an org policy file enforce governance and approval rules?

An org policy file enforces governance and approval rules by serving as the configuration source for Topia's guardian and readiness modules, which read the policy to block non-compliant finalize flows and deployments.

Can I migrate a generic Topia policy template to a custom multi-team configuration?

Yes, you can migrate a generic Topia policy template to a custom multi-team configuration through template-to-custom policy migration, which safely updates .topia/org/org.md while preserving required parser sections and frontmatter.

Does Topia policy setup work for solo developer repositories?

Yes, Topia policy setup works for solo developer repositories by supporting solo workflows during the interview process, allowing individual developers to configure custom review, security, and release governance rules in .topia/org/org.md.

What happens if required parser sections are missing from the org policy file?

If required parser sections are missing, safe policy authoring preserves these required sections and frontmatter during updates, ensuring guardian and readiness modules can still parse and enforce your team's approval rules.

What is the best way to turn team policies into enforced hooks in Topia?

The best way to turn team policies into enforced hooks is configuring the .topia/org/org.md file from structured team interview inputs, translating your governance settings and approval rules into configurations that Topia enforces.