github-closing-draft Skill
为符合条件的 codex-profiles tracker 目标起草 GitHub PR、issue、列表文案或维护者请求时使用。不用于发现、资格筛选、监控、外联或提交。
安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。
技能指令原文(SKILL.md)
GitHub Closing Draft
Purpose
Create target-specific draft artifacts for qualified codex-profiles leads and
leave them approval-gated in the outreach tracker. This skill drafts only; it never opens,
posts, submits, comments, emails, or sends anything externally.
Required Context
Read README.md, policy gates in ops/outreach/launch.md, the live tracker
target, and the target's contribution rules or submission guidelines. Load
references/draft-rules.md before writing copy.
Boundaries
- Consume only tracker targets with
ICP: yes. - Use
Log.Workflow = closingfor every meaningful draft decision. - Update the tracker with the draft, evidence, and approval blocker.
- Set
Next Action = Await approval to submit draftafter a draft is ready. - Follow the target repository's conventions over
codex-profilesconventions. - Do not perform lead discovery.
- Do not qualify
ICP: maybeorICP: notargets; route unclear fit back to
lead qualification.
- Do not submit, open, post, comment, email, DM, or otherwise contact externally.
Accepted Input
- Consume only
Status = Backlogtargets withICP: yesrecorded inNotes
and Next Action = Run closing draft.
- Never draft for
ICP: maybe,ICP: no,Deferred,Declined, orDead
targets; route unclear evidence back to lead qualification.
Tracker Protocol
Create a unique run-- , select the
eligible target, inspect it, and acquire its lease before drafting:
node scripts/outreach-tracker.mjs list --status Backlog --json
node scripts/outreach-tracker.mjs get <key> --json
node scripts/outreach-tracker.mjs claim <key> --by <run-id>
If claim exits 3, skip the target without writing or contacting externally.
Store the draft or its repo-local path in Notes, hold it for approval, log the
stable phase label, and always release:
node scripts/outreach-tracker.mjs upsert <key> \
--next-action "Await approval to submit draft" \
--notes "<draft text or repo-local artifact path plus evidence>"
node scripts/outreach-tracker.mjs log --target <key> \
--workflow closing --action Rechecked \
--result "Draft prepared; explicit approval required" --link "<target-url>"
node scripts/outreach-tracker.mjs release <key> --by <run-id>
Workflow
- Select tracker targets marked
ICP: yeswithNext Action = Run closing draft. - Recheck duplicate PRs, issues, or existing listings before drafting.
- Read contribution rules, templates, accepted examples, and target scope.
- Identify the target repository's file ordering, wording, commit conventions,
branch conventions, PR title format, validation commands, and maintainer
preference for issue-first vs PR-first.
- Choose the draft route:
- Clear awesome-list fit: prepare a PR diff and PR body draft.
- Ambiguous scope: prepare an issue-first draft.
- Directory: prepare listing copy only when guidelines allow CLI or devtool
projects.
- Forum, social, or manual-gated target: prepare copy only and hold.
- Keep claims narrow and source-backed using
references/draft-rules.md. - Update the tracker with the draft artifact location or text, set the approval
next action, and append a closing log entry.
Output
Return drafts grouped by target, the exact approval action needed, and any
targets routed back to qualification or monitoring.