Agent 生成器
- 作者仓库星标 237
- 作者更新于 实时读取
- 作者仓库 skills
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 83 / 100 · 社区维护
- 作者 / 版本 / 许可
- @guo-yu · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。;检出高风险片段:pipe_curl_to_shell
---
name: skill-permissions
description: Skill permission analysis, one-time authorization, analyze skill permissions, batch authorizatio…
category: 通用
runtime: 无特殊运行时
---
# skill-permissions 输出预览
## PART A: 任务判断
- 适用问题:通用任务拆解、检查和交付。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Dangerous Operations Warning / Usage / How It Works”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于通用任务拆解、检查和交付,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Dangerous Operations Warning / Usage / How It Works”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、执行终端命令、会按任务需要访问外部网络、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令;会按任务需要访问外部网络;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文出现了 `/skill-permissions`、`/clear` 这类斜杠命令;如果你的 Agent 支持命令触发,优先用命令开场,再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Dangerous Operations Warning / Usage / How It Works”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: skill-permissions
description: Skill permission analysis, one-time authorization, analyze skill permissions, batch authorizatio…
category: 通用
source: guo-yu/skills
---
# skill-permissions
## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常不需要额外…
- 面向通用任务拆解、检查和交付,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Dangerous Operations Warning / Usage / How It Works」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令;会按任务需要访问外部网络;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "skill-permissions" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Dangerous Operations Warning / Usage / How It Works
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 会按任务需要访问外部网络
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Skill Permissions
Automatically analyze permissions required by all skills in Claude Code and generate one-time authorization commands.
Dangerous Operations Warning
This skill can modify other skill files. The following commands may cause widespread file changes:
| Command | Risk Level | Description |
|---|---|---|
/skill-permissions inject |
High | Batch modify all skill SKILL.md files |
/skill-permissions allow-all |
Medium | Batch modify settings.json |
/skill-permissions allow <name> |
Low | Only modify settings.json |
/skill-permissions <name> |
Safe | Read-only analysis, no file modifications |
Recommendations:
- Prefer explicit commands (e.g.,
/skill-permissions allow port-allocator) - Avoid
injectorallow-allunless you understand the impact - Run
/skill-permissionsfirst to see analysis results before batch operations
Usage
| Command | Description |
|---|---|
/skill-permissions |
Analyze all skills and show permission summary |
/skill-permissions <skill-name> |
Analyze specific skill's permission requirements |
/skill-permissions allow <skill-name> |
Execute one-time authorization for specific skill |
/skill-permissions allow-all |
Execute one-time authorization for all skills |
/skill-permissions inject |
Inject allow command into all skills |
/skill-permissions allow |
Execute one-time authorization for this skill |
How It Works
1. Permission Analysis
Scan skill's SKILL.md file, identifying patterns like:
Bash Command Patterns:
find * → Bash(find *)
ls * → Bash(ls *)
cat ~/.claude/* → Bash(cat ~/.claude/*)
lsof -i:3* → Bash(lsof -i:3*)
git * → Bash(git *)
npm * → Bash(npm *)
Recognition Rules:
- Bash commands in code blocks (
bash ...) - Inline commands (
command) - Explicitly mentioned system commands
2. Permission Rule Generation
Convert identified commands to permissions.allow rules:
{
"permissions": {
"allow": [
"Bash(find * -name package.json *)",
"Bash(ls -d *)",
"Bash(cat ~/.claude/*)",
"Bash(lsof -i:3*)"
]
}
}
Execution Steps
Command: /skill-permissions
Analyze all skills and show permission summary:
Scan all skills
find ~/.claude/skills -name "SKILL.md" -type f 2>/dev/nullAnalyze permissions for each skill
- Read SKILL.md content
- Extract bash code blocks
- Identify command patterns
- Generate permission rules
Output analysis results
Command: /skill-permissions <skill-name>
Analyze specific skill's permission requirements:
Locate skill
SKILL_PATH=$(find ~/.claude/skills -type d -name "<skill-name>" 2>/dev/null | head -1)Read and analyze SKILL.md
Output detailed permission list
Command: /skill-permissions allow <skill-name>
Execute one-time authorization for specific skill:
- Analyze skill permission requirements
- Read existing config
- Merge permission rules (deduplicate, preserve existing rules)
- Write config file
- Output authorization result
Blocked Commands
The following command patterns are automatically blocked and won't be added to the allowlist:
Dangerous File Operations
| Command | Reason |
|---|---|
rm * |
File deletion, may cause data loss |
rm -rf * |
Recursive force delete, extremely dangerous |
sudo * |
Super user privileges |
chmod 777 * |
Opens all permissions |
Dangerous Process Operations
| Command | Reason |
|---|---|
kill -9 * |
Force kill process |
pkill * |
Kill processes by name |
curl * | bash |
Remote code execution |
eval * |
Dynamic code execution |
Dangerous Git Operations
| Command | Reason |
|---|---|
git push --force * |
Force push, may overwrite remote |
git reset --hard * |
Hard reset, loses uncommitted changes |
Output Format
Analysis Result (Single Skill)
Skill: port-allocator
Location: ~/.claude/skills/port-allocator
Detected commands:
- find ~/Codes -maxdepth 3 -name "package.json"
- ls -d */
- cat ~/.claude/port-registry.json
- lsof -i:3000
Generated permission rules:
- Bash(find * -maxdepth * -name package.json *)
- Bash(ls -d *)
- Bash(cat ~/.claude/*)
- Bash(lsof -i:3*)
Run `/skill-permissions allow port-allocator` to authorize
Authorization Success
Permission authorization successful
Skill: port-allocator
Added permission rules:
- Bash(find * -maxdepth * -name package.json *)
- Bash(ls -d *)
- Bash(cat ~/.claude/*)
- Bash(lsof -i:3*)
Config file: ~/.claude/settings.json
New permissions take effect in next session, or run /clear to apply immediately
Configuration Files
- Permission config:
~/.claude/settings.json - Skill directory:
~/.claude/skills/
First Use
If you encounter permission prompts, first run:
/skill-permissions allow
Command: /skill-permissions allow
Execute one-time authorization for this skill:
- Read
~/.claude/settings.json - Merge the following permissions to
permissions.allow:
{
"permissions": {
"allow": [
"Bash(find ~/.claude/skills *)",
"Bash(cat ~/.claude/*)"
]
}
}
- Write config file (preserve existing permissions)
- Output authorization result
Notes
- Conservative analysis - Only identify explicitly appearing commands, avoid over-authorization
- Deduplicated merge - New permissions merge with existing, no duplicates
- No deletion - Only adds permissions, won't delete user's existing permission config
- Wildcards - Use
*to match varying parameter parts - Session effect - Permission updates require new session or /clear to take effect
- Explicit preferred - Recommend explicit commands over batch operations to reduce risks
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核