Comments
Code comments and annotations
reflection-coach
by paperclipai
Reflect on another agent's recent execution record and propose the smallest durable instruction, skill, or tool-description change. Use for evidence-backed coaching proposals, never hot-swaps.
paperclip-task-bridge
by paperclipai
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.
paperclip-converting-plans-to-tasks
by paperclipai
Convert Paperclip plans into executable issue graphs. Use when asked to plan, scope, or break down Paperclip company work into assigned tasks with specialty fit, dependencies, blockers, and parallelization.
task-planning
by paperclipai
Turn a Paperclip issue or request into a structured implementation plan with child task graph, blockers, owners, and acceptance criteria, then save it as the issue plan document.
act-on-feedback
by microsoft
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
code-review
by microsoft
Perform a code review of the current session's changes. Use when the user requests a code review via the Run Code Review button in the Changes toolbar.
Task Lifecycle
by lobehub
🤯 LobeHub is your Chief Agent Operator, organizing your agents into 7×24 operations by hiring, scheduling, and reporting on your entire AI team.
onboard
by wesammustafa
Explains the team's shared Claude Code setup
onboard
by wesammustafa
Claude Code guide in three levels, Beginner to Advanced: hands-on lessons with checked exercises, every volatile fact cited to its source. Independent community guide.
notion
by openclaw
"Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls."
code-simplifier
by brycewang-stanford
Simplify and clean up code after changes are complete. Reduces complexity, improves readability, and ensures consistency.
r-econometrics
by brycewang-stanford
Run IV, DiD, and RDD analyses in R with proper diagnostics
peer-review
by brycewang-stanford
"Systematic peer review toolkit. Evaluate methodology, statistics, design, reproducibility, ethics, figure integrity, reporting standards, for manuscript and grant review across disciplines."
stata-data-cleaning
by brycewang-stanford
Clean and transform messy data in Stata with reproducible workflows
stat-writing
by brycewang-stanford
End-to-end statistical writing assistant for LaTeX - draft title/abstract/keywords, expand outlines into sections, audit manuscripts, write reviewer reports and response letters, and scaffold book manuscripts.
review-paper
by brycewang-stanford
Comprehensive manuscript review covering argument structure, econometric specification, citation completeness, and potential referee objections
submission-guide
by brycewang-stanford
This skill covers academic journal submission, referee responses, and revision management. Use when the user is preparing a manuscript for submission, formatting for a specific journal, responding to referees, or managing revisions. Triggers on "submit", "referee", "revision", "R&R", "response letter", "journal", "formatting", "submission", "resubmit", "cover letter", "referee report", "revise and resubmit".
nature-reviewer
by Yuan1z0825
Simulate Nature-style or general pre-submission peer review from the referee perspective, not an author rebuttal. Use for reviewer reports, mock peer review, manuscript critique, novelty/significance/technical-soundness assessment, 审稿人视角评估, 模拟审稿, 预审, 投稿前自审, 审稿意见模拟, or 帮我审一下论文. Produce evidence-grounded Major Concerns, Minor Comments, and blocking flags. For multiple reviewers, keep every reviewer mutually blind in a separate context, freeze all reports before comparison, and create any synthesis only afterward as a separate editor/author-facing artifact.
batch-all-scrap-issues
by dyoshikawa
Resolve every open maintainer-scrap issue one at a time: fact-check each with web research, close the ones that need no action, and run the goal-pr skill to fix, review, and merge the ones that do — repeating until no actionable scrap issues remain.
batch-all-issues
by dyoshikawa
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the goal-pr skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
triage-issues
by dyoshikawa
Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content
goal-issues-and-release
by dyoshikawa
Clear the open issue backlog and then cut a release, in one autonomous run: use the batch-all-issues skill to resolve every open issue, then the goal-release skill to draft, merge, and see the release through publication. Never asks the user anything — every decision is made autonomously, and blockers are reported at the end instead of interrupting the run.
explain-issue
by dyoshikawa
"Explain a GitHub issue: the background problem and the proposed solution"
resolve-scrap-issues
by dyoshikawa
Fetch recent maintainer-scrap issues, validate each with web research, then either close the ones that need no action or open a single consolidated pull request that resolves the ones that do