技能更新器
- 作者仓库星标 1,104
- 许可证 Complete terms in LICENSE.txt
- 作者仓库 archive
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @dp-archive · Complete terms in LICENSE.txt
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:加载并理解技能
使用analyze_skill.py脚本获得快速概述:这显示:技能名称和描述SKILL.md行/字数所有捆绑资源(脚本/,引用/,资产/)
第 2 步:分析反馈
将反馈分为一种或多种类型: 类型 · 示例反馈 · 典型更改 错误修复 · “脚本在...时失败” · 修复脚本,添加错误处理 缺少功能 · “它还应该支持...” · 添加新功能 清晰度 · “指令令人困惑” · 改进 SKILL.md 文档
第 3 步:制定变更计划
在进行更改之前,创建一个清晰的计划: 列出要修改的特定文件 描述每个文件需要进行哪些更改 确定要创建的任何新文件或要删除的文件 考虑对技能其他部分的影响
第 4 步:实施变更
按照技能设计原则应用更改: 对于 SKILL.md 更改:将正文保持在 500 行以下 使用命令式形式 将详细内容移至参考文献/如果接近限制
第 5 步:验证并打包
实施更改后:
# Skill Updater
This skill provides guidance for updating existing skills based on user feedback.
## When to Use
Use this skill when:
- User provides feedback about an existing skill's performance
- User wants to improve or modify a skill
- User reports issues or bugs with a skill
- User wants to add new functionality to an existing skill
## Required Inputs
1. **Skill Path**: Path to the skill directory or .skill file to update
2. **Feedback**: Description of what needs to change, improve, or be fixed
## Update Process
### Step 1: Load and Understand the Skill
Use the analyze_skill.py script to get a quick overview:
```bash
scripts/analyze_skill.py <skill-path>
```
This shows:
- Skill name and description
- SKILL.md line/word count
- All bundled resources (scripts/, references/, assets/)
- Any structural issues
Then read SKILL.md to understand the detailed instructions:
```bash
cat <skill-path>/SKILL.md
```
For .skill files (zip archives), extract first:
```bash
unzip <skill-path>.skill -d /tmp/skill-extract/
```
### Step 2: Analyze the Feedback
Categorize the feedback into one or more types:
| Type | Example Feedback | Typical Changes |
|------|-----------------|-----------------|
| Bug fix | "The script fails when..." | Fix scripts, add error handling |
| Missing feature | "It should also support..." | Add new functionality |
| Clarity | "Instructions are confusing" | Improve SKILL.md documentation |
| Performance | "Too slow/uses too much context" | Optimize scripts, reduce SKILL.md |
| Trigger | "Doesn't activate when I say..." | Update description in frontmatter |
### Step 3: Plan the Changes
Before making changes, create a clear plan:
1. List specific files to modify
2. Describe what changes each file needs
3. Identify any new files to create or files to delete
4. Consider impact on other parts of the skill
### Step 4: Implement Changes
Apply changes following skill design principles:
**For SKILL.md changes:**
- Keep body under 500 lines
- Use imperative form
- Move detailed content to references/ if approaching limit
- Ensure frontmatter description captures all trigger scenarios
**For script changes:**
- Test scripts after modification
- Maintain existing interfaces unless feedback requires changes
- Add error handling for reported edge cases
**For reference changes:**
- Keep references one level deep from SKILL.md
- Update SKILL.md to reference new files
### Step 5: Validate and Package
After implementing changes:
```bash
# Validate the skill
scripts/quick_validate.py <skill-path>
# Package if validation passes
scripts/package_skill.py <skill-path>
```
## Common Update Patterns
### Pattern 1: Fixing Script Bugs
1. Read the failing script
2. Identify the bug based on feedback
3. Apply fix
4. Test with the scenario from feedback
5. Package
### Pattern 2: Improving Trigger Accuracy
1. Review current frontmatter description
2. Identify missing trigger phrases from feedback
3. Update description to include new triggers
4. Ensure description remains concise (<100 words)
### Pattern 3: Adding New Functionality
1. Determine if new functionality needs:
- New script in scripts/
- New reference in references/
- New asset in assets/
- Updates to SKILL.md instructions
2. Implement required components
3. Update SKILL.md to document new functionality
4. Test end-to-end
### Pattern 4: Reducing Context Usage
1. Identify verbose sections in SKILL.md
2. Move detailed content to references/
3. Replace with concise summary + link
4. Remove redundant examples
5. Verify skill still functions correctly
## Best Practices
- **Minimal changes**: Only change what the feedback requires
- **Test after changes**: Run scripts and validate skill structure
- **Preserve intent**: Maintain the skill's original purpose
- **Document changes**: Update SKILL.md if behavior changes
- **Version awareness**: If the skill has users, consider backward compatibility
章节与文件索引
按说明文件中的顺序排列。
何时使用
所需输入
第 1 步:加载并理解技能
第 2 步:分析反馈
第 3 步:制定变更计划
文件/命令 -> analyze_skill.py · scripts/analyze_skill.py · line/word · tmp/skill-extract · slow/uses · scripts/quick_validate.py · scripts/package_skill.py
内容校验值 -> 6da66b7a4dfd
当前原文的自动摘译,尚未人工审校。
何时使用
在以下情况下使用此技能: 用户提供有关现有技能性能的反馈 用户想要改进或修改技能 用户报告技能问题或错误 用户想要向现有技能添加新功能
所需输入
技能路径:要更新的技能目录或 .skill 文件的路径反馈:需要更改、改进或修复的内容的描述