agentleFS
BryceYuuuBryceYuuu/open-workflow-skills/skills/palette-extractor/SKILL.md

palette-extractor

Skill1 starsChanged 2 months agoMITView on GitHub

Extract dominant colors and map them into semantic design tokens such as primary, surface, text, border, and accent. Use when the user asks for palette extractor or an equivalent workflow.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user explicitly requests palette extractor, or when the requested outcome clearly matches this workflow.

    line 45
  2. Distinctive:

    Do not activate it merely because the topic is related.

    line 47
  3. Distinctive:

    Treat permissions as capabilities to request or verify, not as permissions automatically granted by installing the skill.

    line 68
  4. Distinctive:

    No universal runtime package is required by the skill format itself.

    line 80
  5. Distinctive:

    Verify all expected outputs exist and are readable.

    line 132
  6. Distinctive:

    Verify the source was not unintentionally overwritten.

    line 133
  7. Distinctive:

    Verify structured outputs against their expected schema or invariants.

    line 134
  8. Distinctive:

    Never mark the workflow successful solely because a model produced text.

    line 136
  9. Distinctive:

    Do not invent source facts or claim an external action succeeded without verification.

    line 142
  10. Distinctive:

    If a dependency, credential, connected service, browser session, file, or required permission is unavailable:

    line 148
  11. Distinctive:

    Stop the affected step.

    line 150
  12. Distinctive:

    Do not fabricate a successful result.

    line 153

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Palette Extractor / 配色提取

Purpose / 用途

中文

从参考图提取主要颜色并映射成 Primary、Surface、Text、Border、Accent 等语义色。

English

Extract dominant colors and map them into semantic design tokens such as primary, surface, text, border, and accent.

Status / 状态

  • Workflow status: 🟢 Verified Workflow / 已验证工作流
  • Implementation: ✅ Tested reference implementation / 已测试参考实现
  • Audit grade: A
  • Quality score: 5.0/5
  • Automation level: L2
  • Category: Design & Creative / 设计与创意

Workflow status describes how well the workflow itself is understood. Implementation status separately tells you whether this repository ships runnable code for it. Integration skills still require external services or authorization; experimental skills may need more human review.

Search aliases / 搜索关键词

palette-extractor · Palette Extractor · 配色提取 · color palette extractor · image color palette · design tokens · 色板生成 · AI design · design automation · creative automation · AI设计 · 设计自动化 · 创意工作流

When to use / 何时使用

Use this skill when the user explicitly requests palette extractor, or when the requested outcome clearly matches this workflow.

Do not activate it merely because the topic is related. Confirm the input, desired output, and any consequential external action.

Inputs / 输入

  • Image file(s)
  • Output format, dimensions, or style constraints

Outputs / 输出

  • Generated or transformed design assets
  • Manifest / QA notes

Core stack / 核心工具

Python / image processing

Permissions / 权限

  • filesystem:read
  • filesystem:write

Treat permissions as capabilities to request or verify, not as permissions automatically granted by installing the skill.

Workflow / 工作流

  1. Load image with Pillow
  2. Downsample for bounded runtime
  3. Quantize to requested palette size
  4. Rank colors by pixel count
  5. Write HEX/RGB JSON palette

Dependency suggestions / 依赖建议

  • No universal runtime package is required by the skill format itself. Install only the tools named in Core stack when your chosen implementation needs them.

The Agent Skill itself should remain installable even when optional runtimes are absent. Report missing runtime dependencies instead of silently installing privileged software.

Runnable reference / 可运行参考实现

This skill ships a tested reference runtime in scripts/run.py. From a cloned repository:

ows doctor palette-extractor
ows run palette-extractor -- --help
ows test palette-extractor

runtime.json declares the entrypoint and optional system commands. Runtime dependencies are checked separately from installing the Skill definition.

Install / 安装

Inspect before installing

npx skills add BryceYuuu/open-workflow-skills --list

Install this skill into the current project

npx skills add BryceYuuu/open-workflow-skills --skill palette-extractor

Install for a specific supported agent

npx skills add BryceYuuu/open-workflow-skills --skill palette-extractor --agent codex

npx skills is a community ecosystem CLI, not an OpenAI-official installer. Review third-party skills and scripts before granting shell, filesystem, network, or credential access.

Example invocation / 调用示例

中文

使用 palette-extractor 工作流处理我提供的输入。先检查依赖和权限,不覆盖源文件;执行后给我输出路径、验证结果和需要人工审核的部分。

English

Use the palette-extractor workflow for the provided input. Check dependencies and permissions first, preserve the source, validate the result, and report outputs plus any human-review items.

Validation / 验证

At minimum:

  • Verify all expected outputs exist and are readable.
  • Verify the source was not unintentionally overwritten.
  • Verify structured outputs against their expected schema or invariants.
  • Record warnings, skipped steps, external dependencies, and failed checks.
  • Never mark the workflow successful solely because a model produced text.

See references/QUALITY.md for skill-specific quality expectations.

Safety / 安全

  • Do not invent source facts or claim an external action succeeded without verification.
  • Preserve source files unless the user explicitly requests in-place modification.
  • Surface missing dependencies, permissions, credentials, and failed checks clearly.

Failure handling / 失败处理

If a dependency, credential, connected service, browser session, file, or required permission is unavailable:

  1. Stop the affected step.
  2. Preserve completed safe outputs.
  3. State exactly what is missing.
  4. Do not fabricate a successful result.
  5. Suggest the minimum next action needed to continue.

Files / 文件

  • SKILL.md — workflow instructions
  • references/QUALITY.md — quality/evaluation guidance
  • tests/cases.yaml — example evaluation cases
  • runtime.json — runtime manifest
  • scripts/run.py — runnable reference implementation
  • tests/smoke.py — deterministic smoke test

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.