[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKKCR2FF1RVM7YWG9VZEXK":3,"skill-same:01M6MKKCR2FF1RVM7YWG9VZEXK":63},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":62},"01M6MKKCR2FF1RVM7YWG9VZEXK","setup",null,"Scaffold .nightshift\u002F and propose quality gates for this stack in at most four questions, with every default on one screen; asks, never imposes.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Forwa-mahmoud\u002Fnightshift\u002Fskills\u002Fsetup\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32],"never","for","true","gates","quality gates","stack","quality","nightshift","scaffold","default","with","screen","questions","at","2026-11-10 10:12:30",false,"---\nname: setup\ndescription: Scaffold .nightshift\u002F and propose quality gates for this stack in at most four questions, with every default on one screen; asks, never imposes.\nlicense: MIT\nmetadata:\n  internal: true\n---\n\nSet up Nightshift in this project in at most four questions. Scaffold first, then ask the\nquestions in section 3, apply every answer in the same turn, then print a summary that ends with\nthe one sentence that starts a shift.\n\nThe four state files and what each holds are in\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fshift\u002Fstate-map.md`. Ordinary plans belong in the drafting table, never in Hunt or the parking lot.\n\nResolve `$NIGHTSHIFT_PLUGIN_ROOT` to the copy this host installed, as an absolute path.\nOn Claude Code that is `${CLAUDE_PLUGIN_ROOT}`, on Cursor `${CURSOR_PLUGIN_ROOT}`, and on\nCodex `$PLUGIN_ROOT` when set. A skill loaded from a copy another host installed is the\nwrong runtime — use the copy under this host's plugins directory. When none of those is\nset, use the absolute path this skill was attached from (`skills\u002Fsetup\u002FSKILL.md`). Run every command below through\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\"` — native Windows: `& \"$NIGHTSHIFT_PLUGIN_ROOT\\runtime\\windows\\ns.ps1\"`\nin the PowerShell tool, same verbs — which resolves the host and the workspace; `ns help` lists the\nverbs, and `ns bind` prints the six resolved facts (`TASK_ROOT`, `NIGHTSHIFT_WORKSPACE`, `NS`,\n`NIGHTSHIFT_PLUGIN_ROOT`, `HOST`, `SOURCE`); `$NS` below is that `NS`. Never a bare relative path: the working\ndirectory persists between calls. Each `$NS\u002F...` path below is where the current layout keeps that file;\n`ns path \u003Ckey>` prints where this workspace keeps it, and `ns path --list` names every key.\n\nOnce the workspace and work target are resolved, the bundled mechanical scaffold is\n`ns setup --work-target \"$WORK_TARGET\" --mode \"$WORK_MODE\"`, which exists on native Windows only;\non every other host this skill writes the same templates itself, as below.\nIt copies only absent files, writes state version 2 for a new site, persists the work target and\nwork mode (`-Mode repository` or `-Mode artifact`), and keeps `$NS\u002F` private. It refuses a notes\nfolder under default repository mode: `use -Mode artifact for a notes folder that is not a Git repository`.\nOn an existing site at an older state-version its `migration` field describes the move into the\ncurrent layout, exactly as the preview below would. Read its output back rather than restating it.\nThe skill still owns every owner choice below; the\nscript asks nothing and never invents gates, permissions, profiles, migration approval, a receipts\nchoice, or a tooling policy.\n\nIf the user explicitly identifies a different existing workspace containing `.nightshift\u002F`, show\nboth absolute paths and ask for confirmation. On yes, run\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" link-workspace --host-root \"$TASK_ROOT\" --workspace \"$PROPOSED_WORKSPACE\"`.\nThe pointer is local-only and state remains in the authoritative workspace; never copy it.\n\n## 0. Reject disposable ChatGPT scratch workspaces\n\nBefore creating or changing any file, resolve the project root to an absolute path. If it is under\n`\u002Fworkspace\u002Fscratch\u002F`, this is a disposable ChatGPT scratch workspace that cannot affect the user's\nrepository. **Stop immediately: create no `$NS\u002F` directory, rules, settings, receipts repo,\nor other files.** Tell the user directly:\n\n> Nightshift needs a persistent software project workspace. This ChatGPT conversation is using a\n> temporary workspace, so files created here will not affect your repository.\n>\n> Open your project in Codex (a Git repository or a persistent local folder), or start Codex connected to its GitHub repository. Then mention\n> Nightshift and say: “Set up Nightshift in this project.”\n\nDo not mention Claude Code in this ChatGPT-specific redirect: the user is already in an OpenAI\nproduct, so give them the shortest OpenAI-native route. Do not infer “temporary” merely because the\nproject is not a git repository — local non-git projects and the recommended parent-workspace\nlayout remain valid. The explicit disposable scratch path is the stop signal.\n\nDetect the work mode and the work target. When the choice is ambiguous (several child repositories,\nor a folder that could be either mode), explain it and ask before persisting it; that is section\n3's first question. An obvious single repository is not asked: it is stated in the summary. Use\n`ns_propose_work_mode` (POSIX) or `Get-NSProposedWorkMode` after importing\n`Nightshift.psm1` (native Windows):\n\n- `repository` — the workspace is a Git repository, or exactly one immediate non-hidden child is. Skip a symlink or reparse child; it is not a nested checkout.\n  several child repositories still mean repository mode; show the choices and require an explicit\n  target, never guess.\n- `artifact` — there is no Git repository here. The persistent folder itself is the work target\n  (research, docs, audits, planning). Say so plainly: gates, commits, and stack detection that\n  require Git do not apply; complete each item with a receipt under `$NS\u002Freceipts\u002F`.\n  Completion in that folder is `$NS\u002Freceipts\u002F`, not a git log.\n  When `$NS\u002Freceipts` exists but is not a usable directory, say so and do not treat artifact setup as complete.\n- scratch (`ns_propose_work_mode` status 2, or `Get-NSProposedWorkMode` throwing) — stop; create\n  nothing.\n\nNever persist an ambiguous mode until the owner confirms. Never `git init` a notes folder to change an artifact proposal into repository mode. Then write `$NS\u002Frun\u002Fwork-mode` as `repository` or\n`artifact` (one word, one newline) and `$NS\u002Frun\u002Fwork-target` as the absolute canonical path of the\nchosen folder. On POSIX: `ns_record_work_target \"$NIGHTSHIFT_WORKSPACE\" \"$WORK_TARGET\" \"$WORK_MODE\"`.\nOn later setup runs, validate and retain that mode and target unless the owner explicitly changes\nthem. Repository mode: stack detection, Git checks, gates, commits, and verification operate in\nthe work target. Artifact mode: inspection, edits, and verification operate in that folder without\npretending it is a repository.\n\n## 1. Scaffold `$NS\u002F` (never clobber an existing shift)\n\n```bash\n\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" scaffold\n```\n\nIt writes the files every shift uses that are not already there (the punch list, the parking lot,\nthe snag log, the drafting table and the shift log) and reports `wrote \u003Cpath>` or `kept \u003Cpath>`, so\na name the owner already has is left exactly as it is and a second run is a safe repair. Read its\noutput back. The work orders and the product notebook wait until something needs them: Hunt runs\n`ns scaffold work-orders` when it stages an order, and cutting a product-evolution item runs\n`ns scaffold product`. The copies carry resolved absolute paths — a person pasting a command out of\ntheir own punch list has no `$NS` — and the shipped templates are unchanged. Never write those\ntokens into `rules.json`: revival and clock-out text stay owner-editable, and the gate qualifies\nbare `.nightshift\u002F` mentions at injection time.\n\n**State version.** `$NS\u002Fstate-version` is the schema marker, and it names the layout: this plugin\nwrites version `2`, which groups `$NS\u002F` by purpose. The scaffold writes it into a `$NS\u002F` it creates.\nA site at version `1`, or with no marker (legacy `0`), keeps every state file at the top of `$NS\u002F`\nand goes on working there; offer the move as a line on section 3's defaults screen, with\n\n```bash\n\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" migrate-state\n```\n\nwhich only previews: each file with its old and new path, every link it rewrites, every conflict,\nand what it leaves in place. Show that preview, and run it again with `--apply`\nonly after an explicit yes. It refuses while a shift is armed, a watchman is alive or a lock is\nheld, and it never deletes or overwrites. Never move a state file by hand. A marker newer than `2`, or a malformed\nfile, fails closed: print the diagnostic, do not rewrite or downgrade it, and do not continue\nscaffolding as if the site were current.\n\n## 2. Private by default\n\nKeep run state out of git. If `$NIGHTSHIFT_WORKSPACE` is itself a git repo, append a line\n`.nightshift\u002F` to `$NIGHTSHIFT_WORKSPACE\u002F.gitignore` (create the file if needed; do not duplicate\nthe line). If it is not one — the recommended layout, where the code repo sits a level below —\n`.nightshift\u002F` is already outside every repo, so write no `.gitignore` there. Run history is the\nowner's; it never enters the project repo.\n\nCopy `$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fnightshift-rules-template.json` to\n`$NS\u002Frules.json` as-is if it does not already exist, so section 3 shows real values (section 5\ncovers the file).\n\n## 3. The questions — at most four\n\nAsk these in this order and nothing else. Skip any whose answer is already clear. Never split one\ninto several turns.\n\n1. **Work target** — only when it is ambiguous, as above.\n2. **Gates** — the detected proposal, answered with accept, edit or none (below).\n3. **Defaults** — every remaining choice on one screen (below), answered once.\n4. **Copy-in files** — only when the owner chose a shift worktree: which ignored files the tests\n   need, such as `.env.test`. List only those in `shift.copyIn`; never propose `.env` itself.\n\nA rerun asks the same questions with the owner's current values in place of the defaults, and\nchanges only what the owner names.\n\n### Gates\n\nDetect the stack in the persisted work target from\n`ns catalog-index --catalog gates` and\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fcompose\u002Fgates-catalog.md`\n(monorepo-aware). Read only the stacks whose Detect matches, in the order the index prints them.\nAn owner's stack of the same key replaces the shipped one; say where each proposal came from.\nA plugin or marketplace manifest may sit at the work-target\nroot or one directory down at `plugins\u002F\u003Cname>\u002F.claude-plugin\u002F` \u002F\n`plugins\u002F\u003Cname>\u002F.codex-plugin\u002F`; that nested layout is a match when no\nlanguage-stack row already won. Show the detected proposal with three first-class answers:\n\n- **accept** the proposal as-is,\n- **edit** it — add, remove, or replace with THEIR own commands (any shell command is a valid gate),\n- **none** — fully respected: the shift runs without automated checks.\n\nArtifact mode has no stack to detect: skip this question.\n\n### Defaults\n\nOne list, each line with its value and one line of meaning. The owner answers **accept all**, or\nnames what to change in the same reply (\"worktree yes, 6 hours, deny sudo\"). Apply the changes in\nthat turn; do not ask a second round.\n\n| Line | Shipped value | Meaning |\n| --- | --- | --- |\n| Receipts repo | no | a local-only git repo inside `$NS\u002F`, so every punch-list change has history; never pushed, never touches the project's history |\n| Shift worktree | no | each shift works in its own git worktree and branch, so the owner's checkout and uncommitted edits stay untouched; show the proposed `shift.prepare` command beside it |\n| Site inspection | hourly | the heavier batch (coverage, dead code, Sonar) every N items or H hours; only when gates were accepted or edited |\n| Verification profile | `fast` | `fast`, `balanced`, `strict`, or `custom`: when the `## Gates` commands run |\n| Typical hours | none | the hours a composed shift gets when the owner names none |\n| Execution | `run-direct` | a composed shift starts at once; `review-first` shows it for approval first |\n| Tooling policy | `auto-add` | `auto-add` adds standard development tools the project selects; `review-missing` or `existing-tools` hold back |\n| Recovery | `host-default` | a stalled or finished worker is revived and clocked out under the host's own permissions; `inherit-recorded-scope` restores a recorded Codex sandbox only |\n| Elevation | all allowed | `sudo`, containers, global packages, daemons, external logins; name any to deny |\n| Evidence | check `off`, review `off` | whether a missing evidence file blocks a tick, what happens when it cannot be produced, and whether the agent reviews its own evidence |\n\nThe proposed `shift.prepare` command comes from the work target's lockfile and installs its\ndependencies without changing it (`pnpm-lock.yaml` → `pnpm install --frozen-lockfile`,\n`package-lock.json` → `npm ci`, `yarn.lock` → `yarn install --immutable`, `uv.lock` → `uv sync`,\n`poetry.lock` → `poetry install`, `Gemfile.lock` → `bundle install`, `Cargo.lock` → nothing).\n\nPresent the receipts repo neutrally: never describe the repo as recommended; the default is no.\n\n**Artifact mode** shows only the lines valid there: receipts repo, typical hours, execution,\nrecovery and evidence. It persists `fast` and existing-tools without showing them: a notes folder\nhas no repository toolchain to add, and repository-tool policies (`auto-add` and\n`review-missing`) are invalid there.\n\n**What this version also offers goes on the same screen**, one line each, never a separate question:\n\n- a state move, when `$NS\u002Fstate-version` is older than `2` (section 1): the\n  `ns migrate-state` preview, applied only after an explicit yes;\n- keys this version added to the rules template that the owner's file lacks (section 5);\n- a contract restore, when the owner's punch-list contract differs from the shipped one (section 5);\n- the shipped rule profiles, any one of which may replace the screen's values (section 5).\n\n## 4. Applying the answers\n\n- **Receipts repo** — on yes: if `$NS\u002F.git` does not exist, run `git -C \"$NS\" init` rather than\n `cd`-ing there. The run state is then versioned in its own local-only git repo.\n Ensure `$NS\u002F.gitignore` contains `STOP` and `\u002Frun\u002F`, the runtime's own folder, anchored so each\n archive folder's `run\u002F` records stay versioned; rewrite a bare `run\u002F` line as `\u002Frun\u002F` and\n preserve the other lines. A site still at version `1` keeps the runtime's files at the top of `$NS\u002F`, so there it\n names the transient markers instead: `STOP`, `.stall`, `.notified`, `deadline`, `.session-end`,\n `.shift-pulse`, `.mint-failed`, `.shift-session`, `.shift-session.tmp.*`, `.shift-worker`,\n `.shift-lease`, `.shift-lease.tmp.*`, `.mutex-scope`, `.mutex-scope.tmp.*`, `.watchman`,\n `.watchman-tick`, `.budget.tsv`, `.item-sessions\u002F`, `.plan-room`, `.lock.d\u002F`, and `.lease-lock.d\u002F`; migrate-state adds `\u002Frun\u002F` with the move. Make one initial commit only when setup created the receipts repository.\n Creating the repo does **not** turn on headless auto-commit — that is `receiptsAutoCommit`\n in `rules.json`, shipped `false`; the owner commits the receipts tree when they want.\n **Never add a remote to it, never push it.**\n On native Windows, rerun the bundled scaffold with the same\n `--work-target` plus `--receipts`; the idempotent pass creates only this local receipts repo.\n- **Shift worktree** — on yes set `shift.isolation` to `worktree`, `shift.prepare` to the proposed\n command (or the owner's), and `shift.copyIn` to question 4's answer, in `$NS\u002Frules.json`.\n- **Gates** — write the accepted or edited commands and the site-inspection interval into the\n `## Gates` block of `$NS\u002Fpunch-list.md`, replacing the placeholder. On none, leave the placeholder\n as-is. The block is plain markdown the owner may edit anytime; run Setup again\n (`\u002Fnightshift:setup` on Claude Code, or ask Nightshift to set up on Codex) to re-detect after a\n stack change. The contract's immutability binds the agent, not the owner.\n- **Verification profile, hours, execution, tooling** — persist with\n `\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" shift-policy defaults-set --verificationProfile \u003Cname> --hours \u003Cn|null> --toolingPolicy \u003Cname> --execution review-first|run-direct`.\n The helper writes the `shift` block of `$NS\u002Frules.json` — the one file the owner edits — and\n reports what it stored; never put the answer in the punch list. It only prefills what Hunt and\n Quality compose with; either skill may change it for a single shift.\n- **Recovery, elevation, evidence** — write only the keys the owner changed\n (`recovery.launchScope`, `elevation.\u003Ccategory>.policy`, `receipts.evidence.check`,\n `receipts.evidence.unavailable`, `receipts.evidence.review`) into `$NS\u002Frules.json`, keeping every\n other value byte for byte.\n- **State move, template keys, contract, profile** — apply each only on the owner's explicit yes,\n as section 1 and section 5 describe.\n\n## 5. Permissions — configured by the owner\n\nAn unattended shift cannot answer permission prompts. Say once that the owner configures\npermissions directly in the host before starting unattended work; this is a statement, not a\nquestion. Never write permission modes,\nallowlists, or approval settings, and never enable permission bypass on the owner's behalf.\nNightshift adds no restriction of its own beyond what the host permits unless the owner sets one.\n\nRecovery uses `recovery.launchScope` in `$NS\u002Frules.json`. The shipped `host-default` adds no\npermission arguments and uses the owner's independently configured host permissions; it does not\npromise the same scope as the original session. `inherit-recorded-scope` restores a recorded\nrestricted Codex sandbox when supported; missing or unsupported scopes refuse recovery. The legacy\n`host-grant` value is refused. Never change the active session's permissions. If the owner keeps\ninteractive approvals, say that a prompt or denial can leave unattended work needing their\nattention.\n\n## 6. The rules file — every knob in one place\n\n`$NS\u002Frules.json` is the owner's one config file, defaults inline. It lives in nightshift's own\nfolder on purpose: everything nightshift is in one place, kept out of repo history by the same\n`.nightshift\u002F` gitignore, versioned by the receipts repo when one exists — and deleting `$NS\u002F`\nremoves all of nightshift, rules included. Validate the file with\n`jq -e 'type == \"object\"'` and report a broken one plainly — never half-apply it. On native\nWindows, validate with `Get-Content -Raw -LiteralPath \"$NS\\rules.json\" | ConvertFrom-Json`;\nPowerShell's JSON parser is built in, so native setup has no `jq` or Python prerequisite.\n\nThe template's `$schema` field points at\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fnightshift-rules.schema.json` so editors\ncatch invalid names, types, and values; it is ignored at runtime. Editor discovery is documented\nin https:\u002F\u002Fgithub.com\u002Forwa-mahmoud\u002Fnightshift\u002Fblob\u002Fmain\u002Fdocs\u002Fknobs.md.\n\nThe rules file is portable across hosts, so never generate a host-specific copy. Its `toolDeny`\nmap carries three native question names: `AskUserQuestion` for Claude Code, `request_user_input`\nfor Codex, and `AskQuestion` for Cursor. A non-empty value denies that exact tool with the owner's\nmessage; an empty value allows it. All three entries stay present so deleting a key can never\nactivate an invisible default. JSON has no comments; the schema descriptions and\nhttps:\u002F\u002Fgithub.com\u002Forwa-mahmoud\u002Fnightshift\u002Fblob\u002Fmain\u002Fdocs\u002Fknobs.md#tool-rules are the inline help.\n\nThe hooks read this file directly on every tool call: an owner's edit applies from their very next\naction. Nothing is synced anywhere, nothing needs a restart, and there is no second copy. Env vars\nof the matching names (`NIGHTSHIFT_FORBIDDEN_COMMANDS`, `NIGHTSHIFT_TOOL_RULES`, …) remain\nsession-start overrides for tests and one-off exceptions — say so only if asked. If Claude Code's\n`$TASK_ROOT\u002F.claude\u002Fsettings.local.json` still carries `NIGHTSHIFT_*` env keys an earlier version\nsynced from this file, offer to remove them on the defaults screen: the file is the one copy.\n\n**Local rule profiles.** The defaults screen may list the shipped examples in\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fprofiles\u002F` (every version-1 or version-2 JSON\nfile there). Preview the one the owner names with\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" apply-profile --profile \u003Cname> --mode fill|replace`.\nThe helper prints the preview and the complete next file; read it out rather than describing it.\nApplying requires an explicit yes and `--apply`. Refuse `--apply` while armed. Profiles are a one-time local copy — no network, no\nsubscription. After applying a profile,\nwrite a preset receipt from\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Freceipts\u002Fcycle-specialist-evidence.md` so branch mode,\nallowed sources, verification profile, receipt retention, resource limits, and direct-mode\nboundaries trace to `rules.json`. Owner rules remain authoritative;\npresets never capture hidden policy.\n\n**Template evolution — offer, never impose.** On a re-run with the file already present, compare\nthe shipped template's top-level keys and its nested `toolDeny` keys to the owner's file (read the\nJSON in the skill; do not ask the owner to install `jq` or Python; on native Windows,\n`(Get-Content -Raw -LiteralPath \"$NS\\rules.json\" | ConvertFrom-Json).PSObject.Properties.Name`\nand the same for `.toolDeny`). List each missing key with its default on the defaults screen —\n\"this version added `request_user_input`; add it?\" — and never\ntouch a value the owner already has. A missing native question key is a configuration error, not\npermission to invent a fallback.\n\nSame posture for the contract: if the shipped punch-list template's contract (the text above\n`## Items`) has changed since the owner's copy was scaffolded, or the owner's contract is\nleftover campaign text (a finished branch, release, or issue-close list), put one line on the defaults\nscreen that shows the diff and offers to restore the template contract. The owner's\nwording wins every conflict, and a punch list with open boxes is never touched at all.\nNever rewrite without an explicit yes.\n\n## 7. Summarize\n\nPrint the workspace-state path and resolved work target, what was scaffolded, whether a receipts\nrepo was created, the gates that were written (or that none were), and the defaults now in\n`$NS\u002Frules.json`. End with the one sentence that starts a shift, for example: say *\"improve this\nproject for 5 hours\"*. Hunt composes it from the catalog and starts. Hand-written work goes in\n`$NS\u002Fstaging\u002Fdrafting-table.md`, is promoted into the punch list, and starts with\n`\u002Fnightshift:start` on Claude Code, or by asking Nightshift to start on Codex. Name\n`\u002Fnightshift:customize` for every other setting; editing `$NS\u002Frules.json` by hand or asking in\nplain words works the same. The open-ended product-evolution shift keeps its evidence and ranked\nwork in `$NS\u002Fproduct\u002Fproduct-research.md` and `$NS\u002Fproduct\u002Fopportunity-map.md`, written the first\ntime such an item is cut.\n","Set up Nightshift in this project in at most four questions. Scaffold first, then ask the\nquestions in section 3, apply every answer in the same turn, then print a summary that ends with\nthe one sentence that starts a shift.\n\nThe four state files and what each holds are in\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fshift\u002Fstate-map.md`. Ordinary plans belong in the drafting table, never in Hunt or the parking lot.\n\nResolve `$NIGHTSHIFT_PLUGIN_ROOT` to the copy this host installed, as an absolute path.\nOn Claude Code that is `${CLAUDE_PLUGIN_ROOT}`, on Cursor `${CURSOR_PLUGIN_ROOT}`, and on\nCodex `$PLUGIN_ROOT` when set. A skill loaded from a copy another host installed is the\nwrong runtime — use the copy under this host's plugins directory. When none of those is\nset, use the absolute path this skill was attached from (`skills\u002Fsetup\u002FSKILL.md`). Run every command below through\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\"` — native Windows: `& \"$NIGHTSHIFT_PLUGIN_ROOT\\runtime\\windows\\ns.ps1\"`\nin the PowerShell tool, same verbs — which resolves the host and the workspace; `ns help` lists the\nverbs, and `ns bind` prints the six resolved facts (`TASK_ROOT`, `NIGHTSHIFT_WORKSPACE`, `NS`,\n`NIGHTSHIFT_PLUGIN_ROOT`, `HOST`, `SOURCE`); `$NS` below is that `NS`. Never a bare relative path: the working\ndirectory persists between calls. Each `$NS\u002F...` path below is where the current layout keeps that file;\n`ns path \u003Ckey>` prints where this workspace keeps it, and `ns path --list` names every key.\n\nOnce the workspace and work target are resolved, the bundled mechanical scaffold is\n`ns setup --work-target \"$WORK_TARGET\" --mode \"$WORK_MODE\"`, which exists on native Windows only;\non every other host this skill writes the same templates itself, as below.\nIt copies only absent files, writes state version 2 for a new site, persists the work target and\nwork mode (`-Mode repository` or `-Mode artifact`), and keeps `$NS\u002F` private. It refuses a notes\nfolder under default repository mode: `use -Mode artifact for a notes folder that is not a Git repository`.\nOn an existing site at an older state-version its `migration` field describes the move into the\ncurrent layout, exactly as the preview below would. Read its output back rather than restating it.\nThe skill still owns every owner choice below; the\nscript asks nothing and never invents gates, permissions, profiles, migration approval, a receipts\nchoice, or a tooling policy.\n\nIf the user explicitly identifies a different existing workspace containing `.nightshift\u002F`, show\nboth absolute paths and ask for confirmation. On yes, run\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" link-workspace --host-root \"$TASK_ROOT\" --workspace \"$PROPOSED_WORKSPACE\"`.\nThe pointer is local-only and state remains in the authoritative workspace; never copy it.\n\n## 0. Reject disposable ChatGPT scratch workspaces\n\nBefore creating or changing any file, resolve the project root to an absolute path. If it is under\n`\u002Fworkspace\u002Fscratch\u002F`, this is a disposable ChatGPT scratch workspace that cannot affect the user's\nrepository. **Stop immediately: create no `$NS\u002F` directory, rules, settings, receipts repo,\nor other files.** Tell the user directly:\n\n> Nightshift needs a persistent software project workspace. This ChatGPT conversation is using a\n> temporary workspace, so files created here will not affect your repository.\n>\n> Open your project in Codex (a Git repository or a persistent local folder), or start Codex connected to its GitHub repository. Then mention\n> Nightshift and say: “Set up Nightshift in this project.”\n\nDo not mention Claude Code in this ChatGPT-specific redirect: the user is already in an OpenAI\nproduct, so give them the shortest OpenAI-native route. Do not infer “temporary” merely because the\nproject is not a git repository — local non-git projects and the recommended parent-workspace\nlayout remain valid. The explicit disposable scratch path is the stop signal.\n\nDetect the work mode and the work target. When the choice is ambiguous (several child repositories,\nor a folder that could be either mode), explain it and ask before persisting it; that is section\n3's first question. An obvious single repository is not asked: it is stated in the summary. Use\n`ns_propose_work_mode` (POSIX) or `Get-NSProposedWorkMode` after importing\n`Nightshift.psm1` (native Windows):\n\n- `repository` — the workspace is a Git repository, or exactly one immediate non-hidden child is. Skip a symlink or reparse child; it is not a nested checkout.\n  several child repositories still mean repository mode; show the choices and require an explicit\n  target, never guess.\n- `artifact` — there is no Git repository here. The persistent folder itself is the work target\n  (research, docs, audits, planning). Say so plainly: gates, commits, and stack detection that\n  require Git do not apply; complete each item with a receipt under `$NS\u002Freceipts\u002F`.\n  Completion in that folder is `$NS\u002Freceipts\u002F`, not a git log.\n  When `$NS\u002Freceipts` exists but is not a usable directory, say so and do not treat artifact setup as complete.\n- scratch (`ns_propose_work_mode` status 2, or `Get-NSProposedWorkMode` throwing) — stop; create\n  nothing.\n\nNever persist an ambiguous mode until the owner confirms. Never `git init` a notes folder to change an artifact proposal into repository mode. Then write `$NS\u002Frun\u002Fwork-mode` as `repository` or\n`artifact` (one word, one newline) and `$NS\u002Frun\u002Fwork-target` as the absolute canonical path of the\nchosen folder. On POSIX: `ns_record_work_target \"$NIGHTSHIFT_WORKSPACE\" \"$WORK_TARGET\" \"$WORK_MODE\"`.\nOn later setup runs, validate and retain that mode and target unless the owner explicitly changes\nthem. Repository mode: stack detection, Git checks, gates, commits, and verification operate in\nthe work target. Artifact mode: inspection, edits, and verification operate in that folder without\npretending it is a repository.\n\n## 1. Scaffold `$NS\u002F` (never clobber an existing shift)\n\n```bash\n\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" scaffold\n```\n\nIt writes the files every shift uses that are not already there (the punch list, the parking lot,\nthe snag log, the drafting table and the shift log) and reports `wrote \u003Cpath>` or `kept \u003Cpath>`, so\na name the owner already has is left exactly as it is and a second run is a safe repair. Read its\noutput back. The work orders and the product notebook wait until something needs them: Hunt runs\n`ns scaffold work-orders` when it stages an order, and cutting a product-evolution item runs\n`ns scaffold product`. The copies carry resolved absolute paths — a person pasting a command out of\ntheir own punch list has no `$NS` — and the shipped templates are unchanged. Never write those\ntokens into `rules.json`: revival and clock-out text stay owner-editable, and the gate qualifies\nbare `.nightshift\u002F` mentions at injection time.\n\n**State version.** `$NS\u002Fstate-version` is the schema marker, and it names the layout: this plugin\nwrites version `2`, which groups `$NS\u002F` by purpose. The scaffold writes it into a `$NS\u002F` it creates.\nA site at version `1`, or with no marker (legacy `0`), keeps every state file at the top of `$NS\u002F`\nand goes on working there; offer the move as a line on section 3's defaults screen, with\n\n```bash\n\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" migrate-state\n```\n\nwhich only previews: each file with its old and new path, every link it rewrites, every conflict,\nand what it leaves in place. Show that preview, and run it again with `--apply`\nonly after an explicit yes. It refuses while a shift is armed, a watchman is alive or a lock is\nheld, and it never deletes or overwrites. Never move a state file by hand. A marker newer than `2`, or a malformed\nfile, fails closed: print the diagnostic, do not rewrite or downgrade it, and do not continue\nscaffolding as if the site were current.\n\n## 2. Private by default\n\nKeep run state out of git. If `$NIGHTSHIFT_WORKSPACE` is itself a git repo, append a line\n`.nightshift\u002F` to `$NIGHTSHIFT_WORKSPACE\u002F.gitignore` (create the file if needed; do not duplicate\nthe line). If it is not one — the recommended layout, where the code repo sits a level below —\n`.nightshift\u002F` is already outside every repo, so write no `.gitignore` there. Run history is the\nowner's; it never enters the project repo.\n\nCopy `$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fnightshift-rules-template.json` to\n`$NS\u002Frules.json` as-is if it does not already exist, so section 3 shows real values (section 5\ncovers the file).\n\n## 3. The questions — at most four\n\nAsk these in this order and nothing else. Skip any whose answer is already clear. Never split one\ninto several turns.\n\n1. **Work target** — only when it is ambiguous, as above.\n2. **Gates** — the detected proposal, answered with accept, edit or none (below).\n3. **Defaults** — every remaining choice on one screen (below), answered once.\n4. **Copy-in files** — only when the owner chose a shift worktree: which ignored files the tests\n   need, such as `.env.test`. List only those in `shift.copyIn`; never propose `.env` itself.\n\nA rerun asks the same questions with the owner's current values in place of the defaults, and\nchanges only what the owner names.\n\n### Gates\n\nDetect the stack in the persisted work target from\n`ns catalog-index --catalog gates` and\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fcompose\u002Fgates-catalog.md`\n(monorepo-aware). Read only the stacks whose Detect matches, in the order the index prints them.\nAn owner's stack of the same key replaces the shipped one; say where each proposal came from.\nA plugin or marketplace manifest may sit at the work-target\nroot or one directory down at `plugins\u002F\u003Cname>\u002F.claude-plugin\u002F` \u002F\n`plugins\u002F\u003Cname>\u002F.codex-plugin\u002F`; that nested layout is a match when no\nlanguage-stack row already won. Show the detected proposal with three first-class answers:\n\n- **accept** the proposal as-is,\n- **edit** it — add, remove, or replace with THEIR own commands (any shell command is a valid gate),\n- **none** — fully respected: the shift runs without automated checks.\n\nArtifact mode has no stack to detect: skip this question.\n\n### Defaults\n\nOne list, each line with its value and one line of meaning. The owner answers **accept all**, or\nnames what to change in the same reply (\"worktree yes, 6 hours, deny sudo\"). Apply the changes in\nthat turn; do not ask a second round.\n\n| Line | Shipped value | Meaning |\n| --- | --- | --- |\n| Receipts repo | no | a local-only git repo inside `$NS\u002F`, so every punch-list change has history; never pushed, never touches the project's history |\n| Shift worktree | no | each shift works in its own git worktree and branch, so the owner's checkout and uncommitted edits stay untouched; show the proposed `shift.prepare` command beside it |\n| Site inspection | hourly | the heavier batch (coverage, dead code, Sonar) every N items or H hours; only when gates were accepted or edited |\n| Verification profile | `fast` | `fast`, `balanced`, `strict`, or `custom`: when the `## Gates` commands run |\n| Typical hours | none | the hours a composed shift gets when the owner names none |\n| Execution | `run-direct` | a composed shift starts at once; `review-first` shows it for approval first |\n| Tooling policy | `auto-add` | `auto-add` adds standard development tools the project selects; `review-missing` or `existing-tools` hold back |\n| Recovery | `host-default` | a stalled or finished worker is revived and clocked out under the host's own permissions; `inherit-recorded-scope` restores a recorded Codex sandbox only |\n| Elevation | all allowed | `sudo`, containers, global packages, daemons, external logins; name any to deny |\n| Evidence | check `off`, review `off` | whether a missing evidence file blocks a tick, what happens when it cannot be produced, and whether the agent reviews its own evidence |\n\nThe proposed `shift.prepare` command comes from the work target's lockfile and installs its\ndependencies without changing it (`pnpm-lock.yaml` → `pnpm install --frozen-lockfile`,\n`package-lock.json` → `npm ci`, `yarn.lock` → `yarn install --immutable`, `uv.lock` → `uv sync`,\n`poetry.lock` → `poetry install`, `Gemfile.lock` → `bundle install`, `Cargo.lock` → nothing).\n\nPresent the receipts repo neutrally: never describe the repo as recommended; the default is no.\n\n**Artifact mode** shows only the lines valid there: receipts repo, typical hours, execution,\nrecovery and evidence. It persists `fast` and existing-tools without showing them: a notes folder\nhas no repository toolchain to add, and repository-tool policies (`auto-add` and\n`review-missing`) are invalid there.\n\n**What this version also offers goes on the same screen**, one line each, never a separate question:\n\n- a state move, when `$NS\u002Fstate-version` is older than `2` (section 1): the\n  `ns migrate-state` preview, applied only after an explicit yes;\n- keys this version added to the rules template that the owner's file lacks (section 5);\n- a contract restore, when the owner's punch-list contract differs from the shipped one (section 5);\n- the shipped rule profiles, any one of which may replace the screen's values (section 5).\n\n## 4. Applying the answers\n\n- **Receipts repo** — on yes: if `$NS\u002F.git` does not exist, run `git -C \"$NS\" init` rather than\n `cd`-ing there. The run state is then versioned in its own local-only git repo.\n Ensure `$NS\u002F.gitignore` contains `STOP` and `\u002Frun\u002F`, the runtime's own folder, anchored so each\n archive folder's `run\u002F` records stay versioned; rewrite a bare `run\u002F` line as `\u002Frun\u002F` and\n preserve the other lines. A site still at version `1` keeps the runtime's files at the top of `$NS\u002F`, so there it\n names the transient markers instead: `STOP`, `.stall`, `.notified`, `deadline`, `.session-end`,\n `.shift-pulse`, `.mint-failed`, `.shift-session`, `.shift-session.tmp.*`, `.shift-worker`,\n `.shift-lease`, `.shift-lease.tmp.*`, `.mutex-scope`, `.mutex-scope.tmp.*`, `.watchman`,\n `.watchman-tick`, `.budget.tsv`, `.item-sessions\u002F`, `.plan-room`, `.lock.d\u002F`, and `.lease-lock.d\u002F`; migrate-state adds `\u002Frun\u002F` with the move. Make one initial commit only when setup created the receipts repository.\n Creating the repo does **not** turn on headless auto-commit — that is `receiptsAutoCommit`\n in `rules.json`, shipped `false`; the owner commits the receipts tree when they want.\n **Never add a remote to it, never push it.**\n On native Windows, rerun the bundled scaffold with the same\n `--work-target` plus `--receipts`; the idempotent pass creates only this local receipts repo.\n- **Shift worktree** — on yes set `shift.isolation` to `worktree`, `shift.prepare` to the proposed\n command (or the owner's), and `shift.copyIn` to question 4's answer, in `$NS\u002Frules.json`.\n- **Gates** — write the accepted or edited commands and the site-inspection interval into the\n `## Gates` block of `$NS\u002Fpunch-list.md`, replacing the placeholder. On none, leave the placeholder\n as-is. The block is plain markdown the owner may edit anytime; run Setup again\n (`\u002Fnightshift:setup` on Claude Code, or ask Nightshift to set up on Codex) to re-detect after a\n stack change. The contract's immutability binds the agent, not the owner.\n- **Verification profile, hours, execution, tooling** — persist with\n `\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" shift-policy defaults-set --verificationProfile \u003Cname> --hours \u003Cn|null> --toolingPolicy \u003Cname> --execution review-first|run-direct`.\n The helper writes the `shift` block of `$NS\u002Frules.json` — the one file the owner edits — and\n reports what it stored; never put the answer in the punch list. It only prefills what Hunt and\n Quality compose with; either skill may change it for a single shift.\n- **Recovery, elevation, evidence** — write only the keys the owner changed\n (`recovery.launchScope`, `elevation.\u003Ccategory>.policy`, `receipts.evidence.check`,\n `receipts.evidence.unavailable`, `receipts.evidence.review`) into `$NS\u002Frules.json`, keeping every\n other value byte for byte.\n- **State move, template keys, contract, profile** — apply each only on the owner's explicit yes,\n as section 1 and section 5 describe.\n\n## 5. Permissions — configured by the owner\n\nAn unattended shift cannot answer permission prompts. Say once that the owner configures\npermissions directly in the host before starting unattended work; this is a statement, not a\nquestion. Never write permission modes,\nallowlists, or approval settings, and never enable permission bypass on the owner's behalf.\nNightshift adds no restriction of its own beyond what the host permits unless the owner sets one.\n\nRecovery uses `recovery.launchScope` in `$NS\u002Frules.json`. The shipped `host-default` adds no\npermission arguments and uses the owner's independently configured host permissions; it does not\npromise the same scope as the original session. `inherit-recorded-scope` restores a recorded\nrestricted Codex sandbox when supported; missing or unsupported scopes refuse recovery. The legacy\n`host-grant` value is refused. Never change the active session's permissions. If the owner keeps\ninteractive approvals, say that a prompt or denial can leave unattended work needing their\nattention.\n\n## 6. The rules file — every knob in one place\n\n`$NS\u002Frules.json` is the owner's one config file, defaults inline. It lives in nightshift's own\nfolder on purpose: everything nightshift is in one place, kept out of repo history by the same\n`.nightshift\u002F` gitignore, versioned by the receipts repo when one exists — and deleting `$NS\u002F`\nremoves all of nightshift, rules included. Validate the file with\n`jq -e 'type == \"object\"'` and report a broken one plainly — never half-apply it. On native\nWindows, validate with `Get-Content -Raw -LiteralPath \"$NS\\rules.json\" | ConvertFrom-Json`;\nPowerShell's JSON parser is built in, so native setup has no `jq` or Python prerequisite.\n\nThe template's `$schema` field points at\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fnightshift-rules.schema.json` so editors\ncatch invalid names, types, and values; it is ignored at runtime. Editor discovery is documented\nin https:\u002F\u002Fgithub.com\u002Forwa-mahmoud\u002Fnightshift\u002Fblob\u002Fmain\u002Fdocs\u002Fknobs.md.\n\nThe rules file is portable across hosts, so never generate a host-specific copy. Its `toolDeny`\nmap carries three native question names: `AskUserQuestion` for Claude Code, `request_user_input`\nfor Codex, and `AskQuestion` for Cursor. A non-empty value denies that exact tool with the owner's\nmessage; an empty value allows it. All three entries stay present so deleting a key can never\nactivate an invisible default. JSON has no comments; the schema descriptions and\nhttps:\u002F\u002Fgithub.com\u002Forwa-mahmoud\u002Fnightshift\u002Fblob\u002Fmain\u002Fdocs\u002Fknobs.md#tool-rules are the inline help.\n\nThe hooks read this file directly on every tool call: an owner's edit applies from their very next\naction. Nothing is synced anywhere, nothing needs a restart, and there is no second copy. Env vars\nof the matching names (`NIGHTSHIFT_FORBIDDEN_COMMANDS`, `NIGHTSHIFT_TOOL_RULES`, …) remain\nsession-start overrides for tests and one-off exceptions — say so only if asked. If Claude Code's\n`$TASK_ROOT\u002F.claude\u002Fsettings.local.json` still carries `NIGHTSHIFT_*` env keys an earlier version\nsynced from this file, offer to remove them on the defaults screen: the file is the one copy.\n\n**Local rule profiles.** The defaults screen may list the shipped examples in\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Fprofiles\u002F` (every version-1 or version-2 JSON\nfile there). Preview the one the owner names with\n`\"$NIGHTSHIFT_PLUGIN_ROOT\u002Fruntime\u002Fns\" apply-profile --profile \u003Cname> --mode fill|replace`.\nThe helper prints the preview and the complete next file; read it out rather than describing it.\nApplying requires an explicit yes and `--apply`. Refuse `--apply` while armed. Profiles are a one-time local copy — no network, no\nsubscription. After applying a profile,\nwrite a preset receipt from\n`$NIGHTSHIFT_PLUGIN_ROOT\u002Fskills\u002Fnightshift\u002Freferences\u002Freceipts\u002Fcycle-specialist-evidence.md` so branch mode,\nallowed sources, verification profile, receipt retention, resource limits, and direct-mode\nboundaries trace to `rules.json`. Owner rules remain authoritative;\npresets never capture hidden policy.\n\n**Template evolution — offer, never impose.** On a re-run with the file already present, compare\nthe shipped template's top-level keys and its nested `toolDeny` keys to the owner's file (read the\nJSON in the skill; do not ask the owner to install `jq` or Python; on native Windows,\n`(Get-Content -Raw -LiteralPath \"$NS\\rules.json\" | ConvertFrom-Json).PSObject.Properties.Name`\nand the same for `.toolDeny`). List each missing key with its default on the defaults screen —\n\"this version added `request_user_input`; add it?\" — and never\ntouch a value the owner already has. A missing native question key is a configuration error, not\npermission to invent a fallback.\n\nSame posture for the contract: if the shipped punch-list template's contract (the text above\n`## Items`) has changed since the owner's copy was scaffolded, or the owner's contract is\nleftover campaign text (a finished branch, release, or issue-close list), put one line on the defaults\nscreen that shows the diff and offers to restore the template contract. The owner's\nwording wins every conflict, and a punch list with open boxes is never touched at all.\nNever rewrite without an explicit yes.\n\n## 7. Summarize\n\nPrint the workspace-state path and resolved work target, what was scaffolded, whether a receipts\nrepo was created, the gates that were written (or that none were), and the defaults now in\n`$NS\u002Frules.json`. End with the one sentence that starts a shift, for example: say *\"improve this\nproject for 5 hours\"*. Hunt composes it from the catalog and starts. Hand-written work goes in\n`$NS\u002Fstaging\u002Fdrafting-table.md`, is promoted into the punch list, and starts with\n`\u002Fnightshift:start` on Claude Code, or by asking Nightshift to start on Codex. Name\n`\u002Fnightshift:customize` for every other setting; editing `$NS\u002Frules.json` by hand or asking in\nplain words works the same. The open-ended product-evolution shift keeps its evidence and ranked\nwork in `$NS\u002Fproduct\u002Fproduct-research.md` and `$NS\u002Fproduct\u002Fopportunity-map.md`, written the first\ntime such an item is cut.\n",{"name":5,"license":15,"metadata":38,"description":7},{"internal":39},true,"main","f620abaff09061f8c8b1f1559dca3fdd031a32e5","plugins\u002Forwa-mahmoud\u002Fnightshift\u002Fskills\u002Fsetup",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":39},[52,55,58],{"tool":53,"command":54},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill setup",{"tool":56,"command":57},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill setup",{"tool":59,"command":60},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Forwa-mahmoud\u002Fnightshift\u002Fskills\u002Fsetup\u002FSKILL.md",[],[64,73,81,89,97,105],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"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":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":72},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":72},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":72},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":72},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":72},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]