pywf-oss-add-community-skill
Install an optional community Agent Skill from the pinned catalog after a security review, or add or update a catalog entry from a GitHub link. Use when the user asks which community skills are availa
SKILL.md.claude/skills/pywf-oss-add-community-skill/SKILL.md
GitHubInstall a community skill from the catalog, or add or update a catalog entry. A script does the installing; this skill picks the entry, reviews the staged content, and keeps the catalog correct.
Read ../pywf-oss-base/SKILL.md, then:
- ../pywf-oss-base/references/26-community-skills.md
Catalog: ../pywf-oss-base/assets/community-skills.toml
Install a skill
The script commands are in 26-community-skills.md section 3.
- Pick. Run the script with
--list, match the user's need against each entry'swhen_to_use, and confirm the choice with the user. - Stage with
--name <skill_name>, without--install. - Review the staged folder as in
26-community-skills.mdsection 4. Report what the skill does, what each script touches, and anything risky. - Install. After the user's yes, rerun with
--install. Report the installed path and its.source.json. - Git. The skill is git-ignored by default. Ask whether it should be committed with the repo; if yes, delete its line from
.gitignore.
Add or update a catalog entry
- From the user's GitHub link, find the skill folder and pin it, as in
26-community-skills.mdsection 2. - Show the new or changed entry, with a proposed
when_to_use, and save it after the user's yes. For a new entry, also add its.gitignoreline. - Optionally stage it once, to prove the URL works.
Boundaries
- Never install a skill that has not been staged and reviewed.
- Never run any of a downloaded skill's scripts during the review.
- Never overwrite an installed skill without the user's yes (
--force).