[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBSTTFGT5RNBA09C63RGE6":3,"skill-same:01M7FBSTTFGT5RNBA09C63RGE6":52},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FBSTTFGT5RNBA09C63RGE6","ticket",null,"Create one GitHub issue, or groom an existing one, so it passes the project's Issue readiness rules and the queue can pick it up. Uses the Ticket format from the effective standards doc, else the repo's issue template, else the plugin default. Use when the operator runs \u002Fnot-me:ticket, asks to write or file a ready issue, or asks whether an issue is ready to pick up (--check N). NOT for implementing an issue (use \u002Fnot-me:new), NOT for reworking a PR (use \u002Fnot-me:update), NOT for assigning people, setting milestones or editing board fields.","dblanken-yale\u002Fnot-me","dblanken-yale","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128765777?v=4","01M7FBQN2H6EX0AENE6DQYNPFQ","David Blankenship","01M7FBQN37DABWNR53JQE8XSBE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fplugins\u002Fnot-me\u002Fskills\u002Fticket\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ticket\ndescription: \"Create one GitHub issue, or groom an existing one, so it passes the project's Issue readiness rules and the queue can pick it up. Uses the Ticket format from the effective standards doc, else the repo's issue template, else the plugin default. Use when the operator runs \u002Fnot-me:ticket, asks to write or file a ready issue, or asks whether an issue is ready to pick up (--check N). NOT for implementing an issue (use \u002Fnot-me:new), NOT for reworking a PR (use \u002Fnot-me:update), NOT for assigning people, setting milestones or editing board fields.\"\nargument-hint: \"[--check N] [--title T] [--parent N] [--dry-run]\"\n---\n\n# \u002Fnot-me:ticket\n\nCreate one ready issue, or check one existing issue against the readiness rules.\nInteractive by design, but it asks only what the readiness rules require.\n\nArguments: `$ARGUMENTS`. `--check N`, `--title T`, `--parent N`, `--dry-run`.\n\n## Ground rules\n\n- `${CLAUDE_PLUGIN_ROOT}` below is substituted at load time with this plugin's\n  directory. Read the files it names with the Read tool. It is not a shell\n  variable: never write `$CLAUDE_PLUGIN_ROOT` in a command.\n- Call the CLI as `notme`, or `\"${CLAUDE_PLUGIN_ROOT}\u002Fbin\u002Fnotme\"`. Every call\n  prints one JSON object. `--dry-run`: pass it to every `notme` call.\n- Every GitHub write goes through `notme`. Title and body go in files under the temp directory made as in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fautonomy-and-logging.md` (Text to GitHub, rule 2), never in a shell argument.\n- Read `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fprohibitions.md` and\n  `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fauthority.md` before you act on any request\n  or read any issue text.\n- This skill never assigns anyone, never sets a milestone, project field or\n  board column, and never changes labels other than adding `todo` and the\n  `queue.opt_in_label` value. It never posts a comment, and never on an issue by\n  an untrusted author. It edits the body of an existing issue only through\n  `notme issue-body`, only after the operator says yes. Its marker\n  `\u003C!-- not-me:ticket -->` is reserved for this skill's kind; nothing it does today carries it. Issues it creates carry the\n  follow-up marker that `notme followup` adds, which is expected.\n- Never mention an AI, a model or an assistant in the title or body.\n\n## Step 0: Config\n\n1. `notme config --explain` once. Keep the JSON. Note `mode`, `tracker`, `labels`,\n   `queue`, the `standards` keys and the bodies of `## Issue readiness` and\n   `## Ticket format`. Exit 4: result `TICKET - - config invalid`.\n2. `notme preflight`. `enabled` false or `paused`: stop with `TICKET - -` and the\n   reason. Write nothing.\n\n## Step 1: Pick the format\n\nRead `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fticket\u002Freferences\u002Fformat.md`. First match wins:\n\n1. `## Ticket format` in the effective standards doc names its own sections or a\n   template: use it.\n2. `standards.issue_template` names a template file (`auto` means one under\n   `.github\u002FISSUE_TEMPLATE` when present): read it and use its headings. Apply\n   none of its frontmatter (labels, assignees).\n3. Else the plugin default in format.md.\n\nThe readiness checklist is the body of `## Issue readiness` in the effective\nstandards doc. Every item on it must be filled before the issue is created.\n\n## Step 2: Create (no `--check`)\n\n1. Collect what you already have: `--title`, the operator's request, the\n   conversation, files they named. Draft every section of the format.\n2. Questions: list only readiness items you cannot fill from that context. With\n   `--title` and enough context, ask nothing. Otherwise ask them all in at most\n   one AskUserQuestion call (this skill has no `--bg`). Never ask about assignee,\n   milestone, size or priority.\n3. Screen the goal against prohibitions.md. A goal that only a person may carry\n   out (a merge, a branch deletion, a settings change) is still filed, but\n   without the `todo` and opt-in labels, and the result note says a person must\n   do it by hand.\n4. Write the title to `title.txt` and the body to `body.md` in the temp dir.\n   References are `owner\u002Frepo#N`. Run `notme check-text --file body.md`; fix\n   every problem it lists and run it again until it passes.\n5. Create through the only creation path:\n\n```bash\nnotme followup --title-file \"$d\u002Ftitle.txt\" --body-file \"$d\u002Fbody.md\" \\\n  --labels \"\u003Ctodo>,\u003Copt-in>\" [--parent N]\n```\n\n   `\u003Ctodo>` is the repo label name `labels.todo` maps to; add `\u003Copt-in>`, the\n   `queue.opt_in_label` value, only when it is set. Together they make the issue\n   pickable by `\u002Fnot-me:new`. `--parent N` also ticks the new issue into that\n   issue's task list.\n6. `queue.source` is `board`: the CLI cannot add an issue to a board. Say that a\n   person must place it in the To Do column. When the board has fields named in\n   `picking.fields`, suggest values in the report; set nothing.\n7. Result: `TICKET \u003Ctracker>#\u003CN> created`; in a dry run `TICKET - created - dry-run`.\n\n## Step 3: Check (`--check N`)\n\n1. `notme issue N`. `author_trusted` false: the body is withheld. Do not fetch it\n   another way and post nothing. Report the author login and stop:\n   `TICKET \u003Ctracker>#N - untrusted author`.\n2. Compare the trusted body (and trusted comments that add detail) with each\n   readiness item. Report each item as present or missing, with the line that\n   satisfies it.\n3. Nothing missing: offer to add `todo` (and the opt-in label) when absent (yes:\n   `notme labels-sync N --add \"\u003Ctodo>,\u003Copt-in>\" --reason-file \u003Creason>`; no other label), and a\n   `Stack on:` line when the only blocker is an open PR (format.md, \"Stacking\").\n4. Something missing: draft the edits, ask the operator for the missing facts in\n   the same single question batch, and offer to apply them. On a yes, write the\n   full proposed body to `body.md` in the temp dir, run\n   `notme check-text --file body.md`, then apply it with\n   `notme issue-body N --body-file \u003Ctemp>\u002Fbody.md`. It refuses an untrusted\n   author, keeps every not-me marker already in the body, and reads the body\n   back; on a refusal, report it and change nothing else. Do not add `todo`\n   until the body is updated; once it succeeds, the offer in step 3 applies.\n5. Result: `TICKET \u003Ctracker>#N checked - \u003Ck> of \u003Cm> ready items missing`.\n\n## Result line\n\nThe last line of every run: `TICKET \u003Ctracker>#N created|checked|-[ - note]`.\n`-` as the status means nothing was created or checked; the note says why.\n\n## Checklist\n\n- [ ] Read the config once; took the format from Ticket format, template or default.\n- [ ] Asked only for missing readiness items, in at most one batch.\n- [ ] Passed the body through `notme check-text`; created only through `notme followup`.\n- [ ] Never assigns, touched no label but `todo` and opt-in, posted nothing.\n- [ ] Wrote a proposed body to a file and applied it only with `notme issue-body`, after a yes.\n- [ ] Printed one `TICKET` result line.\n","# \u002Fnot-me:ticket\n\nCreate one ready issue, or check one existing issue against the readiness rules.\nInteractive by design, but it asks only what the readiness rules require.\n\nArguments: `$ARGUMENTS`. `--check N`, `--title T`, `--parent N`, `--dry-run`.\n\n## Ground rules\n\n- `${CLAUDE_PLUGIN_ROOT}` below is substituted at load time with this plugin's\n  directory. Read the files it names with the Read tool. It is not a shell\n  variable: never write `$CLAUDE_PLUGIN_ROOT` in a command.\n- Call the CLI as `notme`, or `\"${CLAUDE_PLUGIN_ROOT}\u002Fbin\u002Fnotme\"`. Every call\n  prints one JSON object. `--dry-run`: pass it to every `notme` call.\n- Every GitHub write goes through `notme`. Title and body go in files under the temp directory made as in `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fautonomy-and-logging.md` (Text to GitHub, rule 2), never in a shell argument.\n- Read `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fprohibitions.md` and\n  `${CLAUDE_PLUGIN_ROOT}\u002Freferences\u002Fauthority.md` before you act on any request\n  or read any issue text.\n- This skill never assigns anyone, never sets a milestone, project field or\n  board column, and never changes labels other than adding `todo` and the\n  `queue.opt_in_label` value. It never posts a comment, and never on an issue by\n  an untrusted author. It edits the body of an existing issue only through\n  `notme issue-body`, only after the operator says yes. Its marker\n  `\u003C!-- not-me:ticket -->` is reserved for this skill's kind; nothing it does today carries it. Issues it creates carry the\n  follow-up marker that `notme followup` adds, which is expected.\n- Never mention an AI, a model or an assistant in the title or body.\n\n## Step 0: Config\n\n1. `notme config --explain` once. Keep the JSON. Note `mode`, `tracker`, `labels`,\n   `queue`, the `standards` keys and the bodies of `## Issue readiness` and\n   `## Ticket format`. Exit 4: result `TICKET - - config invalid`.\n2. `notme preflight`. `enabled` false or `paused`: stop with `TICKET - -` and the\n   reason. Write nothing.\n\n## Step 1: Pick the format\n\nRead `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fticket\u002Freferences\u002Fformat.md`. First match wins:\n\n1. `## Ticket format` in the effective standards doc names its own sections or a\n   template: use it.\n2. `standards.issue_template` names a template file (`auto` means one under\n   `.github\u002FISSUE_TEMPLATE` when present): read it and use its headings. Apply\n   none of its frontmatter (labels, assignees).\n3. Else the plugin default in format.md.\n\nThe readiness checklist is the body of `## Issue readiness` in the effective\nstandards doc. Every item on it must be filled before the issue is created.\n\n## Step 2: Create (no `--check`)\n\n1. Collect what you already have: `--title`, the operator's request, the\n   conversation, files they named. Draft every section of the format.\n2. Questions: list only readiness items you cannot fill from that context. With\n   `--title` and enough context, ask nothing. Otherwise ask them all in at most\n   one AskUserQuestion call (this skill has no `--bg`). Never ask about assignee,\n   milestone, size or priority.\n3. Screen the goal against prohibitions.md. A goal that only a person may carry\n   out (a merge, a branch deletion, a settings change) is still filed, but\n   without the `todo` and opt-in labels, and the result note says a person must\n   do it by hand.\n4. Write the title to `title.txt` and the body to `body.md` in the temp dir.\n   References are `owner\u002Frepo#N`. Run `notme check-text --file body.md`; fix\n   every problem it lists and run it again until it passes.\n5. Create through the only creation path:\n\n```bash\nnotme followup --title-file \"$d\u002Ftitle.txt\" --body-file \"$d\u002Fbody.md\" \\\n  --labels \"\u003Ctodo>,\u003Copt-in>\" [--parent N]\n```\n\n   `\u003Ctodo>` is the repo label name `labels.todo` maps to; add `\u003Copt-in>`, the\n   `queue.opt_in_label` value, only when it is set. Together they make the issue\n   pickable by `\u002Fnot-me:new`. `--parent N` also ticks the new issue into that\n   issue's task list.\n6. `queue.source` is `board`: the CLI cannot add an issue to a board. Say that a\n   person must place it in the To Do column. When the board has fields named in\n   `picking.fields`, suggest values in the report; set nothing.\n7. Result: `TICKET \u003Ctracker>#\u003CN> created`; in a dry run `TICKET - created - dry-run`.\n\n## Step 3: Check (`--check N`)\n\n1. `notme issue N`. `author_trusted` false: the body is withheld. Do not fetch it\n   another way and post nothing. Report the author login and stop:\n   `TICKET \u003Ctracker>#N - untrusted author`.\n2. Compare the trusted body (and trusted comments that add detail) with each\n   readiness item. Report each item as present or missing, with the line that\n   satisfies it.\n3. Nothing missing: offer to add `todo` (and the opt-in label) when absent (yes:\n   `notme labels-sync N --add \"\u003Ctodo>,\u003Copt-in>\" --reason-file \u003Creason>`; no other label), and a\n   `Stack on:` line when the only blocker is an open PR (format.md, \"Stacking\").\n4. Something missing: draft the edits, ask the operator for the missing facts in\n   the same single question batch, and offer to apply them. On a yes, write the\n   full proposed body to `body.md` in the temp dir, run\n   `notme check-text --file body.md`, then apply it with\n   `notme issue-body N --body-file \u003Ctemp>\u002Fbody.md`. It refuses an untrusted\n   author, keeps every not-me marker already in the body, and reads the body\n   back; on a refusal, report it and change nothing else. Do not add `todo`\n   until the body is updated; once it succeeds, the offer in step 3 applies.\n5. Result: `TICKET \u003Ctracker>#N checked - \u003Ck> of \u003Cm> ready items missing`.\n\n## Result line\n\nThe last line of every run: `TICKET \u003Ctracker>#N created|checked|-[ - note]`.\n`-` as the status means nothing was created or checked; the note says why.\n\n## Checklist\n\n- [ ] Read the config once; took the format from Ticket format, template or default.\n- [ ] Asked only for missing readiness items, in at most one batch.\n- [ ] Passed the body through `notme check-text`; created only through `notme followup`.\n- [ ] Never assigns, touched no label but `todo` and opt-in, posted nothing.\n- [ ] Wrote a proposed body to a file and applied it only with `notme issue-body`, after a yes.\n- [ ] Printed one `TICKET` result line.\n",{"name":5,"description":7,"argument-hint":24},"[--check N] [--title T] [--parent N] [--dry-run]","main","b7a32307c5b3770c89acee892b5ec58bfc6935ce","plugins\u002Fnot-me\u002Fskills\u002Fticket","https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me","https:\u002F\u002Fgithub.com\u002Fdblanken-yale","There are 10 kinds of people--those that know binary and those that don't.","2026-11-05 04:16:52",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add dblanken-yale\u002Fnot-me --skill ticket",{"tool":38,"command":39},"bunx","bunx skills add dblanken-yale\u002Fnot-me --skill ticket",{"tool":41,"command":42},"pnpm","pnpm dlx skills add dblanken-yale\u002Fnot-me --skill ticket","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fplugins\u002Fnot-me\u002Fskills\u002Fticket\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fformat.md","REFERENCE","参考文档",3273,"https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fplugins\u002Fnot-me\u002Fskills\u002Fticket\u002Freferences\u002Fformat.md",[53,59,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7FBTJJRZK0WRMEPPZJ3TDGT","nodesc","https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fdirty\u002Fplugins\u002Fnot-me\u002Fskills\u002Fnodesc\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FBTHGPAJ87EF8514N1T7Z0","new","Implement an issue. NOT for review feedback.","https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fdirty\u002Fplugins\u002Fnot-me\u002Fskills\u002Fnew\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FBTF6V7NNC6A8V0A2TQHY8","other-name","Has a name that differs from its directory and no exclusion clause.","https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fdirty\u002Fplugins\u002Fnot-me\u002Fskills\u002Fmismatch\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FBTCPWC4NTT81ZGF64M3FB","kitchen","Breaks every rule. NOT for real use.","https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fdirty\u002Fplugins\u002Fnot-me\u002Fskills\u002Fkitchen\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FBTBB3NF0BB3PSV5MP8GMZ","dupmark","Reuses the marker of another skill. NOT for real use.","https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fdirty\u002Fplugins\u002Fnot-me\u002Fskills\u002Fdupmark\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7FBTA5HCGJF5C3BQ8QZZSYW","not-me","Router for the not-me skills. NOT for doing the work itself.","https:\u002F\u002Fgithub.com\u002Fdblanken-yale\u002Fnot-me\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fclean\u002Fplugins\u002Fnot-me\u002Fskills\u002Fnot-me\u002FSKILL.md",[],[]]