Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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...
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...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
When returning code: If code is 10 lines or fewer, inline code block is allowed. If code is over 10 lines, prefer GitHub Gist. Default to secret gist unless user asks for public. Return a short summary + gist URL; avoid pasting long duplicate code in chat. Never publish secrets in shared code. If sensitive values are needed, use placeholders and tell user to fill them locally.
Verify GitHub CLI auth: gh auth status If not authenticated (or missing gist scope), ask user to run: gh auth login Keep behavior simple: do not auto-fallback to alternate sharing backends by default; prefer guiding user to configure GitHub properly.
Before sharing code, scan for sensitive data and remove it. Never include API keys, tokens, passwords, private keys, cookies, session IDs, webhook secrets, phone/email PII, or absolute local secret paths. If code requires secrets, replace with placeholders, for example: API_KEY="<FILL_ME>" TOKEN="<YOUR_TOKEN_HERE>" .env entry with empty value Add a short note telling the user to fill placeholders locally after copying.
When user asks to modify previously shared code, prefer updating the same gist link (new revision) instead of creating a new gist. Use: ./scripts/update_gist.sh <gist_url_or_id> <file> "<short description>" [public|secret] [lang] Behavior: Keep the same gist URL. Save changes as a new revision. Return the same fixed 3-line response format. Create a new gist only when: user explicitly asks for a new link, or existing gist is not editable by current GitHub account.
Use: gh gist create <file> --desc "<short description>" If code is generated in-session, write it to a temp file in workspace first. Use language-appropriate extension (.py, .js, .ts, etc.) so Gist syntax highlighting works well. With bundled script: ./scripts/create_gist.sh <file> "<short description>" [public|secret] [lang] If <file> has no extension, pass [lang] (for example python, typescript) so the script can upload with a proper extension. Default behavior: do not use --web (automation-friendly). Optional: use --web only when the user explicitly asks to open the gist in browser immediately.
Always use exactly this 3-line format: One sentence on what was shared. Gist URL (separate line). File: <filename> ยท Lines: <line_count> Example: Shared the full script as a secret Gist for clean copy/paste. https://gist.github.com/... File: lc761_solution.py ยท Lines: 42
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.