[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79R395S4TS1XENQWWCSBT56":3,"skill-same:01M79R395S4TS1XENQWWCSBT56":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79R395S4TS1XENQWWCSBT56","ticket",null,"Capture a brain-dump as a well-formed work item - verb-first title, acceptance criteria, file paths when known, an out-of-scope line. Files a GitHub issue in tickets mode or appends a numbered PLAN.md task in document mode; unknowns are marked TBD, never invented. Use when the user brain-dumps an idea, bug, or task to capture for later, or asks to ticket, file, or note something as work.","AaravChadha\u002Facstack","AaravChadha","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224610398?v=4","01M79QZCAGEMRNH32DKH6VC5RJ","01M79QZCB37TR94RNR32TM7YTV",2,"MIT","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fticket\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ticket\ndescription: Capture a brain-dump as a well-formed work item - verb-first title, acceptance criteria, file paths when known, an out-of-scope line. Files a GitHub issue in tickets mode or appends a numbered PLAN.md task in document mode; unknowns are marked TBD, never invented. Use when the user brain-dumps an idea, bug, or task to capture for later, or asks to ticket, file, or note something as work.\nargument-hint: \"\u003Cbrain-dump>\"\n---\n\n# \u002Fticket — capture without friction, file without slop\n\nThe frictionless entry point that keeps ideas from routing around the\nsystem. A thought arrives half-formed; it leaves as a work item the\nnext session can pick up cold — or it honestly wears a TBD.\n\n`Adjacent skills:` \u002Fdo (does the work; \u002Fticket only captures it) ·\n\u002Ftriage (grooms the many existing items; \u002Fticket files one new one).\n\n\u003C!-- acstack:runtime -->\nRun before the skill's steps — per invocation, not per session (4.36); failures degrade to markdown:\n```bash\nlink=\"$(readlink \"$HOME\u002F.claude\u002Fskills\u002Fhealth\" 2>\u002Fdev\u002Fnull || true)\"   # empty = not symlinked\npack=\"$(dirname \"$(dirname \"$link\")\")\"   # NEVER trust this unless $link was non-empty\nif [ \"${link#\u002F}\" != \"$link\" ] && [ -x \"$pack\u002Fbin\u002Facstack-config\" ] && ! \"$pack\u002Fbin\u002Facstack-config\" runtime | grep -q '=off'; then\n  \"$pack\u002Fbin\u002Facstack-config\" || true          # resolved keys, with sources\n  \"$pack\u002Fbin\u002Facstack-update-check\" || true    # ≤1 fetch\u002Fday; silent ONLY if already checked today\n  \"$pack\u002Fbin\u002Facstack-recall\" || true          # LEARNINGS.md + bug-class names, capped 3KB\nelse\n  echo \"runtime off — proceeding without recall\u002Fupdate-check\"\nfi\n```\n\u003C!-- \u002Facstack:runtime -->\n\n\u003C!-- acstack:principles -->\n## Operating principles\n\n- Be direct. Push back in writing when the plan or the user is wrong. No sycophancy.\n- Never delete a decision. Supersede it: `~~old~~ → **Verdict (YYYY-MM-DD):** new call — reason.`\n- Never fix, tune, or delete a test or eval case to raise a score. Log the miss honestly and leave the case unchanged.\n- Name exact things: regex patterns, function signatures, model names, before → after numbers. Never \"fixed bugs\".\n- Attribution: follow the project's `attribution` setting (default `none`) — no AI-tool mentions in generated docs, no attribution trailers in commits or PRs. Commit with explicit `-m`\u002F`-F` messages only.\n- Config: read `.claude\u002Facstack.md` at the project root (fall back to `~\u002F.claude\u002Facstack.md`) before acting. `## Settings` keys override pack defaults; a `## \u003Cskill-name>` section overrides both. Unknown keys and sections are ignored.\n- Docs: BRIEF.md (frozen seed) \u002F PLAN.md (living plan) \u002F JOURNAL.md (rolling journal). If the repo uses legacy names (PLANNING_PROMPT.md \u002F PLANNING.md \u002F STATUS.md), use those instead — never create both.\n- Recall: if `LEARNINGS.md` exists at the project root, read it before starting.\n- Conduct: follow the `acstack-conduct` block in this repo's AGENTS.md — the word is the mode; the user sets the pace.\n- Hackathon lane: if the project's AGENTS.md carries the `acstack:hackathon-lane` block, only `\u002Fdo` changes the repository during the event. Any other skill that would write a tracked file, commit or push says what it would have done and stops; a change that is not a task goes through the lane's operator route.\n\u003C!-- \u002Facstack:principles -->\n\n**One document set.** Resolve exactly ONE BRIEF\u002FPLAN\u002FJOURNAL set and name\nits path in the report's scope line. If more than one candidate set exists\n— a monorepo, nested products, an `apps\u002F*` tree each with its own docs —\nlist the candidates and STOP. Never pick one silently: a confident answer\nabout the wrong product is worse than no answer (conduct rule 8).\n\n## The bar\n\nEvery filed item has:\n\n- **Verb-first title** — `fix scheme-name matching for hyphenated funds`,\n  not `scheme names`.\n- **Acceptance criteria** — runnable where possible; observable always.\n- **File paths** — when known or cheaply inferable from the dump.\n- **Out-of-scope line** — the adjacent thing this item deliberately does\n  NOT cover; the line that prevents scope osmosis later.\n\nWhat the dump doesn't say and the repo can't cheaply tell you is marked\nexplicitly — `Acceptance: TBD — needs \u003Cwhat>` — never invented. A wrong\nguessed acceptance is worse than an honest TBD: it fails silently at \u002Fdo\ntime.\n\nAt most ONE round of clarifying questions, and only when the item would\notherwise be unfileable (no discernible action at all). Friction is the\nenemy here: a captured-but-imperfect item beats a perfect item the user\ngave up on filing.\n\n## Tickets mode (`tracking: tickets`)\n\nPreconditions — `gh` installed, `gh auth status` succeeding, and a\nGitHub remote present. Any failure names WHICH one failed and offers\ndocument mode; never guess. Then `gh issue create`:\n\n- Body follows `.github\u002FISSUE_TEMPLATE\u002Ftask.md` (acceptance \u002F files \u002F\n  out-of-scope sections).\n- Best-fit label from the standard set (`bug` \u002F `feature` \u002F `chore`);\n  items with TBD acceptance also get `needs-acceptance`.\n- Milestone: the current one, unless the dump clearly targets another —\n  ask only when genuinely ambiguous, and never more than once.\n\n## Document mode\n\nAppend a numbered task to PLAN.md:\n\n- Under the current open phase, taking the next free task number — existing\n  tasks are NEVER renumbered. **One carve-out: a number allocated on a\n  branch is provisional until the branch merges.** Two sessions reading the\n  same plan draw the same number, and when the filings land at different\n  offsets git merges them with no conflict (measured 2026-09-16, 5.17.1).\n  So place the new task at the **physical end** of the phase's list, where a\n  concurrent filing collides visibly instead of merging silently — and when\n  two filings do collide, keep both and renumber the **later-merged** one;\n  never drop either.\n- With its acceptance line (or the explicit TBD).\n- No obvious phase → a dated checkbox under `## Open items` instead;\n  \u002Ftriage or the next `\u002Fplan replan` finds it a home.\n- **No PLAN.md at all** → do NOT create one. A plan scaffolded as a side\n  effect of filing a ticket is a plan nobody designed. Say the item cannot\n  be filed in document mode, print the well-formed task text so nothing is\n  lost, and name `\u002Fplan seed` as what creates the document.\n\n## Report and stop\n\nReport what was filed — the issue URL or the exact PLAN.md line, and in\ndocument mode that the number is provisional until the branch merges — and\nstop. Capture never starts the work (CONDUCT rule 5): \u002Fticket writing\ncode because the fix \"looked quick\" is exactly the failure mode this\nskill exists to prevent.\n","# \u002Fticket — capture without friction, file without slop\n\nThe frictionless entry point that keeps ideas from routing around the\nsystem. A thought arrives half-formed; it leaves as a work item the\nnext session can pick up cold — or it honestly wears a TBD.\n\n`Adjacent skills:` \u002Fdo (does the work; \u002Fticket only captures it) ·\n\u002Ftriage (grooms the many existing items; \u002Fticket files one new one).\n\n\u003C!-- acstack:runtime -->\nRun before the skill's steps — per invocation, not per session (4.36); failures degrade to markdown:\n```bash\nlink=\"$(readlink \"$HOME\u002F.claude\u002Fskills\u002Fhealth\" 2>\u002Fdev\u002Fnull || true)\"   # empty = not symlinked\npack=\"$(dirname \"$(dirname \"$link\")\")\"   # NEVER trust this unless $link was non-empty\nif [ \"${link#\u002F}\" != \"$link\" ] && [ -x \"$pack\u002Fbin\u002Facstack-config\" ] && ! \"$pack\u002Fbin\u002Facstack-config\" runtime | grep -q '=off'; then\n  \"$pack\u002Fbin\u002Facstack-config\" || true          # resolved keys, with sources\n  \"$pack\u002Fbin\u002Facstack-update-check\" || true    # ≤1 fetch\u002Fday; silent ONLY if already checked today\n  \"$pack\u002Fbin\u002Facstack-recall\" || true          # LEARNINGS.md + bug-class names, capped 3KB\nelse\n  echo \"runtime off — proceeding without recall\u002Fupdate-check\"\nfi\n```\n\u003C!-- \u002Facstack:runtime -->\n\n\u003C!-- acstack:principles -->\n## Operating principles\n\n- Be direct. Push back in writing when the plan or the user is wrong. No sycophancy.\n- Never delete a decision. Supersede it: `~~old~~ → **Verdict (YYYY-MM-DD):** new call — reason.`\n- Never fix, tune, or delete a test or eval case to raise a score. Log the miss honestly and leave the case unchanged.\n- Name exact things: regex patterns, function signatures, model names, before → after numbers. Never \"fixed bugs\".\n- Attribution: follow the project's `attribution` setting (default `none`) — no AI-tool mentions in generated docs, no attribution trailers in commits or PRs. Commit with explicit `-m`\u002F`-F` messages only.\n- Config: read `.claude\u002Facstack.md` at the project root (fall back to `~\u002F.claude\u002Facstack.md`) before acting. `## Settings` keys override pack defaults; a `## \u003Cskill-name>` section overrides both. Unknown keys and sections are ignored.\n- Docs: BRIEF.md (frozen seed) \u002F PLAN.md (living plan) \u002F JOURNAL.md (rolling journal). If the repo uses legacy names (PLANNING_PROMPT.md \u002F PLANNING.md \u002F STATUS.md), use those instead — never create both.\n- Recall: if `LEARNINGS.md` exists at the project root, read it before starting.\n- Conduct: follow the `acstack-conduct` block in this repo's AGENTS.md — the word is the mode; the user sets the pace.\n- Hackathon lane: if the project's AGENTS.md carries the `acstack:hackathon-lane` block, only `\u002Fdo` changes the repository during the event. Any other skill that would write a tracked file, commit or push says what it would have done and stops; a change that is not a task goes through the lane's operator route.\n\u003C!-- \u002Facstack:principles -->\n\n**One document set.** Resolve exactly ONE BRIEF\u002FPLAN\u002FJOURNAL set and name\nits path in the report's scope line. If more than one candidate set exists\n— a monorepo, nested products, an `apps\u002F*` tree each with its own docs —\nlist the candidates and STOP. Never pick one silently: a confident answer\nabout the wrong product is worse than no answer (conduct rule 8).\n\n## The bar\n\nEvery filed item has:\n\n- **Verb-first title** — `fix scheme-name matching for hyphenated funds`,\n  not `scheme names`.\n- **Acceptance criteria** — runnable where possible; observable always.\n- **File paths** — when known or cheaply inferable from the dump.\n- **Out-of-scope line** — the adjacent thing this item deliberately does\n  NOT cover; the line that prevents scope osmosis later.\n\nWhat the dump doesn't say and the repo can't cheaply tell you is marked\nexplicitly — `Acceptance: TBD — needs \u003Cwhat>` — never invented. A wrong\nguessed acceptance is worse than an honest TBD: it fails silently at \u002Fdo\ntime.\n\nAt most ONE round of clarifying questions, and only when the item would\notherwise be unfileable (no discernible action at all). Friction is the\nenemy here: a captured-but-imperfect item beats a perfect item the user\ngave up on filing.\n\n## Tickets mode (`tracking: tickets`)\n\nPreconditions — `gh` installed, `gh auth status` succeeding, and a\nGitHub remote present. Any failure names WHICH one failed and offers\ndocument mode; never guess. Then `gh issue create`:\n\n- Body follows `.github\u002FISSUE_TEMPLATE\u002Ftask.md` (acceptance \u002F files \u002F\n  out-of-scope sections).\n- Best-fit label from the standard set (`bug` \u002F `feature` \u002F `chore`);\n  items with TBD acceptance also get `needs-acceptance`.\n- Milestone: the current one, unless the dump clearly targets another —\n  ask only when genuinely ambiguous, and never more than once.\n\n## Document mode\n\nAppend a numbered task to PLAN.md:\n\n- Under the current open phase, taking the next free task number — existing\n  tasks are NEVER renumbered. **One carve-out: a number allocated on a\n  branch is provisional until the branch merges.** Two sessions reading the\n  same plan draw the same number, and when the filings land at different\n  offsets git merges them with no conflict (measured 2026-09-16, 5.17.1).\n  So place the new task at the **physical end** of the phase's list, where a\n  concurrent filing collides visibly instead of merging silently — and when\n  two filings do collide, keep both and renumber the **later-merged** one;\n  never drop either.\n- With its acceptance line (or the explicit TBD).\n- No obvious phase → a dated checkbox under `## Open items` instead;\n  \u002Ftriage or the next `\u002Fplan replan` finds it a home.\n- **No PLAN.md at all** → do NOT create one. A plan scaffolded as a side\n  effect of filing a ticket is a plan nobody designed. Say the item cannot\n  be filed in document mode, print the well-formed task text so nothing is\n  lost, and name `\u002Fplan seed` as what creates the document.\n\n## Report and stop\n\nReport what was filed — the issue URL or the exact PLAN.md line, and in\ndocument mode that the number is provisional until the branch merges — and\nstop. Capture never starts the work (CONDUCT rule 5): \u002Fticket writing\ncode because the fix \"looked quick\" is exactly the failure mode this\nskill exists to prevent.\n",{"name":5,"description":7,"argument-hint":23},"\u003Cbrain-dump>","main","6b5be39937ce3823cf8f58c68aadcfdfda839fa0","skills\u002Fticket",0,"https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack","https:\u002F\u002Fgithub.com\u002FAaravChadha","2026-09-28 13:07:41",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add AaravChadha\u002Facstack --skill ticket",{"tool":37,"command":38},"bunx","bunx skills add AaravChadha\u002Facstack --skill ticket",{"tool":40,"command":41},"pnpm","pnpm dlx skills add AaravChadha\u002Facstack --skill ticket","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fticket\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M79R3MBE63G66XVKHV652YAD","why","Decision archaeology - answers why the code, config, or plan is the way it is by searching the record in a fixed order: BRIEF constraints, dated PLAN decisions, JOURNAL entries, then git history. Stops at the first real answer, cites it with a date, and says no recorded rationale rather than inventing one. Use when someone asks why something is this way, why a choice was made, or where a decision is written down.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M79R3G7EA313SYFS30H1K51A","verify","Audit a completion claim made by someone else - another session, agent, or teammate - against the running system rather than the diff. Re-derives what the claim's acceptance demands, runs it, and returns CONFIRMED, OVERSTATED, FALSE or UNVERIFIABLE with the command and its output. Never fixes, never edits the claim or the acceptance. Use when handed a \"done\", \"all green\", \"merged\" or \"it works\" you did not produce yourself.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M79R3CPD2F05EKE9N8XCMM90","triage","Backlog hygiene sweep - stale items, duplicate pairs, missing acceptance criteria, unblocked-but-unassigned work, and milestone burn, delivered as a report first with only user-approved actions applied. Works on GitHub Issues in tickets mode and on PLAN.md checkboxes in document mode. Use when the user asks to triage, groom, or clean up the backlog or the plan's open tasks.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M79R358JKQ1EB3TQKT2MPSB6","ship","Branch-level release with five gates before the act - clean-state, tests, eval-vs-target, docs drift, and attribution sweep; any failing gate stops the release with its output. Then push, and under push: branch-pr open a report-shaped PR wiring the issue-closing reference in tickets mode or PLAN task IDs in document mode. Use when the user asks to ship, release, cut, or open the PR for a feature or branch.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M79R2ZXGVB7W1J8ZH8TRGWDN","secure","Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high\u002Fmedium\u002Flow confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization\u002Fcrypto\u002Ftransport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fsecure\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M79R2WPCWE214XBCZB1KKQ9M","retro","Trend review across many sessions - velocity vs planned dates, eval-score trend toward target, failure-category trends from journal triage and investigations, and a status check on every open PLAN risk. Reads JOURNAL\u002FPLAN\u002Feval history, writes a dated retro entry into JOURNAL.md. Use when the user asks for a retro, a weekly review, or a phase-end wrap-up.","https:\u002F\u002Fgithub.com\u002FAaravChadha\u002Facstack\u002Fblob\u002Fmain\u002Fskills\u002Fretro\u002FSKILL.md",[],[]]