community-publish

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

88|108|Updated Apr 7, 2026

Search Tags:#secret scanning #pii redaction #github pull request #community publishing #template packaging #telegram approval #open-source contribution

Ready to run

npx skills add https://github.com/grandamenium/cortextos --skill community-publish-grandamenium

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: community-publish
Source: https://github.com/grandamenium/cortextos/tree/main/templates/analyst/.claude/skills/community-publish
Command: npx skills add https://github.com/grandamenium/cortextos --skill community-publish-grandamenium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents accidental leakage of personal or sensitive information when packaging a local skill, agent, or org template for public sharing.

Core Features & Use Cases

PII and secret stripping: Removes personal data and performs a scan for common sensitive artifacts before anything is shared.
Controlled submission workflow: Produces a clean staged submission after a dry-run and requires explicit user approval via Telegram.
Automated community contribution: Supports both local-only submissions and full upstream contributions by creating a branch, updating the catalog, pushing to your fork, and opening a PR via the GitHub CLI.

Quick Start

Ask the Skill to package and stage your local template by saying: "Package the skill at ./skills/morning-review named morning-review for community sharing and show me the dry-run results first."

Frequently Asked Questions about community-publish

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

FAQPage Schema

How do I remove PII and scan for secrets before sharing a local template?▼

Secret scanning and PII redaction for local template sharing work by automatically stripping personal data and scanning for sensitive artifacts before packaging. This staged dry-run process ensures no confidential information remains in the files submitted for public catalog contribution.

How do I package a local skill for open-source contribution via GitHub pull request?▼

Packaging a local skill for open-source contribution involves creating a git branch, updating the catalog, pushing to your fork, and opening a PR via the gh CLI. This automated workflow requires explicit Telegram approval before finalizing the upstream submission.

Can I require explicit Telegram approval before opening a GitHub pull request?▼

Yes, you can require explicit Telegram approval before opening a GitHub pull request. The community publishing workflow enforces a staged dry-run and prompts the user via Telegram to authorize the final branch creation and PR submission.

What is the best way to prevent accidental leakage of sensitive data in community publishing?▼

The best way to prevent accidental leakage in community publishing is to apply a staged dry-run that performs PII redaction and secret scanning. This ensures local templates are completely sanitized before any public sharing or upstream contribution occurs.

Does community publishing work with local-only submissions or do I need to push to a fork?▼

Community publishing supports both local-only submissions and full upstream contributions. You can stage your template locally for dry-run review, or proceed with pushing to your fork and opening a PR via the gh CLI after granting Telegram approval.