Skip to content
Back to skills

Reporting

ASecurity

Report formatting guidelines for gh-aw workflows (header levels, collapsible details, run-ID links)

  • 5,344 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 2, 2026
ai-agentsgit

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add github/gh-aw --skill reporting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Reporting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Reporting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/github-reporting-gh-aw/badge)](https://www.skillsdirectory.com/skills/github-reporting-gh-aw)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Report formatting guidelines for gh-aw workflows (header levels, collapsible details, run-ID links)
---

- Use `###` (or lower) headers only.
- Keep summary and critical actions visible; move long detail into `<details>` blocks.
- Structure reports as: overview → key metrics/issues → collapsible detail → next actions.
- Format run IDs as links: `[§12345](https://github.com/owner/repo/actions/runs/12345)`.
- Include up to 3 most relevant run URLs at end under `**References:**`.
- Do NOT add footer attribution (system adds automatically).

Files in this skill

  • SKILL.md625 B
  • ssl.json2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.