Skip to content

Add meeting-case-study skill#15

Open
williamjameshandley wants to merge 10 commits into
mainfrom
add-meeting-case-study-skill
Open

Add meeting-case-study skill#15
williamjameshandley wants to merge 10 commits into
mainfrom
add-meeting-case-study-skill

Conversation

@williamjameshandley

Copy link
Copy Markdown
Contributor

Summary

  • New skill at `skills/meeting-case-study/SKILL.md` covering live (or post-hoc) Otter-transcript-based meeting capture.
  • Sibling of the existing `recipe` skill (which handles Claude Code session JSONL forensics).
  • Documents the workflow used for the 26 May 2026 thesis-writing workshop. Reference output: the private repo at handley-lab/thesis-writing-workshop and its `CASE_STUDY.md`.

What it does

Phases 0–8: identify the meeting in Otter → decide Chatham House discipline → live or post-hoc polling → first OpenAI synthesis pass → apply a LaTeX style (default matplotlib `tab10`, or pulled from email via the separate `tex-style-from-email` skill) → iterate during/after the meeting → build a private group repo with verbatim transcripts → write `CASE_STUDY.md` matching the jaxwavelets exemplar → hand off to the `website` skill to publish at `/cookbook//`.

Test plan

  • Skim the new `SKILL.md` for any private content that slipped through (none expected — the reference run was anonymised under Chatham House).
  • Next live meeting: invoke this skill and confirm the workflow runs without needing manual intervention beyond the documented `check` prompts.
  • After publishing the thesis-writing-workshop case study to `_recipes/`, verify the card schema and companion-page slug match.

Replaces the auto-publish `script/posts/arxiv.py` workflow that produced
~88 unreviewed posts. New posts are drafted via this skill on a
`paper/<arxiv-id>` branch and merged only after human review by someone
who is not the paper's lead author.

Tone constraints baked in:
- exact paper title (no clever rewrites)
- no press-release language
- no AI-generated body text and no synthetic AI illustrations
- 200-500 words; the paper is the long-form artefact
- explicit "How AI helped (or didn't)" section is the differentiator;
  honest "didn't help" answers are acceptable

This is a baseline produced during the 5 May 2026 workshop. The first
real paper post written through it (Toby Lovick's latest ALCS paper) is
expected to drive the next iteration.

Refs #3
Removes 88 .md files from `_posts/` and 82 .png illustrations from
`assets/images/posts/`. These were generated by the legacy
`script/posts/arxiv.py` pipeline and shipped to `main` without human
review. The 5 May 2026 workshop converged on phasing out that pipeline
in favour of PR-reviewed paper posts via the `paper` skill (added
elsewhere in this PR).

Effect: `/papers/` now renders only its index intro (no posts listed)
until the first PR-reviewed post lands.

Recovery: anything worth re-publishing is recoverable from git history
(`git show <commit>:<path>`); copy back to `_posts/` only via the
`paper` skill workflow with human review.

Also gitignores the orchestrator-day `context/` scratch directory and
`.playwright-mcp/` browser cache, which were accidentally included in
the previous commit.
Toby Lovick, David Yallup, Will Handley — "Automatic Laplace Collapsed
Sampling: Scalable Marginalisation of Latent Parameters via Automatic
Differentiation". The first post produced through skills/paper, included
in this PR as a worked example of what the skill produces from a single
arXiv ID.

Per the skill's tone constraints: paper title verbatim; no synthetic AI
illustration; no press-release language; ~140 words on the science. The
"How AI helped" section is left as a TODO for Toby, because the skill
explicitly requires the lab author to fill it — it's the load-bearing
differentiator from the arXiv abstract and not the agent's voice.

Reviewer should not be Toby (the lead author). The TODO blocks need
filling before the post is "done"; merging this PR ships them publicly
as TODOs, which is intentional during the workshop iteration phase.

Refs #3
The post layout now keys off the `arxiv:` frontmatter field:
- a clickable arXiv-id badge renders near the top of the post header
- if `assets/images/papers/<arxiv-id>.png` exists, it auto-renders as a
  figure linked to the PDF, captioned "First page of arXiv:<id>"

This means paper post markdown no longer repeats the arXiv link as the
first body line — the badge handles it. Body content starts with the
human authors line, then "What the paper does", then "How AI helped".

Includes:
- _layouts/post.html: rewritten header + first-page figure block;
  MathJax updated to v3 (was a broken reference to mathjax.org/latest)
- _sass/minima/custom-styles.scss: arxiv-badge and paper-firstpage styles
- assets/images/papers/2603.26644.png: rendered first page (pdftoppm at
  150 DPI) of the ALCS paper, ~340 KB
- skills/paper/SKILL.md: documents the load-bearing `arxiv:` field,
  the auto-included first-page screenshot, and the pdftoppm command;
  drops the previous "manual cropped figure" wording
- _posts/2026-03-27-2603.26644.md: drops the redundant first body line
  pointing at the paper (now the badge does that)

Refs #3
/papers/ list: each entry is now a card-row with the first-page
thumbnail on the left, date, arXiv badge, title, authors, and an
optional excerpt on the right. Posts without an arxiv frontmatter
field still render with a placeholder thumbnail box.

Post page: the first-page figure is now a 150px floated thumbnail
beside the header rather than a full-width inline figure. Caption
is hidden (the badge already labels the source). On narrow viewports
it falls back to centered above the body.
Splitting PR #6 into two: this branch keeps the paper skill, the auto-
generated-post purge, the post-layout improvements (arXiv badge +
first-page thumbnail) and the /papers/ index card-row treatment.

Toby's ALCS paper post (`_posts/2026-03-27-2603.26644.md` and
`assets/images/papers/2603.26644.png`) lands in a follow-up PR
authored on his behalf so he can review and adjust the 'How AI helped'
section before merge.
First post produced by an agent following the skills/paper baseline,
ready for review by @tobyLovick (the lead author).

The post itself contains a TODO block for the 'How AI helped' section,
which only Toby can fill. The agent did NOT speculate about the AI
involvement in the research — that section is the load-bearing
differentiator from the arXiv abstract and must come from the lab
author.

Refs #3 #6
Sibling of recipe skill but for Otter-transcript-based meeting capture
rather than Claude Code session JSONL forensics. Documents the workflow
used for the 26 May 2026 thesis-writing workshop (private repo:
handley-lab/thesis-writing-workshop).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant