Managing Linear notifications inbox. Use when listing, filtering, or triaging Linear notifications.
Manages Linear notifications inbox by listing, filtering, archiving, or marking them as read.
npx claudepluginhub bendrucker/claudeThis skill is limited to using the following tools:
Manage the Linear notifications inbox via linear api.
linear api 'query {
notifications(first: 50, filter: { readAt: { null: true } }) {
nodes {
id type readAt archivedAt
... on IssueNotification {
issue { identifier title url state { name } }
comment { body }
}
}
}
}'
| Type | Description |
|---|---|
IssueAssignedToYou | Issue assigned to you |
IssueCommentMention | Mentioned in a comment |
IssueStatusChanged | Status change on subscribed issue |
IssuePriorityUrgent | Issue marked urgent |
Archive:
linear api 'mutation($id: String!) { notificationArchive(input: { id: $id }) { success } }' --variable id=NOTIFICATION_ID
Mark all read:
linear api 'mutation { notificationMarkAllAsRead(input: {}) { success } }'
Add filters to the query:
notifications(first: 50, filter: { type: { eq: "IssueAssignedToYou" } })
notifications(first: 50, filter: { archivedAt: { null: true } })
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.