Lenny Skills is a collection of product-management and engineering workflows for Claude Code and other AI agents, covering areas such as strategy, research, planning, shipping, growth, and hiring. Each skill gives an agent specialized guidance, frameworks, checklists, or templates for product work, and the catalogue contains many of these skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add RefoundAI/lenny-skills --skill running-meetingsgit clone --depth 1 https://github.com/RefoundAI/lenny-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/refoundai/lenny-skills/running-meetings)<a href="https://agentmods.dev/skills/refoundai/lenny-skills/running-meetings"><img src="https://agentmods.dev/badge/skills/refoundai/lenny-skills/running-meetings/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/refoundai/lenny-skills/running-meetings"><img src="https://agentmods.dev/badge/skills/refoundai/lenny-skills/running-meetings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.01271 |
| Opus 5 | $0.00015 | $0.00635 |
| Sonnet 5 | $0.00006 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
running-meetings scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running Effective Meetings
Transform calendars from soul-crushing time-sinks into high-velocity alignment machines.
Help the user with running effective meetings using insights from 12 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Audit current meetings - Analyze the purpose and frequency of existing recurring sessions to ensure they solve specific problems that cannot be addressed asynchronously.
- Design the agenda - Structure sessions with clear objectives, silent reading periods, and psychological safety rituals to maximize participation.
- Facilitate real-time alignment - Use active listening and synthesis techniques to ensure stakeholders feel heard and blockers are surfaced.
- Streamline post-meeting debt - Implement rituals to finalize action items and documentation during the meeting rather than after it.
Core Principles
Separate discovery from decision
Annie Duke: "People generally think the purpose of a meeting is for three things, discover, discuss, decide. The only thing that's ever supposed to happen in a meeting is the discussion part."
Complete the information gathering phase asynchronously before the meeting starts so synchronous time is reserved for high-value debate and final choices.
Prioritize psychological safety
From "Ideal sprint length, designer vs. PM roles, running PM team meetings, running post-mortems, best product/executive coaches, and much more": "Our PM team has a section carved out for “what feels hard [harder than it should be]?” The purpose of this section is to discuss sticking points up and down the stack: troubleshooting comms with Team X; doing a teardown of a PRD that has raised unexpected questions and gotten “stuck”; trying on versions of a Vision/Strategy."
Create a dedicated space for vulnerability where team members feel safe to surface what is hard and seek help from their peers.
Solve for administrative debt
From "Product manager is an unfair role. So work unfairly.": "Instead of adding action items from meetings to a to-do list, do the action items live in the meeting. With everyone watching. While screensharing."
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 85 lines · 30 tokens per session scan A 31abfb2f3b81
running-meetings is a skill published in the GitHub repository RefoundAI/lenny-skills (1,321 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,271 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
linear
Manage Linear issues, projects, and teams via the GraphQL API. Create, update, search, and organize issues. Uses API key auth (no OAuth needed). All operations via curl — no dependencies.
notion
Notion API for creating and managing pages, databases, and blocks via curl. Search, create, update, and query Notion workspaces directly from the terminal.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.