agentsclimarketplace

Messy notes to decision log

Skill alexzhu0/agent-ready-skills/skills/messy-notes-to-decision-log

Ten practical AI-agent skills for turning messy work into clear context, evals, reviews, and launch-ready artifacts.

Install
npx -y skills add alexzhu0/agent-ready-skills --skill messy-notes-to-decision-log

Assembled 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

Use when turning rough notes, chat dumps, meeting fragments, scratch documents, or mixed planning material into a decision log with evidence, owners, dates, and unresolved questions.

SKILL.md

1.4 KB, 248 tokens by cl100k_base, as published. Nobody here has run it

Messy Notes To Decision Log

Purpose

Extract durable decisions and unresolved questions from rough material.

Fit

  • Use when rough notes contain mixed decisions, proposals, actions, and questions.
  • Do not use when the material is a clean task list that only needs formatting.

Inputs

  • Notes, chat excerpts, meeting fragments, or planning scratchpads.
  • Date, participants, project name, and desired decision format if available.
  • Any known owners or deadlines.

Workflow

  1. Identify explicit decisions, implied decisions, proposals, and open questions.
  2. Keep evidence snippets short and source-linked when possible.
  3. Assign owners and dates only when stated; otherwise mark them missing.
  4. Separate decisions from action items.
  5. Surface contradictions that need follow-up.

Output

Produce Markdown with:

  • Source Snapshot
  • Decision Log
  • Action Items
  • Open Questions
  • Contradictions
  • Missing Owners Or Dates

Validation

  • No decision is marked final without evidence.
  • Implied decisions are labeled as inferred.
  • Owners and deadlines are not fabricated.
  • Contradictions are preserved instead of smoothed over.
  • The result is compact enough to paste into a project tracker.

Gives 0 of the 12 instructions most note taking skills give in 248 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06

  • include a visual element on every slidein 44 of 686, across 13 files
  • use wikilinks for internal vault linksin 35 of 686, across 11 files
  • commit to a single visual motif across every slidein 34 of 686, across 9 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
  • use subagents to visually inspect rendered slidesin 30 of 686, across 6 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 10 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

  • keep evidence snippets short and source-linked
  • assign owners and dates only when stated
  • surface contradictions needing follow-up

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.