[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWP7FBQQ2H9R6RQJ6Y4353":3,"skill-same:01M6JWP7FBQQ2H9R6RQJ6Y4353":59},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6JWP7FBQQ2H9R6RQJ6Y4353","tokenchronicle-setup",null,"Initialize, diagnose, or open the local TokenChronicle Codex activity archive without importing any packaged user data.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHuaHuiJian\u002Ftokenchronicle-marketplace\u002Fskills\u002Ftokenchronicle-setup\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"setup","tokenchronicle setup","codex","diagnose","data","open","archive","initialize","user","local","activity","2026-11-10 10:12:30",false,"---\nname: tokenchronicle-setup\ndescription: Initialize, diagnose, or open the local TokenChronicle Codex activity archive without importing any packaged user data.\n---\n\n# TokenChronicle Setup\n\nResolve the plugin root first. If a signed bundled executable exists under\n`bin\u002F\u003Cplatform>\u002Ftokenchronicle\u002F`, use `tokenchronicle` on macOS or `tokenchronicle.exe` on Windows. Use the\nexact executable matching macOS arm64, macOS x86_64, or Windows x86_64; never execute a binary for a\ndifferent platform and never download a replacement. A public plugin release may support only a subset\nof platforms. If this installed plugin has no executable for the current platform, report that the\nplatform client has not been published and stop; do not download or substitute an unrelated launcher.\nFor an unpacked development bundle only,\nresolve the plugin root relative to this skill and use its bundled Python package. Use `python3` plus\n`PYTHONPATH` on macOS\u002FLinux and `py -3` plus PowerShell environment syntax on Windows. Never copy a\nUnix environment-assignment command unchanged into Windows.\n\n## Guided entry\n\nStart every setup request by running the read-only `readiness` command. Installation alone is never\nproof that TokenChronicle is initialized or protecting activity. Continue from the returned `state`\ninstead of restarting completed steps. Do not describe onboarding as complete while the state is\n`not_initialized`, `first_archive_required`, `schedule_choice_required`,\n`first_scheduled_run_pending`, `daily_protection_off`, or `attention_required`.\n\nTreat the Marketplace default prompt, \"initialize TokenChronicle\", \"set up TokenChronicle\", and their\nclear Chinese equivalents as requests to start the guided initialization flow. Before explicit privacy\nacceptance, only explain the product and run read-only commands such as `guide` and `preflight`; do not\ncreate directories, write configuration, start an archive, enable background work, or send network\nrequests.\n\nAfter presenting the available choices, summarize the selected Codex source, archive directory,\nlanguage, viewer port, and whether to run the first full archive. Ask the user to confirm that summary\nin natural language. Do not require a memorized or verbatim consent sentence. The confirmation must\nunambiguously accept the current privacy notice and the listed initialization choices. Consent to setup\nor the first archive never implies consent to scheduling, Codex Automation, feedback transmission,\ncloud backup, or historical migration.\n\n## Initialize\n\n1. Run `guide`, then explain that TokenChronicle privately preserves searchable Codex inputs, replies,\n   process evidence, and usage trends for review, audit, idea recovery, and future personal insights.\n2. Explain that no dedicated project or working directory is required. TokenChronicle reads the chosen\n   Codex home read-only and writes only to its separate user-owned application data directory.\n   Distinguish the installed plugin\u002Fruntime, operational application state, and durable archive library.\n   Use host-provided `PLUGIN_DATA` for plugin operational state when available.\n3. Run the read-only `preflight` command. Report Python support, Codex state availability, selected data\n   path, current archive size, free disk space, viewer port status, and every failing check.\n4. Give the user a real choice before setup:\n   - accept the operating-system defaults;\n   - choose a different Codex home with `--codex-home`;\n   - choose an exact durable archive library with `--archive-dir`;\n   - choose a different local port with `--port`.\n   - follow the system language with `--language auto`, or select Simplified Chinese with `zh-CN`\n     or English with `en`.\n   Do not ask the user to create these directories manually.\n   Explain that Documents is visible and portable but may be processed by iCloud, enterprise sync,\n   search indexing, or backup software. The default application-data location is less visible.\n   If the selected data directory is outside the current sandbox, show the exact path and request the\n   required filesystem approval. If the user declines, do not work around the decision; offer another\n   user-selected writable location and rerun `preflight`.\n5. Explain that all scheduling is disabled by default, so the default model-token use is `0\u002Fday`.\n   Recommend the bundled local OS scheduler after a successful manual archive; it runs deterministic\n   commands with zero model tokens and requires `--confirm-background-schedule`. If the user instead\n   asks to create a daily Codex Automation, disclose the planning estimate: `0.7M-2.0M`\n   total tokens per run, commonly `1.0M-1.5M`, or about `21M-60M` over 30 daily runs. State that\n   cached input is included, the estimate is not a billing quote, and first or broad scans can reach\n   approximately `1.5M-4.0M`.\n6. Explain that archives can grow to multiple GB and recommend at least 5 GB of free space before the\n   first archive. A low-space warning informs the user but does not silently delete data.\n7. Ask for explicit privacy acceptance before initialization. Ask separately before enabling the local\n   OS scheduler, creating Codex Automation, or enabling feedback transmission; one consent never implies another.\n8. After the user selects paths and accepts privacy, run `setup --accept-privacy` with the selected flags.\n   Do not enable optional features.\n9. Run `doctor` and `usage-notice`, report every failing check, then run the consented first-use\n   sequence: `archive`, `serve`, and optionally `memory-daily`. After the first archive passes, do not\n   end the guided task until the user makes one explicit choice:\n   - recommended: run `run-daily`, then explicitly consent to `schedule enable`; or\n   - run `schedule manual --confirm-manual-only` after the user accepts that no automatic daily archive\n     will occur.\n   Keep any legacy Codex Automation active until the new schedule has a verified run, then avoid\n   running both schedulers long term.\n   Treat an unavailable viewer port as either an already-running viewer or a conflict; check before\n   recommending a different port.\n10. Finish by running `readiness`. `operational` means verified automatic daily protection.\n    `manual_only` means onboarding is complete but automatic daily protection is off. Report this\n    distinction prominently. Any other state means onboarding is incomplete and its `next_action`\n    must be handled or clearly reported as blocked.\n11. Explain that the Web language can be switched at any time. Translate only product UI and guidance;\n    preserve user inputs, session titles, Codex responses, process evidence, and archived files verbatim.\n\n## Safety boundaries\n\n- Do not copy packaged sample conversations because the plugin contains none.\n- Do not modify Codex hooks, configuration, memories, or automation state.\n- Do not enable network feedback or synchronization without explicit consent.\n- Keep all generated data in the configured TokenChronicle application data directory.\n","# TokenChronicle Setup\n\nResolve the plugin root first. If a signed bundled executable exists under\n`bin\u002F\u003Cplatform>\u002Ftokenchronicle\u002F`, use `tokenchronicle` on macOS or `tokenchronicle.exe` on Windows. Use the\nexact executable matching macOS arm64, macOS x86_64, or Windows x86_64; never execute a binary for a\ndifferent platform and never download a replacement. A public plugin release may support only a subset\nof platforms. If this installed plugin has no executable for the current platform, report that the\nplatform client has not been published and stop; do not download or substitute an unrelated launcher.\nFor an unpacked development bundle only,\nresolve the plugin root relative to this skill and use its bundled Python package. Use `python3` plus\n`PYTHONPATH` on macOS\u002FLinux and `py -3` plus PowerShell environment syntax on Windows. Never copy a\nUnix environment-assignment command unchanged into Windows.\n\n## Guided entry\n\nStart every setup request by running the read-only `readiness` command. Installation alone is never\nproof that TokenChronicle is initialized or protecting activity. Continue from the returned `state`\ninstead of restarting completed steps. Do not describe onboarding as complete while the state is\n`not_initialized`, `first_archive_required`, `schedule_choice_required`,\n`first_scheduled_run_pending`, `daily_protection_off`, or `attention_required`.\n\nTreat the Marketplace default prompt, \"initialize TokenChronicle\", \"set up TokenChronicle\", and their\nclear Chinese equivalents as requests to start the guided initialization flow. Before explicit privacy\nacceptance, only explain the product and run read-only commands such as `guide` and `preflight`; do not\ncreate directories, write configuration, start an archive, enable background work, or send network\nrequests.\n\nAfter presenting the available choices, summarize the selected Codex source, archive directory,\nlanguage, viewer port, and whether to run the first full archive. Ask the user to confirm that summary\nin natural language. Do not require a memorized or verbatim consent sentence. The confirmation must\nunambiguously accept the current privacy notice and the listed initialization choices. Consent to setup\nor the first archive never implies consent to scheduling, Codex Automation, feedback transmission,\ncloud backup, or historical migration.\n\n## Initialize\n\n1. Run `guide`, then explain that TokenChronicle privately preserves searchable Codex inputs, replies,\n   process evidence, and usage trends for review, audit, idea recovery, and future personal insights.\n2. Explain that no dedicated project or working directory is required. TokenChronicle reads the chosen\n   Codex home read-only and writes only to its separate user-owned application data directory.\n   Distinguish the installed plugin\u002Fruntime, operational application state, and durable archive library.\n   Use host-provided `PLUGIN_DATA` for plugin operational state when available.\n3. Run the read-only `preflight` command. Report Python support, Codex state availability, selected data\n   path, current archive size, free disk space, viewer port status, and every failing check.\n4. Give the user a real choice before setup:\n   - accept the operating-system defaults;\n   - choose a different Codex home with `--codex-home`;\n   - choose an exact durable archive library with `--archive-dir`;\n   - choose a different local port with `--port`.\n   - follow the system language with `--language auto`, or select Simplified Chinese with `zh-CN`\n     or English with `en`.\n   Do not ask the user to create these directories manually.\n   Explain that Documents is visible and portable but may be processed by iCloud, enterprise sync,\n   search indexing, or backup software. The default application-data location is less visible.\n   If the selected data directory is outside the current sandbox, show the exact path and request the\n   required filesystem approval. If the user declines, do not work around the decision; offer another\n   user-selected writable location and rerun `preflight`.\n5. Explain that all scheduling is disabled by default, so the default model-token use is `0\u002Fday`.\n   Recommend the bundled local OS scheduler after a successful manual archive; it runs deterministic\n   commands with zero model tokens and requires `--confirm-background-schedule`. If the user instead\n   asks to create a daily Codex Automation, disclose the planning estimate: `0.7M-2.0M`\n   total tokens per run, commonly `1.0M-1.5M`, or about `21M-60M` over 30 daily runs. State that\n   cached input is included, the estimate is not a billing quote, and first or broad scans can reach\n   approximately `1.5M-4.0M`.\n6. Explain that archives can grow to multiple GB and recommend at least 5 GB of free space before the\n   first archive. A low-space warning informs the user but does not silently delete data.\n7. Ask for explicit privacy acceptance before initialization. Ask separately before enabling the local\n   OS scheduler, creating Codex Automation, or enabling feedback transmission; one consent never implies another.\n8. After the user selects paths and accepts privacy, run `setup --accept-privacy` with the selected flags.\n   Do not enable optional features.\n9. Run `doctor` and `usage-notice`, report every failing check, then run the consented first-use\n   sequence: `archive`, `serve`, and optionally `memory-daily`. After the first archive passes, do not\n   end the guided task until the user makes one explicit choice:\n   - recommended: run `run-daily`, then explicitly consent to `schedule enable`; or\n   - run `schedule manual --confirm-manual-only` after the user accepts that no automatic daily archive\n     will occur.\n   Keep any legacy Codex Automation active until the new schedule has a verified run, then avoid\n   running both schedulers long term.\n   Treat an unavailable viewer port as either an already-running viewer or a conflict; check before\n   recommending a different port.\n10. Finish by running `readiness`. `operational` means verified automatic daily protection.\n    `manual_only` means onboarding is complete but automatic daily protection is off. Report this\n    distinction prominently. Any other state means onboarding is incomplete and its `next_action`\n    must be handled or clearly reported as blocked.\n11. Explain that the Web language can be switched at any time. Translate only product UI and guidance;\n    preserve user inputs, session titles, Codex responses, process evidence, and archived files verbatim.\n\n## Safety boundaries\n\n- Do not copy packaged sample conversations because the plugin contains none.\n- Do not modify Codex hooks, configuration, memories, or automation state.\n- Do not enable network feedback or synchronization without explicit consent.\n- Keep all generated data in the configured TokenChronicle application data directory.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHuaHuiJian\u002Ftokenchronicle-marketplace\u002Fskills\u002Ftokenchronicle-setup",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill tokenchronicle-setup",{"tool":51,"command":52},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill tokenchronicle-setup",{"tool":54,"command":55},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill tokenchronicle-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHuaHuiJian\u002Ftokenchronicle-marketplace\u002Fskills\u002Ftokenchronicle-setup\u002FSKILL.md",true,[],[60,70,78,86,94,102],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":69},"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.","MIT","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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":69},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":69},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":69},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":69},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":69},"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",[],[]]