Token导航 LogoToken导航

Agent Skill · 前端设计

skill-development(技能发展)

skill-development 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

skill-development 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 3,315。

总安装 1,398周安装 56GitHub Stars 3,478下载 452核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:skill-development(技能发展)
来源仓库:https://github.com/galaxy-dawn/claude-scholar
仓库路径:skills/skill-development
安装命令:
npx skills add https://github.com/galaxy-dawn/claude-scholar --skill skill-development
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/galaxy-dawn/claude-scholar --skill skill-development

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

skill-development 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。

通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。注意该技能属于前端设计类,实际功能以来源仓库文档为准。

来源仓库内路径:skills/skill-development

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/galaxy-dawn/claude-scholar --skill skill-devel…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

skill-development 怎么安装?

在终端执行 npx skills add https://github.com/galaxy-dawn/claude-scholar --skill skill-development。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

skill-development 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

skill-development 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

skill-development 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

skill-development 用的人多吗?

公开数据是累计安装 1,398 次,近一周安装 56 次,下载 452 次,GitHub 3,478 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

skill-development 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 3,478 星,维护活跃度相对可查。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
skill-development

技能发展 · 本页

1,3983,478只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Skill Development

Use this skill to create or repair Claude skills in the current local environment, not in an abstract plugin template.

Goal

Produce a skill that is:

  • easy to trigger,
  • lean at the SKILL.md layer,
  • backed by real references/, examples/, and scripts/ files when they are mentioned,
  • free of dead local references.

Core rules

  • Keep one skill = one durable job.
  • Treat the frontmatter description as the main trigger surface.
  • Keep SKILL.md focused on workflow and boundaries.
  • Move detailed catalogs, templates, and long explanations into references/ or examples/.
  • Do not mention files that do not exist.
  • Do not inherit stale names, agents, or sibling skill references without verifying they exist locally.

Default workflow

1. Inspect the current environment first

Before writing anything:

  • inspect the target skill directory,
  • inspect neighboring skills that already solve a similar problem,
  • verify which agents, commands, and sibling skills actually exist,
  • identify stale references before adding new ones.

Use the local inventory as the authority. Do not write guidance against an imagined plugin layout.

2. Lock the skill contract

Define four things before editing:

  1. what the skill does,
  2. what triggers it,
  3. what it explicitly does not do,
  4. which bundled resources are actually needed.

If the skill only needs a short workflow, keep it short. Do not create references/, examples/, or scripts/ just because the directories are conventional.

3. Write or repair the frontmatter

The frontmatter should:

  • use the real skill identifier in name,
  • use a third-person trigger description,
  • include concrete phrases a user would naturally say,
  • stay short enough to scan quickly.

Prefer descriptions of this form:

---
name: skill-name
description: This skill should be used when the user asks to "...", "...", or needs help with ....
---

4. Keep the main file lean

A good SKILL.md should usually contain:

  • a short goal section,
  • role boundaries,
  • a default workflow,
  • safety or quality rules,
  • a short list of additional resources.

Move these out of the main file when they get long:

  • templates,
  • exhaustive checklists,
  • edge-case catalogs,
  • sample outputs,
  • long examples.

5. Add only real bundled resources

Use bundled resources deliberately:

  • references/ for detailed guidance that may be loaded selectively,
  • examples/ for real example outputs or scaffolds,
  • scripts/ for deterministic helper logic.

If a resource is mentioned in SKILL.md, it must exist. If a resource exists but is never referenced or used, delete it.

6. Run integrity checks before closing

At minimum, verify:

  • frontmatter parses,
  • referenced local files exist,
  • sibling skill or agent references are real,
  • SKILL.md is not overloaded with material that belongs in references,
  • temporary logs, caches, and editor artifacts are not left inside the skill directory.

Typical repair patterns

When the skill is too long

  • keep the trigger and workflow in SKILL.md,
  • move catalogs and deep detail into references/,
  • keep a short read order so another model knows what to load first.

When the skill is too thin

  • add a default workflow,
  • add at least one concrete example or checklist,
  • make the boundaries explicit so the skill is not just a slogan.

When the skill has stale references

  • remove dead paths immediately,
  • replace historical names with current local names,
  • re-check neighboring agents/commands/skills against the live directory.

Recommended output shape

When creating or repairing a skill, prefer ending with:

  • what changed,
  • which files were created or updated,
  • what integrity checks were run,
  • what still needs manual follow-up, if anything.

References

Load only what is needed:

  • references/checklist.md - compact quality checklist before closing a skill edit
  • references/integrity-checks.md - concrete local checks for missing files, dead references, and drift
  • references/skill-creator-original.md - legacy background reference; use for context, not as the live source of truth

平台分布

Codex

38.13%
按下载量换算172

Claude

30.04%
按下载量换算136

Cursor

19.7%
按下载量换算89

Gemini CLI

8.63%
按下载量换算39

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills