agentsclimarketplace

Meeting

Skill slogsdon/skills-vault-knowledge/skills/meeting

Twenty Obsidian knowledge-work skills for Claude Code: connect, contradict, emerge, trace, ghost, weekly-learnings.

Install
npx -y skills add slogsdon/skills-vault-knowledge --skill meeting

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

Turn a raw meeting / call / 1:1 transcript or notes into a structured Meetings note with key points and action items. Use when /meeting is invoked, when the user says "process this meeting", "clean up these notes", "extract action items from this", or pastes a raw conversation and asks for a summary. Reads from Obsidian Inbox by default; can take inline content. Do NOT use for general note-taking — use the obsidian skill or /log for that.

SKILL.md

3.0 KB, 671 tokens by cl100k_base, as published. Nobody here has run it

Skill: /meeting

Process a raw Inbox note into a structured Meetings note with key points, actions, and a Person stub — the Inbox item is deleted (or archived) after.

Don't: use this for general note-taking — use /log for that. Don't archive instead of deleting unless Shane says so — default is delete.

Steps

  1. Find the raw note

    • If the user named a note (e.g. "Chat with Sean"), run: obsidian search query='Chat with Sean' to confirm it exists, then obsidian read file='Chat with Sean'
    • If no name given, run ls "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal/Inbox/" and pick the most recently modified non-fixture file, then obsidian read file='Note Name' (strip .md)
    • Read the full note content
  2. Extract structured content

    • Identify the other person(s) in the conversation
    • Extract key points: meaningful decisions, context shared, topics discussed — one tight bullet per point, no filler
    • Separate action items into two buckets:
      • Shane's actions (owner implied)
      • Their actions (prefix with PersonName:)
  3. Write the processed note

    • Determine the date from the filename or content (format: YYYY-MM-DD)
    • Run obsidian create name='Meetings/[original filename without .md]' silent with the following content:
    ---
    date: YYYY-MM-DD
    people: [[People/PersonName]]
    ---
    
    # [Title] — [Month Day]
    
    ## Key Points
    - (bullet per meaningful point, concise)
    
    ## Actions
    - [ ] (Shane's action items)
    - [ ] PersonName: (their action items)
    
  4. Check/create Person note

    • Run obsidian read file='PersonName' — if it errors or returns empty, the note doesn't exist
    • If missing, run obsidian create name='People/PersonName' silent with this stub:
    ---
    type: person
    role: 
    ---
    
    # PersonName
    
    ## Context
    - 
    
    ## Preferences & Working Style
    -
    
    ## Related
    
  5. Handle the raw Inbox note

    • Delete the raw note from Inbox/ using bash (obsidian CLI has no delete command): rm "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal/Inbox/[filename].md"
    • Or move to Archive/ if user prefers to keep it
    • Default: delete unless user says otherwise
  6. Commit vault changes

    VAULT="$HOME/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal"
    git -C "$VAULT" add -A && git -C "$VAULT" commit -m "docs: process meeting note [filename]"
    
  7. Confirm

    • Tell Shane what was written and where
    • Surface any action items that need immediate attention

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.