跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 skill-from-github

Skill From Github

通过学习高质量的 GitHub 项目创造技能

480 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

通过学习高质量的 GitHub 项目创造技能

何时用

当用户描述任务时,您想要找到现有工具/项目来学习:

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Skill from GitHub、When to Use、Workflow、Step 1: Understand User Intent、Step 2: Search GitHub、Step 3: Present Options to User。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Create skills by learning from high-quality GitHub projects

Skill from GitHubWhen to UseWorkflowStep 1: Understand User IntentStep 2: Search GitHubStep 3: Present Options to UserFound X projects that can helpOption 1: [project-name](github-url)Option 2: ...Step 4: Deep Dive into Selected ProjectStep 5: Summarize UnderstandingUnderstanding [project-name]

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
skill-from-github
description
Create skills by learning from high-quality GitHub projects
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「skill-from-github」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-b408f3aa0a069ca8-%E5%9F%BA%E5%9B%BE%E5%B8%83%E7%9A%84%E6%8A%80%E8%89%BA.html
请存为 .cursor/skills/skill-from-github/SKILL.md 或 .claude/skills/skill-from-github/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/gbsoss/skill-from-masters' --list

npx skills add 'https://github.com/gbsoss/skill-from-masters' --skill 'skill-from-github'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: skill-from-github description: Create skills by learning from high-quality GitHub projects model: sonnet --- # Skill from GitHub When users want to accomplish something, search GitHub for quality projects that solve the problem, understand them deeply, then create a skill based on that knowledge. ## When to Use When users describe a task and you want to find existing tools/projects to learn from: - "I want to be able to convert markdown to PDF" - "Help me analyze sentiment in customer reviews" - "I need to generate API documentation from code" ## Workflow ### Step 1: Understand User Intent Clarify what the user wants to achieve: - What is the input? - What is the expected output? - Any constraints (language, framework, etc.)? ### Step 2: Search GitHub Search for projects that solve this problem: ``` {task keywords} language:{preferred} stars:>100 sort:stars ``` **Search tips:** - Start broad, then narrow down - Try different keyword combinations - Include "cli", "tool", "library" if relevant **Quality filters (must meet ALL):** - Stars > 100 (community validated) - Updated within last 12 months (actively maintained) - Has README with clear documentation - Has actual code (not just awesome-list) ### Step 3: Present Options to User Show top 3-5 candidates: ```markdown ## Found X projects that can help ### Option 1: [project-name](github-url) - Stars: xxx | Last updated: xxx - What it does: one-line description - Why it's good: specific strength ### Option 2: ... Which one should I dive into? Or should I search differently? ``` **Wait for user confirmation before proceeding.** ### Step 4: Deep Dive into Selected Project Once user selects a project, thoroughly understand it: 1. **Read README** - Understand purpose, features, usage 2. **Read core source files** - Understand how it works 3. **Check examples** - See real usage patterns 4. **Note dependencies** - What it relies on 5. **Identify key concepts** - The mental model behind it Extract: - Core algorithm/approach - Input/output formats - Error handling patterns - Best practices encoded in the code ### Step 5: Summarize Understanding Present what you learned to user: ```markdown ## Understanding [project-name] ### Core Approach How it solves the problem... ### Key Techniques 1. ... 2. ... ### Limitations - ... ### What I'll encode in the skill - ... Does this look right? Should I proceed to create the skill? ``` **Wait for user confirmation.** ### Step 6: Create Skill via skill-creator Hand off to skill-creator with: 1. **Clear purpose** - What the skill does 2. **Methodology** - The approach learned from the project 3. **Step-by-step process** - Concrete instructions 4. **Quality criteria** - What good output looks like 5. **Common pitfalls** - What to avoid (learned from project issues/docs) **Important:** The skill should encode the *knowledge* from the project, not just wrap the tool. The skill should work even without the original project installed. ## Example **User:** "I want to write better commit messages" **Step 2 - Search:** ``` commit message convention stars:>100 sort:stars ``` **Step 3 - Present:** ``` ## Found 4 projects ### Option 1: conventional-commits/conventionalcommits.org (4.2k ⭐) - Specification for human and machine readable commit messages - Why: Industry standard, used by Angular, Vue, etc. ### Option 2: commitizen/cz-cli (15k ⭐) - CLI tool for creating conventional commits - Why: Battle-tested, lots of adapters ### Option 3: carloscuesta/gitmoji (14k ⭐) - Emoji guide for commit messages - Why: Visual, fun approach Which one interests you? ``` **User:** "Let's go with conventional commits" **Step 4 - Deep dive:** - Read the specification - Understand types (feat, fix, docs, etc.) - Learn about scopes, breaking changes - Study real-world examples **Step 5 - Summarize:** ``` ## Understanding Conventional Commits ### Core Approach Structured format: (): ### Key Types - feat: new feature - fix: bug fix - docs: documentation - ... ### Benefits Learned - Automated changelog generation - Semantic versioning - Clear history Ready to create a commit message skill based on this? ``` **Step 6 - Create skill with these principles encoded** ## Important Notes 1. **Always get user confirmation** - At step 3 (project selection) and step 5 (before creating) 2. **Prefer learning over wrapping** - Encode the knowledge, not just "run this tool" 3. **Check license** - Mention if project has restrictive license 4. **Credit the source** - Include attribution in generated skill 5. **Quality over speed** - Take time to truly understand the project ## What This Skill is NOT - NOT a package installer - NOT a tool wrapper - It's about **learning from the best projects** and encoding that knowledge into a reusable skill

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…