来自的技能
- 作者仓库星标 1,408
- 作者仓库 skill-from-masters
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @GBSOSS · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
commit message convention stars:>100 sort:stars
第 1 步:了解用户意图
明确用户想要实现的目标:输入是什么?预期产出是多少?有什么限制(语言、框架等)?
第二步:搜索GitHub
搜索解决此问题的项目: 搜索提示:从广泛开始,然后缩小范围 尝试不同的关键字组合 包括“cli”、“tool”、“library”(如果相关)
第 3 步:向用户提供选项
显示前 3-5 个候选者:等待用户确认后再继续。
第 4 步:深入研究选定的项目
用户选择项目后,请彻底理解它: 阅读自述文件 - 了解目的、功能、用途 阅读核心源文件 - 了解它是如何工作的 检查示例 - 查看真实的使用模式 注意依赖关系 - 它依赖什么
第五步:总结理解
向用户展示您学到的内容:等待用户确认。
第6步:通过技能创建器创建技能
交给技能创造者: 明确的目的 - 技能的作用 方法论 - 从项目中学到的方法 分步过程 - 具体说明 质量标准 - 好的输出是什么样的
# 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: <type>(<scope>): <description>
### 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
章节与文件索引
按说明文件中的顺序排列。
何时使用
第 1 步:了解用户意图
第二步:搜索GitHub
第 3 步:向用户提供选项
第 4 步:深入研究选定的项目
文件/命令 -> tools/projects · algorithm/approach · Input/output · issues/docs · conventional-commits/conventionalcommits.org · commitizen/cz-cli · carloscuesta/gitmoji
内容校验值 -> f03accd2d032
当前原文的自动摘译,尚未人工审校。
何时使用
当用户描述一项任务并且您想要找到现有的工具/项目来学习时:“我希望能够将 markdown 转换为 PDF”“帮助我分析客户评论中的情绪”“我需要从代码生成 API 文档”