Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

infocard-skills Skill

Repository ↗

by shaom★ 5191 skills

Install

What it does

Open-source agent skills for generating editorial-style information cards from natural-language input.

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category Design and web UI
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/shaom-infocard-skills.svg)](https://mcp.popnx.com/en/skills/shaom-infocard-skills)

Use together with

MCP servers that connect the AI to services for the same work

Next AI Draw.io

draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand

by DayuanJiangWidely used↓ 21.7K/wk★ 37K Stars for the whole repoUpdated 3 days ago

MCP · Connects a serviceRuns on your computer

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

by pascalorgWidely used↓ 1K/wk★ 25.5K Stars for the whole repoUpdated 4 days ago

MCP · Connects a serviceComputer or cloud✓ service owner · pascal.app

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
infocard-skills
impeccablediagram-designfrontend-slidesguizang-ppt-skill
Makershaompbakauscathrynlaveryzarazhangruiop7418
Skills11111
GitHub stars519111,26567,61332,40729,891
Last code changeJun 13, 2026Nov 17, 2026Nov 13, 2026Jun 24, 2026Oct 30, 2026
LicenseMITApache-2.0MITMITAGPL-3.0

1 skills (instruction sets) by shaom that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Not stated by the maker · SKILL.md skills work in apps that support Agent Skills, such as Claude Code, Codex and Cursor

Install

Is it safe?

  • Who made it

    GitHub account shaom (person), 14 years old

  • Use and upkeep

    ★ 519 stars · code last changed Jun 13, 2026

  • Any scripts?

    1 scripts that can run on a computer: scripts/capture_card.sh

  • Uses the internet?

    No internet calls found in the scripts

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit e112107 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (467). Use "Let the AI install it" instead

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /editorial-card-screenshot or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /editorial-card-screenshot or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the editorial-card-screenshot folder at ~/.agents/skills/editorial-card-screenshot

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick editorial-card-screenshot

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick editorial-card-screenshot

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
name: editorial-card-screenshot
description: "Generate high-density editorial HTML info cards in a modern magazine and Swiss-international style, then capture them as ratio-specific screenshots. Use when the user provides text or core information and wants: (1) a complete responsive HTML info card, (2) the design to follow the stored editorial prompt, (3) output in fixed visual ratios such as 3:4, 4:3, 1:1, 16:9, 9:16, 2.35:1, 3:1, or 5:2, or (4) both HTML and a rendered PNG cover/card from the same content."
metadata: {"clawdbot":{"requires":{"bins":["google-chrome","chromium","chrome"]}}}
---

# Editorial Card Screenshot

## Overview

Turn source text into a compact, high-contrast HTML information card that follows the user's editorial prompt, then render a screenshot in one of the supported aspect ratios.
The goal is not just density but editorial quality: clear hierarchy, strong visual anchors, and screenshot-stable rendering without accidental cropping or dead space.

Always preserve three output stages unless the user explicitly asks to skip one:
1. Write one sentence judging the information density as high, medium, or low.
2. Output the complete HTML with embedded CSS.
3. Self-check that body text remains readable on mobile.

## Workflow

### 1. Analyze Content Density

Read [references/content-fit.md](references/content-fit.md). Inventory semantic units, estimate density, and choose layout strategy from both density and ratio:
- Use "big-character" composition when content is sparse and a single phrase, number, or hook can carry the page.
- Use a two-column or three-column editorial grid when content is dense and needs stronger hierarchy.
- Use oversized numbers, heavy rules, tinted blocks, and pull-quote scale to avoid dead space.
- Do not force dense content into evenly weighted tiles. Build primary blocks, secondary blocks, and lighter supporting blocks.
- Match structure to content type:
  - Ranking / recommendation content: allow asymmetric hero + structured list.
  - Tutorial / analysis / interpretation content: group into overview, core judgment, interpretation, boundary, and conclusion.
- Write a short space-allocation plan before final HTML. Assign approximate area to hero, primary module, support area, and footer.
- Do not use the starter template's current arrangement as evidence that it is the right skeleton.

Before compressing content, first change the layout skeleton.
- Ratio changes should primarily change reading path, hierarchy, and module arrangement.
- Do not treat ratio changes as a reason to delete content by default.
- Only compress, group, or summarize when the current ratio cannot hold the content clearly after layout has already been restructured.

### 2. Apply the Stored Editorial Rules

Use these defaults unless the user overrides them:
- Import Google Fonts:
  ```html
  <link href="https://fonts.googleapis.com/css2?family=Noto+Serif+SC:wght@700;900&family=Noto+Sans+SC:wght@400;500;700&family=Oswald:wght@500;700&family=Inter:wght@400;600;700&display=swap" rel="stylesheet">
  ```
- Keep body text at `18px` to `20px` on a 900px-wide composition.
- Keep meta/tag text at `13px` minimum.
- Use compact spacing: container padding `40px` to `50px`, component gaps `30px` to `40px`, line-height `1.5` to `1.6`.
- Add visual weight with `4px` to `6px` accent rules, subtle gray planes, and `4%` noise overlays.
- Favor `#f5f3ed` or similar warm-paper backgrounds unless the user supplies another palette.
- Preserve breathing room. Do not shrink outer margins so much that the card loses composure.
- For title zones, prefer larger line-height and clearer separation from subtitle / summary blocks.
- In dense right-side modules, reduce font weight slightly so the page stays clear without feeling heavy.
- Use stronger internal structure inside blocks: subheads, bullets, numbered lines, compare rows, or secondary labels.
- Avoid equal-weight boxes when the card is dense. At least one module should feel visually heavier than the others.
- Avoid making every module use the exact same visual language. Differentiate at least one or two areas through tone, scale, background treatment, or typographic weight.
- Default to a calm editorial mode with selective highlights. If the user asks for stronger expression, you may push toward:
  - `Bold`: more cover-like, stronger anchors, larger weak-background text, heavier accents.
  - `Refined`: lighter contrast, quieter accents, more restrained paper-like atmosphere.
  - `Hybrid`: the recommended default when style is not specified; refined overall with a few bold anchor moments.
- Keep Google Fonts imports, but always provide local fallback stacks so the rendered PNG stays structurally stable when remote fonts fail to load.
- If the user explicitly provides a title, use that exact title as the main headline by default. Only compress or reinterpret it when the user asks or when the ratio cannot hold it clearly after layout changes.
- Put interpretation, summary, and framing in the subtitle / deck / summary fields instead of silently rewriting the main title.
- Do not hard-code personal signatures, creator avatars, or account handles into reusable cards unless the user explicitly asks for branding.

### 3. Choose the Right Layout Skeleton

Pick ratio-specific structure before writing final copy.

#### `4:3`
- Best for full analytical spread or ranked lists.
- Prefer: hero + summary band + dense two-column list + stronger footer.
- Use one main judgment block before the list so the page does not become a flat wall of 10 equal items.
- Recommended reusable skeleton:
  - left heavy primary module for the main process / sequence / framework
  - right narrower stack for takeaways, pitfalls, or judgments
  - a light but intentional source / core-judgment strip at the bottom
- Avoid making `4:3` a symmetrical two-column newspaper wall from top to bottom.

#### `3:4`
- Keep the same information ambition, but change the reading path.
- Prefer: title band + insight row + mixed large/small body modules.
- Use mixed scales: one heavy primary block, one or two medium blocks, and smaller support blocks.
- Do not let the whole portrait card collapse into a long single column.
- Recommended reusable skeleton:
  - strong cover-style title zone
  - compact stat strip or insight strip
  - one large primary module
  - one medium judgment module
  - two smaller lower modules for takeaways / pitfalls / examples
- Avoid lower-half layouts that become two large empty boxes with only a few lines of copy.

#### `1:1`
- Best for ability map, grouped comparison, or balanced editorial overview.
- Prefer: strong hero + one heavier quadrant + three supporting quadrants + dense footer strip.
- Square layouts should feel centered and modular, not evenly tiled.
- Do not treat `1:1` as the default skeleton for every card. Pick it only when the output ratio is actually square.
- Recommended reusable skeleton:
  - strong title / subtitle hero across the top
  - one compact stat strip
  - one heavy left module for the main framework or sequence
  - one upper-right judgment module
  - one lower-right split for takeaways / pitfalls or compare blocks
  - one thin source / core-judgment strip at the bottom
- Avoid four equal quadrants and avoid tiny typography spread across too many boxes.

#### Wide covers (`3:1`, `5:2`, `2.35:1`)
- Reduce paragraph length aggressively.
- Use fewer but larger blocks, stronger headlines, and short support lines.

#### `16:9`
- Prefer a horizontal hero plus one structured support area.
- Keep the comfortable capacity to roughly two to five primary-point equivalents.

#### `9:16`
- Use a staged vertical reading path with a compact hero, one dominant middle module, and grouped lower supports.
- Avoid repeating same-height modules down the full canvas.

### 4. Build HTML for Rendering

When HTML will be screenshotted, design the page as a fixed-size canvas instead of a responsive webpage:
- Match the exact

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
519
Maker
shaom
License
MIT
Last code change
Jun 13, 2026
SKILL.md files in the repo (including translated copies and templates)
1
Topics
agent-skills, editorial-design, infocard