coauthor-brief

Generates a Markdown handoff brief summarizing git deltas, artifact states, and reproduction steps for collaborators.

4|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/stevejbickley/arcbita-geek-seminars --skill coauthor-brief-stevejbickley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coauthor-brief
Source: https://github.com/stevejbickley/arcbita-geek-seminars/tree/main/sessions/2026-07-29-ClaudeCodeforAppliedSocialScience/starter/.claude/skills/coauthor-brief
Command: npx skills add https://github.com/stevejbickley/arcbita-geek-seminars --skill coauthor-brief-stevejbickley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-author research projects lose time when collaborators must dig through git history and scattered notes to understand what changed, what is blocked, and how to run the pipeline locally. This Skill produces a single concise handoff brief covering the delta since the last brief, the state of each artifact, open questions, reproduction steps, and restricted-data access procedures. ## Core Features & Use Cases - Delta Summarization: Groups commits by area (manuscript, analysis, slides, infrastructure) since a tag, date, or the previous brief, with sensible fallbacks. - Artifact Status Roll-up: Reports manuscript, analysis, and slides state plus reproducibility passport results (PASS / FAIL / EXPLAINED) in a compact table. - Onboarding Support: Documents environment restore commands (renv, pip, Stata) and restricted-data access steps without exposing confidential values or credentials. - Use Case: Before sending a co-author the repository, run the brief so they receive a one-page summary of changes since last week, open decisions, and exact commands to reproduce the analysis on their machine. ## Quick Start Ask the assistant to write a coauthor handoff brief covering changes since the last tag for your collaborator.

Frequently Asked Questions about coauthor-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a handoff brief for a co-author on a research project?▼

Run the coauthor-brief skill, which gathers the git delta since a tag, date, or the previous brief, then writes a Markdown document covering changes, artifact states, open questions, and reproduction steps. The output is saved to quality_reports/handoffs/ with a dated filename.

How do I onboard a new collaborator to a reproducible analysis repo?▼

Generate a handoff brief that includes the environment restore command (renv::restore, pip install, or a Stata setup do-file), the pipeline run command, and verification steps. It also summarizes restricted-data access procedures without exposing any confidential values.

Can I limit the brief to changes since a specific date or git tag?▼

Yes, pass --since with a git tag, an ISO date, or a relative window like 14days. If omitted, the skill uses the date of the previous brief in quality_reports/handoffs/, falling back to 14 days when no prior brief exists.

Does the coauthor brief include restricted or confidential data?▼

No. The brief describes only the process to obtain access, such as DUA or IRB steps, and never copies restricted values, live data paths, or credentials. Use --no-data-section to skip that section entirely.

When should I use a handoff brief instead of a checkpoint?▼

Use a checkpoint when you are resuming your own work, and a coauthor brief when someone else needs to pick up part of the project. The brief answers what a collaborator needs to know to take over, not where you left off.