Manage AI output style files with frontmatter schema across global and project directories.
npx skills add https://github.com/Dwsy/agent --skill output-style-manager
Please help me install this Agent Skill. Skill: output-style-manager Source: https://github.com/Dwsy/agent/tree/main/skills/output-style-manager Command: npx skills add https://github.com/Dwsy/agent --skill output-style-manager
Centralizes reading, creation, and organization of AI output style definitions stored in local directories, enabling consistent prompts and responses.
Create or update a style named "default" under ~/.pi/agent/output-styles and set it as the active style to apply it to future AI responses.
High-intent search queries and answers about installing and using this skill.
You can manage AI output styles by reading, creating, and activating style files in global or project-specific directories. This enforces consistent runtime formatting across environments by applying a standardized style to future responses.
The required frontmatter schema for AI output style files includes the fields name, description, and keepCodingInstructions. This metadata structure validates the style file and surfaces necessary configuration for tooling integration.
To activate a markdown style, list the available styles from your local directories and select one to set as active. The system applies this chosen style configuration to subsequent AI responses within that specific context.
Yes, you can create a custom style file under the local output-styles directory with specific formatting rules. Activating this configuration standardizes the assistant tone for customer support across all future sessions.
The output style manager supports both global and project-specific directories, reading style files from both locations. This ensures you can apply broad formatting rules globally while overriding them with localized project configurations.
Project-specific output styles require proper frontmatter validation including name, description, and keepCodingInstructions. If the schema is invalid or the file is not explicitly activated, the system defaults to the active global style configuration.
jykimFormat, validate and fix Obsidian wiki links to conform with vault conventions.
ToXMonExtract style profiles and validate text against YAML style guides.
gabriellpequenoEnforce external UI guideline compliance during front-end design reviews and critiques.
ChaoTzuJungManage multi-thread conversations in assistant-ui with CRUD operations.
