Editorial Card Screenshot
Generate responsive editorial HTML cards and browser-rendered PNG screenshots
- What
- Generate responsive editorial HTML cards and browser-rendered PNG screenshots
- Cost
- Free
- Needs
- Chrome/Chromium installed on your machine (required for the browser-rendered screenshot step). No account, no API keys. Most useful if you publish explainers, quotes, stats, or social visuals.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — produces beautiful information cards the reliable way: it generates clean, responsive editorial HTML cards (stats, quotes, explainers, social-ready visuals) and then renders them to PNG screenshots with a real headless browser, so what you see in the file is exactly what the layout produced — no hallucinated pixels, no approximated mockups. The HTML-first approach means you can tweak text and styling and re-render until it's right. Discovered via skills.sh, listed here with credit to its creator by @shaom. Honest caveats: requires a working Chrome/Chromium for the screenshot step — that's the core of the method, not an optional extra; it makes information cards, not full web pages or apps; typography and layout taste is yours to direct, the skill executes faithfully. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Version:
Install
Prerequisites: Chrome/Chromium installed on your machine (required for the browser-rendered screenshot step). No account, no API keys. Most useful if you publish explainers, quotes, stats, or social visuals. Install "Editorial Card Screenshot" for me. It generates clean, responsive editorial HTML information cards and renders them to exact PNG screenshots with a real headless browser — HTML-first, tweakable, re-renderable. Repository: https://github.com/shaom/infocard-skills 1. Fetch the SKILL.md file for the editorial-card-screenshot skill (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "editorial-card-screenshot". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm Chrome/Chromium is installed, and describe the first card you want). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.