Organize notes
Agent skills for my personal needs, some of which may be useful to others
npx -y skills add openjck/agent-skills --skill organize-notesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Rewrite and reorganize rough notes, highlighting any action items.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.1 KB, 633 tokens by cl100k_base, as published. Nobody here has run it
When organizing the rough notes provided by the user, respond with text. You may use any text format that is appropriate, as long as you also follow the instructions below.
If you are unsure about anything, you can ask any number of questions, within reason, to clarify your understanding before you produce the final result.
In the final result, do not include any introductory text (e.g., "Here is the information you asked for...") or any closing text (e.g., "Let me know if you have any other questions..."). Print only the content that is described in these instructions.
Sections
Provide two top-level sections in your response, each clearly labelled.
Notes improved by AI
Label the first top-level section "Notes improved by AI". Directly below the header for this top-level section, print the following text in italics: "These notes were written with the help of AI based on rough notes that were provided to it." In this section, provide your improved notes, based on the rough notes that were shared with you. If, and only if, there are any action items, include two sub-sections: "Notes", for your improved notes, and "Action items", for a list of action items. If there are no action items, don't create any sub-sections; just print your improved notes. Try to group action items somewhat logically, putting related action items near each other and/or putting the action items in the order they should be completed.
For each abbreviation in the rough notes, if the abbreviation is non-obvious and you are confident about what it means, expand the abbreviation the first time it's used and put the abbreviation in parentheses (e.g., "DHCP" should become "Dynamic Host Configuration Protocol (DHCP)" if that's what the notes are referring to). Do not do this any other time the abbreviation is used, since once is enough. If you don't know what the abbreviation stands for, just use the abbreviation, rather than slowing things down by asking what it stands for.
Raw notes
Label the second top-level section "Raw notes". Directly below the header for this top-level section, print the following text in italics: "These are the raw, rough notes that were provided to AI as input for the above, improved notes." Below that, provide an identical copy of any textual notes that were shared with you.
If you received any notes in a non-textual format (e.g., photographs of pages in a notebook, a screenshot of a note-taking app, or an audio recording someone made to record important information), add one subsection for each of these sources. Make the subsection heading(s) use the title "Transcribed from [source]" where [source] is a human-readable description of the multimedia source (e.g., "a photograph of a page in a notebook" or "an audio recording"). In each subsection, put the transcribed notes described by the corresponding header.
Gives 0 of the 12 instructions most note taking skills give in 633 tokens
Counted across 686 of the 876 authors here whose files we hold, read 2026-08-07
- include a visual element on every slidein 44 of 686, across 13 files
- use wikilinks for internal vault linksin 36 of 686, across 12 files
- commit to a single visual motif across every slidein 34 of 686, across 9 files
- use subagents to visually inspect rendered slidesin 31 of 686, across 7 files
- read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
- keep 0.5 inch minimum marginsin 30 of 686, across 7 files
- re-verify affected slides after every fixin 27 of 686, across 5 files
- run content QA checks before declaring successin 26 of 686, across 3 files
- Use Markdown links for external URLs onlyin 26 of 686, across 11 files
- pick a bold topic specific color palettein 24 of 686, across 2 files
- read editing guide before editing existing presentationsin 23 of 686, across 1 file
- use one dominant color across all slidesin 23 of 686, across 1 file
Said here and by no other author read
- rewrite and reorganize rough notes
- highlight action items
- print only content described in instructions
- provide two top-level sections
- label first section notes improved by ai
- print italic disclaimer under first header
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.