Markit
shift-labs-ai/markit
Convert files and URLs to Markdown. An agent skill from shift-labs-ai/markit.
Post Q&A entries from markdown writeups as comments to a GitHub Discussion.
Install Discussion Commenter
$ npx skills add pamelafox/presentation-skills --skill discussion-commenter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pamelafox/presentation-skills discussion-commenter --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pamelafox/presentation-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/discussion-commenter .claude/skills/discussion-commenter && rm -rf skills-srcUse ~/.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/
Install the "discussion-commenter" agent skill from https://github.com/pamelafox/presentation-skills/tree/main/.agents/skills/discussion-commenter into .claude/skills/discussion-commenter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-commenter", 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 install https://github.com/pamelafox/presentation-skills/tree/main/.agents/skills/discussion-commenterType 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.
$ npx skills add pamelafox/presentation-skills --skill discussion-commenter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pamelafox/presentation-skills discussion-commenter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pamelafox/presentation-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/discussion-commenter .agents/skills/discussion-commenter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "discussion-commenter" agent skill from https://github.com/pamelafox/presentation-skills/tree/main/.agents/skills/discussion-commenter into .agents/skills/discussion-commenter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-commenter", 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.
$ npx skills add pamelafox/presentation-skills --skill discussion-commenter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pamelafox/presentation-skills discussion-commenter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pamelafox/presentation-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/discussion-commenter .cursor/skills/discussion-commenter && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "discussion-commenter" agent skill from https://github.com/pamelafox/presentation-skills/tree/main/.agents/skills/discussion-commenter into .cursor/skills/discussion-commenter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-commenter", 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 https://github.com/pamelafox/presentation-skills.git --path .agents/skills/discussion-commenter--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pamelafox/presentation-skills --skill discussion-commenter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pamelafox/presentation-skills discussion-commenter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pamelafox/presentation-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/discussion-commenter .gemini/skills/discussion-commenter && rm -rf skills-srcUse ~/.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/
Install the "discussion-commenter" agent skill from https://github.com/pamelafox/presentation-skills/tree/main/.agents/skills/discussion-commenter into .gemini/skills/discussion-commenter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-commenter", 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.
$ gh skill install pamelafox/presentation-skills discussion-commenterInstalls 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).
$ npx skills add pamelafox/presentation-skills --skill discussion-commenter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pamelafox/presentation-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/discussion-commenter .github/skills/discussion-commenter && rm -rf skills-srcUse ~/.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/
Install the "discussion-commenter" agent skill from https://github.com/pamelafox/presentation-skills/tree/main/.agents/skills/discussion-commenter into .github/skills/discussion-commenter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-commenter", 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.
$ npx skills add pamelafox/presentation-skills --skill discussion-commenter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pamelafox/presentation-skills discussion-commenter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pamelafox/presentation-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/discussion-commenter .opencode/skills/discussion-commenter && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "discussion-commenter" agent skill from https://github.com/pamelafox/presentation-skills/tree/main/.agents/skills/discussion-commenter into .opencode/skills/discussion-commenter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-commenter", 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
discussion-commenter- GitHub stars
- 125
- Token cost
- ~307 tokens
- SKILL.md length
- 109 words
- Files
- 2
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Post Q&A entries from markdown writeups as comments to a GitHub Discussion.
- Works in 3 steps: writeup_path - Path to the markdown… → discussion_url - Full URL to the GitHub… → date - Date string to prefix each…
- The user wants to post writeup content to a discussion thread
- SKILL.md covers Usage, Arguments, Options and Requirements, plus 1 more section
- Runs Python scripts from its folder; calls uv; reaches github.com
What it does
Discussion Commenter is an agent skill from pamelafox/presentation-skills. Post Q&A entries from markdown writeups as comments to a GitHub Discussion. Use when the user wants to post writeup content to a discussion thread.
Its SKILL.md is about 310 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `post_qas.py`).
It sits in Documents & Office. It works with GitHub. The repository describes itself as: Skills for AI agents to process presentations - helpful for teachers and speakers. The licence is MIT.
When your agent uses it
- The user wants to post writeup content to a discussion thread
Example prompts
- “/discussion-commenter”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- writeup_path - Path to the markdown writeup file containing Q&As
- discussion_url - Full URL to the GitHub discussion
- date - Date string to prefix each comment (e.g., "2026/01/06")
What it can do on your machine
Read from SKILL.md and the folder at commit 2b809b3. 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
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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
Discussion Commenter loads about 307 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 109 words of instructions outside code blocks.
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 pamelafox/presentation-skills at commit 2b809b3, republished under its MIT licence (© pamelafox). 109 words, ~307 tokens.
Download SKILL.mdSave it as
.claude/skills/discussion-commenter/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- discussion-commenter
- description
- Post Q&A entries from markdown writeups as comments to a GitHub Discussion. Use when the user wants to post writeup content to a discussion thread.
Discussion Commenter
Post Q&A entries from markdown writeups as individual comments to a GitHub Discussion.
Usage
Run the script with the writeup file path, discussion URL, and date:
uv run .agents/skills/discussion-commenter/post_qas.py \
"path/to/writeup.md" \
"https://github.com/orgs/ORG/discussions/NUMBER" \
"2026/01/06"Arguments
writeup_path- Path to the markdown writeup file containing Q&Asdiscussion_url- Full URL to the GitHub discussiondate- Date string to prefix each comment (e.g., "2026/01/06")
Options
--dry-run- Parse and display what would be posted without actually posting
Requirements
- GitHub CLI (
gh) must be installed and authenticated - User must have permission to comment on the discussion
Output
Each ## Question section in the writeup becomes a separate comment, formatted as:
**2026/01/06: Question Title**
Answer content...Subsections (### Follow-up) are included in the parent question's comment.
© pamelafox, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/discussion-commenter of pamelafox/presentation-skills.
- SKILL.md
- post_qas.py
Open the folder on GitHubat commit 2b809b3
Compare with similar skills
Discussion Commenter 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Discussion Commenter this skillpamelafox/presentation-skills | 125 | — | ~307 | Automated safety check: Pass | MIT | |
| Markitshift-labs-ai/markit | 1.3k | — | ~299 | Automated safety check: Pass | MIT | |
| Asu Resume Audit SkillClaycui828/ASu-resume-skills | 371 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Best SkillsLinklyAI/best-skills | 633 | — | ~575 | Automated safety check: Pass | CC-BY-4.0 | |
| Deepxiv Baseline TableDeepXiv/deepxiv_sdk | 804 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Editor Updateqwrtln/Homm3BG-mission-book | 110 | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Asu Resume Audit Skill
Claycui828/ASu-resume-skills
以证据为中心的简历真实性审计与报告生成技能。用户要求核验简历、打假履历、调查候选人经历、分析 GitHub/开源贡献、识别 contributor 到 maintainer/core author 的角色膨胀、核验中外合作办学或学校 title、检查业务指标、梳理公开争议，或者把调查结果制作成 HTML/PDF…
Best Skills
LinklyAI/best-skills
Daily cross-platform rankings of AI agent skills (skills.sh, ClawHub, Tencent SkillHub, GitHub, X/HN/Bluesky).
Deepxiv Baseline Table
DeepXiv/deepxiv_sdk
Build a markdown baseline table for a research topic using deepxiv search, brief, head, and experiment-section reads, extracting paper title, URL, open-source status, datasets, benchmark scores, and…
Editor Update
qwrtln/Homm3BG-mission-book
Build a feature or fix a bug in the browser scenario builder under web/ — app, shared parsers, compile/PDF preview, GitHub pull-request flow, picker, search, routes — with tests and every…
Release Latex Fork
zly2006/zhihu-plus-plus
Release the LaTeX fork used by Zhihu++. An agent skill from zly2006/zhihu-plus-plus.
More from pamelafox/presentation-skills
All 14 skills in this repoGenerate Images Mai
pamelafox/presentation-skills
Generate or edit bitmap images with Microsoft MAI-Image-2.5 through the Azure AI image APIs.
Make Revealjs Presentation
pamelafox/presentation-skills
Create or update a RevealJS HTML presentation using the repository's bundled slide template.
Capture Video Frames
pamelafox/presentation-skills
Capture frames from a YouTube video at a regular interval, produce a manifest mapping filenames to timestamps, and describe each frame with an LLM.
Fetch Slides
pamelafox/presentation-skills
Fetch presentation slides from a URL and convert them to PDF.
Generate Writeup
pamelafox/presentation-skills
Generate an annotated blog-style write-up from a presentation's slides and video recording.
Outline Slides
pamelafox/presentation-skills
Generate a numbered outline of presentation slides with one-sentence summaries.
Related
Works with
Categories
Questions about Discussion Commenter
What does Discussion Commenter do?
Post Q&A entries from markdown writeups as comments to a GitHub Discussion. Discussion Commenter is an agent skill from pamelafox/presentation-skills. Post Q&A entries from markdown writeups as comments to a GitHub Discussion.
When should I use Discussion Commenter?
Discussion Commenter fits situations like: the user wants to post writeup content to a discussion thread.
How do I install Discussion Commenter in Claude Code?
Run `npx skills add pamelafox/presentation-skills --skill discussion-commenter -a claude-code`. Or copy the skill folder (.agents/skills/discussion-commenter in pamelafox/presentation-skills) into .claude/skills/discussion-commenter in your project. Claude Code loads it when a task matches its description.
How do I install Discussion Commenter in Codex?
Run `npx skills add pamelafox/presentation-skills --skill discussion-commenter -a codex`. Or copy the skill folder (.agents/skills/discussion-commenter in pamelafox/presentation-skills) into .agents/skills/discussion-commenter in your project. Codex loads it when a task matches its description.
Can I use Discussion Commenter 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 pamelafox/presentation-skills --skill discussion-commenter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discussion-commenter, .gemini/skills/discussion-commenter, .github/skills/discussion-commenter and .opencode/skills/discussion-commenter in your project.
What does Discussion Commenter need to run?
Going by SKILL.md and its folder, Discussion Commenter needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.
Does Discussion Commenter access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Discussion Commenter 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 Discussion Commenter use?
Discussion Commenter 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 Discussion Commenter use?
About 307 tokens (SKILL.md is roughly 1.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Discussion Commenter?
Skills that share tags, products or a category with Discussion Commenter: Markit (shift-labs-ai/markit, 1.3k stars), Asu Resume Audit Skill (Claycui828/ASu-resume-skills, 371 stars), Best Skills (LinklyAI/best-skills, 633 stars) and Deepxiv Baseline Table (DeepXiv/deepxiv_sdk, 804 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Discussion Commenter?
pamelafox (a GitHub user) maintains it in pamelafox/presentation-skills, which has 125 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 2, 2026.
Source: pamelafox/presentation-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.