Workflows to Update
The following workflow generates a discussion report but its template uses h2 (##) headers, contradicting the style guideline stated within the same file:
| Workflow File |
Issues Found |
.github/workflows/github-mcp-structural-analysis.md |
Report template uses ## Executive Summary, ## Usefulness Ratings, etc. (h2), but guideline on line 351 states "Use h3 (###) or lower" |
Required Changes
For .github/workflows/github-mcp-structural-analysis.md, update the report template (inside the <details><summary>Full Structural Analysis Report</summary> block) to replace all ## headers with ### :
Current (non-compliant):
## Executive Summary
## Usefulness Ratings for Agentic Work
## Schema Analysis
## Response Size Analysis
## Tool-by-Tool Analysis
## 30-Day Trend Summary
## Recommendations
## Visualizations
### Response Size by Toolset
Required (compliant):
### Executive Summary
### Usefulness Ratings for Agentic Work
### Schema Analysis
### Response Size Analysis
### Tool-by-Tool Analysis
### 30-Day Trend Summary
### Recommendations
### Visualizations
#### Response Size by Toolset
1. Header Levels
The file already has the correct instruction at line 351:
"Use h3 (###) or lower for all headers in the discussion report to maintain proper document hierarchy."
The template itself must match this instruction.
2. Progressive Disclosure
The outer <details> block is good. No additional changes needed here.
Design Principles (Airbnb-Inspired)
The updated template should create discussions that:
- Build trust through clarity: Most important info immediately visible
- Exceed expectations: Add helpful context, trends, comparisons
- Create delight: Use progressive disclosure to reduce overwhelm
- Maintain consistency: Follow the same patterns as other reporting workflows
Example Reference
See .github/workflows/daily-token-consumption-report.md or .github/workflows/daily-ambient-context-optimizer.md for good examples of structured reporting with compliant h3+ headers.
Agent Task
Update .github/workflows/github-mcp-structural-analysis.md: replace all ## headers inside the report template's <details> block with ### (and any ### sub-headers inside with #### ). The surrounding workflow structure uses ## correctly for the prompt document itself — only the output template inside the markdown code fence needs updating.
Generated by 🔧 Workflow Normalizer · sonnet46 1.1M · ◷
Workflows to Update
The following workflow generates a discussion report but its template uses h2 (
##) headers, contradicting the style guideline stated within the same file:.github/workflows/github-mcp-structural-analysis.md## Executive Summary,## Usefulness Ratings, etc. (h2), but guideline on line 351 states "Use h3 (###) or lower"Required Changes
For
.github/workflows/github-mcp-structural-analysis.md, update the report template (inside the<details><summary>Full Structural Analysis Report</summary>block) to replace all##headers with###:Current (non-compliant):
Required (compliant):
1. Header Levels
The file already has the correct instruction at line 351:
The template itself must match this instruction.
2. Progressive Disclosure
The outer
<details>block is good. No additional changes needed here.Design Principles (Airbnb-Inspired)
The updated template should create discussions that:
Example Reference
See
.github/workflows/daily-token-consumption-report.mdor.github/workflows/daily-ambient-context-optimizer.mdfor good examples of structured reporting with compliant h3+ headers.Agent Task
Update
.github/workflows/github-mcp-structural-analysis.md: replace all##headers inside the report template's<details>block with###(and any###sub-headers inside with####). The surrounding workflow structure uses##correctly for the prompt document itself — only the output template inside the markdown code fence needs updating.