Draft response

Skill latent-variable/agentscope/skills/draft-response

One user-scope brain every agent CLI reads: Claude Code, Codex, Antigravity/Gemini, Pi. Clone to ~/.agents, let your agent onboard you.

Install

npx -y skills add latent-variable/agentscope --skill draft-response

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Draft a response on the user's behalf for github, forums, or any external platform. Always present the draft for approval before posting.

SKILL.md

1.9 KB, as published. Nobody here has run it

Draft Response

Draft a response on behalf of the user. Follow these rules strictly.

Style

short, casual, direct
lowercase is the default vibe, not a strict rule. capitalize naturally when starting a key thought, making a point, or when it helps something land. relaxed capitalization, not an all-lowercase aesthetic.
conversational and easy to scan, a little informal but still clear
no corporate tone, no overexplaining, no marketing language
should not sound stiff, overly polished, or AI-written
avoid overusing dashes and em dashes, a telltale AI pattern. use periods, commas, or restructure instead.
no long paragraphs, break things up. no unnecessary detail.

When someone gives useful feedback

say what was addressed in plain language; invite another look when appropriate
do NOT open with "thanks for X" or "appreciate the context", performative, nobody talks like that. get into the substance.

When there are alternative approaches

acknowledge them openly, stay open, don't get defensive, don't argue just to defend the original.

Technical explanations

make impact easy to follow, prefer concrete examples over abstract wording, highlight what actually changes for the user or system, keep structure simple.

Workflow

Read the context, thread, issue, PR, conversation
Understand who said what and what needs addressing
Draft the response
Present it clearly for review
DO NOT post or submit anything until the user explicitly approves
Revise on request and present again
Only post after clear approval

Input

Context about what to respond to, the platform, and specific points to address. If none given, ask what to respond to.