skills.rest
mishahanin
mishahaninCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

publish-corporate

Synchronize classified files from a private overlay to a shared repository with leak scanning.

10|1|Updated Jun 29, 2026
Search Tags:#automation#git#publishing#security#executive#corporate
One-click install
npx skills add https://github.com/mishahanin/heading-os --skill publish-corporate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-corporate
Source: https://github.com/mishahanin/heading-os/tree/main/.claude/skills/publish-corporate
Command: npx skills add https://github.com/mishahanin/heading-os --skill publish-corporate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of securely and selectively distributing sensitive corporate-classified content from a private executive data repository to a shared corporate repository without exposing personal or private information.

Core Features & Use Cases

  • Selective Publishing: Allows the CEO to push specific files to the corporate repo while maintaining strict separation between private and public data.
  • Safety Guardrails: Includes a critical-leak scanner to prevent accidental exposure of sensitive data like personal contacts, API keys, or private threads.
  • Version Control: Automatically increments version numbers and updates the changelog in the corporate repository upon successful publication.

Quick Start

Invoke the publish corporate skill by typing /publish-corporate followed by a description of the content you wish to distribute to the executive team.

Frequently Asked Questions about publish-corporate

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

FAQPage Schema
How do I securely publish executive content from a private repository to a corporate repository?▼

Securely publishing executive content involves selectively synchronizing files from a private data overlay to a shared repository while applying file classification and critical-leak scanning to prevent accidental exposure.

How does automated versioning work for corporate content publishing?▼

Automated versioning for corporate publishing increments version numbers and updates the changelog in the shared repository upon successful publication, ensuring organizational transparency without manual file edits.

Can I prevent accidental data leaks when distributing classified files to a shared corporate repository?▼

Preventing accidental data leaks during corporate distribution requires a critical-leak scanner to identify and block sensitive information like personal contacts or API keys before files reach the shared repository.

What is the best way to selectively synchronize corporate content without exposing private data?▼

The best way to selectively synchronize corporate content is using a routing-map configuration to manage file classification and push only approved items from a private data overlay to a shared executive repository.

Do I need to manually verify administrative identity to distribute executive content?▼

Yes, distributing executive content requires manual verification of administrative identity to ensure strict adherence to routing-map configurations and maintain secure separation between private and public data.

Why does corporate content publishing require a routing-map configuration?▼

Corporate content publishing requires a routing-map configuration to manage selective synchronization, ensuring strict separation between private and public data while routing classified files to the correct shared repository.

Related Skills

Explore More Content & Communication Skills→
cajiascajias

rsi-loop

Manage recursive self-improvement workflows for evaluating research-agent rewrites.

Community
Advanced
mishahaninmishahanin
10

push-updates

Propagate workspace updates and corporate-classified content across distributed executive systems.

Community
Advanced
florianbuetowflorianbuetow
12

secrets

Scans source code, configuration files, and git history for hardcoded credentials, API keys, tokens, and private keys.

Community
Advanced
giladresisigiladresisi
3

commit

Stage all Git changes, scan for secrets, and commit with conventional format.

Community
Intermediate