421 skills · sorted by relevance
Review and manage issues, projects, and planning data in Linear. Use it to examine development cycles, find carried-over tickets and release blockers, and update issue status, assignees, priorities, or milestones with the required access.
Turn previously fetched pull request reviews into an ordered action plan. Separate distinct findings, track deferred work in Linear, validate that every triage decision is complete, and produce JSON and Markdown files for the implementation phase.
Prepare feature work by reading a Linear ticket and its context, checking development tools, and looking for existing implementation or pull requests. Route requested PR changes to a separate review workflow before development proceeds.
Turn a work-items.md file (produced by /plan-work-items) into Linear issues, one per slice, in a single target Linear team. Use when you want to publish work items as Linear issues, create implementation tickets to track in Linear, or push a broken-down plan into a Linear team. Requires a configured Linear MCP server and a target team. Reads the team's real workflow states, labels, Projects, and members and resolves every option against them before creating anything; defaults each issue to the team's initial state, unassigned, uncategorized, with no parent or Project unless you ask. Links within-file `Depends on` relationships as native Linear "blocked by" relations and annotates the source file so re-runs resume cleanly. Does not produce the work-items file itself — use plan-work-items first. Does not post to Jira — use work-items-to-jira. Does not post to GitHub — use work-items-to-issues.
The English summary is being prepared. Showing the original description.
Configure Factory board behavior and GitHub or Linear event handlers in deployment code. Adjust stage transitions, phase meanings, and tool-result handling, then check the changes with focused tests and versioned audit records.
Prepare new hires' onboarding from Google Workspace group records and documented role standards. Plan accounts and memberships, invite hires to Slack channels, and create first-week Linear checklists, while holding Workspace access changes for human approval.
Organize work in Linear with clear issue ownership, priorities, completion criteria, and delivery plans. Helps structure cycles, meaning time-boxed work periods, define project milestones, and plan automated status updates through GitHub integrations or the GraphQL API.
Build a realistic Linear cycle plan using priorities, dependencies, estimates, unfinished work, and team capacity. Separate essential work from optional additions, flag blockers and missing estimates, and wait for approval before changing issues, estimates, or owners.
Manages Linear issues, teams, and projects via CLI. Lists issues, creates tasks, views details, links issues, and runs GraphQL queries. Must use for "my Linear issues", "create Linear task", "link issues in Linear", "Linear API query", or any Linear project management request.
The English summary is being prepared. Showing the original description.
Save, organize, synchronize, and retrieve documents, conversations, and project information across local files, memory tools, knowledge repositories, and databases. Check for duplicates before storing information and choose a suitable home for each type of knowledge.
Investigates GitHub or Linear issues through code, change history, and reproduction attempts. Produces a structured handoff covering causes, assumptions, effort, and impact, then requests the appropriate Factory workflow stage update when applicable.
Investigate opaque errors in shipped OpenWork builds using local logs and Sentry exception reports. Identify the change that caused the failure, reproduce it on the affected runtime, file a Linear issue, and reply to the original report.
Turn a sales call transcript into an updated HubSpot deal, Linear tasks for commitments, and a recap email draft. Ambiguous deal matches are flagged for a person to check, and the email stays unsent for the representative's review.
Find Linear issues by text, assignee, or status, and read their details and comments. Prepare new issues, comments, and status changes for user approval, then return identifiers and links so results can be checked.
Draft a Linear project update by comparing current issues with the previous report. Explain progress, added scope, schedule risks, and one needed decision, then publish the update to the project after the user approves it.
Find Linear issues reporting the same underlying bug, compare their evidence, and propose which issue to keep. After approval, transfer unique findings and relevant people’s details, then close duplicates with links to the surviving issue.
Turn validated Codex Security findings into tracked work in Linear, Jira, GitHub issues, or draft GitHub security advisories. Check for duplicates, preview exact content and audience, and record approved creations, updates, or reuse.
Review Linear issues, check for duplicates, and organize confirmed facts, reproduction details, impact, and missing information. The skill recommends priorities, labels, statuses, and owners using the team's existing conventions and available evidence.
Fetch a Linear ticket's title + description (the source of all warp route parameters) from a ticket ID or URL, using whichever Linear access the agent has — a Linear integration/tool if present, otherwise the Linear GraphQL API with LINEAR_API_KEY — and halt clearly if no access is configured. Referenced by every warp deploy/update skill that reads a ticket.
The English summary is being prepared. Showing the original description.
Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.
The English summary is being prepared. Showing the original description.
Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.
The English summary is being prepared. Showing the original description.
Scan Gmail (default: today's inbox), produce an anonymized summary with action points, then export each email to Linear as an issue with a sensible priority. No personal details — names, email addresses, or company identifiers — ever leave the summary or reach Linear. Use when the user types /gmail-linear-exports, or asks to turn their inbox into Linear issues / export emails to Linear.
The English summary is being prepared. Showing the original description.
Scan Gmail (default: today's inbox), produce an anonymized summary with action points, then export each email to Linear as an issue with a sensible priority. No personal details — names, email addresses, or company identifiers — ever leave the summary or reach Linear. Use when the user types /gmail-linear-exports, or asks to turn their inbox into Linear issues / export emails to Linear.
The English summary is being prepared. Showing the original description.
Coordinate work across apps connected through Aident Loadout, such as finding issues and sharing summaries. The skill checks available actions, account connections, and costs, then obtains required approval before changing external data.