code-share
Share code via GitHub Gist instead of inline chat blocks. Use when code output exceeds 10 lines, when the user asks for copy-friendly code sharing in Discord/chat, or when preserving formatting is important.
Why use this skill?
Learn how to use the code-share OpenClaw skill to automatically manage, update, and share your code via GitHub Gists, keeping your workspace clean and efficient.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/jeromestein/code-shareWhat This Skill Does
The code-share skill acts as an efficient bridge between OpenClaw and GitHub Gists, allowing the AI to offload lengthy or complex codebases into a persistent, readable, and copy-friendly format. By leveraging the GitHub CLI, the skill ensures that long-form coding outputs are hosted externally rather than bloating the chat history. This creates a cleaner interface while maintaining full syntax highlighting and version control for the code being discussed. The skill is designed to handle sensitive data proactively by sanitizing inputs and utilizing secret Gists by default to protect user intellectual property.
Installation
To integrate this utility, run the following command in your terminal: clawhub install openclaw/skills/skills/jeromestein/code-share. Ensure the GitHub CLI is installed on your host system and that you have run gh auth login to provide the necessary permissions for creating and updating Gists.
Use Cases
This skill is perfect for developers working on projects requiring long scripts, configuration files, or data structures that exceed 10 lines of text. It is especially useful for collaborative troubleshooting, where you need to share a robust snippet with a colleague or store a specific iteration of a script for later reference. It is also the standard for versioned updates, allowing you to iterate on code blocks without flooding your chat history with duplicate versions of the same file.
Example Prompts
- "Here is the full implementation of the API integration script; please share it as a Gist so I can copy it into my project."
- "I've modified the previous script to include error handling, please update the existing Gist with these changes."
- "Could you create a public Gist for this solution so I can share it with my team on Slack?"
Tips & Limitations
Always remember to check your code for hardcoded secrets or API keys before triggering a share. While the skill encourages safe practices, the onus remains on the user to ensure sensitive data is replaced with placeholders. Note that the skill is optimized for GitHub; if your organization uses an internal repository or a different platform, this skill will not natively support those alternatives. Keep your files named appropriately with correct extensions to ensure the best syntax highlighting in the Gist interface.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-jeromestein-code-share": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write, external-api