action-items
Skill7 starsChanged 26 days agoMITView on GitHub
Pull decisions, tasks, and owners out of messy notes or a meeting transcript. Use to turn a raw log into a clean follow-up list.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- schalk-conradie/skillstheir own version, first seen Nov 1, 2026
- chuckle123/job-search-ostheir own version, first seen Feb 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- chuckle123/job-search-os★ 9same name
- schalk-conradie/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 15
Read the whole input and separate the substance from the chit-chat.
- Distinctive: line 17
Write each TODO as "owner: task (due date if stated)".
- Distinctive: line 18
Write each DECISION as a short statement of what was chosen and, if given, why.
- Distinctive: line 19
Keep each item to one line.
- Distinctive: line 32
Do we gate signups behind an invite code?
≈ “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.
Files
action-items
When to use
The user pastes meeting notes, a call transcript, a chat log, or scattered notes and wants the concrete outcomes extracted so nothing gets lost.
Instructions
- Read the whole input and separate the substance from the chit-chat. Ignore greetings, tangents, and thinking-out-loud that led nowhere.
- Sort what remains into three groups: DECISIONS (what was settled), TODOS (what someone will do), and OPEN QUESTIONS (what is unresolved).
- Write each TODO as "owner: task (due date if stated)". If no owner is named, mark it "unassigned". Preserve names and dates exactly as written.
- Write each DECISION as a short statement of what was chosen and, if given, why.
- Keep each item to one line. Do not invent owners, dates, or actions that were not in the source.
- Output the three lists in that order. Omit a list only if it is genuinely empty.
Example
DECISIONS
- Ship the beta to the waitlist on Monday, not the public.
TODOS
- Sam: send the waitlist export to marketing (by Fri).
- unassigned: write the launch FAQ.
OPEN QUESTIONS
- Do we gate signups behind an invite code?
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
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.