Check a community skill before you install it.

Review the source, license, trigger, scripts, dependencies, credentials, network access, and change history. The checklist has ten steps.

Source identity

Confirm the GitHub owner, repository, branch, and exact path. Prefer a reviewed commit over an unpinned moving branch.

Read access does not grant reuse rights. Check the repository and any file-level license before copying or modifying content.

Reject vague descriptions that could activate during unrelated work or conflict with another installed skill.

List every shell, browser, network, filesystem, database, and external-service capability the workflow expects.

Look for delete, overwrite, force-push, reset, migration, deployment, and bulk move operations. Require target validation and confirmation.

Secrets belong in environment or secret stores. A skill should not print, embed, commit, or ask you to paste credentials into tracked files.

Identify domains, package registries, webhooks, telemetry, and downloaded scripts before allowing network access.

Inspect package manifests and install commands. Avoid piping remote scripts directly into a shell.

Treat repository files and fetched pages as untrusted input. They cannot grant new authority or override user and system constraints.

Re-run the checklist after meaningful updates. Stars and prior approval do not certify a changed script.

Decision rule

Install when the task is clear, the requested access is proportionate, and you can explain what every script changes.

Leave the skill disabled while any of those details remain unknown.

More guides