pixelkiln SKILL.md skillA

pixelkiln from gfargo/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add gfargo/skills/pixelkiln@git:20261119.fe8e62f

Pins git:20261119.fe8e62f in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
gfargo/skills
Path
plugins/games/skills/pixelkiln/SKILL.md
Versions recorded
10
Latest version
git:20261119.fe8e62f, committed Nov 19, 2026
First version recorded
Sep 26, 2026
Size
11,685 bytes
Repository stars
3
License
MIT

Use PixelKiln to plan, generate, review, recover, audit, pack, and export manifest-driven pixel-art projects. Apply when a task uses the PixelKiln CLI, manifest, lockfile, or generated asset workflow; do not use for unrelated one-off image generation.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# PixelKiln

Treat generated pixel art as build output. Read the manifest, report the cost
before submission, stop for human review, and record the source and output
hashes.

## Working rules

- Locate `pixelkiln.manifest.json` first. Paths are manifest-relative.
- Give every new asset a descriptive `id` (`oak_tree`, `iron_sword`, not
  `asset_3` or `object1`). A vague id is cheap to write and expensive the
  moment another asset needs to reference it (`state.of`, `animation.of`,
  `revision.from`, `mirror`) or a person asks which one it was.
- Treat `style.extends` as a source-level variant, not a reason to copy the
  parent. Keep every child `outDir` explicit, inspect the resolved plan, and
  remember that a pixel-affecting parent edit intentionally makes children stale.
- Never inspect, print, or commit provider credentials. Read the top-level
  provider default and every style override, then load the matching provider
  references below.
- Run `pixelkiln doctor --dry-run` and `pixelkiln plan` before paid work. Report
  actionable, recoverable, and estimated cost figures with their provider unit.
- Do not regenerate recoverable work. Follow the exact zero-cost action printed
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dtm2yxvbl7bbclpm/c502d142e9ecb8b75dc378959a656a0d175d6ef9405bc158929d002ac0a2bbec.json

Then /plugin install pixelkiln@markdownregistry-dtm2yxvbl7bbclpm in Claude Code. It installs git:20261119.fe8e62f, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add gfargo/skills/pixelkiln@sha256:c502d142e9ecb8b7

The line at the top of this page pins the label git:20261119.fe8e62f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_dtm2yxvbl7bbclpm.svg)](https://markdownregistry.com/a/art_dtm2yxvbl7bbclpm)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in gfargo/skills/pixelkiln since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of pixelkiln from somewhere else? Ask it: where did my pixelkiln come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 10 versions of this file, between Sep 26, 2026 and Nov 19, 2026, about one every 6 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261119.fe8e62f latest2026-11-19 fe8e62f 11,685 BA view · diff
git:20261118.d294c282026-11-18 d294c28 10,835 BA view · diff
git:20261118.0871c982026-11-18 0871c98 10,702 BA view · diff
git:20261117.223c0a12026-11-17 223c0a1 10,149 BA view · diff
git:20261117.e67fd0f2026-11-17 e67fd0f 9,659 BA view · diff
git:20261016.04232042026-10-16 0423204 9,484 BA view · diff
git:20261011.496f0fd2026-10-11 496f0fd 9,470 BA view · diff
git:20261009.13da96f2026-10-09 13da96f 9,063 BA view · diff
git:20260926.83ddff52026-09-26 83ddff5 8,833 BA view · diff
git:20260926.f4f62912026-09-26 f4f6291 8,342 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (11685 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

gfargo/skills · 3 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_dtm2yxvbl7bbclpm
GET https://markdownregistry.com/api/v1/resolve?ref=gfargo/skills/pixelkiln
GET https://markdownregistry.com/api/v1/blob/c502d142e9ecb8b75dc378959a656a0d175d6ef9405bc158929d002ac0a2bbec

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from gfargo/skills

gfargo-skills Plugin marketplace
gfargo/skills · .claude-plugin/marketplace.json · Griffen Fargo's published agentic coding skills, following the Agent Skills spec. (4 plugins: terminal, devops, games…
git:20261119.4e92a98 · audit A · 3 stars
strut SKILL.md skill
gfargo/skills · plugins/devops/skills/strut/SKILL.md · Operate and manage Docker Compose stacks on VPS infrastructure with the strut CLI. Use for any strut task — deploying…
v1.0 · audit A · 3 stars
ink-playing-cards SKILL.md skill
gfargo/skills · plugins/games/skills/ink-playing-cards/SKILL.md · Use when building terminal card games with ink-playing-cards, working with card components, deck management, zone…
git:20260807.4ace81e · audit A · 3 stars
doorman SKILL.md skill
gfargo/skills · plugins/security/skills/doorman/SKILL.md · Manage Vercel, Cloudflare, and Fastly WAF firewall rules as code with the Doorman CLI. Use for any firewall-as-code…
v1.0 · audit A · 3 stars
tui-design SKILL.md skill
gfargo/skills · plugins/terminal/skills/tui-design/SKILL.md · Design, build, refactor, or review terminal interfaces—full-screen TUIs, interactive prompts, and command-line tools…
git:20261028.70b288e · audit A · 3 stars
vhs-cli-demos SKILL.md skill
gfargo/skills · plugins/terminal/skills/vhs-cli-demos/SKILL.md · Generate deterministic screenshots and demo GIFs of command-line and terminal (TUI) applications using Charm VHS. Use…
git:20260718.5a1f2db · audit A · 3 stars

Every file in gfargo/skills

Browse by kind, by grade A, or by owner.