Validate OpenProse Skill Units with mandatory SKILL.md and YAML frontmatter metadata.
npx skills add https://github.com/openprose/prose --skill open-prose-openprose
Please help me install this Agent Skill. Skill: open-prose Source: https://github.com/openprose/prose/tree/main/skills/open-prose Command: npx skills add https://github.com/openprose/prose --skill open-prose-openprose
Identify and validate Skill Units by enforcing a mandatory SKILL.md at the root and exposing a YAML frontmatter with name and description.
Start by examining the built-in SKILL.md and prose.md to learn how to define agents and sessions, then run an example program from the examples directory.
High-intent search queries and answers about installing and using this skill.
Validating YAML frontmatter metadata for AI workflow automation units requires a mandatory SKILL.md file at the root directory. This file must expose standardized name and description fields to ensure machine discovery and proper session orchestration.
A Skill Unit in AI session orchestration is a self-contained, discovery-driven package composed of a SKILL.md file and optional resources. It enables consistent activation and on-demand loading of scripts, references, and assets during automated workflows.
Standardizing dependencies and components metadata across automation workflows involves enforcing a mandatory SKILL.md file at the repository root. This structures dependency tracking and toxicity checks into a standardized YAML format for reliable machine discovery.
Yes, a SKILL.md file at the root is strictly required to use OpenProse automation workflows. It serves as the entry point for validation, exposing the YAML frontmatter necessary for orchestrating AI sessions and discovering optional assets.
Yes, you can include optional scripts, references, and assets alongside the mandatory SKILL.md file in a YAML frontmatter validated workflow. These resources accompany the core file to support on-demand execution during AI session orchestration.
Enforcing mandatory SKILL.md for workflow discovery limits unit activation to directories strictly containing this root file. Units lacking the required YAML frontmatter structure for name and description will fail machine discovery and orchestration validation.
tnezInitialize the .docent directory structure and configuration for new projects.
TrevokeDispatch per-task subagents and enforce two-stage reviews for plan execution.
vibbsScan project artifact directories to generate status summaries and validate gate readiness.
fcouryGenerate structured PRDs with markdown and prd.json output.
