report

Generate Discord summaries and full reports from technical findings.

Updated Jan 27, 2026

Search Tags:#templates #reporting #discord #summaries #test-results #technical-report

Ready to run

npx skills add https://github.com/IstoraMandiri/etc-nexus --skill report-istoramandiri

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: report
Source: https://github.com/IstoraMandiri/etc-nexus/tree/main/.claude/skills/report
Command: npx skills add https://github.com/IstoraMandiri/etc-nexus --skill report-istoramandiri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams transform technical findings, test results, and analyses into structured, shareable reports, reducing manual drafting time and ensuring consistency.

Core Features & Use Cases

Discord-ready summaries: Generate concise, readable summaries suitable for quick sharing.
Full report generation: Produce detailed reports with sections for context, findings, root cause, impact, and recommendations.
Standardized templates: Enforce a consistent structure and naming convention for reports stored under reports/YYMMDD_SLUG.md.
Use case: When new test results arrive, generate both a short Discord summary and a comprehensive report for archival.

Quick Start

Summarize the latest test findings into a Discord-ready summary and save a full report to reports/YYMMDD_SLUG.md.

Frequently Asked Questions about report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a structured technical report from test results?▼

To generate a structured technical report from test results, this Skill transforms raw findings into standardized documents. It enforces sections for executive summary, context, findings, root cause, impact, and recommendations, saving the output to reports/YYMMDD_SLUG.md.

Can I create a Discord summary from QA findings automatically?▼

Yes, you can create a Discord summary from QA findings automatically. The Skill generates concise, readable summaries specifically formatted for quick sharing on Discord alongside the full detailed technical report.

What sections are required in a standardized technical report?▼

Required sections in a standardized technical report include executive summary, context, findings, root cause, impact, and recommendations. The Skill enforces this consistent structure to reduce manual drafting time for QA and test automation contexts.

What is the best way to format technical findings for team archival?▼

The best way to format technical findings for archival is using a standardized naming convention. This Skill stores generated documents under reports/YYMMDD_SLUG.md, ensuring full reports are consistently structured and easily retrievable for future review.

Do I need defined frontmatter to generate a test automation report?▼

Yes, you need defined frontmatter to generate a test automation report. The Skill requires a specified frontmatter containing the name and description before producing the full document and Discord summary outputs.