AgentStack
SKILL verified MIT Self-run

Html Brief Artifact

skill-markoblogo-abvx-agent-skills-html-brief-artifact · by markoblogo

Create a self-contained HTML brief for plans, status updates, PR summaries, incident notes, research explainers, or other structured narrative deliverables. Use when the user wants a polished standalone artifact instead of markdown, slides, or a full frontend.

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-markoblogo-abvx-agent-skills-html-brief-artifact

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Html Brief Artifact? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

HTML Brief Artifact

Produce a standalone HTML brief, not a production app surface.

Review:

  • references/implementation-plan-example.html
  • references/pr-review-example.html
  • references/style-notes.md

Best Fit

  • implementation plans;
  • status reports;
  • PR summaries;
  • incident notes;
  • research explainers;
  • concept briefs.

Not The Best Fit

  • live product UI;
  • long manuals or knowledge bases;
  • spreadsheets or dense data tables better served by other tools;
  • vague "make a webpage" requests without a document goal.

Output Contract

Create one self-contained .html file that:

  • has no build step or external dependency by default;
  • uses clear narrative hierarchy and structured sections;
  • includes dark mode with CSS variables, toggle, persistence, and pre-paint theme setup;
  • reads cleanly on desktop and mobile;
  • stays close to source meaning unless the user asked for a rewrite.

Content Rules

  • Preserve the user's meaning. Improve clarity, not authorship drift.
  • Organize into a small number of sections with clear labels.
  • Use timelines, summary strips, chips, callouts, comparison blocks, or checklists only when they improve scanning.
  • Keep copy concrete and operational.
  • Do not inflate a short brief into a faux strategy deck.
  • If uncertainty exists, label it explicitly instead of smoothing it away.

Visual Rules

  • Favor calm, document-like presentation over app chrome.
  • Use one accent family and disciplined spacing.
  • Let headings carry hierarchy.
  • Use cards, tables, and lists as tools, not defaults.
  • Avoid generic landing-page composition.

Verification

Before finishing:

  1. Open the artifact in a browser.
  2. Check desktop and mobile readability.
  3. Check long lines, wrapping, and section spacing.
  4. Check the theme toggle and persistence.
  5. Check print-like readability if the artifact is document-heavy.
  6. Report inferred structure or content gaps honestly.

Pair with browser-verification when browser tooling is available.

Final Report

Include:

  • output file path;
  • brief type;
  • source material transformed;
  • browser checks run;
  • assumptions made.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.