News Aggregator Skill
cclank/news-aggregator-skill
Comprehensive news aggregator that fetches, filters, and deeply analyzes real-time content from 44+ sources including Hacker News, Lobsters, Dev.to, GitHub, arXiv, Hugging Face Papers, AIHOT, TLDR…
Structured meeting summarization that captures decisions, action items, and open questions in a consistent format.
Install Summarize Meeting
$ npx skills add borghei/Claude-Skills --skill summarize-meeting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills summarize-meeting --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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/execution/summarize-meeting .claude/skills/summarize-meeting && 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 "summarize-meeting" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/summarize-meeting into .claude/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", 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/borghei/Claude-Skills/tree/main/project-management/execution/summarize-meetingType 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 borghei/Claude-Skills --skill summarize-meeting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills summarize-meeting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/project-management/execution/summarize-meeting .agents/skills/summarize-meeting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "summarize-meeting" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/summarize-meeting into .agents/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", 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 borghei/Claude-Skills --skill summarize-meeting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills summarize-meeting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/project-management/execution/summarize-meeting .cursor/skills/summarize-meeting && 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 "summarize-meeting" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/summarize-meeting into .cursor/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", 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/borghei/Claude-Skills.git --path project-management/execution/summarize-meeting--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 borghei/Claude-Skills --skill summarize-meeting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills summarize-meeting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/project-management/execution/summarize-meeting .gemini/skills/summarize-meeting && 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 "summarize-meeting" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/summarize-meeting into .gemini/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", 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 borghei/Claude-Skills summarize-meetingInstalls 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 borghei/Claude-Skills --skill summarize-meeting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/project-management/execution/summarize-meeting .github/skills/summarize-meeting && 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 "summarize-meeting" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/summarize-meeting into .github/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", 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 borghei/Claude-Skills --skill summarize-meeting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills summarize-meeting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/project-management/execution/summarize-meeting .opencode/skills/summarize-meeting && 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 "summarize-meeting" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/summarize-meeting into .opencode/skills/summarize-meeting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "summarize-meeting", 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
summarize-meeting- GitHub stars
- 886
- Token cost
- ~1.3k tokens
- SKILL.md length
- 581 words
- Files
- 9 (incl. scripts, references, assets)
- Skills in repo
- 354
- Repo updated
- First seen
- Licence
- MIT
At a glance
Structured meeting summarization that captures decisions, action items, and open questions in a consistent format.
- Tasks that involve Summarization
- SKILL.md covers Overview, Core Capabilities, When to Use and Clarify First, plus 4 more sections
- Runs Python scripts from its folder
What it does
Summarize Meeting is an agent skill from borghei/Claude-Skills. Structured meeting summarization that captures decisions, action items, and open questions in a consistent format.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `assets/meeting_summary_template.md`, `examples/product-review-may-22.md` and `references/meeting-facilitation-guide.md`).
It sits in Writing & Content, covering Summarization. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Tasks that involve Summarization
Example prompts
- “/summarize-meeting”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. 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 3 files in scripts/ (Python), which the agent can run.
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
Summarize Meeting loads about 1.3k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 33 tokens; SKILL.md has 581 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); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 581 words, ~1,337 tokens.
Download SKILL.mdSave it as
.claude/skills/summarize-meeting/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- summarize-meeting
- description
- Structured meeting summarization that captures decisions, action items, and open questions in a consistent format.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.1
- metadata.author
- borghei
- metadata.category
- project-management
- metadata.domain
- pm-execution
- metadata.updated
- 2026-06-15
- metadata.tech-stack
- meeting-facilitation, action-tracking, decision-logging
Meeting Summary Expert
Overview
Transform meeting notes, transcripts, or recordings into clear, actionable summaries. Every summary follows a consistent structure that makes it easy for attendees and non-attendees alike to understand what was discussed, what was decided, and who is doing what by when.
Core Capabilities
- Metadata capture — date, time, participants with roles, topic, location
- Discussion synthesis — summarize substantive topics in plain language; note disagreements and resolutions
- Action extraction — one owner, concrete deliverable, and a specific calendar due date per item
- Decision logging — numbered decisions with rationale and decision-maker
- Open-question tracking — unresolved items with owner and target date
- Consistent output — fixed template plus naming convention and 24-hour distribution discipline
When to Use
- After any meeting where decisions were made or actions were assigned.
- Sprint ceremonies -- planning, retro, backlog refinement, sprint review.
- Stakeholder meetings -- steering committees, executive reviews, client calls.
- Ad-hoc discussions -- when an impromptu conversation produces commitments that need tracking.
Clarify First
Before summarizing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- The source material and its fidelity — raw notes, transcript, or recording (summary quality is bounded by input; missing owners/dates for action items cannot be invented)
- Meeting type — planning, retro, steering committee, or client call (tailors discussion synthesis and which decisions matter)
- Distribution scope + confidentiality — attendees, non-attendees, or execs, and any sensitivity limits (determines whether standard 24-hour distribution applies)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/summarization-process.md — the full six-step methodology (metadata → discussion → actions → decisions → open questions → distribute), the output template, focus priorities, troubleshooting table, and success criteria. Read when producing a summary.
- references/meeting-facilitation-guide.md — meeting types, note-taking strategies, and anti-patterns. Read to tailor the summary to the meeting type or improve input quality.
- references/red-flags.md — common ways summaries go wrong with bad/good examples. Read before posting, emailing, or linking a summary.
- assets/meeting_summary_template.md — ready-to-use fill-in template. Use to draft the summary directly.
Show full SKILL.md (236 more words)Show less
Integration with Other Skills
- Feed decisions into
wwas/to create backlog items with strategic context. - Use action items to create tickets via
../jira-expert/. - Document recurring meeting outcomes in
../confluence-expert/templates.
Scope & Limitations
In Scope: Capturing meeting metadata, extracting key discussion points, documenting decisions with rationale, recording action items with owners and due dates, capturing open questions, distributing summaries, maintaining consistent naming conventions and storage.
Out of Scope: Meeting facilitation and agenda design, real-time transcription (use a transcription tool as input), project status tracking (hand off to ../jira-expert/), strategic decision frameworks (hand off to ../senior-pm/), recording or video management.
Limitations: Summary quality is bounded by the quality of input notes or transcript. Automated transcription tools may introduce errors that the summarizer must catch. The skill does not replace the need for a skilled facilitator -- poorly run meetings produce poor summaries regardless of template quality. Sensitive or confidential meetings may require restricted distribution that the standard workflow does not address.
Integration Points
| Integration | Direction | What Flows |
|---|---|---|
wwas/ | Meetings -> WWAS | Decisions and commitments from meetings become WWAS backlog items |
job-stories/ | Meetings -> Stories | Discovery discussions surface situations and motivations for job stories |
../jira-expert/ | Meetings -> Jira | Action items create Jira tickets; decisions update issue comments |
../confluence-expert/ | Meetings -> Confluence | Summaries stored in Confluence using meeting notes template |
../senior-pm/ | Meetings -> PM | Steering committee and stakeholder meeting summaries feed portfolio reporting |
../delivery-manager/ | Meetings -> DM | Release planning and incident review meeting outcomes feed delivery tracking |
© borghei, 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 8 other files (scripts, references, assets) in project-management/execution/summarize-meeting of borghei/Claude-Skills.
- SKILL.md
- assets/meeting_summary_template.md
- examples/product-review-may-22.md
- references/meeting-facilitation-guide.md
- references/red-flags.md
- references/summarization-process.md
- scripts/action_item_tracker.py
- scripts/decision_log_builder.py
- scripts/meeting_effectiveness_scorer.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Summarize Meeting 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 |
|---|---|---|---|---|---|---|
| Summarize Meeting this skillborghei/Claude-Skills | 886 | — | ~1.3k | Automated safety check: Pass | MIT | |
| News Aggregator Skillcclank/news-aggregator-skill | 1.3k | — | ~2.1k | Automated safety check: Pass | None | |
| AI Daily Newsgeekjourneyx/ai-daily-skill | 235 | — | ~2.3k | Automated safety check: Pass | None | |
| Vss Search ArchiveNVIDIA-AI-Blueprints/video-search-and-summarization | 1.9k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| AnalyzeriBigQiang/feedgrab | 614 | — | ~1k | Automated safety check: Pass | MIT | |
| Reportmicrosoft/data-formulator | 18k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
AI Daily News
geekjourneyx/ai-daily-skill
Fetches AI news from smol.ai RSS and generates structured markdown with intelligent summarization and categorization.
Vss Search Archive
NVIDIA-AI-Blueprints/video-search-and-summarization
A skill your agent uses when a user wants to search archived VSS video or ingest or delete a source for search.
Analyzer
iBigQiang/feedgrab
Content Analyzer — any content (URL, text, transcript) into structured analysis report with actionable insights.
- Official
Report
microsoft/data-formulator
Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded…
Tldr
earlyaidopters/claudeclaw
Summarize the current conversation into a TLDR note and save it to your notes folder.
More from borghei/Claude-Skills
All 354 skills in this repoAgent Harness
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
Agents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Related
Categories
Questions about Summarize Meeting
What does Summarize Meeting do?
Structured meeting summarization that captures decisions, action items, and open questions in a consistent format. Summarize Meeting is an agent skill from borghei/Claude-Skills. Structured meeting summarization that captures decisions, action items, and open questions in a consistent format.
When should I use Summarize Meeting?
Summarize Meeting fits situations like: tasks that involve Summarization.
How do I install Summarize Meeting in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill summarize-meeting -a claude-code`. Or copy the skill folder (project-management/execution/summarize-meeting in borghei/Claude-Skills) into .claude/skills/summarize-meeting in your project. Claude Code loads it when a task matches its description.
How do I install Summarize Meeting in Codex?
Run `npx skills add borghei/Claude-Skills --skill summarize-meeting -a codex`. Or copy the skill folder (project-management/execution/summarize-meeting in borghei/Claude-Skills) into .agents/skills/summarize-meeting in your project. Codex loads it when a task matches its description.
Can I use Summarize Meeting 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 borghei/Claude-Skills --skill summarize-meeting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/summarize-meeting, .gemini/skills/summarize-meeting, .github/skills/summarize-meeting and .opencode/skills/summarize-meeting in your project.
What does Summarize Meeting need to run?
Going by SKILL.md and its folder, Summarize Meeting needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Summarize Meeting 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 Summarize Meeting 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Summarize Meeting use?
Summarize Meeting is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Summarize Meeting use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 5.9k tokens, read only when the agent opens those files.
What are the alternatives to Summarize Meeting?
Skills that share tags, products or a category with Summarize Meeting: News Aggregator Skill (cclank/news-aggregator-skill, 1.3k stars), AI Daily News (geekjourneyx/ai-daily-skill, 235 stars), Vss Search Archive (NVIDIA-AI-Blueprints/video-search-and-summarization, 1.9k stars) and Analyzer (iBigQiang/feedgrab, 614 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Summarize Meeting?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.