[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJCQHBST97KWJ949HKJDEV":3,"skill-same:01M7EJCQHBST97KWJ949HKJDEV":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7EJCQHBST97KWJ949HKJDEV","oak-ticket-start",null,"Starts work on a Linear ticket by listing the tickets ready to start, summarising the chosen one with its acceptance criteria, creating a local branch from the latest default branch, moving the ticket to In Progress, then offering to plan the work. Use when asked to start, pick up or begin a ticket or issue, or to create a branch for one.","oaknational\u002Foak-agent-skills","oaknational","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63889701?v=4","01M71E8KA6A3R1XEZH7NVDPNYK","Oak National Academy","01M7EJBV1G62V115Z34X72Q938",0,"MIT","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcentral\u002Foak-ticket-start\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: oak-ticket-start\ndescription: Starts work on a Linear ticket by listing the tickets ready to start, summarising the chosen one with its acceptance criteria, creating a local branch from the latest default branch, moving the ticket to In Progress, then offering to plan the work. Use when asked to start, pick up or begin a ticket or issue, or to create a branch for one.\nlicense: MIT\nmetadata:\n  owner: '@oaknational\u002Fskills-maintainers'\n  updated: '2026-10-27'\n---\n\n# Starting a ticket\n\nStart work from a Linear ticket: help the user pick one, read it out, create a branch for it, and mark it as started. Ask for approval before creating the branch, and don't change anything else.\n\n- Create the branch locally and never push it. There's nothing to push until there's work to ship, and opening the pull request is `oak-pr-create`'s job.\n- In Linear, this skill only moves the chosen ticket to In Progress once the branch exists, and assigns it to the user if they agree. Don't change its description or comments.\n- Never show names or email addresses from Linear. Refer to people by role.\n\nThis skill needs the Linear MCP server. If its tools aren't available, say so, ask the user to paste the ticket's text, and continue from [Step 3](#step-3-read-out-the-ticket).\n\n## Step 1: work out the scope\n\nThe user's message may include:\n\n- **a ticket identifier**, such as `ENG-123`. Go straight to [Step 3](#step-3-read-out-the-ticket);\n- **a base branch** to start from instead of the default branch. Step 4 still confirms it.\n\nFind where to list tickets from, in this order:\n\n1. A Linear team or project named in the repository's `AGENTS.md`.\n2. A team or project the user names.\n3. Otherwise, call `list_teams`, suggest the closest match to the repository, and ask.\n\n## Step 2: list the tickets ready to start\n\nCall `get_user` with `\"me\"` to learn the user's id. Then call `list_issues` for the team or project three times, once for each state type: `started`, `unstarted` and `backlog`. Pass `fields: [\"id\",\"title\",\"priority\",\"status\",\"statusType\",\"assigneeId\"]`, and page through the results while `hasNextPage` is true.\n\nA team can have several `started` states. Keep only the one for active work, such as In Progress, and leave out review states, such as In Review: they aren't work to start.\n\nShow one numbered list, grouped In Progress, then Todo, then Backlog, and within each group ordered Urgent, High, Medium, Low, then no priority. Give each ticket one line: its identifier, its priority and its title.\n\n```text\n**In Progress**\n1. ENG-110  --      Add a health check endpoint\n2. ENG-115  --      Cache the search results page  (someone else's)\n\n**Todo**\n3. ENG-126  Urgent  Fix the broken sign-in redirect\n4. ENG-123  High    Add filters to lesson search\n\n**Backlog**\n5. ENG-122  --      Remove the old analytics script\n```\n\nIn Progress comes first, because people often move a ticket on the board before starting it. Mark an In Progress ticket assigned to someone else as `(someone else's)`, without naming them, so the user doesn't start work that's already under way.\n\nThen stop and wait for the user to choose, by number or identifier.\n\n## Step 3: read out the ticket\n\nCall `get_issue` with the identifier and `includeRelations: true`, because the list shortens descriptions. Then give the user:\n\n- one sentence on what the ticket asks for and why;\n- **the acceptance criteria, quoted word for word as a checklist.** The work is judged against them, so don't paraphrase. If the ticket has none, say so, and list what it does specify as the scope;\n- any constraints, and the tickets blocking this one, flagging any blocker that isn't done.\n\n## Step 4: confirm the branch name and base\n\nPropose both in one message, and wait until the user approves both:\n\n```text\nBranch:  feat\u002FENG-123-lesson-search-filters\nBase:    main  (the default; name another branch if this work builds on it)\n```\n\n- **Branch name.** Follow the convention in `AGENTS.md` if it has one. Otherwise use `\u003Ctype>\u002F\u003CTICKET-ID>-\u003Cslug>`: `feat`, or `fix` or `chore` when the ticket is clearly a bug fix or a chore. Make the slug from the title's distinctive words, in lowercase, joined by single hyphens, about 20 characters long, without cutting a word.\n- **Base.** The repository's default branch (`git symbolic-ref --short refs\u002Fremotes\u002Forigin\u002FHEAD`), unless the user named another. If they name another, check it exists with `git ls-remote --exit-code --heads origin \u003Cbase>` before going further.\n\n## Step 5: create the branch\n\n1. Run `git status --porcelain`. If there are uncommitted changes, show them and ask whether to stash them. Only if the user agrees, run `git stash push -u -m \"oak-ticket-start: \u003CTICKET-ID>\"` and tell them `git stash pop` brings the changes back. If they don't agree, stop.\n2. Fetch, then branch from the fetched base, so the branch starts from the latest version rather than a stale local copy:\n\n   ```bash\n   git fetch origin\n   git switch -c \u003Cbranch> origin\u002F\u003Cbase>\n   ```\n\n## Step 6: move the ticket to In Progress\n\nOnly once the branch exists, call `save_issue` with the identifier and `state: \"In Progress\"`. If the team has no state with that name, use its active `started` state.\n\nSkip this when the ticket is already In Progress or further along, such as In Review or Done: never move a ticket backwards.\n\nTell the user which state the ticket moved from, or that it was left as it was. If the update fails, say so plainly: the branch exists, but the board doesn't show the work has started.\n\nIf the ticket has no assignee, ask whether to assign it to the user, and only if they agree, call `save_issue` with `assignee: \"me\"`. Never reassign a ticket that already has an assignee.\n\n## Step 7: offer to plan\n\nConfirm the branch exists locally and hasn't been pushed. Then offer to plan the work against the acceptance criteria from Step 3, in the agent's planning mode if it has one. Don't switch into planning mode until the user agrees.\n","# Starting a ticket\n\nStart work from a Linear ticket: help the user pick one, read it out, create a branch for it, and mark it as started. Ask for approval before creating the branch, and don't change anything else.\n\n- Create the branch locally and never push it. There's nothing to push until there's work to ship, and opening the pull request is `oak-pr-create`'s job.\n- In Linear, this skill only moves the chosen ticket to In Progress once the branch exists, and assigns it to the user if they agree. Don't change its description or comments.\n- Never show names or email addresses from Linear. Refer to people by role.\n\nThis skill needs the Linear MCP server. If its tools aren't available, say so, ask the user to paste the ticket's text, and continue from [Step 3](#step-3-read-out-the-ticket).\n\n## Step 1: work out the scope\n\nThe user's message may include:\n\n- **a ticket identifier**, such as `ENG-123`. Go straight to [Step 3](#step-3-read-out-the-ticket);\n- **a base branch** to start from instead of the default branch. Step 4 still confirms it.\n\nFind where to list tickets from, in this order:\n\n1. A Linear team or project named in the repository's `AGENTS.md`.\n2. A team or project the user names.\n3. Otherwise, call `list_teams`, suggest the closest match to the repository, and ask.\n\n## Step 2: list the tickets ready to start\n\nCall `get_user` with `\"me\"` to learn the user's id. Then call `list_issues` for the team or project three times, once for each state type: `started`, `unstarted` and `backlog`. Pass `fields: [\"id\",\"title\",\"priority\",\"status\",\"statusType\",\"assigneeId\"]`, and page through the results while `hasNextPage` is true.\n\nA team can have several `started` states. Keep only the one for active work, such as In Progress, and leave out review states, such as In Review: they aren't work to start.\n\nShow one numbered list, grouped In Progress, then Todo, then Backlog, and within each group ordered Urgent, High, Medium, Low, then no priority. Give each ticket one line: its identifier, its priority and its title.\n\n```text\n**In Progress**\n1. ENG-110  --      Add a health check endpoint\n2. ENG-115  --      Cache the search results page  (someone else's)\n\n**Todo**\n3. ENG-126  Urgent  Fix the broken sign-in redirect\n4. ENG-123  High    Add filters to lesson search\n\n**Backlog**\n5. ENG-122  --      Remove the old analytics script\n```\n\nIn Progress comes first, because people often move a ticket on the board before starting it. Mark an In Progress ticket assigned to someone else as `(someone else's)`, without naming them, so the user doesn't start work that's already under way.\n\nThen stop and wait for the user to choose, by number or identifier.\n\n## Step 3: read out the ticket\n\nCall `get_issue` with the identifier and `includeRelations: true`, because the list shortens descriptions. Then give the user:\n\n- one sentence on what the ticket asks for and why;\n- **the acceptance criteria, quoted word for word as a checklist.** The work is judged against them, so don't paraphrase. If the ticket has none, say so, and list what it does specify as the scope;\n- any constraints, and the tickets blocking this one, flagging any blocker that isn't done.\n\n## Step 4: confirm the branch name and base\n\nPropose both in one message, and wait until the user approves both:\n\n```text\nBranch:  feat\u002FENG-123-lesson-search-filters\nBase:    main  (the default; name another branch if this work builds on it)\n```\n\n- **Branch name.** Follow the convention in `AGENTS.md` if it has one. Otherwise use `\u003Ctype>\u002F\u003CTICKET-ID>-\u003Cslug>`: `feat`, or `fix` or `chore` when the ticket is clearly a bug fix or a chore. Make the slug from the title's distinctive words, in lowercase, joined by single hyphens, about 20 characters long, without cutting a word.\n- **Base.** The repository's default branch (`git symbolic-ref --short refs\u002Fremotes\u002Forigin\u002FHEAD`), unless the user named another. If they name another, check it exists with `git ls-remote --exit-code --heads origin \u003Cbase>` before going further.\n\n## Step 5: create the branch\n\n1. Run `git status --porcelain`. If there are uncommitted changes, show them and ask whether to stash them. Only if the user agrees, run `git stash push -u -m \"oak-ticket-start: \u003CTICKET-ID>\"` and tell them `git stash pop` brings the changes back. If they don't agree, stop.\n2. Fetch, then branch from the fetched base, so the branch starts from the latest version rather than a stale local copy:\n\n   ```bash\n   git fetch origin\n   git switch -c \u003Cbranch> origin\u002F\u003Cbase>\n   ```\n\n## Step 6: move the ticket to In Progress\n\nOnly once the branch exists, call `save_issue` with the identifier and `state: \"In Progress\"`. If the team has no state with that name, use its active `started` state.\n\nSkip this when the ticket is already In Progress or further along, such as In Review or Done: never move a ticket backwards.\n\nTell the user which state the ticket moved from, or that it was left as it was. If the update fails, say so plainly: the branch exists, but the board doesn't show the work has started.\n\nIf the ticket has no assignee, ask whether to assign it to the user, and only if they agree, call `save_issue` with `assignee: \"me\"`. Never reassign a ticket that already has an assignee.\n\n## Step 7: offer to plan\n\nConfirm the branch exists locally and hasn't been pushed. Then offer to plan the work against the acceptance criteria from Step 3, in the agent's planning mode if it has one. Don't switch into planning mode until the user agrees.\n",{"name":5,"license":15,"metadata":24,"description":7},{"owner":25,"updated":26},"@oaknational\u002Fskills-maintainers","2026-10-27","main","aa4f22c3a1650bc207889cf83b762af943a0e08a","skills\u002Fcentral\u002Foak-ticket-start",1,"https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills","https:\u002F\u002Fgithub.com\u002Foaknational","https:\u002F\u002Fwww.thenational.academy\u002F","Creating an openly licensed, fully resourced and AI-enabled curriculum for teachers and pupils as a not for profit and independent Arm's Length Body of UK Gov","2026-11-11 04:39:53",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add oaknational\u002Foak-agent-skills --skill oak-ticket-start",{"tool":42,"command":43},"bunx","bunx skills add oaknational\u002Foak-agent-skills --skill oak-ticket-start",{"tool":45,"command":46},"pnpm","pnpm dlx skills add oaknational\u002Foak-agent-skills --skill oak-ticket-start","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcentral\u002Foak-ticket-start\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7EJD9XXYMZVYTDQNRJHH3ZM","owa-routing","Routing for the web application. Use when a test needs a bundle skill.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Frepos\u002Fowa\u002Fowa-routing\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7EJD6PTM1D7YJE47QP531MG","oc-tokens","Design tokens for the component library. Use when a test needs another bundle.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Frepos\u002Foc\u002Foc-tokens\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7EJD3SSF5KRDS2WVD3EZ5QK","oak-gamma","The gamma test skill. Use when a test needs gamma.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Fcentral\u002Foak-gamma\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EJD0QWKB318A0XG98Z9ANJ","oak-beta","The beta test skill. Use when a test needs beta.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Fcentral\u002Foak-beta\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7EJCXV42PQNWG6VGWQHDHWB","oak-alpha","The alpha test skill. Use when a test needs alpha.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Fcentral\u002Foak-alpha\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7EJCW482706XRCJ5Q5636KT","oak-example","An example skill for tests. Use it when a test needs a valid skill.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fcentral-repo\u002Fskills\u002Fcentral\u002Foak-example\u002FSKILL.md",[],[]]