skills.rest
00200200
00200200COMMUNITY
Explore all skills by this author →
GitHub

mkl-write-maintainer-reply

Draft evidence-based replies to issues, PR discussions, and support reports.

11|1|Updated Sep 13, 2026
Search Tags:#open source#github#communication#bug report#issue triage#technical support#maintainer reply
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-write-maintainer-reply-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-write-maintainer-reply
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-write-maintainer-reply
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-write-maintainer-reply-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers often struggle to write replies to bug reports and discussions that are accurate, respectful, and free of unsupported promises. This Skill drafts ready-to-send responses grounded only in available evidence, avoiding invented commitments or premature claims. ## Core Features & Use Cases - Evidence-grounded drafting: Distinguishes reported behavior, observed reproduction, proposed fix, merged fix, and released fix so replies never overstate the current state. - Focused information requests: Asks only for the smallest useful reproduction, such as a redacted configuration or synthetic example, instead of secrets or full production data. - Use Case: A user reports "Install fails on Windows with Python 3.11, PermissionError" with no command or path. The Skill drafts a reply requesting exactly those two missing details while acknowledging the known environment and stating the error has not been reproduced. ## Quick Start Ask the assistant to draft a maintainer reply to the attached issue report using the available evidence and project policy.

Frequently Asked Questions about mkl-write-maintainer-reply

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

FAQPage Schema
How do I write a good reply to a vague bug report?▼

Identify what the reporter already provided, then request only the smallest missing details needed to reproduce the issue, such as the failing command and destination path. State what is known before what is needed, and explain why each request helps.

How to respond to GitHub issues without overpromising fixes?▼

Distinguish reported behavior, observed reproduction, proposed fix, merged fix, and released fix, and only claim a state the evidence supports. Avoid inventing deadlines, maintenance promises, or decisions to close a discussion.

Should a maintainer reply ask for production data or credentials?▼

No. Request the smallest useful reproduction instead, such as a redacted configuration or a small synthetic example. Asking for secrets or complete production datasets is unnecessary and discouraged.

Can this Skill post replies or close issues automatically?▼

No. It only produces a ready-to-send draft. Posting, closing issues, applying labels, or assigning people are separate external actions that require existing user authorization.

What are the limitations of AI-drafted maintainer replies?▼

The draft is only as accurate as the supplied evidence and project policy. It cannot verify reproductions itself, so maintainers must confirm technical claims and links before sending.

Related Skills

Explore More Software Engineering Skills→
zivtechzivtech

donquixote-query

Map topics to donquixote's documented positions with drupal.org issue citations.

Official
Advanced
ValescoAgencyValescoAgency

triage

Triage tracker issues and generate Agent Briefs for AFK eligibility.

Official
Advanced
wimpysworldwimpysworld
716

contribution-voice

Structures public-facing comments, reviews, and pull request descriptions within strict length budgets.

Official
Basic
jbreel77888jbreel77888

canned-responses

Generate jurisdiction-specific legal response templates with escalation trigger checks.

Community
Intermediate