skills.rest
MrWest3
MrWest3COMMUNITY
Explore all skills by this author →
GitHub

community-publish

Package local skills, agents, or org templates for community submission via PR.

Updated Aug 27, 2026
Search Tags:#automation#templates#community#publish#pr#submission#pii-scan
One-click install
npx skills add https://github.com/MrWest3/west-command-center --skill community-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: community-publish
Source: https://github.com/MrWest3/west-command-center/tree/main/templates/analyst/.claude/skills/community-publish
Command: npx skills add https://github.com/MrWest3/west-command-center --skill community-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Package a local skill, agent template, or org template for community sharing. Strips PII, scans for secrets, prepares a clean submission, and opens a PR to the community catalog.

Core Features & Use Cases

  • Dry-run packaging to preview what would be shared.
  • Automated PII and secret scanning to ensure privacy and compliance.
  • One-click submission to the community catalog via PR workflow.
  • Supports sharing skills, agents, or org templates with clear governance.

Quick Start

Prepare a dry-run of a submission for a skill, agent, or org template with wcc bus prepare-submission <type> <source-path> <item-name> --dry-run.

Frequently Asked Questions about community-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a local skill template to a community catalog safely?▼

To publish a local skill template safely, use a dry-run packaging flow to preview shared assets, apply automated PII stripping and secrets scanning, then open a PR to the community catalog for explicit approval.

What does dry-run packaging do before submitting assets to a community catalog?▼

Dry-run packaging previews exactly what local skills, agent templates, or org templates would be shared before submission, applying PII and secret scanning to verify no sensitive data leaks during the community publish flow.

Do I need a GitHub-based workflow to submit templates via PR?▼

Yes, template submission requires a GitHub-based workflow with pull requests. The packaging flow opens a PR to a configurable community catalog, relying on explicit user approval steps to merge the shared assets.

Can I scan for secrets and PII before opening a pull request for a skill?▼

Yes, automated PII stripping and secrets scanning execute during the dry-run phase before PR creation. This ensures the packaged skill, agent, or org template is clean before opening a pull request to the community catalog.

What is the best way to share org templates with clear governance?▼

The best way to share org templates with clear governance is through a submission flow with explicit user approval steps, which packages the template, strips PII, scans for secrets, and opens a governed PR to the community catalog.

Related Skills

Explore More Content & Communication Skills→
jamesjlundinjamesjlundin
32

secrets-scanner

Scan codebases for secrets, credentials, and PII patterns.

Community
Intermediate
andreadellacorteandreadellacorte
5

groove-groovebook-review

Browse and review open learning pull requests in a groovebook repository.

Community
Intermediate
grandameniumgrandamenium
88

community-publish

Package local templates for community submission while stripping PII and scanning for secrets.

Community
Intermediate
openakitaopenakita
2.0k

submit-skill-repo

Submit a GitHub repository URL to the OpenAkita Skill Store for indexing.

Community
Basic