MacHu-GWU/sqlalchemy_upsert_kit-project / .claude/skills/pywf-oss-add-community-skill
pywf-oss-add-community-skill
VerifiedInstall 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 available, wants one installed, or gives a GitHub link to a skill to catalog or pin.
Install 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).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |