agentsclimarketplace
Sign in

Html brief artifact

Skill markoblogo/abvx-agent-skills/skills/html-brief-artifact

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.From its SKILL.md

Install
npx -y skills add markoblogo/abvx-agent-skills --skill html-brief-artifact

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, 445 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 5 files

11.1 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,861. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.