PO

positron-intake-rotation

Guidelines for efficiently managing repository issue intake rotation duties.

Install

mkdir -p .claude/skills/positron-intake-rotation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2313" && unzip -o skill.zip -d .claude/skills/positron-intake-rotation && rm skill.zip

Installs to .claude/skills/positron-intake-rotation

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

This skill should be used when handling issue intake rotation duties for the Positron repository. It provides workflows for reviewing and organizing new issues, responding to discussions, handling support tickets, and searching for related content. Use this skill when on intake rotation duty, when helping someone with intake tasks, or when learning the intake rotation process.
379 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • →Triage new GitHub issues
  • →Categorize backlog items
  • →Draft responses for community discussions
  • →Identify duplicate issues

How it works

Applies a manual triage protocol to analyze and propose actions for intake rotation tasks.

Inputs & outputs

You give it
Issue content or discussion prompt
You get back
Recommended response and categorization

When to use positron-intake-rotation

  • →Triage incoming GitHub issues
  • →Draft responses to community discussions
  • →Categorize and label backlog items
  • →Search for related existing issues

About this skill

Positron intake rotation

Get incoming issues, discussions, and support tickets ready for the weekly triage meeting. Intake's job is not to prioritize or schedule -- it is to make sure nothing is dropped, and that whatever reaches triage is actionable.

The team process lives on the wiki's Intake Rotation page. This skill is the operational version of it. If the two disagree, the wiki wins -- open a PR here to bring the skill back in line.

Usage

/positron-intake-rotation                    # sweep: ranked worklist across all three sources
/positron-intake-rotation --fast             # quick re-check later in the day
/positron-intake-rotation 15693              # drill into one issue
/positron-intake-rotation d15526             # drill into a discussion (d-prefix)
/positron-intake-rotation PSTRNESC-15        # drill into a support ticket

Prerequisites

  • gh, authenticated with access to posit-dev. Everything GitHub-side runs through it.
  • The Atlassian connector (MCP), for support tickets. Without it, say so once, point the person at the Positron Escalations board, and carry on with the GitHub side.
  • Optional: read access to the private posit-dev/assistant repo, for AI-related duplicate searches. See references/upstream-and-assistant.md for the fallback.

Approval model -- read this before doing anything

Nothing user-visible goes out without showing the exact text and getting an explicit go-ahead. Not a summary of the comment. The comment.

Requires approval, per item, full text shown first:

  • comments on issues and discussions
  • closing an issue, including as duplicate
  • creating an issue from a discussion or a support ticket
  • retitling an issue
  • Jira comments, Zendesk-tab replies to Support, status moves like With Support

Requires approval but batchable ("apply the metadata you proposed"):

  • labels, issue type, project Status -> Triage

No approval needed: all reads. The queue, issue bodies, comments, duplicate searches, upstream searches, assistant-repo searches, Jira ticket details.

Also gated: reproduction, because it launches an app on the person's machine. Propose the recipe, let the person choose.

Do not batch a write across items the person only approved for one item. When unsure whether something counts as user-visible, treat it as if it does. If the person says they will post something themselves, hand over the draft and stop -- do not also post it.

How to render a draft so it survives copy-paste

Drafts get copied into the GitHub comment box by hand often enough that the rendering matters. Two things silently destroy the markdown on the way:

  • Blockquote prefixes travel. Wrapping a draft in > to set it off visually means every line carries a > when it is copied, so GitHub renders the whole comment as a quotation, and any ## headings inside it stop being headings.
  • Copying rendered chat loses the source characters. The chat surface renders markdown, so a selection taken from it yields the display form: **bold** arrives as bold, `code` loses its backticks, tables lose their pipes.

So: put every drafted comment in a fenced code block tagged markdown, using a four-backtick fence.

