Adds attributed inline comments to Markdown documents using a structured marker syntax.
npx skills add https://github.com/alatyshau/duet --skill commentary-alatyshau
Please help me install this Agent Skill. Skill: commentary Source: https://github.com/alatyshau/duet/tree/main/packages/skills/modes/commentary Command: npx skills add https://github.com/alatyshau/duet --skill commentary-alatyshau
::: AUTHOR ::: marker inside list items, with nesting rules that define which lines belong to a comment. - Full AI Attribution: AI agents sign comments with Name (Client@Model) format, e.g. ::: Socrates (Cursor@Opus) :::, so you can later trace which model produced which reasoning. - Contextual Placement & Dialogue Rules: Comments attach to list items or paragraphs, replies sit at the same level as the original comment, and existing comments are never overwritten during edits. - Use Case: During a design review, ask the AI to comment on an architecture document; it inserts attributed remarks inline, you reply at the same level, and the structured debate remains archived in the file. ## Quick Start Enter commentary mode and add attributed comments to the open Markdown document, then return to dialogue mode when finished.High-intent search queries and answers about installing and using this skill.
Use list items with the ::: AUTHOR ::: marker placed as nested sub-items under the target line or as first-level items after a paragraph. The original text stays untouched, and everything indented deeper than the marker belongs to that comment.
AI agents use the full format ::: Name (Client@Model) :::, for example ::: Socrates (Cursor@Opus) :::. This records the persona, the IDE or tool, and the model, giving traceability of which brain produced each comment.
Yes. Nest your reply marker directly under the specific line inside the comment you are addressing. Replies to a whole comment go at the same indentation level as that comment, never nested directly under another comment marker.
All existing comments must be preserved during edits. You may add your own attributed replies, and a separate Secretary step can prettify or transform comments during archiving, but overwriting others' comments is not allowed.
Inline commentary fits when feedback must persist with the document, such as design debates or architecture reviews. Chat feedback disappears with the session, while attributed comments keep the dialectic archived in the file itself.
cellarwoodCreate, organize, and distribute content across Google Workspace.
tankygranny05Download, prettify, and archive @anthropic-ai/claude-code npm packages with git history.
danielmiesslerRuns multi-agent debates with topic-briefed personas producing round-by-round transcripts and synthesis.
ArangoGutierrezClassify GitHub PR review comments and propose rule additions for uncovered findings.