Agent skill

GitHub Closing Draft

A skill your agent uses when drafting GitHub PRs, issues, listing copy, or maintainer requests for qualified codex-profiles tracker targets.

MITAuto-check passedWriting & Content

Install GitHub Closing Draft

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-closing-draft -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-closing-draft --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/github-closing-draft .claude/skills/github-closing-draft && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "github-closing-draft" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-closing-draft into .claude/skills/github-closing-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-closing-draft", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-closing-draft

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-closing-draft -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-closing-draft --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/github-closing-draft .agents/skills/github-closing-draft && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "github-closing-draft" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-closing-draft into .agents/skills/github-closing-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-closing-draft", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-closing-draft -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-closing-draft --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/github-closing-draft .cursor/skills/github-closing-draft && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "github-closing-draft" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-closing-draft into .cursor/skills/github-closing-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-closing-draft", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Ducksss/codex-profiles.git --path .agents/skills/github-closing-draft

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-closing-draft -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-closing-draft --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/github-closing-draft .gemini/skills/github-closing-draft && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "github-closing-draft" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-closing-draft into .gemini/skills/github-closing-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-closing-draft", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-closing-draft

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-closing-draft -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/github-closing-draft .github/skills/github-closing-draft && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "github-closing-draft" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-closing-draft into .github/skills/github-closing-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-closing-draft", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ducksss/codex-profiles --skill github-closing-draft -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Ducksss/codex-profiles github-closing-draft --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ducksss/codex-profiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/github-closing-draft .opencode/skills/github-closing-draft && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "github-closing-draft" agent skill from https://github.com/Ducksss/codex-profiles/tree/main/.agents/skills/github-closing-draft into .opencode/skills/github-closing-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-closing-draft", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: github-closing-draft
GitHub stars: 177
Token cost: ~913 tokens
SKILL.md length: 382 words
Files: 3 (incl. references)
Skills in repo: 4
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when drafting GitHub PRs, issues, listing copy, or maintainer requests for qualified codex-profiles tracker targets.

Works in 7 steps: Select tracker targets marked ICP: yes… → Recheck duplicate PRs, issues, or… → Read contribution rules, templates,… → …
Drafting GitHub PRs
SKILL.md covers Purpose, Required Context, Boundaries and Accepted Input, plus 3 more sections
Calls node

What it does

