decocms/mcps/generate-report
Claude Code and agent skill by decocms/mcps
- community
Checking that the SKILL.md file is still in the repository.
Generate a structured Markdown report with YAML frontmatter for repository health monitoring. Use when the user asks to create a report, health check, audit, scan result, or status update for a repository.
Install
npx vskill@latest install decocms/mcps/generate-reportSKILL.md
Generate Report
You are writing a report as a Markdown file with YAML frontmatter. Follow these instructions exactly.
File format
Every report is a .md file. Metadata goes in YAML frontmatter delimited by ---. Any markdown content below the frontmatter becomes the report body.
Frontmatter fields
| Field | Required | Type | Description | ||||
|---|---|---|---|---|---|---|---|
title | Yes | string | Human-readable report title. | ||||
category | Yes | string | Category for filtering (e.g., performance, security, quality). See category list below. | ||||
status | Yes | `"passing" \ | "warning" \ | "failing" \ | "info"` | Overall health outcome. | |
summary | Yes | string | One-line summary of findings. Keep it concise — this is shown in list views. | ||||
updatedAt | Yes | string | ISO 8601 timestamp of when the report was generated (YYYY-MM-DDTHH:mm:ssZ). | ||||
source | Optional | string | Name of the agent or service that generated this report (e.g., lighthouse, security-scanner). | ||||
tags | Optional | string[] | Free-form tags for filtering (e.g., [homepage, mobile, ci]). | ||||
sections | Optional | ReportSection[] | Structured content sections (metrics, tables, markdown). See section types below. |
Always provide title, category, status, summary, and updatedAt. Do not leave them empty or omit them.
File placement and tagging
Place report files inside a reports/ directory. Subdirectories automatically become tags on the report.
Directory-derived tags are merged with any tags declared in frontmatter, deduplicated.
Choose a filename that is a short, descriptive, kebab-case slug (e.g., dependency-scan.md, homepage-vitals.md).
Section types
Sections appear in the order listed in frontmatter. The markdown body (if present) is appended as a final section after all frontmatter sections. Put the most important information first.
Markdown section
Free-form text rendered as GitHub Flavored Markdown.
Metrics section
Key performance indicators with optional deltas and per-metric status.
Each metric item:
| Field | Required | Type | Description | ||||
|---|---|---|---|---|---|---|---|
label | Yes | string | Metric name (e.g., "LCP", "Coverage"). | ||||
value | Yes | `number \ | string` | Current value. | |||
unit | Optional | string | Unit of measurement (e.g., "s", "ms", "%", "score"). | ||||
previousValue | Optional | `number \ | string` | Previous value for delta comparison. | |||
status | Optional | `"passing" \ | "warning" \ | "failing" \ | "info"` | Status of this individual metric. |
Table section
Tabular data with column headers.
Status reference
| Status | When to use | |
|---|---|---|
passing | Everything is within acceptable thresholds. | |
warning | Some metrics are degraded or approaching thresholds. | |
failing | Critical issues that need immediate attention. | |
info | Informational report with no pass/fail judgment. |
Category conventions
| Category | Use case | |
|---|---|---|
performance | Web vitals, bundle size, load times. | |
security | Vulnerability scans, dependency audits. | |
accessibility | WCAG compliance, axe-core results. | |
seo | Meta tags, structured data, crawlability. | |
quality | Code quality, test coverage, lint results. | |
uptime | Health checks, availability monitoring. | |
compliance | License audits, policy checks. |
Git workflow
Reports are stored on a dedicated git branch (typically reports).
Committing a report
Creating the branch for the first time
Additional resources
- For complete examples of different report types, see examples.md
Your task
Based on the user's request ($ARGUMENTS), generate a complete report file following the format above. Analyze the relevant code, data, or context in the repository before writing the report. Make sure the report contains real, accurate data — not placeholder values.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckinggithub-repo-reports-plugin/skills/generate-report/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/decocms/mcps/generate-report)