open-as-html

Included with Lifetime

$97 forever

Convert markdown or conversation output to a clean HTML file and open it in the browser. Use when the user wants to copy content into Google Docs, share formatted output, preview content as a web page, or says things like "open that as HTML," "make that pasteable," "put that in a doc," or "open that in the browser."

Web Dev

What this skill does


# Open as HTML

Convert content from the conversation into a styled HTML file and open it in the default browser for easy copy-paste into Google Docs or other rich text editors.

## Arguments

- `$0`: (optional) description of what content to convert. If not provided, convert the most recent substantive output from the conversation.

## Workflow

1. Identify the content to convert — either specified by the user or the most recent substantive output.
2. Convert it to clean, semantic HTML with this structure:
   - Use `<h1>`, `<h2>`, `<h3>` for headings
   - Use `<ol>`/`<ul>` for lists
   - Use `<em>` and `<strong>` for emphasis
   - Use `<table>` for any tabular data
   - Use `<pre><code>` for code blocks
3. Wrap in a minimal HTML document with basic styling:
   ```html
   <!DOCTYPE html>
   <html>
   <head>
   <style>
     body { font-family: Arial, sans-serif; max-width: 700px; margin: 40px auto; padding: 0 20px; }
     li { margin-bottom: 8px; }
     table { border-collapse: collapse; margin: 16px 0; }
     th, td { border: 1px solid #ccc; padding: 8px 12px; text-align: left; }
     pre { background: #f5f5f5; padding: 12px; border-radius: 4px; overflow-x: auto; }
   </style>
   </head>
   <body>
   <!-- content here -->
   </body>
   </html>
   ```
4. Write to `/tmp/claude-output.html`.
5. Open with: `xdg-open /tmp/claude-output.html 2>/dev/null || open /tmp/claude-output.html 2>/dev/null`

Files: 1

Size: 1.8 KB

Complexity: 12/100

Category: Web Dev

Source: https://github.com/czue/agent-tools/tree/main/skills/open-as-html

Related in Web Dev

generating-lwc-components

Included

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.

Web Devscripts

document-processor-api

Included

Process documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.

Web Devscripts

nutrient-document-processing

Included

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.

Web Devscripts

accelint-nextjs-best-practices

Included

Next.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.

Web Devscripts