GitHub Closing Draft is an agent skill from Ducksss/codex-profiles. Use when drafting GitHub PRs, issues, listing copy, or maintainer requests for qualified codex-profiles tracker targets. Not for discovery, qualification, monitoring, outreach, or submission.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/draft-rules.md`).

It sits in Writing & Content, covering Copywriting. It works with GitHub, OpenAI and Bash. The repository describes itself as: Named CODEXHOME profiles and ChatGPT Desktop windows with separate local state, without copying tokens. The licence is MIT.

When your agent uses it

Drafting GitHub PRs
Maintainer requests for qualified codex-profiles tracker targets

Example prompts

“/github-closing-draft”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Select tracker targets marked ICP: yes with Next 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,
Choose the draft route
Keep claims narrow and source-backed using references/draft-rules.md.
Update the tracker with the draft artifact location or text, set the approval

What it can do on your machine

Read from SKILL.md and the folder at commit 7152cd5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Closing Draft loads about 913 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 382 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~913
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Ducksss/codex-profiles at commit 7152cd5, republished under its MIT licence (© Ducksss). 382 words, ~913 tokens.

Download SKILL.mdSave it as .claude/skills/github-closing-draft/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: github-closing-draft
description: Use when drafting GitHub PRs, issues, listing copy, or maintainer requests for qualified codex-profiles tracker targets. Not for discovery, qualification, monitoring, outreach, or submission.

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 = closing for every meaningful draft decision.
Update the tracker with the draft, evidence, and approval blocker.
Set Next Action = Await approval to submit draft after a draft is ready.
Follow the target repository's conventions over codex-profiles conventions.
Do not perform lead discovery.
Do not qualify ICP: maybe or ICP: no targets; route unclear fit back to lead qualification.
Do not submit, open, post, comment, email, DM, or otherwise contact externally.

Accepted Input

Consume only Status = Backlog targets with ICP: yes recorded in Notes and Next Action = Run closing draft.
Never draft for ICP: maybe, ICP: no, Deferred, Declined, or Dead targets; route unclear evidence back to lead qualification.

Tracker Protocol

Create a unique run-<UTC-timestamp>-<random-suffix> <run-id>, 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>

Show full SKILL.md (152 more words)Show less

Workflow

Select tracker targets marked ICP: yes with Next 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.

Files

SKILL.md and 2 other files (references) in .agents/skills/github-closing-draft of Ducksss/codex-profiles.

SKILL.md
agents/openai.yaml
references/draft-rules.md

Open the folder on GitHubat commit 7152cd5

Compare with similar skills

GitHub Closing Draft next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Closing Draft compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
GitHub Closing Draft this skillDucksss/codex-profiles	177	—	~913	Automated safety check: Pass	MIT	today
Unslop TextJCarterJohnson/vibecoded-design-tells	511	—	~3.5k	Automated safety check: Pass	Custom licence	3 mo ago
Humanizer RuVladimir-Human/humanizer-ru	126	—	~4k	Automated safety check: Pass	MIT	5 days ago
Publish ReleaseAyuilos/Miffan	192	—	~635	Automated safety check: Pass	AGPL-3.0	yesterday
Tech Trend Spiderwenbochang888/github-trending-spider	159	—	~703	Automated safety check: Pass	MIT	yesterday
Book Publisherdmccreary/ibook-skills	105	—	~1.3k	Automated safety check: Pass	CC-BY-NC-4.0	today

Similar skills

Unslop Text
JCarterJohnson/vibecoded-design-tells
Strips the cues that make prose read as AI-generated and forces a deliberate human voice instead of the model's default register.
511 GitHub stars~3.5k tokensUpdated 3 mo ago
DevelopmentAuto-check passed
Humanizer Ru
Vladimir-Human/humanizer-ru
Не для обхода детекторов; не для текста, который тебе не принадлежит.
126 GitHub stars~4k tokensUpdated 5 days ago
Writing & ContentAuto-check passed
Publish Release
Ayuilos/Miffan
Publish a GitHub release for this fork, with a bilingual changelog that separates fork-owned changes from changes introduced by upstream merges.
192 GitHub stars~635 tokensUpdated yesterday
MobileAuto-check passed
Tech Trend Spider
wenbochang888/github-trending-spider
当用户想获取、查看、汇总、分析或本地过滤 AI 最相关的最新信息时使用本 Skill；只要请求有哪怕 1% 与 AI 最新动态、技术趋势、开源热榜、社区讨论或工程实践相关，就必须优先调用本 Skill。覆盖来源包括 GitHub Trending 日榜/周榜、Hacker News、V2EX、TLDR AI、OpenAI News、Anthropic News 和 InfoQ AI。本…
159 GitHub stars~703 tokensUpdated yesterday
Writing & ContentAuto-check passed
Book Publisher
dmccreary/ibook-skills
Publishes and promotes a finished intelligent textbook - GitHub README with badges and site statistics, LinkedIn announcement posts, LinkedIn carousel document posts (PPTX/PDF slideshows), and…
105 GitHub stars~1.3k tokensUpdated today
Writing & ContentAuto-check passed
Map Your Market
Varnan-Tech/opendirectory
Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences…
674 GitHub stars~4.3k tokensUpdated 1 mo ago
Writing & ContentAuto-check passed

Questions about GitHub Closing Draft

What does GitHub Closing Draft do?

A skill your agent uses when drafting GitHub PRs, issues, listing copy, or maintainer requests for qualified codex-profiles tracker targets. GitHub Closing Draft is an agent skill from Ducksss/codex-profiles. Use when drafting GitHub PRs, issues, listing copy, or maintainer requests for qualified codex-profiles tracker targets.

When should I use GitHub Closing Draft?

GitHub Closing Draft fits situations like: drafting GitHub PRs; maintainer requests for qualified codex-profiles tracker targets.

How do I install GitHub Closing Draft in Claude Code?

Run `npx skills add Ducksss/codex-profiles --skill github-closing-draft -a claude-code`. Or copy the skill folder (.agents/skills/github-closing-draft in Ducksss/codex-profiles) into .claude/skills/github-closing-draft in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Closing Draft in Codex?

Run `npx skills add Ducksss/codex-profiles --skill github-closing-draft -a codex`. Or copy the skill folder (.agents/skills/github-closing-draft in Ducksss/codex-profiles) into .agents/skills/github-closing-draft in your project. Codex loads it when a task matches its description.

Can I use GitHub Closing Draft in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ducksss/codex-profiles --skill github-closing-draft -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-closing-draft, .gemini/skills/github-closing-draft, .github/skills/github-closing-draft and .opencode/skills/github-closing-draft in your project.

What does GitHub Closing Draft need to run?

Going by SKILL.md and its folder, GitHub Closing Draft needs the command-line tools its instructions call (node).

Does GitHub Closing Draft access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is GitHub Closing Draft safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Closing Draft use?

GitHub Closing Draft is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Closing Draft use?

About 913 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 494 tokens, read only when the agent opens those files.

What are the alternatives to GitHub Closing Draft?

Skills that share tags, products or a category with GitHub Closing Draft: Unslop Text (JCarterJohnson/vibecoded-design-tells, 511 stars), Humanizer Ru (Vladimir-Human/humanizer-ru, 126 stars), Publish Release (Ayuilos/Miffan, 192 stars) and Tech Trend Spider (wenbochang888/github-trending-spider, 159 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Closing Draft?

Ducksss (a GitHub user) maintains it in Ducksss/codex-profiles, which has 177 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.

Source: Ducksss/codex-profiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

GitHub Closing Draft

Install GitHub Closing Draft

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

GitHub Closing Draft

Purpose

Required Context

Boundaries

Accepted Input

Tracker Protocol

Workflow

Output

Files

Compare with similar skills

Similar skills

Unslop Text

Humanizer Ru

Publish Release

Tech Trend Spider

Book Publisher

Map Your Market

More from Ducksss/codex-profiles

GitHub Lead Gen

GitHub Lead Qualification

GitHub Monitoring

Questions about GitHub Closing Draft

Install GitHub Closing Draft

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

GitHub Closing Draft

Purpose

Required Context

Boundaries

Accepted Input

Tracker Protocol

Workflow

Output

Files

Compare with similar skills

Similar skills

More from Ducksss/codex-profiles

Related

Questions about GitHub Closing Draft