OpenClaw

skill-shell

Evaluate external skills before installation and decide whether to install, reject, or absorb only the useful ideas. Use when a user shares a ClawHub/GitHub skill link, asks whether a skill is worth installing, asks for a code/safety review before installation, or wants to compare a skill's workflow with the current OpenClaw workflow.

g-hanasq0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install g-hanasq/skill-shell

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Skill Shell

Use this skill to gate external skills before they enter the current OpenClaw workflow.

Core rule

Do not treat every published skill as worth installing. First decide what problem the user is actually trying to solve. Then inspect the package, judge the risks, and decide one of three outcomes:

Install candidate
Review-only / absorb ideas
Reject / do not install

Preferred workflow

Clarify the real capability the user wants.
Classify the skill type before judging it.
Inspect the package contents, not just the landing page.
Separate static review from dynamic validation.
Check whether it fits the current OpenClaw workflow or drags in another ecosystem.
Check whether it adds ongoing token cost, hooks, background behavior, or unstable config changes.
Check environment landing zone and validation level: shell, gateway, LaunchAgent, cron.
Explain the recommendation in plain language.
Install only after explicit user approval.

Skill type classification

Classify the candidate into one primary type before making a recommendation:

Capability skill: adds a concrete new capability (search, extraction, automation, generation, file handling)
Integration skill: depends on credentials, env vars, services, or runtime placement to become usable
Automation skill: controls browsers, CLIs, workflows, or long-running operational behavior
Workflow / methodology skill: mostly guidance, process, prompts, or ways of thinking
Shell / incomplete skill: mostly docs/meta, or promises code/assets that are not actually present

Different types require different scrutiny. Do not evaluate them all with one generic standard.

Static review vs dynamic validation

Static review

Static review asks:

what files are actually present
whether docs match the package
what dependencies and scripts exist
whether the package looks coherent or misleading
whether Codex should be use...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/g-hanasq/skill-shell
Version: —
Commit: d2973e1d6077bbdec9b24b447f09a7874b1dbee6
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Skill Shell

Use this skill to gate external skills before they enter the current OpenClaw workflow.

## Core rule

Do not treat every published skill as worth installing.
First decide what problem the user is actually trying to solve.
Then inspect the package, judge the risks, and decide one of three outcomes:

1. **Install candidate**
2. **Review-only / absorb ideas**
3. **Reject / do not install**

## Preferred workflow

1. Clarify the real capability the user wants.
2. Classify the skill type before judging it.
3. Inspect the package contents, not just the landing page.
4. Separate **static review** from **dynamic validation**.
5. Check whether it fits the current OpenClaw workflow or drags in another ecosystem.
6. Check whether it adds ongoing token cost, hooks, background behavior, or unstable config changes.
7. Check environment landing zone and validation level: shell, gateway, LaunchAgent, cron.
8. Explain the recommendation in plain language.
9. Install only after explicit user approval.

## Skill type classification

Classify the candidate into one primary type before making a recommendation:

- **Capability skill**: adds a concrete new capability (search, extraction, automation, generation, file handling)
- **Integration skill**: depends on credentials, env vars, services, or runtime placement to become usable
- **Automation skill**: controls browsers, CLIs, workflows, or long-running operational behavior
- **Workflow / methodology skill**: mostly guidance, process, prompts, or ways of thinking
- **Shell / incomplete skill**: mostly docs/meta, or promises code/assets that are not actually present

Different types require different scrutiny. Do not evaluate them all with one generic standard.

## Static review vs dynamic validation

### Static review

Static review asks:
- what files are actually present
- whether docs match the package
- what dependencies and scripts exist
- whether the package looks coherent or misleading
- whether Codex should be use...

搜索