operating-pack-composer

Compose minimal Markdown Operating Packs from verified project instructions and conventions.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/rickvang/Persona-Library --skill operating-pack-composer-rickvang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: operating-pack-composer
Source: https://github.com/rickvang/Persona-Library/tree/main/.agents/skills/operating-pack-composer
Command: npx skills add https://github.com/rickvang/Persona-Library --skill operating-pack-composer-rickvang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project rules, architecture notes, conventions, and constraints are often scattered across repositories, making them hard to navigate and reuse. This Skill compiles that verified context into a minimal, file-based Operating Pack with a clear AGENTS.md entrypoint. ## Core Features & Use Cases - Bounded Pack Composition: Builds only the Markdown files the evidence justifies, such as AGENTS.md, ARCHITECTURE.md, CONVENTIONS.md, TESTING.md, SECURITY.md, and workflows/*.md. - Context Classification: Distinguishes verified rules, best practices, local conventions, inference, and unresolved gaps so readers know the authority of each statement. - Proposal and Update Modes: Returns a file plan without mutating anything in proposal mode, or applies only an authorized named change while preserving revision history. - Use Case: A team adopting a new repository asks the AI to gather its architecture, conventions, and validation commands into a navigable Operating Pack, then hands off to operating-pack-reconciliation after the durable change. ## Quick Start Use $operating-pack-composer to compile a minimal AGENTS.md-led Operating Pack from this repository's verified context and constraints.

Frequently Asked Questions about operating-pack-composer

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

FAQPage Schema
How do I create an Operating Pack for a project repository?▼

Confirm the outcome, domain, target location, authorization, and source material first, then build the smallest useful structure with AGENTS.md as the entrypoint. Add files like ARCHITECTURE.md or CONVENTIONS.md only when the domain has supported content needing that separation.

What files should an Operating Pack contain?▼

A minimal pack is acceptable; AGENTS.md is the required entrypoint stating scope, precedence, and navigation. ARCHITECTURE.md, CONVENTIONS.md, TESTING.md, SECURITY.md, ACCESSIBILITY.md, and workflows/*.md are recommended only when evidence justifies them.

When should I use operating-pack-research instead of composing a pack?▼

Use operating-pack-research when evidence or scope is not yet clear. The composer runs only after an accepted research proposal identifies a real need, or when an existing pack needs a bounded, authorized composition update.

Can an Operating Pack execute workflows or grant tool permissions?▼

No. A pack is not an execution runtime, MCP server, installer, or Playbook. It holds contextual rules only; reusable expertise stays in Skills, execution and permission stay in Tools, and Playbooks coordinate outcomes.

Does the composer modify files without authorization?▼

No. In proposal mode it returns a file plan without mutating live records or files. For an authorized update it applies only the named change, preserves revision history, and then hands off to operating-pack-reconciliation.