audit-icon-pipeline
About
This skill audits icon assets by comparing registries against mapping files and directories to detect missing glyphs, icons, and HD variants. It generates a structured gap report for skills, agents, and teams across all palettes. Use it for pre-render checks, after registry updates, or for periodic pipeline health checks.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/audit-icon-pipelineCopy and paste this command in Claude Code to install this skill
Documentation
Audit Icon Pipeline
Detect missing glyphs, icons, stale manifests → compare registries vs glyph mappings, icon dirs, manifests. Structured gap report → skills, agents, teams.
Use When
- After add new skills/agents/teams → icons needed?
- Pre-full pipeline render → identify missing
- After registry updates → manifests in sync
- Periodic health check of icon pipeline
In
- Optional: Entity type filter —
skill,agent,team,all(default:all) - Optional: Palette (default:
cyberpunk— reference)
Do
Step 1: Read Registries
Collect entity IDs from source-of-truth registries.
skills/_registry.yml→ all skill IDs across all domainsagents/_registry.yml→ all agent IDsteams/_registry.yml→ all team IDs- Record counts: total skills, agents, teams
→ 3 lists of entity IDs w/ counts matching total_skills, total_agents, total_teams.
If err: Registry file missing → report path + skip that type.
Step 2: Read Glyph Mappings
Collect mapped entity IDs from glyph mapping files.
viz/R/glyphs.R→ all keys fromSKILL_GLYPHSlistviz/R/agent_glyphs.R→ all keys fromAGENT_GLYPHSlistviz/R/team_glyphs.R→ all keys fromTEAM_GLYPHSlist
→ 3 lists of mapped IDs.
If err: Glyph file missing → report + mark all entities of that type unmapped.
Step 3: Compute Missing Glyphs
Diff registry IDs vs mapped IDs.
- Missing skill glyphs:
registry_skill_ids - mapped_skill_ids - Missing agent glyphs:
registry_agent_ids - mapped_agent_ids - Missing team glyphs:
registry_team_ids - mapped_team_ids
→ Lists of entity IDs in registries w/o glyph fn mapped.
If err: Diff fails → verify ID formats match (underscores vs hyphens).
Step 4: Check Rendered Icons
Verify mapped glyphs have corresponding rendered icon files.
- Per mapped skill ID → check
viz/public/icons/<palette>/<domain>/<skillId>.webp - Per mapped agent ID → check
viz/public/icons/<palette>/agents/<agentId>.webp - Per mapped team ID → check
viz/public/icons/<palette>/teams/<teamId>.webp - HD variants in
viz/public/icons-hd/same structure
→ Lists of entities w/ glyphs but missing rendered icons (standard/HD).
If err: Icon dir missing → pipeline not run → report all as missing.
Step 5: Check Manifest Freshness
Compare manifest counts vs registry counts.
viz/public/data/icon-manifest.json→ count entriesviz/public/data/agent-icon-manifest.json→ count entriesviz/public/data/team-icon-manifest.json→ count entries- Compare vs registry totals
→ Manifest counts match registry counts. Discrepancy = stale.
If err: Manifest files missing → data pipeline must run first (node build-data.js && node build-icon-manifest.js).
Step 6: Detect Orphan Icons
Walk viz/public/icons*/ → flag WebP files whose <palette>/<domain>/<skillId> triple absent from icon-manifest.json.
- Enumerate all WebPs:
find viz/public/icons* -name "*.webp" - Per file → extract
<domain>/<id>from path - Check
<domain>/<id>has entry inicon-manifest.json - Non-matching = orphans → exist on disk but no longer referenced
# Quick orphan count per palette
node -e "
const fs = require('fs');
const manifest = JSON.parse(fs.readFileSync('viz/public/data/icon-manifest.json'));
const ids = new Set(manifest.map(e => e.domain + '/' + e.id));
const orphans = require('child_process')
.execSync('find viz/public/icons -name \"*.webp\"').toString().trim().split('\n')
.filter(p => { const parts = p.split('/'); const id = parts.slice(-2).join('/').replace('.webp',''); return !ids.has(id); });
console.log('Orphans:', orphans.length);
orphans.forEach(p => console.log(' ', p));
"
→ Zero orphans. Any = skills re-homed to diff domain w/o cleanup (18 orphans per re-homing = 9 palettes × 2 sizes).
If err: Delete orphans manually → no manifest entry, won't be served. Re-home events rare → manual cleanup OK.
Step 7: Generate Gap Report
Structured summary.
- Format out as clear table/list:
=== Icon Pipeline Audit === MISSING GLYPHS (no glyph function): Skills: 5 missing — [list] Agents: 2 missing — [list] Teams: 0 missing MISSING ICONS (glyph exists, no rendered WebP): Standard (512px): 3 skills, 1 agent HD (1024px): 8 skills, 3 agents, 1 team STALE MANIFESTS: icon-manifest.json: 320 entries vs 326 registry (stale) agent-icon-manifest.json: 66 entries vs 66 registry (OK) team-icon-manifest.json: 15 entries vs 15 registry (OK) - Suggest next actions from findings
→ Complete gap report w/ actionable next steps.
If err: All checks pass, zero gaps → report "Pipeline fully in sync" as positive outcome.
Check
- All 3 registries read
- All 3 glyph mapping files checked
- Icon dirs scanned both standard + HD
- Manifest freshness verified
- Orphan icons checked (disk paths vs manifest)
- Gap report produced w/ counts + entity lists
- Actionable next steps provided
Traps
- ID format mismatch: Registry = kebab-case (
create-skill), glyph maps may use snake_case → normalize comparison - Palette assumption: Only checking cyberpunk misses palette-specific gaps
- Empty dirs: Domain dir exists but empty → counts as "icons present" w/ globbing → check file existence, not dir
- HD not rendered: HD icons in separate tree (
icons-hd/) → don't confuse w/ standard - Orphans after re-homing: Skill domain change →
build.shcreates icons at new path but NOT deletes old → always run Step 6 orphan check after any domain migration
→
- create-glyph — create missing glyph identified by this audit
- enhance-glyph — improve quality of existing glyphs
- render-icon-pipeline — run full pipeline → generate missing icons
GitHub Repository
Related Skills
content-collections
MetaThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
polymarket
MetaThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
creating-opencode-plugins
MetaThis skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
sglang
MetaSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
