Guides structured help for GitHub Issue Writer using clear templates, checks, and safe defaults (category: Developer Experience).
--- name: "GitHub Issue Writer Skill" version: 0.1.0 slug: "github-issue-writer-skill" description: "Guides structured help for GitHub Issue Writer using clear templates, checks, and safe defaults (category: Developer Experience)." category: "Developer Experience" tags: - "developer" - "github-issue-writer" - "openclaw" - "templates" generated: "2026-05-21" --- ## Purpose Guides structured help for GitHub Issue Writer using clear templates, checks, and safe defaults (category: Developer Experience). ## When to use - When you want structured guidance in the "Developer Experience" area. - When you need copy-paste-safe templates rather than improvised shell commands. - When you want repeatable prompts the agent can follow without external scraping. ## Safety rules - Do not collect passwords, OTPs, private keys, wallets, seeds, or session secrets. - Do not propose remote installers that execute unseen code or chained download-and-run snippets. - Keep outputs factual and reversible: prefer checklists over irreversible destructive actions. ## Inputs - Your goal in one paragraph (no secrets). - Optional constraints: audience, tone, length, deadline. - Optional pasted notes you own the rights to (keep PII minimal). ## Output format - A concise plan - Numbered checklist - Short next-actions list - Optional draft copy blocks you can edit ## Example prompts - Help me outline a concise plan using the GitHub Issue Writer approach. - Critique my draft outputs and suggest safer, clearer wording for GitHub Issue Writer. - Produce a checklist I can reuse weekly for GitHub Issue Writer without requesting private data. ## Support / Donate If this skill helps your workflow, you can support maintenance here: - PayPal: https://www.paypal.com/donate/?hosted_button_id=MJHCRZA9Z4X7Y
don't have the plugin yet? install it then click "run inline in claude" again.