agentleFS
Sign inStart free
itseffiitseffi/agentic-os/.agents/skills/ideas-summary/SKILL.md

ideas-summary

Skill114 starsChanged 10 months agoMITView on GitHub

Summarize meetings using IDEAS framework - Insights, Decisions, Engagements, Actions, Summary. Use after any meeting.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After any meeting to create a structured summary.

    line 12
  2. Distinctive:

    Use bullet points for clarity

    line 30
  3. Distinctive:

    Do engagements have clear owners?

    line 59
  4. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

ComponentWhat to Capture
InsightsKey realizations, important information surfaced
DecisionsChoices made during the meeting
EngagementsTasks/responsibilities assigned to people
ActionsImmediate next steps needed
SummaryOverall impact and significance

The Process

  1. Review the meeting transcript/notes
  2. Extract items for each category
  3. Use bullet points for clarity
  4. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free