DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to turn meeting notes into linked wiki pages with Graybox

Paste raw meeting notes and get people, projects, tasks, and decisions as cross-linked Markdown pages.

Credentials. Meeting notes often contain names and work details, and the LLM API key must be kept out of shared or synced folders.

Who it is forA team lead or project owner who takes quick notes in meetings and wants owners, due dates, and decisions tracked without manual filing.

The problemDecisions, owners, and deadlines from meetings get lost in scattered notes and chat threads.

The outcomeA set of wiki pages for the people, projects, tasks, and decisions in the notes, each linked to its original capture.

What you need first

  • Python 3.10 or newer
  • Access to an LLM provider and its API key, set in an .env file or as GRAYBOX_LLM_API_KEY
  • A config.yaml based on config.example.yaml with your LLM and workspace details

Steps

  1. Install the tool with pip install graybox and set your LLM API key in an .env file or as GRAYBOX_LLM_API_KEY.
  2. Copy the config file into your working directory and update it with your LLM and workspace details.
  3. Capture the meeting notes with graybox capture "<meeting notes>". (inferred, check the README)
  4. Preview the result with graybox organize --dry-run, then run graybox organize to write the pages.
  5. Review the generated pages with graybox pages.

Prompt for your agent

Use the Aaryanverma/graybox repo to capture the notes in <notes-file> with `graybox capture`, then run `graybox organize --dry-run` and `graybox organize`. Expected output: a list of new wiki pages for people, projects, tasks, and decisions. Verify that `graybox pages` lists the pages and that each one links back to its source capture.

Caveat. Organization runs through the LLM you configure, so extraction quality depends on that model and the page results should be reviewed.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page