关于
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.
快速安装
Claude Code
推荐npx 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-pipeline在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
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 仓库
Frequently asked questions
What is the audit-icon-pipeline skill?
audit-icon-pipeline is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform audit-icon-pipeline-related tasks without extra prompting.
How do I install audit-icon-pipeline?
Use the install commands on this page: add audit-icon-pipeline to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does audit-icon-pipeline belong to?
audit-icon-pipeline is in the Meta category, tagged ai.
Is audit-icon-pipeline free to use?
Yes. audit-icon-pipeline is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
相关推荐技能
Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。
这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。
该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。
SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。