````markdown
Comment text goes here, with its **bold**, `backticks`, ## headings,
tables, and any ```json fenced blocks of its own, all intact.

Four backticks, not three, because drafts routinely contain their own three-backtick
blocks (a `settings.json` snippet, a command to run). A three-backtick outer fence gets
closed early by the first inner one and the rest of the draft escapes as prose. This is
verified behavior on GitHub's own renderer, not a precaution.

Do not put the draft in a blockquote, and do not add commentary inside the fence. Notes
about the draft go outside it, in normal prose.

The higher-fidelity path, when the draft is long or the person wants to edit before
posting: write it to a temporary file (outside the repo), verify it is ASCII, tell the
person where it is so they can open and edit it, and post with
`gh issue comment --body-file`. That file is the exact bytes that get posted, so nothing
is lost in transit. Prefer this for the two-comment split, where there are two distinct
blocks to keep straight.

## 1. Sweep

From the repo root:

```bash
node .claude/skills/positron-intake-rotation/scripts/sweep.ts
```

About a minute for a complete scan of all open issues and discussions (the two page
through GitHub in parallel). It emits a verdict line, then the issue queue bucketed by
what each item is waiting on, then discussions needing a reply. If a queued issue
cannot be loaded, the report lists it as such rather than failing; check it by hand.

Flags: `--fast`, `--json`, `--no-discussions`, `--discussion-days N`,
`--stale-days N`, `--fast-clean-pages N`.

### What counts as a discussion needing attention

**No Posit reply anywhere in the thread.** Not "the user had the last word" -- those
are very different sets (21 vs 186 repo-wide as of Aug 2026), and a thread where we
answered and the reporter wrote back has already been handled.

Two details that are easy to get wrong:

- **Check nested replies, not just top-level comments.** Team answers often land as
  replies inside a thread. Missing them inflated the count by a third on its own.
- **A community-accepted answer counts as resolved** even with no Posit reply, so
  `isAnswered` threads are excluded.

Because the team always has someone on rotation, the recent end is normally empty and
the real list is a couple of items at most. The sweep splits them: anything from the
last 30 days is the work; the older never-answered tail is shown separately and is
mostly stale feature wishes nobody is waiting on. Do not treat a 500-day-old unanswered
Feedback post as urgent because it appears on the list.

### `--fast`: the re-check mode

**About 10 seconds instead of a minute.** The intended pattern is one complete sweep to
open the session, then `--fast` for every re-check after that.

That is not just a speed preference, it is why the mode is sound: new issues get the
newest numbers and new discussion activity sorts to the top, so **anything that arrives
after your full sweep lands exactly where `--fast` looks.** The full sweep already ruled
out an old untriaged straggler, so the one risk `--fast` carries is retired for the day.

Two different mechanisms, and only one is a heuristic:

- **Issues -- heuristic.** Pages newest-first, stops after 3 consecutive pages (300
  issues) with nothing unstatused, since untriaged issues cluster at the new end. It is
  a partial scan and says so, including how far back it reached. Tune with
  `--fast-clean-pages N`.
- **Discussions -- exact.** Results come back ordered by last update, and `updatedAt` is
  always at least the last comment date, so once a page falls outside the window every
  remaining discussion does too. Stopping there loses nothing. Only the older backlog
  age-band counts go uncomputed.

What `--fast` deliberately is **not**: a filter on `updatedAt`. A recency window on
"last touched" would exclude the `gone-quiet` bucket by construction, since those are
precisely the items nobody has touched recently.

Residual gap worth knowing: if someone *clears* the Status on an old issue mid-day,
pushing it back into the queue, `--fast` will not reach it. Rare, and a full scan next
session catches it.

Run the complete scan at least once per session before treating the queue as whole.

The buckets are the point. An empty `Status` field means very different things:

| Bucket | Meaning | Action |
|---|---|---|
| `user-replied` | the reporter has the last word after we engaged or set `info needed` | re-assess; drop `info needed` if set |
| `untouched` | nobody from the team has commented | full triage |
| `needs-status` | team engaged and has the last word, no `info needed`, `Status` still empty | probably just needs `Triage` |
| `waiting-on-user` | `info needed` set, the reporter has not answered | **no action** -- tracking only |
| `gone-quiet` | `info needed`, silent past the threshold | propose closing |

"The reporter" means the issue's author. A +1 or a bot comment from someone else does
not count as an answer, so it leaves the issue where it was. Silence for `gone-quiet` is
measured from our last comment, or from the last activity if `info needed` was set
without one.

`waiting-on-user` is not work. A queue that is entirely `waiting-on-user` is a quiet
day; say so rather than walking the person through six items they cannot act on.

### Then add Jira

The script cannot reach Jira (MCP is not available to subprocesses). Query it directly:

```
project = PSTRNESC AND statusCategory != Done ORDER BY updated DESC
```

`PSTRNESC` is the **Positron Escalations** board. Positron tickets used to live in the
shared `IDEESC` project behind a `Positron` label; by early Oct 2026 they had all moved to
`PSTRNESC` (new keys, same workflow), so querying `IDEESC` now returns nothing and
looks like a quiet day. The wiki's Intake Rotation page is the source of truth for where
tickets live; if this query ever returns zero, check the board link there before
believing it.

Then one straggler check, since a ticket escalated to the shared board without the
`Positron` label never moves over:

```
project = IDEESC AND statusCategory != Done AND summary ~ "Positron" ORDER BY updated DESC
```

Anything it finds is not ours to work in place. Report it in one line so Support can
move it to `PSTRNESC`.

Use `cloudId: positpbc.atlassian.net`. **Request narrow `fields` and do not request
`description`** -- these tickets carry enormous Zendesk-relay descriptions, thousands of
tokens each. `summary`, `status`, `priority`, `labels`, `created`, `updated`, `assignee`
is enough for the worklist. Pull the

---

*Content truncated.*

When not to use it

  • →Directly closing issues or merging PRs
  • →Writing code fixes for bugs
  • →Managing non-GitHub repositories

Prerequisites

GitHub account access

Limitations

  • →Requires manual action for all changes
  • →Does not execute automated repository management

How it compares

It provides a systematic response framework without automating repository state changes.

Compared to similar skills

positron-intake-rotation side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
positron-intake-rotation (this skill)21yReviewBeginner
linear105moNo flagsBeginner
zapier-workflows1112moReviewBeginner
attio-skill-generator710moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by posit-dev

View all by posit-dev →

positron-e2e-tests

posit-dev

This skill should be used when writing, debugging, or maintaining Playwright e2e tests for Positron. Load this skill when creating new test files, adding test cases, fixing flaky tests, or understanding the test infrastructure.

610

port-from-bslib

posit-dev

Comprehensive guide for porting UI components from R's bslib package to py-shiny. Use this skill when: (1) User asks to "port this feature" or "port a component" and mentions bslib or links to a bslib PR (e.g., github.com/rstudio/bslib/pull/...), (2) Porting a new component from bslib to py-shiny, (3) Adding a new input, output, or UI component that exists in bslib, (4) Implementing feature parity with bslib, (5) Working on bslib-related features or components. Covers the complete workflow including understanding source implementation, creating Python equivalents, vendoring assets (SCSS, CSS, JavaScript), creating tests, documentation, and all necessary project files.

17

positron-issue-creator

posit-dev

This skill should be used when drafting GitHub issues for the Positron repository. It provides workflows for searching duplicates, selecting appropriate labels, gathering complete context through questioning, and writing terse, fluff-free issues that precisely describe what is needed or wrong. The skill prepares issues for manual submission by the user. Use this skill when the user asks to draft or prepare an issue for Positron.

14

positron-pr-helper

posit-dev

Generates well-structured PR bodies with dynamically fetched e2e test tags

16

positron-qa-verify

posit-dev

Generates clear, actionable verification guides for QA testing of Positron bug fixes and features

12

positron-abstract-svg

posit-dev

>

00

You might also like

linear

lobehub

Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.

10117

zapier-workflows

davila7

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.

11101

attio-skill-generator

kesslerio

Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.

7100

automation-brainstorm

MacroMan5

Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.

778

daily-briefing

anthropics

Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".

761

jira

davila7

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

1152

Search skills

Search the agent skills registry