skills/guo-yu/skill-permissions/SKILL.md
Skill permission analysis, one-time authorization, analyze skill permissions, batch authorization
npx skillsauth add aiskillstore/marketplace skill-permissionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automatically analyze permissions required by all skills in Claude Code and generate one-time authorization commands.
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:
/skill-permissions allow port-allocator)inject or allow-all unless you understand the impact/skill-permissions first to see analysis results before batch operations| 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 |
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 ... )command)Convert identified commands to permissions.allow rules:
{
"permissions": {
"allow": [
"Bash(find * -name package.json *)",
"Bash(ls -d *)",
"Bash(cat ~/.claude/*)",
"Bash(lsof -i:3*)"
]
}
}
/skill-permissionsAnalyze all skills and show permission summary:
Scan all skills
find ~/.claude/skills -name "SKILL.md" -type f 2>/dev/null
Analyze permissions for each skill
Output analysis results
/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
/skill-permissions allow <skill-name>Execute one-time authorization for specific skill:
The following command patterns are automatically blocked and won't be added to the allowlist:
| 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 |
| Command | Reason |
|---------|--------|
| kill -9 * | Force kill process |
| pkill * | Kill processes by name |
| curl * \| bash | Remote code execution |
| eval * | Dynamic code execution |
| Command | Reason |
|---------|--------|
| git push --force * | Force push, may overwrite remote |
| git reset --hard * | Hard reset, loses uncommitted changes |
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
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
~/.claude/settings.json~/.claude/skills/If you encounter permission prompts, first run:
/skill-permissions allow
/skill-permissions allowExecute one-time authorization for this skill:
~/.claude/settings.jsonpermissions.allow:{
"permissions": {
"allow": [
"Bash(find ~/.claude/skills *)",
"Bash(cat ~/.claude/*)"
]
}
}
* to match varying parameter partsdevelopment
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.