Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器clawhub未标认证来源可访问clear审计通过

design-platform-search设计平台搜索

Agent Skill

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

总安装

2,584

周安装

111

GitHub Stars

公开资料未说明

下载量

906
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:design-platform-search(设计平台搜索)
来源仓库:https://github.com/joeyyyy0430/design-platform-search
安装命令:
openclaw skills install design-platform-search
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install design-platform-search

简介

在 Dribbble、Pinterest 与 Behance 上执行免登录设计搜索。

  • 适用于设计师寻找参考作品与趋势灵感。design-platform-search 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 返回标准化字段如标题、封面图与作者信息。
  • 搜索结果受平台公开数据限制,无法访问私有或下架内容。
  • 建议结合筛选器使用,提高结果相关性与效率。

SKILL.md

name
design-platform-search
description
Run public design search flows on Dribbble, Pinterest, and Behance without login, and extract normalized result fields such as title, search-page cover image, author, source URL, and publish time when available. Use when Codex needs a reusable method for public inspiration retrieval across major design platforms, especially when the collection strategy should stay lightweight and search-page-first.

Public Design Search

Use public search pages as the primary source of truth and keep the workflow login-free.

Workflow

  1. Choose search tags.

- Prefer English tags for these three platforms unless a platform clearly supports another language. - Load references/tag-taxonomy.md for generic tag-selection guidance and example category/tag patterns. - Keep tag choice independent from platform-specific extraction logic.

  1. Build public search URLs.

- Dribbble: https://dribbble.com/search/<urlencoded-tag> - Pinterest: https://www.pinterest.com/search/pins/?q=<urlencoded-tag>&rs=typed - Behance: https://www.behance.net/search/projects?search=<urlencoded-tag>

  1. Collect candidate cards from the search page.

- Prefer browser automation over raw HTTP for all three platforms. - Normalize search-card fields first: title, source_url, cover_image_url, summary, author_name when exposed, and raw_metrics when exposed.

  1. Backfill sparingly.

- Default: keep the search-page cover_image_url. - Use detail pages primarily for publish_time. - Only backfill author_name when the search card exposes nothing and the request budget allows it. - On constrained servers or proxy-heavy environments, disable Pinterest detail backfill entirely and rely on search-page results.

  1. Return a normalized public-only record.

- Keep unstable fields nullable. - Record the input tag or matched tag set when useful. - Do not fabricate authors, publish times, or engagement metrics.

Extraction Priorities

  • title: search-card title first, then safe public meta/title fallback.
  • cover_image_url: search-page image first; only do light URL upgrades when the site uses obvious small fixed-size variants.
  • author_name: search-card author first; leave Unknown if public search does not expose it reliably.
  • publish_time: detail-page public metadata when available; otherwise null.
  • summary: normalized title or short public snippet.

Platform-specific rules live in:

Network Guidance

  • Pinterest and Behance may require VPN or proxy access in restricted regions.
  • Browser traffic may work best through SOCKS5 while image download or pHash download may need an HTTP proxy.
  • Verify network reachability before changing selectors.
  • If a platform is reachable only through unstable proxies, reduce detail backfill before changing the tag set.

Guardrails

  • Public pages only. No login-only APIs, cookies, or authenticated sessions.
  • Prefer search-page fields over detail scraping whenever they are good enough.
  • Do not chase high-resolution cover images unless the search-page image is clearly unusable.
  • Treat missing metrics as normal.
  • Expect DOM drift and anti-bot behavior.
  • These three platforms are effectively English-first in most reusable workflows.

Output Shape

Normalize results into a shape close to:

{
  "title": "",
  "platform": "dribbble|pinterest|behance",
  "source_url": "",
  "cover_image_url": "",
  "author_name": "",
  "publish_time": null,
  "keyword": "",
  "matched_tags": []
}

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

86.59%
按下载量换算785

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills