agentleFS
ethosagentethosagent/ethos/skills/document/make-html-report/SKILL.md

make-html-report

Skill22 starsChanged 10 days agoMITView on GitHub

Generate a self-contained HTML report file with all CSS inline in a <style> block and no external dependencies. Uses write_file only — no CLI tools required. Output is a single .html file written to the working directory as <slug>.html that can be opened directly in any browser.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use a single <style> block in <head> — no external stylesheets, no CDN links.

    line 44
  2. Distinctive:

    Use CSS variables for theming (see palette below).

    line 45
  3. Very specific:

    Use write_file to write the complete HTML to a relative path, which resolves inside the working directory:

    line 157
  4. Distinctive:

    Write the complete document in one pass — do not write partial HTML and patch it.

    line 165
  5. Distinctive:

    All generated files go to the working directory.

    line 184
  6. Distinctive:

    Always tell the user the exact output path and that they can open it in any browser.

    line 185
  7. Very specific:

    All CSS must be inline in a single <style> block — no <link> tags, no CDN, no @import url(...).

    line 186
  8. Very specific:

    Always include <meta charset="UTF-8"> and a descriptive <title>.

    line 187

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Make HTML Report

Generate a self-contained HTML report with inline CSS. No installation required — this skill uses write_file only. The output is a single .html file written to the working directory as <slug>.html that opens in any browser without internet access.

When to use this skill

  • User asks for an HTML report, a web-based report, a formatted report to open in a browser, or an export they can view locally.
  • User says "make an HTML version of this", "I want to open this in a browser", "generate a report page".
  • User needs a document with tables, sections, and readable formatting but does not need PDF.

When NOT to use this skill

  • User explicitly wants a PDF — use make-pdf.
  • User wants a spreadsheet — use export-excel or export-csv.
  • User wants a chart — use make-chart (optionally embed the PNG in the HTML report afterward).
  • The output needs to be emailed as an attachment where PDF is more appropriate.

HTML template contract

All reports must:

  1. Use a single <style> block in <head> — no external stylesheets, no CDN links.
  2. Use CSS variables for theming (see palette below).
  3. Be responsive (max-width: 960px; margin: 0 auto on the body or a wrapper).
  4. Include a <meta charset="UTF-8"> and <meta name="viewport" content="width=device-width, initial-scale=1.0">.
  5. Include a <title> matching the report name.

Colour palette (CSS variables)

:root {
  --accent:   #2563eb;  /* primary blue — links, headings, borders */
  --bg:       #f8fafc;  /* page background */
  --surface:  #ffffff;  /* card / table background */
  --text:     #1e293b;  /* body text */
  --muted:    #64748b;  /* secondary text, captions */
  --border:   #e2e8f0;  /* dividers, table borders */
  --success:  #16a34a;  /* positive values */
  --danger:   #dc2626;  /* negative values, errors */
}

Minimal starter template

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Report Title</title>
  <style>
    :root {
      --accent:  #2563eb;
      --bg:      #f8fafc;
      --surface: #ffffff;
      --text:    #1e293b;
      --muted:   #64748b;
      --border:  #e2e8f0;
      --success: #16a34a;
      --danger:  #dc2626;
    }
    * { box-sizing: border-box; margin: 0; padding: 0; }
    body {
      font-family: system-ui, -apple-system, sans-serif;
      font-size: 14px;
      line-height: 1.6;
      color: var(--text);
      background: var(--bg);
      padding: 32px 16px;
    }
    .wrapper { max-width: 960px; margin: 0 auto; }
    h1 { font-size: 24px; color: var(--accent); margin-bottom: 4px; }
    h2 { font-size: 18px; margin: 32px 0 12px; border-bottom: 1px solid var(--border); padding-bottom: 6px; }
    .meta { color: var(--muted); font-size: 12px; margin-bottom: 32px; }
    .card {
      background: var(--surface);
      border: 1px solid var(--border);
      border-radius: 8px;
      padding: 20px;
      margin-bottom: 24px;
    }
    table { width: 100%; border-collapse: collapse; font-size: 13px; }
    th {
      background: var(--bg);
      border: 1px solid var(--border);
      padding: 8px 12px;
      text-align: left;
      font-weight: 600;
      color: var(--muted);
      text-transform: uppercase;
      letter-spacing: 0.04em;
    }
    td { border: 1px solid var(--border); padding: 8px 12px; }
    tr:nth-child(even) td { background: var(--bg); }
    .positive { color: var(--success); font-weight: 600; }
    .negative { color: var(--danger); font-weight: 600; }
    .badge {
      display: inline-block;
      padding: 2px 8px;
      border-radius: 9999px;
      font-size: 11px;
      font-weight: 600;
      background: #dbeafe;
      color: var(--accent);
    }
  </style>
</head>
<body>
  <div class="wrapper">
    <h1>Report Title</h1>
    <p class="meta">Generated <!-- date --></p>

    <div class="card">
      <h2>Section</h2>
      <!-- content -->
    </div>
  </div>
</body>
</html>

Workflow

Step 1: Design the report structure

From the user's content, identify:

  • Report title and generation date.
  • Sections (one <div class="card"> per logical section).
  • Tables (rows and columns).
  • Any numeric values that need positive/negative colouring (use .positive / .negative classes).

Step 2: Write the HTML file

Use write_file to write the complete HTML to a relative path, which resolves inside the working directory:

<slug>.html

Where <slug> is a lowercase-hyphenated identifier derived from the report title (e.g. q2-summary, onboarding-checklist).

Write the complete document in one pass — do not write partial HTML and patch it.

Step 3: Confirm to the user

Tell the user:

"HTML report created at: <slug>.html in the working directory — visible in the Documents tab. Open it in any browser — no internet connection needed."

Anti-patterns

  • Do not link to external CSS frameworks (Bootstrap, Tailwind CDN) — the file must be self-contained.
  • Do not use JavaScript unless the user explicitly asks for interactivity — keep reports static.
  • Do not use inline style= attributes for anything the CSS classes already cover — use the defined classes.
  • Do not omit the <meta charset="UTF-8"> — non-ASCII characters (accented letters, currency symbols) will render incorrectly without it.
  • Do not deviate from the colour palette without a user request — consistency across reports matters.

Hard rules

  • All generated files go to the working directory. Always write a relative path — never write outside the working directory.
  • Always tell the user the exact output path and that they can open it in any browser.
  • All CSS must be inline in a single <style> block — no <link> tags, no CDN, no @import url(...).
  • Always include <meta charset="UTF-8"> and a descriptive <title>.
  • The slug must be lowercase, hyphen-separated, and contain no spaces or special characters.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.