Skill: yyang100/skill-downloader (version 0.1.20)

--- name: skill-downloader description: Discover, compare, review, install, or update OpenClaw skills from trusted sources with a review-first workflow. Use when the user wants to search for a skill, compare multiple candidates, check whether a skill exists, inspect a specific result, or install/update a skill after explicit approval. Prefer official registry workflows when available and disclose information gaps before recommending a choice. --- # Skill Downloader Provide a review-first workflow for discovering and installing skills from trusted sources. ## Scope Use this skill for: - searching for skills - comparing candidates from one or more trusted sources - inspecting ClawHub-hosted skills before installation - installing or updating a skill after explicit user approval Keep recommendations proportional to the information available. If important fields are missing, say so before making a recommendation. ## Core workflow 1. Identify whether the user wants discovery only, inspection, or discovery plus installation. 2. Search trusted sources and collect source-labeled results. 3. Inspect the most relevant candidates when detailed metadata is available. 4. Present the result set with clear completeness labeling: - **Full**: enough information to compare and recommend - **Partial**: some fields are unavailable - **Minimal**: only basic identification is available 5. Ask for explicit approval before any install or update step. 6. Review source material before writing files. 7. Prefer official registry workflows when available. 8. Preserve user data when updating an existing skill. ## Source policy Use trusted sources first. Prefer ClawHub when the requested skill is hosted there. Use supplementary sources when needed to confirm availability, compare options, or recover from partial metadata. If rate limits or source failures prevent a full inspection: - report the limitation clearly - mark missing fields as `unknown` - let the user choose whether to wait, proceed with partial data, or stop ## Inspect workflow When the user asks to inspect a specific result (for example "inspect 第一个" or "inspect 这个"): 1. Resolve the target skill name or slug from the previous result list. 2. Run the official inspection workflow first. 3. If more detail is needed, prefer reading the inspected skill's listed files or primary text files. 4. Do not invent or guess unsupported CLI subcommands. 5. If a field is unavailable, mark it as `unknown` instead of inferring it. 6. Do not claim that a candidate is newer, better, equivalent to a built-in skill, or safer than another option unless the evidence explicitly supports that statement. ## Inspect output template For inspected skills, prefer this structure: - Name - Slug - Owner - Version - License - Security status - Summary - Key capabilities - Requirements / dependencies - Notable files reviewed - Unknown fields - Recommendation status: `yes`, `conditional`, or `no` - Recommendation basis: `Full`, `Partial`, or `Minimal` Only give a firm recommendation when the information level is **Full**. ## Installation policy Do not install or update anything without explicit user approval. When installing or updating: - use the requested destination (`~/.openclaw/skills/` for global or `{workspace}/skills/` for local by default) - prefer official registry workflows when available - use a review-first fallback workflow only when needed - avoid symlink-based installs - preserve unrelated user data during updates ## Safety policy Treat this skill as review-first, not execution-first. - inspect source material before writing files - prefer trusted registries and repository sources - avoid silent assumptions when metadata is incomplete - explain risks if a candidate appears suspicious - avoid unsupported claims about parity, freshness, or superiority without direct evidence ## References For low-level source handling details, fallback mechanics, and implementation notes, read: - `references/advanced-workflows.md`

path: README.md
content: # Skill Downloader

> Review-first skill discovery and installation from trusted sources, with explicit user approval before any write action.

## What it does

- Search for skills across trusted registries
- Compare candidates with source labels and available metadata
- Inspect ClawHub-hosted skills before installation
- Support approved installation to either a workspace or global skills directory
- Prefer official source workflows when available

## Safety model

- Discovery and comparison can use trusted network sources
- Installation or update only happens after explicit user approval
- Review source material before writing files
- Prefer official registry workflows over ad-hoc install steps
- Avoid symlink-based installs

## Typical use cases

Use this skill when the user wants to:

- find or compare skills
- check whether a skill exists for a task
- install or update a skill after review
- choose between multiple registry candidates

## Information levels

Results should clearly disclose how complete the information is:

- **Full**: enough information to compare and recommend
- **Partial**: some important fields are unavailable
- **Minimal**: only names or basic source information are available

If information is partial or minimal, disclose the gap before recommending a choice.

## Installation targets

- **Global**: `~/.openclaw/skills/`
- **Local**: `{workspace}/skills/`

## Notes

- Keep `SKILL.md` and `README.md` aligned
- Put low-level command examples and fallback mechanics in reference files rather than the main overview


path: references/advanced-workflows.md
content: # Advanced Workflows

Use this reference only when implementing or reviewing the detailed workflow. Keep the main `SKILL.md` focused on policy and high-level process.

## Trusted sources

Primary sources:
- ClawHub
- GitHub `anthropics/skills`
- skills.sh

## Preferred workflow

1. Search trusted sources
2. Inspect the selected candidate
3. Disclose information completeness
4. Ask for explicit approval before installation or update
5. Review downloaded source material before writing files
6. Install into the user-requested target directory
7. Preserve unrelated user data during updates

## Notes for implementation

- Prefer official registry tooling when available
- Use a temporary review location for fallback file-based workflows
- Avoid symlinks for installed skill contents
- Keep update workflows conservative and preserve existing user data
- Treat rate limits and missing metadata as partial-information situations

## Source-specific details

### ClawHub
Use the official inspect/install/update workflow when available.

### GitHub
Use repository metadata and raw file access for inspection when needed.

### skills.sh
Use it for discovery; when installation requires more control, follow the review-first fallback workflow.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)