openwiki-meeting-curation

openwiki-meeting-curation is a skill for Claude Code, Codex from joe-broadhead/open-cowork. It costs 32 tokens per session (956 once invoked), scanned A, original, MIT.

A process for turning meeting transcripts into OpenWiki pages, entity updates, decisions, and action items. It searches existing wiki content first and prepares proposed changes for review.

In plain words
What is it for?
Use it to curate meetings, update existing people or project pages, propose new summaries, and report unresolved ambiguities.
Why use it?
It reduces duplicate pages, unsupported conclusions, and accidental changes based on ambiguous transcript details.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw; mentions OpenCode.

Good fit Use it to curate meetings, update existing people or project pages, propose new summaries, and report unresolved ambiguities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joe-broadhead/open-cowork/openwiki-meeting-curation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add joe-broadhead/open-cowork --skill openwiki-meeting-curation
Clone the repo
git clone --depth 1 https://github.com/joe-broadhead/open-cowork

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for openwiki-meeting-curation

README.md
[![agentmods](https://agentmods.dev/badge/skills/joe-broadhead/open-cowork/openwiki-meeting-curation/github.svg)](https://agentmods.dev/skills/joe-broadhead/open-cowork/openwiki-meeting-curation)
Your own site
<a href="https://agentmods.dev/skills/joe-broadhead/open-cowork/openwiki-meeting-curation"><img src="https://agentmods.dev/badge/skills/joe-broadhead/open-cowork/openwiki-meeting-curation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for openwiki-meeting-curation

Your own site · 80×15
<a href="https://agentmods.dev/skills/joe-broadhead/open-cowork/openwiki-meeting-curation"><img src="https://agentmods.dev/badge/skills/joe-broadhead/open-cowork/openwiki-meeting-curation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 956 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00956
Opus 5 $0.00016 $0.00478
Sonnet 5 $0.00006 $0.00191
Haiku 4.5 $0.00003 $0.00096

Measured 12d ago against content hash 337bd26165f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

openwiki-meeting-curation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

products/wiki/integrations/opencode/skills/openwiki-meeting-curation/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenWiki Meeting Curation

Use this skill after transcript intake has identified a meeting or call that should become durable wiki knowledge.

Required Sequence

  1. Read the inbox item and linked transcript source.
  2. Search existing pages for people, organizations, projects, topics, meetings, and decisions before proposing new pages.
  3. Draft a meeting curation plan before proposing changes. Include inbox item ID, source ID, page creations, page updates, entity candidates, merge candidates, unresolved ambiguities, and validation warnings.
  4. Decide whether to update an existing page or propose a new synthesis page.
  5. Use wiki.propose_edit for existing pages and wiki.propose_synthesis for new pages. Do not include YAML frontmatter in proposal bodies.
  6. Include source IDs only when the transcript source is already canonical.
  7. Call wiki.read_proposal_detail for every proposal.
  8. Report proposal IDs, validation status, and unresolved ambiguity.

Page Families

Use these practical defaults unless the wiki's local conventions say otherwise:

Type Path Family Use
meeting wiki/meetings/<slug>.md One page per durable meeting or transcript.
person wiki/people/<slug>.md People mentioned, attending, owning work, or making decisions.
organization wiki/organizations/<slug>.md Companies, teams, vendors, customers, and groups.
project wiki/projects/<slug>.md Recurring initiatives, workstreams, or products.
topic wiki/topics/<slug>.md Durable subject areas and open-question indexes.
decision wiki/decisions/<slug>.md Durable decisions made or referenced.
action wiki/actions/<slug>.md Follow-ups with owner and due date only when stated.

Title and slug rules:

  • Prefer stable human titles: YYYY-MM-DD Topic Meeting for dated meetings when the date is explicit, otherwise use the transcript title.
  • Search by likely aliases before creating people, organization, and project pages. Update the existing page when a same-type page has the same normalized title or alias.
  • Keep local ontology customizable. Do not force every organization to use all page families.

Read the full file on GitHub · 116 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 116 lines · 32 tokens per session scan A 337bd26165f5

Subscribe to this mod's changes

openwiki-meeting-curation is a skill published in the GitHub repository joe-broadhead/open-cowork (11 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 956 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.