reporting
Applies HTML details and summary tag formatting to technical reports.
Install
mkdir -p .claude/skills/reporting && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6509" && unzip -o skill.zip -d .claude/skills/reporting && rm skill.zipInstalls to .claude/skills/reporting
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Format reports with HTML details/summary blocks for readable output.Key capabilities
- →Format reports with collapsible sections
- →Wrap content in HTML details tags
- →Use summary tags for titles
- →Structure content with markdown headers
How it works
It wraps report sections in HTML details and summary elements to allow users to expand or collapse content.
Inputs & outputs
When to use reporting
- →Formatting complex technical reports
- →Collapsing long sections of documentation
- →Standardizing report output styles
About this skill
- 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).
When not to use it
- →When content is too short to collapse
- →When the target platform does not support HTML tags
Limitations
- →Depends on markdown renderer support for HTML
- →Limited to basic details/summary structure
How it compares
It improves readability of long reports by providing a collapsible structure instead of a flat document.
Compared to similar skills
reporting side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| reporting (this skill) | 1 | 6mo | No flags | Beginner |
| ml-paper-writing | 48 | 9mo | Review | Advanced |
| docs-review | 10 | 11mo | No flags | Beginner |
| claude-md-improver | 21 | 10mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by githubnext
View all by githubnext →You might also like
ml-paper-writing
davila7
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
docs-review
metabase
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
claude-md-improver
anthropics
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.
update-docs
vercel
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
wiki-architect
microsoft
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.