Screenshot
nexu-io/open-design
Capture desktop, app windows, or pixel regions across OS platforms.
Reproducibly capture in-product UI screenshots (admin popovers, settings teasers, dashboard widgets) used as embedded images in premium upsell teasers.
No licenceAuto-check: notes
Install Teaser Screenshots
$ npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bonny/WordPress-Simple-History teaser-screenshots --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/teaser-screenshots .claude/skills/teaser-screenshots && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "teaser-screenshots" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/teaser-screenshots into .claude/skills/teaser-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teaser-screenshots", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/teaser-screenshotsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bonny/WordPress-Simple-History teaser-screenshots --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/teaser-screenshots .agents/skills/teaser-screenshots && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "teaser-screenshots" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/teaser-screenshots into .agents/skills/teaser-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teaser-screenshots", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bonny/WordPress-Simple-History teaser-screenshots --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/teaser-screenshots .cursor/skills/teaser-screenshots && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "teaser-screenshots" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/teaser-screenshots into .cursor/skills/teaser-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teaser-screenshots", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bonny/WordPress-Simple-History.git --path .claude/skills/teaser-screenshots--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bonny/WordPress-Simple-History teaser-screenshots --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/teaser-screenshots .gemini/skills/teaser-screenshots && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "teaser-screenshots" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/teaser-screenshots into .gemini/skills/teaser-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teaser-screenshots", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bonny/WordPress-Simple-History teaser-screenshotsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/teaser-screenshots .github/skills/teaser-screenshots && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "teaser-screenshots" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/teaser-screenshots into .github/skills/teaser-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teaser-screenshots", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bonny/WordPress-Simple-History teaser-screenshots --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/teaser-screenshots .opencode/skills/teaser-screenshots && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "teaser-screenshots" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/teaser-screenshots into .opencode/skills/teaser-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teaser-screenshots", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
teaser-screenshots- GitHub stars
- 317
- Token cost
- ~2.1k tokens
- SKILL.md length
- 947 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- None found
At a glance
Reproducibly capture in-product UI screenshots (admin popovers, settings teasers, dashboard widgets) used as embedded images in premium upsell teasers.
- Works in 4 steps: Premium add-on must be installed on the… → At least one user in the visible log… → JS bundle must be current if you changed… → …
- A teaser image needs refreshing after the underlying UI changes
- SKILL.md covers Captured screenshots, Pre-flight, Capture command and When to re-run, plus 3 more sections
- Calls npm, brew and curl
What it does
Teaser Screenshots is an agent skill from bonny/WordPress-Simple-History. Reproducibly capture in-product UI screenshots (admin popovers, settings teasers, dashboard widgets) used as embedded images in premium upsell teasers. Use whenever a teaser image needs refreshing after the underlying UI changes.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 🔍🕵️♀️ WordPress audit log that track user changes in WordPress admin using a nice activity feed.
When your agent uses it
- A teaser image needs refreshing after the underlying UI changes
Example prompts
- “/teaser-screenshots”
Requirements
- Docker
- Pre-approved tools (allowed-tools): Read, Bash, Edit, Write
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Premium add-on must be installed on the stable WP install (the orchestrator handles activate/deactivate itself, but the plugin files need…
- At least one user in the visible log needs real IP/UA history. On Pär's stable install this is user 1 (par) — that's the user the spec…
- JS bundle must be current if you changed the PremiumTeaserBlurred component — npm run build first so the free-mode capture sees the latest…
- Auth cache: delete tests/playwright/.auth/admin.json to force a fresh login (otherwise re-uses cached session). Usually fine to leave alone.
What it can do on your machine
Read from SKILL.md and the folder at commit 24f337f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashEditWrite
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmbrewcurl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Teaser Screenshots loads about 2.1k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 947 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Edit, Write
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 947 words (~2,080 tokens).
“These screenshots are embedded inside the free version's UI (e.g. the user card teaser block) to show "this is what the same surface looks like with premium." Real screenshots beat blurred placeholders for honesty, conversion, and WP.org compliance (see freemium_upsell_strategy.md…”
- name
- teaser-screenshots
- allowed-tools
- Read, Bash, Edit, Write
- disable-model-invocation
- false
Files
Just SKILL.md in .claude/skills/teaser-screenshots of bonny/WordPress-Simple-History.
Open the folder on GitHubat commit 24f337f
Compare with similar skills
Teaser Screenshots next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Teaser Screenshots this skillbonny/WordPress-Simple-History | 317 | — | ~2.1k | Automated safety check: Notes | None | |
| Screenshotnexu-io/open-design | 100k | — | ~291 | Automated safety check: Pass | Apache-2.0 | |
| Adminyc-software/qm | 15k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Terminal Screenshot CaptureQwenLM/qwen-code | 28k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Tabler Screenshot Makertabler/tabler | 42k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Capturealirezarezvani/claude-skills | 28k | 1 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Admin
yc-software/qm
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster & external users, audit/errors/metrics/egress)…
Terminal Screenshot Capture
QwenLM/qwen-code
Drives a CLI through a TypeScript scenario and saves terminal screenshots at each step, so pull requests that change command output can be checked visually.
Tabler Screenshot Maker
tabler/tabler
Makes reproducible screenshots of Tabler components and screens for release notes, the website and social posts, using the repository's screenshots app.
Capture
alirezarezvani/claude-skills
Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss.
Manage Settings
asgeirtj/system_prompts_leaks
Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool…
More from bonny/WordPress-Simple-History
All 21 skills in this repoBlueprint
bonny/WordPress-Simple-History
A skill your agent uses when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources…
Action Links
bonny/WordPress-Simple-History
Guides implementation of structured action links on log events.
Changelog
bonny/WordPress-Simple-History
Adds changelog entries to readme.txt following keepachangelog format.
Code Quality
bonny/WordPress-Simple-History
Runs linting and static analysis on PHP/CSS/JS using phpcs, phpstan, and rector.
Create Logger
bonny/WordPress-Simple-History
Guides creation of custom loggers for Simple History. An agent skill from bonny/WordPress-Simple-History.
Logger Messages
bonny/WordPress-Simple-History
Enforces active voice for logger messages and the Event Details API.
Questions about Teaser Screenshots
What does Teaser Screenshots do?
Reproducibly capture in-product UI screenshots (admin popovers, settings teasers, dashboard widgets) used as embedded images in premium upsell teasers. Teaser Screenshots is an agent skill from bonny/WordPress-Simple-History. Reproducibly capture in-product UI screenshots (admin popovers, settings teasers, dashboard widgets) used as embedded images in premium upsell teasers.
When should I use Teaser Screenshots?
Teaser Screenshots fits situations like: A teaser image needs refreshing after the underlying UI changes.
How do I install Teaser Screenshots in Claude Code?
Run `npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a claude-code`. Or copy the skill folder (.claude/skills/teaser-screenshots in bonny/WordPress-Simple-History) into .claude/skills/teaser-screenshots in your project. Claude Code loads it when a task matches its description.
How do I install Teaser Screenshots in Codex?
Run `npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a codex`. Or copy the skill folder (.claude/skills/teaser-screenshots in bonny/WordPress-Simple-History) into .agents/skills/teaser-screenshots in your project. Codex loads it when a task matches its description.
Can I use Teaser Screenshots in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bonny/WordPress-Simple-History --skill teaser-screenshots -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/teaser-screenshots, .gemini/skills/teaser-screenshots, .github/skills/teaser-screenshots and .opencode/skills/teaser-screenshots in your project.
What does Teaser Screenshots need to run?
Going by SKILL.md and its folder, Teaser Screenshots needs the command-line tools its instructions call (npm, brew and curl). Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Bash, Edit, Write.
Does Teaser Screenshots access the network?
SKILL.md contains no URLs. Its commands use npm and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Teaser Screenshots safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Teaser Screenshots use?
No licence was found for Teaser Screenshots or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Teaser Screenshots use?
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Teaser Screenshots?
Skills that share tags, products or a category with Teaser Screenshots: Screenshot (nexu-io/open-design, 100k stars), Admin (yc-software/qm, 15k stars), Terminal Screenshot Capture (QwenLM/qwen-code, 28k stars) and Tabler Screenshot Maker (tabler/tabler, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Teaser Screenshots?
bonny (a GitHub user) maintains it in bonny/WordPress-Simple-History, which has 317 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.
Source: bonny/WordPress-Simple-History on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.