[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M713HPB4GG89MG4WC0H0FSQH":3,"skill-same:01M713HPB4GG89MG4WC0H0FSQH":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M713HPB4GG89MG4WC0H0FSQH","manuwright",null,"Medical manuscript workflow with the ManuWright engine. Use when planning, drafting, revising or checking a paper in a folder that has project.json, drafts\u002Fdraft_plan.md or knowledge\u002Fevidence.md, or when the user mentions ManuWright, draft plan, analysis plan, evidence.md, EVID citations, reviewer response or submission build.","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\u002Fgrotyx\u002FAcademic_writing_c_claudecode\u002Fskills\u002Fmanuwright\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"draft","drafting","when","submission","drafts","manuscript","with","medical","project","workflow","evidence","use","reviewer","engine","plan","knowledge","analysis","Citations","planning","2026-11-10 10:12:30",false,"---\nname: manuwright\ndescription: Medical manuscript workflow with the ManuWright engine. Use when planning, drafting, revising or checking a paper in a folder that has project.json, drafts\u002Fdraft_plan.md or knowledge\u002Fevidence.md, or when the user mentions ManuWright, draft plan, analysis plan, evidence.md, EVID citations, reviewer response or submission build.\n---\n\n# ManuWright workflow\n\n1. Load the rules for the current step: `manuwright rules \u003Ckeyword>` (for example `Citation Integrity`, `Draft Plan`, `Verification Gates`, `Phase 4`). Run `manuwright rules` once for the full workflow when the phase is unclear.\n2. Phase order: setup and evidence, then analysis plan (approved), analysis, draft plan (approved), drafting (Methods, Results, Introduction, Discussion, Conclusion, Abstract, Title), style polish, QC (3+ rounds), finalize, revision.\n3. Plan first. If `drafts\u002Fdraft_plan.md` or `data\u002Fanalysis_plan.md` is missing, incomplete or not approved by the author, stop and help complete it. Show the plan to the author. When they approve it explicitly in chat (\"승인\", \"approve\"), record it with `manuwright approve \u003Cplan> --kind analysis|draft --approved-by \"\u003Cauthor>\" --quote \"\u003Ctheir exact words>\"` (ticks the box, notes who\u002Fwhen\u002Fwhat, writes the hashed receipt). Never approve on your own judgement or from a general \"continue\".\n4. Grounding. Cite only `[EVID:id]` keys in `knowledge\u002Fevidence.md` and use only numbers in `results\u002F*.csv`. Register new sources in `evidence.md` (verified PMID\u002FDOI) before citing them: `manuwright search \"\u003Cquery>\"`.\n5. Analysis code runs in the paper's own environment: `manuwright env` (once; uv-managed Python with the packages in `data\u002Frequirements.txt`), then `manuwright run data\u002Fpy\u002F\u003Cscript>.py`. Do not install packages into, or debug, the system\u002FHomebrew\u002Fpyenv Python; add packages to `data\u002Frequirements.txt` and rerun `manuwright env`. Cite the versions in `data\u002Fenvironment.lock.txt` in Methods.\n6. Verify before saying a step is done (see the `manuwright-verify` skill).\n7. Academic writing: before drafting or rewriting a section, run `manuwright style card \u003Csection>` and write to that card (moves, rules, phrasebank, register of the model paragraphs, the author's learned corpus style). Never reuse the model paragraphs' facts, numbers or citations. Fix the academic-prose findings reported after each edit; in `strict` mode a write with high-severity findings is blocked until rewritten. After a style rewrite of existing text, `manuwright style preserve \u003Cbefore> \u003Cafter>` must print OK.\n8. Evidence and revision safeguards: record `Claim Strength` for each evidence.md entry and run `manuwright claim-strength drafts`; `manuwright search audit` (metadata match, retractions) before submission; letter-blind re-review (`manuwright blind-review packet` \u002F `check`) before recording response_alignment; `manuwright style edits` proposes rules from the author's edits, which only the author approves. When the author asks in chat, run the tool for them: \"내 문체 배워줘\" \u002F \"learn my style\" -> `manuwright style learn \u003Cfolder>` (3+ papers); \"내가 고친 거 배워줘\" -> `manuwright style edits --git \u003Crev>` (or two files), show the proposals, and after they approve a rule in chat run `manuwright style edits --approve \"\u003Crule>\" --approved-by \"\u003Cauthor>\" --quote \"\u003Ctheir words>\" --apply`; \"과장 표현 검사해줘\" -> `manuwright claim-strength drafts`; \"참고문헌 다시 확인해줘\" -> `manuwright search audit`; \"블라인드 재검토\" -> `manuwright blind-review packet ...`.\n9. Guides live in the engine, not in the paper folder: read any `docs\u002F\u003Cname>.md` the rules cite with `manuwright guide \u003Cname>` (several at once allowed; `manuwright guide` lists them). Every `manuwright rules` output ends with the guides it cites; read the ones for the current step in full before doing it.\n\n## Journal fit and suggestions\n\n\"Does it fit Spine J?\" \u002F \"which journal?\": build a PubMed query from the population, intervention and outcome, then `manuwright journal fit \"\u003CNLM abbreviation>\" --query \"...\"` or `manuwright journal suggest --query \"...\" [--review]`. With no journal profile, create one (`manuwright journal profile \"\u003Cjournal>\" --url \u003Cofficial page>`), read the official Aims & Scope \u002F Guide for Authors yourself and fill it; mark it verified only after the author confirms. Never state an impact factor, acceptance rate or policy that is not in the profile (docs\u002Fcritical_review_protocol.md section 6).\n\n## Personal library (reused across papers)\n\n`manuwright library` shows where it is (`~\u002F.manuwright\u002Flibrary\u002F`, or `$MANUWRIGHT_HOME\u002Flibrary`). New papers get copies from it at `manuwright init`; Word styles are chosen per paper in `manuwright target`.\n\n**\"Register my writing style\"** (the author added papers with `manuwright library writing add \u003Cpdf|md> --kind own|landmark|target_journal`):\n1. Read the engine's `Style\u002Fstyle_guide.md` (folder next to `manuwright rules --path`) and follow its Extraction Framework and copyright policy: patterns, metrics and short phrases, never copied paragraphs.\n2. For each source in `library\u002Fwriting\u002FPDF\u002F\u003Ckind>\u002F` without a matching `library\u002Fwriting\u002F\u003Ckind>\u002F\u003Csame basename>.md`, write that markdown anchor.\n3. Measure instead of guessing: run `manuwright style learn` (it reads the library PDFs, or pass files) so every section card carries the measured style and model paragraphs, and `manuwright style extract \u003Ctext or md files>` for sentence length and citation density in the anchors.\n4. Update `library\u002Fwriting\u002Fterminology.md` (preferred and forbidden terms with context) and write `library\u002Fwriting\u002Fstyle_spec.md` from the engine's `docs\u002Fstyle_spec_template.md` (`manuwright guide style_spec_template`), bound to the author's own papers.\n5. Show the author a short summary of the voice you found and the files you wrote; do not change any paper folder.\n\n**\"Fill my team profile\"** (from a CV, author list or earlier title page the author gives you): edit `library\u002Fprofile\u002Fauthors.md` (`manuwright library profile` creates it from the template). Copy names, degrees, affiliations, ORCID, emails and grant numbers exactly as given; leave `[...]` placeholders for anything not given; never guess an ORCID or grant number. Ask the author to check it. Papers created later copy it to `profile\u002Fauthors.md`; an existing paper keeps its own copy.\n\n**Keep what the author teaches across papers (memory).** When the author asks you to remember something (\"기억해\", \"앞으로는 X 대신 Y\", \"공동저자 추가해줘\", \"소속이 바뀌었어\", \"remember\", \"from now on\"), save it in the personal library, additions only, and say in one line what you saved where:\n- a wording rule: `manuwright library term --prefer \"X\" --avoid \"Y\" [--context \"...\"]` (library and this paper; a CONFLICT means the library already prefers another word: ask);\n- one author, affiliation, ORCID, email or grant: edit only that person's lines in `library\u002Fprofile\u002Fauthors.md` and in this paper's `profile\u002Fauthors.md` if it exists; show the changed lines first; never delete other people or guess numbers;\n- any other lesson (journal requirements, reviewer preferences, method choices): `manuwright library note \"\u003Cone sentence>\" --topic journal|reviewer|writing|method|other`; notes appear at every session start in paper folders.\n\"라이브러리 최신으로 받아줘\" = `manuwright library sync --pull`; \"이 논문 것을 라이브러리에 올려줘\" = `manuwright library sync --push`; \"차이 보여줘\" = `manuwright library sync`. Sync only adds; a \"differs\" line (style spec, team profile) is merged by you on request, line by line, with the author's confirmation. Rules the author approves with `style edits --apply` go to the library automatically, and a session in a paper folder pulls the library's additions automatically (`manuwright config set library-sync auto|ask|off`).\n","# ManuWright workflow\n\n1. Load the rules for the current step: `manuwright rules \u003Ckeyword>` (for example `Citation Integrity`, `Draft Plan`, `Verification Gates`, `Phase 4`). Run `manuwright rules` once for the full workflow when the phase is unclear.\n2. Phase order: setup and evidence, then analysis plan (approved), analysis, draft plan (approved), drafting (Methods, Results, Introduction, Discussion, Conclusion, Abstract, Title), style polish, QC (3+ rounds), finalize, revision.\n3. Plan first. If `drafts\u002Fdraft_plan.md` or `data\u002Fanalysis_plan.md` is missing, incomplete or not approved by the author, stop and help complete it. Show the plan to the author. When they approve it explicitly in chat (\"승인\", \"approve\"), record it with `manuwright approve \u003Cplan> --kind analysis|draft --approved-by \"\u003Cauthor>\" --quote \"\u003Ctheir exact words>\"` (ticks the box, notes who\u002Fwhen\u002Fwhat, writes the hashed receipt). Never approve on your own judgement or from a general \"continue\".\n4. Grounding. Cite only `[EVID:id]` keys in `knowledge\u002Fevidence.md` and use only numbers in `results\u002F*.csv`. Register new sources in `evidence.md` (verified PMID\u002FDOI) before citing them: `manuwright search \"\u003Cquery>\"`.\n5. Analysis code runs in the paper's own environment: `manuwright env` (once; uv-managed Python with the packages in `data\u002Frequirements.txt`), then `manuwright run data\u002Fpy\u002F\u003Cscript>.py`. Do not install packages into, or debug, the system\u002FHomebrew\u002Fpyenv Python; add packages to `data\u002Frequirements.txt` and rerun `manuwright env`. Cite the versions in `data\u002Fenvironment.lock.txt` in Methods.\n6. Verify before saying a step is done (see the `manuwright-verify` skill).\n7. Academic writing: before drafting or rewriting a section, run `manuwright style card \u003Csection>` and write to that card (moves, rules, phrasebank, register of the model paragraphs, the author's learned corpus style). Never reuse the model paragraphs' facts, numbers or citations. Fix the academic-prose findings reported after each edit; in `strict` mode a write with high-severity findings is blocked until rewritten. After a style rewrite of existing text, `manuwright style preserve \u003Cbefore> \u003Cafter>` must print OK.\n8. Evidence and revision safeguards: record `Claim Strength` for each evidence.md entry and run `manuwright claim-strength drafts`; `manuwright search audit` (metadata match, retractions) before submission; letter-blind re-review (`manuwright blind-review packet` \u002F `check`) before recording response_alignment; `manuwright style edits` proposes rules from the author's edits, which only the author approves. When the author asks in chat, run the tool for them: \"내 문체 배워줘\" \u002F \"learn my style\" -> `manuwright style learn \u003Cfolder>` (3+ papers); \"내가 고친 거 배워줘\" -> `manuwright style edits --git \u003Crev>` (or two files), show the proposals, and after they approve a rule in chat run `manuwright style edits --approve \"\u003Crule>\" --approved-by \"\u003Cauthor>\" --quote \"\u003Ctheir words>\" --apply`; \"과장 표현 검사해줘\" -> `manuwright claim-strength drafts`; \"참고문헌 다시 확인해줘\" -> `manuwright search audit`; \"블라인드 재검토\" -> `manuwright blind-review packet ...`.\n9. Guides live in the engine, not in the paper folder: read any `docs\u002F\u003Cname>.md` the rules cite with `manuwright guide \u003Cname>` (several at once allowed; `manuwright guide` lists them). Every `manuwright rules` output ends with the guides it cites; read the ones for the current step in full before doing it.\n\n## Journal fit and suggestions\n\n\"Does it fit Spine J?\" \u002F \"which journal?\": build a PubMed query from the population, intervention and outcome, then `manuwright journal fit \"\u003CNLM abbreviation>\" --query \"...\"` or `manuwright journal suggest --query \"...\" [--review]`. With no journal profile, create one (`manuwright journal profile \"\u003Cjournal>\" --url \u003Cofficial page>`), read the official Aims & Scope \u002F Guide for Authors yourself and fill it; mark it verified only after the author confirms. Never state an impact factor, acceptance rate or policy that is not in the profile (docs\u002Fcritical_review_protocol.md section 6).\n\n## Personal library (reused across papers)\n\n`manuwright library` shows where it is (`~\u002F.manuwright\u002Flibrary\u002F`, or `$MANUWRIGHT_HOME\u002Flibrary`). New papers get copies from it at `manuwright init`; Word styles are chosen per paper in `manuwright target`.\n\n**\"Register my writing style\"** (the author added papers with `manuwright library writing add \u003Cpdf|md> --kind own|landmark|target_journal`):\n1. Read the engine's `Style\u002Fstyle_guide.md` (folder next to `manuwright rules --path`) and follow its Extraction Framework and copyright policy: patterns, metrics and short phrases, never copied paragraphs.\n2. For each source in `library\u002Fwriting\u002FPDF\u002F\u003Ckind>\u002F` without a matching `library\u002Fwriting\u002F\u003Ckind>\u002F\u003Csame basename>.md`, write that markdown anchor.\n3. Measure instead of guessing: run `manuwright style learn` (it reads the library PDFs, or pass files) so every section card carries the measured style and model paragraphs, and `manuwright style extract \u003Ctext or md files>` for sentence length and citation density in the anchors.\n4. Update `library\u002Fwriting\u002Fterminology.md` (preferred and forbidden terms with context) and write `library\u002Fwriting\u002Fstyle_spec.md` from the engine's `docs\u002Fstyle_spec_template.md` (`manuwright guide style_spec_template`), bound to the author's own papers.\n5. Show the author a short summary of the voice you found and the files you wrote; do not change any paper folder.\n\n**\"Fill my team profile\"** (from a CV, author list or earlier title page the author gives you): edit `library\u002Fprofile\u002Fauthors.md` (`manuwright library profile` creates it from the template). Copy names, degrees, affiliations, ORCID, emails and grant numbers exactly as given; leave `[...]` placeholders for anything not given; never guess an ORCID or grant number. Ask the author to check it. Papers created later copy it to `profile\u002Fauthors.md`; an existing paper keeps its own copy.\n\n**Keep what the author teaches across papers (memory).** When the author asks you to remember something (\"기억해\", \"앞으로는 X 대신 Y\", \"공동저자 추가해줘\", \"소속이 바뀌었어\", \"remember\", \"from now on\"), save it in the personal library, additions only, and say in one line what you saved where:\n- a wording rule: `manuwright library term --prefer \"X\" --avoid \"Y\" [--context \"...\"]` (library and this paper; a CONFLICT means the library already prefers another word: ask);\n- one author, affiliation, ORCID, email or grant: edit only that person's lines in `library\u002Fprofile\u002Fauthors.md` and in this paper's `profile\u002Fauthors.md` if it exists; show the changed lines first; never delete other people or guess numbers;\n- any other lesson (journal requirements, reviewer preferences, method choices): `manuwright library note \"\u003Cone sentence>\" --topic journal|reviewer|writing|method|other`; notes appear at every session start in paper folders.\n\"라이브러리 최신으로 받아줘\" = `manuwright library sync --pull`; \"이 논문 것을 라이브러리에 올려줘\" = `manuwright library sync --push`; \"차이 보여줘\" = `manuwright library sync`. Sync only adds; a \"differs\" line (style spec, team profile) is merged by you on request, line by line, with the author's confirmation. Rules the author approves with `style edits --apply` go to the library automatically, and a session in a paper folder pulls the library's additions automatically (`manuwright config set library-sync auto|ask|off`).\n",{"name":5,"description":7},"main","f620abaff09061f8c8b1f1559dca3fdd031a32e5","plugins\u002Fgrotyx\u002FAcademic_writing_c_claudecode\u002Fskills\u002Fmanuwright",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill manuwright",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill manuwright",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill manuwright","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgrotyx\u002FAcademic_writing_c_claudecode\u002Fskills\u002Fmanuwright\u002FSKILL.md",true,[],[68,78,86,94,102,110],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":77},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":77},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":77},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":77},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":77},"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",[],[]]