skills.rest
dr-robert-li
dr-robert-liCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reporting

Structure WordPress diagnostic findings into audience-tailored reports with severity ratings.

27|1|Updated Feb 16, 2026
Search Tags:#documentation#technical writing#communication#reporting#diagnostics#action logging
One-click install
npx skills add https://github.com/dr-robert-li/cowork-wordpress-expert --skill reporting-dr-robert-li
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reporting
Source: https://github.com/dr-robert-li/cowork-wordpress-expert/tree/main/skills/reporting
Command: npx skills add https://github.com/dr-robert-li/cowork-wordpress-expert --skill reporting-dr-robert-li

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized, clear, and actionable framework for reporting diagnostic findings, ensuring that information is communicated effectively to both technical and non-technical stakeholders.

Core Features & Use Cases

  • Structured Reporting: Generates detailed reports for each phase of a diagnostic process (Discovery, Diagnosis, Remediation, Testing, Documentation).
  • Audience-Specific Communication: Tailors explanations for both technical experts and non-technical users, using plain language and analogies where appropriate.
  • Severity Ratings: Assigns clear severity levels (Critical, High, Medium, Low, Informational) to findings.
  • Action Logging: Maintains a detailed log of all actions taken during a diagnostic session.
  • Use Case: After diagnosing a website performance issue, use this Skill to generate a comprehensive report that explains the problem to the client (site owner) and provides precise technical steps for the development team to implement the fix.

Quick Start

Use the reporting skill to structure the findings from a recent website diagnosis into a clear report.

Frequently Asked Questions about reporting

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

FAQPage Schema
How do I structure technical diagnostic findings into a report for non-technical stakeholders?▼

Structure technical diagnostic findings into audience-tailored reports that translate complex technical details and remediation steps into plain language and analogies for non-technical stakeholders. This ensures clear communication of business impact and recommended fixes.

What is the best way to log actions during a WordPress diagnostic session?▼

The best way to log actions during a WordPress diagnostic session is to maintain a detailed, structured action log alongside your reporting phases. This records all discovery, diagnosis, remediation, testing, and documentation steps to ensure full accountability and traceability.

How do I assign severity ratings to website issues in a technical report?▼

Assign severity ratings to website issues by categorizing findings into defined levels: Critical, High, Medium, Low, and Informational. This severity rating framework helps prioritize remediation efforts and clarifies the urgency of each technical issue for stakeholders.

Can I generate a single report that covers multiple phases like discovery, diagnosis, and remediation?▼

Yes, you can generate a single comprehensive report covering multiple phases including discovery, diagnosis, remediation, testing, and documentation. This structured reporting approach ensures continuity and tracks the entire lifecycle of a technical issue within one document.

Does this reporting framework work for communicating WordPress performance issues to a development team?▼

Yes, this reporting framework effectively communicates WordPress performance issues to a development team by providing precise technical details and recommended fixes. It simultaneously explains the business impact to site owners using audience-specific communication.

What should a technical diagnostic report include to ensure recommended fixes are actionable?▼

A technical diagnostic report should include audience-tailored explanations, clear severity ratings, a detailed action log, and structured findings across all diagnostic phases. This combination ensures recommended fixes are actionable for technical teams and clear for non-technical clients.

Related Skills

Explore More Content & Communication Skills→
dr-robert-lidr-robert-li
27

report-generator

Compile WordPress diagnostic findings into structured markdown reports with health grades.

Community
Advanced
FavioVazquezFavioVazquez
59

audit

Audits UI designs for accessibility, performance, and visual issues.

Community
Advanced
tuliopc23tuliopc23

axiom-metrickit-ref

Reference Apple's MetricKit framework for parsing MXMetricPayload and MXDiagnosticPayload data.

Community
Intermediate
khoabdkhoabd

pr-report

Analyze pull requests and generate severity-ordered HTML or Markdown review reports.

Community
Advanced