Terminal Opener
affaan-m/ECC
Open an executable and its argument array in a visible terminal window through a reusable, shell-free launch plan with dry-run, JSON, capability detection, detached fallback, and standalone recovery…
Generate and audit Microsoft Clarity browser instrumentation from the terminal.
$ npx skills add mvanhorn/printing-press-library --skill pp-clarity -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clarity --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/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-clarity .claude/skills/pp-clarity && 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 "pp-clarity" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clarity into .claude/skills/pp-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clarity", 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/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clarityType 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 mvanhorn/printing-press-library --skill pp-clarity -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clarity --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-clarity .agents/skills/pp-clarity && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-clarity" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clarity into .agents/skills/pp-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clarity", 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 mvanhorn/printing-press-library --skill pp-clarity -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clarity --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-clarity .cursor/skills/pp-clarity && 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 "pp-clarity" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clarity into .cursor/skills/pp-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clarity", 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/mvanhorn/printing-press-library.git --path cli-skills/pp-clarity--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 mvanhorn/printing-press-library --skill pp-clarity -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clarity --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-clarity .gemini/skills/pp-clarity && 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 "pp-clarity" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clarity into .gemini/skills/pp-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clarity", 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 mvanhorn/printing-press-library pp-clarityInstalls 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 mvanhorn/printing-press-library --skill pp-clarity -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-clarity .github/skills/pp-clarity && 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 "pp-clarity" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clarity into .github/skills/pp-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clarity", 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 mvanhorn/printing-press-library --skill pp-clarity -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clarity --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-clarity .opencode/skills/pp-clarity && 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 "pp-clarity" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clarity into .opencode/skills/pp-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clarity", 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.
pp-clarityGenerate and audit Microsoft Clarity browser instrumentation from the terminal.
Pp Clarity is an agent skill from mvanhorn/printing-press-library. Generate and audit Microsoft Clarity browser instrumentation from the terminal. Trigger phrases: generate a Clarity snippet, audit Clarity instrumentation, add Microsoft Clarity identify call.
Its SKILL.md is about 2.6k 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: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d9a1696. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goclaudenpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
MICROSOFT_CLARITY_API_TOKENCLARITY_API_TOKENPP_CLARITY_API_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Clarity loads about 2.6k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 1,057 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated 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.
The full file from mvanhorn/printing-press-library at commit d9a1696, republished under its Apache-2.0 licence (© mvanhorn). 1,057 words, ~2,585 tokens.
.claude/skills/pp-clarity/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/marketing/clarity/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the clarity-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install clarity --cli-onlyclarity-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):
go install github.com/mvanhorn/printing-press-library/library/marketing/clarity/cmd/clarity-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
Use this CLI when you need to add, review, or explain Microsoft Clarity browser instrumentation. It is strongest for generating snippets and auditing local HTML; it is not a replacement for the Clarity dashboard.
Do not activate this CLI for requests that require creating, updating, deleting, publishing, commenting, upvoting, inviting, ordering, sending messages, booking, purchasing, or changing remote state. This printed CLI exposes read-only commands for inspection, export, sync, and analysis.
These capabilities aren't available in any other tool for this API.
snippet install — Render a complete Clarity tracking snippet for a project ID, plus focused snippets for every documented client API call.
Use this when adding Clarity to a site or handing implementation-ready code to another agent.
clarity-pp-cli snippet install abc123 --format htmlaudit html — Inspect an HTML file for a Clarity tag script, masking attributes, and common window.clarity client API calls.
Use this before shipping page changes that are supposed to include Clarity instrumentation.
clarity-pp-cli audit html ./index.html --json --select found_project_id,callstag — Inspect the Microsoft Clarity tracking tag script
clarity-pp-cli tag <project_id> — Fetch the Clarity tracking tag script for a project IDHand-written commands
clarity-pp-cli snippet install — Render the tracking snippet for a Clarity project IDclarity-pp-cli snippet consent — Render the Cookie consent client API callclarity-pp-cli snippet identify — Render the custom identifiers client API callclarity-pp-cli snippet set — Render the custom tags client API callclarity-pp-cli snippet event — Render the custom event client API callclarity-pp-cli snippet upgrade — Render the session-priority client API callclarity-pp-cli snippet mask — Render Clarity mask or unmask HTML attributesclarity-pp-cli audit html — Check an HTML file for a Clarity install snippet and client API callsclarity-pp-cli insights live — Fetch Microsoft Clarity Data Export API live insightsWhen you know what you want to do but not which command does it, ask the CLI directly:
clarity-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
clarity-pp-cli snippet install abc123 --format htmlProduces the tracking snippet that belongs in the page head.
clarity-pp-cli snippet event newsletterSignupProduces the documented event call for a named user action.
clarity-pp-cli audit html ./index.html --json --select found_project_id,calls,mask_count,unmask_countNarrows audit output for agent consumption.
Client-side snippet commands only need the public Clarity project ID.
For Data Export API reads, set a token in the environment. Do not paste token values into chat or commit them to files:
export PP_CLARITY_API_TOKEN="..."
clarity-pp-cli insights live --days 1 --dimension OS --jsonFor local agent testing, prefer the local token file:
mkdir -p ~/.config/clarity-pp-cli
printf '%s' 'YOUR_TOKEN_HERE' > ~/.config/clarity-pp-cli/api-token
chmod 600 ~/.config/clarity-pp-cli/api-tokenThe command also accepts MICROSOFT_CLARITY_API_TOKEN, CLARITY_API_TOKEN, or PP_CLARITY_API_TOKEN_FILE.
Run clarity-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
clarity-pp-cli tag mock-value --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.
When you (or the agent) notice something off about this CLI, record it:
clarity-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
clarity-pp-cli feedback --stdin < notes.txt
clarity-pp-cli feedback list --json --limit 10Entries are stored locally at ~/.clarity-pp-cli/feedback.jsonl. They are never POSTed unless CLARITY_CLIENT_FEEDBACK_ENDPOINT is set AND either --send is passed or CLARITY_CLIENT_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
clarity-pp-cli profile save briefing --json
clarity-pp-cli --profile briefing tag mock-value
clarity-pp-cli profile list --json
clarity-pp-cli profile show briefing
clarity-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show clarity-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/marketing/clarity/cmd/clarity-pp-mcp@latestclaude mcp add clarity-pp-mcp -- clarity-pp-mcpclaude mcp listwhich clarity-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:clarity-pp-cli <command> [subcommand] [args] --agentclarity-pp-cli <command> --help.© mvanhorn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cli-skills/pp-clarity of mvanhorn/printing-press-library.
Open the folder on GitHubat commit d9a1696
Pp Clarity 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 |
|---|---|---|---|---|---|---|
| Pp Clarity this skillmvanhorn/printing-press-library | 2.1k | — | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Terminal Openeraffaan-m/ECC | 276k | — | ~635 | Automated safety check: Pass | MIT | |
| Observability And Instrumentationsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Terminal Opsaffaan-m/ECC | 276k | 2 repos | ~750 | Automated safety check: Pass | MIT | |
| Terminal Opsaffaan-m/ECC | 276k | — | ~439 | Automated safety check: Pass | MIT | |
| Terminal Opsaffaan-m/ECC | 276k | — | ~323 | Automated safety check: Pass | MIT |
affaan-m/ECC
Open an executable and its argument array in a visible terminal window through a reusable, shell-free launch plan with dry-run, JSON, capability detection, detached fallback, and standalone recovery…
sickn33/agentic-awesome-skills
Instruments code so production behavior is visible and diagnosable.
affaan-m/ECC
Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.
affaan-m/ECC
ECCのための証拠優先のリポジトリ実行ワークフロー。ユーザーがコマンドの実行、リポジトリの確認、CIの失敗のデバッグ、正確な実行と検証の証明を伴う狭い修正のプッシュを必要とする場合に使用する。
affaan-m/ECC
基于证据优先的仓库执行工作流,适用于ECC。当用户需要运行命令、检查仓库、调试CI失败或推送带有精确执行和验证证明的窄修复时使用。
github/awesome-copilot
Instrument a webapp to send useful telemetry data to Azure App Insights
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Generate and audit Microsoft Clarity browser instrumentation from the terminal. Pp Clarity is an agent skill from mvanhorn/printing-press-library. Generate and audit Microsoft Clarity browser instrumentation from the terminal.
Pp Clarity fits situations like: phrases: generate a Clarity snippet; audit Clarity instrumentation; add Microsoft Clarity identify call.
Run `npx skills add mvanhorn/printing-press-library --skill pp-clarity -a claude-code`. Or copy the skill folder (cli-skills/pp-clarity in mvanhorn/printing-press-library) into .claude/skills/pp-clarity in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-clarity -a codex`. Or copy the skill folder (cli-skills/pp-clarity in mvanhorn/printing-press-library) into .agents/skills/pp-clarity in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvanhorn/printing-press-library --skill pp-clarity -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-clarity, .gemini/skills/pp-clarity, .github/skills/pp-clarity and .opencode/skills/pp-clarity in your project.
Going by SKILL.md and its folder, Pp Clarity needs the command-line tools its instructions call (go, claude and npx) and credentials named MICROSOFT_CLARITY_API_TOKEN, CLARITY_API_TOKEN and PP_CLARITY_API_TOKEN. Our summary lists: Node.js; A credential in PP_CLARITY_API_TOKEN; A credential in MICROSOFT_CLARITY_API_TOKEN. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Pp Clarity is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Clarity: Terminal Opener (affaan-m/ECC, 276k stars), Observability And Instrumentation (sickn33/agentic-awesome-skills, 47k stars), Terminal Ops (affaan-m/ECC, 276k stars) and Terminal Ops (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.