output-style-setup
Skill66 starsChanged 7 months agoApache-2.0View on GitHub
Install bkit output styles to your project or user directory. Copies output style files from bkit plugin to the appropriate location.
In this repository42 other files it gives its agents.
- auditSkill
- batchSkill
- bkend-authSkill
- bkend-cookbookSkill
- bkend-dataSkill
- bkend-guidesSkill
- bkend-mcpSkill
- bkend-quickstartSkill
- bkend-securitySkill
- bkend-storageSkill
- bkit-rulesSkill
- bkit-templatesSkill
- btwSkill
- code-reviewSkill
- controlSkill
- deploySkill
- desktop-appSkill
- development-pipelineSkill
- dynamicSkill
- enterpriseSkill
- gemini-cli-learningSkill
- loopSkill
- mobile-appSkill
- pdcaSkill
- phase-1-schemaSkill
- phase-2-conventionSkill
- phase-3-mockupSkill
- phase-4-apiSkill
- phase-5-design-systemSkill
- phase-6-ui-integrationSkill
- phase-7-seo-securitySkill
- phase-8-reviewSkill
- phase-9-deploymentSkill
- plan-plusSkill
- pm-discoverySkill
- qa-phaseSkill
- rollbackSkill
- simplifySkill
- skill-createSkill
- skill-statusSkill
- starterSkill
- zero-script-qaSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 62
After installation, run /output-style-setup verify to confirm:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Output Style Setup Skill
Install and configure bkit output styles for your project. Output styles control the formatting and structure of all bkit-generated responses.
Usage
/output-style-setup
/output-style-setup list
/output-style-setup install <style-name>
/output-style-setup verifyAvailable Styles
| Style | Description | Best For |
standard | Default bkit formatting with tables and sections | General development |
compact | Minimal output, reduced whitespace | CI/CD pipelines |
detailed | Verbose output with full context | Documentation work |
executive | Summary-first with key metrics highlighted | PM and stakeholder reviews |
Installation Steps
- List available styles: Shows all styles bundled with bkit
- Select a style: Choose the style that fits your workflow
- Install: Copies style configuration to
.gemini/context/output-style.md - Verify: Confirms the style is active and correctly loaded
Installation Targets
- Project-level (default):
.gemini/context/output-style.md - User-level:
~/.gemini/context/output-style.md
Project-level styles override user-level styles.
Verification
After installation, run /output-style-setup verify to confirm:
- Style file exists at the expected path
- Style file is valid and parseable
- Style is being loaded by Gemini context system
- Sample output matches expected formatting
Custom Styles
You can create custom styles by placing a markdown file in .gemini/context/output-style.md with the following structure:
## Output Style: <your-style-name>
### Response Structure
(Define section ordering and required sections)
### Formatting Rules
(Define table formats, code block usage, heading levels)
### Tone and Language
(Define formality level, technical depth)Reset
To reset to the default style:
/output-style-setup install standardDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.