Ideas summary
Agentic personal OS to automate high-leverage workflows with Codex, Claude Code, Pi, OpenClaw and other coding agents/ runtime platforms.
npx -y skills add itseffi/agentic-os --skill ideas-summaryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
Summarize meetings using IDEAS framework - Insights, Decisions, Engagements, Actions, Summary. Use after any meeting.
SKILL.md
1.6 KB, as published. Nobody here has run it
IDEAS Meeting Summary
Summarize meetings using the IDEAS framework for clear, actionable notes.
When to Use
After any meeting to create a structured summary.
The Framework
IDEAS = Insights, Decisions, Engagements, Actions, Summary
| Component | What to Capture |
|---|---|
| Insights | Key realizations, important information surfaced |
| Decisions | Choices made during the meeting |
| Engagements | Tasks/responsibilities assigned to people |
| Actions | Immediate next steps needed |
| Summary | Overall impact and significance |
The Process
- Review the meeting transcript/notes
- Extract items for each category
- Use bullet points for clarity
- Focus on most important points (not every detail)
Output Format
## Insights
- [Key realization 1]
- [Key realization 2]
## Decisions
- [Decision made]
- [Decision made]
## Engagements
- [Person]: [Responsibility assigned]
- [Person]: [Responsibility assigned]
## Actions
- [Immediate action needed]
- [Immediate action needed]
## Summary
[1-2 sentences on meeting's impact and significance]
Quality Check
- Are all decisions captured?
- Do engagements have clear owners?
- Are actions specific and immediate?
- Would someone who missed the meeting understand what happened?
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.