[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBADE6FHNVVXB18VWJ99EF":3,"skill-same:01M6MBADE6FHNVVXB18VWJ99EF":172},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MBADE6FHNVVXB18VWJ99EF","treatment-plans",null,"Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.","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\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"plans","treatment plans","images","verified","Variables","clinical","shared","local","reconciliation","clinical documentation","files","documentation","only","decision","plan","healthcare","credentials","network","release","packages","2026-11-10 10:12:30",false,"---\nname: treatment-plans\ndescription: Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.\nlicense: MIT\ncompatibility: Python 3.11+ standard library; local JSON files only. Bundled CLIs require no network, external services, models, images, credentials, environment variables, or third-party packages.\nmetadata:\n  version: '2.2'\n  category: clinical-and-health\n  maintainer: Kalaris Labs\n  tags: treatment plans, clinical documentation, medicine, healthcare\n---\n\n# Treatment-Plan Documentation\n\n## Hard safety boundary\n\nThis skill only **formats and validates documentation of decisions already made, supplied, and verified by authorized licensed professionals**.\n\nNever use it to:\n\n- diagnose, assess, classify, or screen a person;\n- select, rank, recommend, substitute, or compare therapies;\n- choose a medication, dose, route, frequency, duration, or monitoring threshold;\n- start, stop, hold, resume, titrate, taper, or deprescribe anything;\n- check interactions, allergies, contraindications, organ-function suitability, or treatment eligibility;\n- infer missing clinical content, intervals, dates, targets, escalation criteria, or instructions;\n- triage, determine urgency, provide emergency advice, or create a safety plan;\n- predict outcomes, prognosis, response, benefit, harm, or clinical appropriateness;\n- replace medication reconciliation, pharmacist review, informed consent, clinician review, or an authorized clinical system;\n- claim FDA approval, HIPAA compliance, legal compliance, completeness of care, clinical safety, or standard-of-care conformity.\n\nIf a request crosses a boundary, stop. Ask for a locally verified clinician-authored record or route the matter to the responsible licensed professional. Do not redirect to another skill to obtain a patient-specific recommendation.\n\nIf a concern may be urgent or emergent, stop this workflow and route it through the institution's current clinical escalation or emergency process. This skill does not decide urgency and does not provide emergency instructions.\n\n## Required visible notice\n\nEvery component and derived schedule must display:\n\n> **DRAFT — NOT MEDICAL ADVICE — DOCUMENTATION-ONLY — AUTHORIZED CLINICIAN SIGN-OFF REQUIRED**\n\nStructural success never removes this notice. Only the authorized local workflow may set the release gate.\n\n## Data gate\n\nPrefer synthetic or qualified de-identified structured manifests. Do not place patient names, medical-record numbers, contact details, dates of birth, addresses, free-text notes, images, or other direct identifiers in examples.\n\nFor any real-patient or patient-derived data:\n\n1. Work only in a locally authorized environment under the institution's current privacy, security, retention, and access policies.\n2. Use the minimum information necessary for the documented purpose, even when a legal exception may apply.\n3. Do not send content to a model, search engine, API, image service, telemetry service, or any other external tool.\n4. Do not copy content into chat prompts, command history, logs, test fixtures, examples, screenshots, or reports.\n5. Run bundled scripts only against local paths. Their reports identify rule codes and field paths, not clinical values.\n6. Require qualified privacy review before treating patient-derived material as de-identified or releasing it.\n\nIf these conditions are not documented, do not read or process the content. Use synthetic templates only.\n\n## Allowed inputs\n\nAccept only bounded UTF-8 JSON objects built from these generic templates:\n\n- `assets\u002Fsource_fact_manifest_template.json`\n- `assets\u002Fclinician_authored_intervention_template.json`\n- `assets\u002Fgoals_monitoring_checkpoint_template.json`\n- `assets\u002Finformed_preference_shared_decision_template.json`\n- `assets\u002Ftransition_reconciliation_template.json`\n- `assets\u002Fintended_use_handoff_template.json`\n\nThe templates contain no disease-specific recommendations, example patients, clinical intervals, doses, targets, thresholds, or inferred care pathways. Empty template arrays and pending attestations are intentional release blockers.\n\n## Workflow\n\n### 1. Establish authority and intended use\n\n- Confirm the accountable clinical owner and authorized licensed signatory.\n- Confirm that every clinical decision already exists in a verified local source.\n- Record jurisdiction, institution, setting, document owner, local policies, retention rule, and intended recipients.\n- Record whether the package is synthetic, qualified de-identified, or real-patient minimum-necessary data.\n- Keep the release gate `blocked` until every required review is complete.\n\nRead `references\u002Fsafety_scope.md` and `references\u002Fprivacy_governance.md` before processing patient-derived material.\n\n### 2. Generate a generic package\n\n```bash\npython3 scripts\u002Fgenerate_template.py \\\n  --output-dir .\u002Flocal-plan-package \\\n  --subject-ref SYNTHETIC-CASE-001 \\\n  --classification synthetic\n```\n\nThe generator copies all six templates. It does not create clinical content and does not overwrite existing files.\n\n### 3. Transcribe supplied decisions without inference\n\n- Copy only clinician-authored facts and interventions from verified local sources.\n- Preserve source locators, versions\u002Fdates, author role, verification role, and verification time.\n- Record goals, monitoring items, checkpoint dates, and transition dates exactly as supplied.\n- Record options, benefits, harms, uncertainty, preferences, and the outcome only as documented by the responsible clinician.\n- Leave missing fields unresolved. Never fill them from general knowledge.\n- For medication content, record the clinician-authored text and current local source references; do not interpret or validate it.\n\nSee `references\u002Fdocumentation_workflow.md`, `references\u002Fsource_boundaries.md`, and `references\u002Fshared_decision_handoff.md`.\n\n### 4. Run deterministic local checks\n\nFrom the skill directory:\n\n```bash\npython3 scripts\u002Fvalidate_treatment_plan.py .\u002Flocal-plan-package\npython3 scripts\u002Fvalidate_traceability.py .\u002Flocal-plan-package\npython3 scripts\u002Fcheck_completeness.py .\u002Flocal-plan-package\npython3 scripts\u002Fprivacy_process_check.py .\u002Flocal-plan-package\npython3 scripts\u002Fcheck_consistency.py .\u002Flocal-plan-package\npython3 scripts\u002Ftimeline_generator.py .\u002Flocal-plan-package \\\n  --output .\u002Flocal-plan-package\u002Fexplicit-date-schedule.json\n```\n\nThe scripts:\n\n- reject non-local paths, symlinks, duplicate JSON keys, unknown fields, oversized inputs, excessive nesting, and unbounded collections;\n- never use network access, environment variables, dynamic execution, pickle, subprocesses, images, or LLMs;\n- never assess diagnosis, medication safety, interactions, contraindications, clinical appropriateness, urgency, prognosis, or guideline concordance;\n- schedule only dates already supplied in the package and never derive recurrence or clinical intervals;\n- minimize reports to counts, rule codes, document types, and field paths.\n\n### 5. Human review and release\n\nRequire the accountable authorized team to:\n\n- compare every transcribed item with its signed source;\n- perform medication reconciliation and all clinical checks in approved systems;\n- verify current FDA labeling, Medication Guide, REMS materials, and local formulary\u002Fpolicy when applicable;\n- resolve every discrepancy and missing item;\n- review shared-decision and informed-preference documentation;\n- review transition recipients, ownership, pending results, and local escalation routing;\n- complete privacy, security, legal, regulatory, records, and institutional review as applicable;\n- sign, date, and release through the authorized record system.\n\nThe final handoff must retain provenance and unresolved-item routing. A script pass is not authorization to use the package for care.\n\n## Source boundaries\n\n- Use FDA labeling databases, current Medication Guides, and REMS materials as authoritative source records only when an authorized clinician or pharmacist verifies applicability. This skill does not interpret them.\n- Use WHO or Joint Commission transition guidance only for process structure such as information transfer, reconciliation documentation, ownership, and checklists.\n- Use AHRQ, NICE, or applicable professional guidance to document that shared decision-making occurred; do not generate options or risk estimates.\n- Apply CMS documentation requirements only when the exact program, provider type, jurisdiction, and current local policy are confirmed.\n- Route safety events, product reports, privacy incidents, and other reportable matters through current local governance. This skill records a route; it does not submit reports.\n\nSee `references\u002Fsource_ledger.md` for the dated official-source ledger.\n\n## Verification\n\n```bash\nPYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover \\\n  -s tests\u002Ftreatment-plans -p 'test_*.py' -v\n```\n\nRun AST parsing without bytecode:\n\n```bash\nPYTHONDONTWRITEBYTECODE=1 python3 -c \\\n  \"import ast,pathlib; [ast.parse(p.read_text()) for p in pathlib.Path('scripts').glob('*.py')]\"\n```\n\n## Reference map\n\n- `references\u002FREADME.md` — scope and navigation\n- `references\u002Fsafety_scope.md` — refusal, routing, and release boundaries\n- `references\u002Fprivacy_governance.md` — local handling and de-identification limits\n- `references\u002Fdocumentation_workflow.md` — package lifecycle and review gates\n- `references\u002Fsource_boundaries.md` — FDA labeling, REMS, and governance boundaries\n- `references\u002Fshared_decision_handoff.md` — informed preferences, reconciliation, and transitions\n- `references\u002Fsource_ledger.md` — dated authoritative sources\n- `references\u002Fsecurity_validation.md` — baseline findings and validation record\n\n## Agent operating procedure\n\n1. **Check the environment.** Confirm data access permissions, de-identification status and the governing regulations or protocols.\n2. **Pin down the inputs.** Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.\n3. **Run a small version first.** Work on a de-identified sample or synthetic data first.\n4. **Execute the full task** using the instructions and references above.\n5. **Validate the result.** Check outputs against clinical guidelines and reporting standards; have a qualified human review clinical content.\n6. **Report.** State what was run (versions, commands, parameters), what was checked, and what is still uncertain.\n\n| If this happens | Do this |\n|---|---|\n| Data appears to contain identifiable patient information | Stop and ask the user before processing further. |\n| A function, flag or endpoint in these instructions is missing in the installed version | Check the installed version's own documentation (`help()`, `--help`, official docs), adapt, and tell the user. Never invent an API. |\n| A required input, identifier or parameter is ambiguous | Ask the user, or state the assumption explicitly before running. |\n\n**Integrity rules**\n\n- Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.\n- Outputs are decision support for qualified professionals, not medical advice; never present them as diagnoses or orders.\n- Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.\n- Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.\n\n## Related skills\n\n- `clinical-decision-support`: Prepare and validate research-only clinical decision-support evaluation, evidence-profile, cohort, survival, biomarker\u002Fmodel, privacy, and…\n- `ara-research-manager`: Records research provenance at the end of a coding or research session by scanning the conversation and writing decisions, experiments, dea…\n","# Treatment-Plan Documentation\n\n## Hard safety boundary\n\nThis skill only **formats and validates documentation of decisions already made, supplied, and verified by authorized licensed professionals**.\n\nNever use it to:\n\n- diagnose, assess, classify, or screen a person;\n- select, rank, recommend, substitute, or compare therapies;\n- choose a medication, dose, route, frequency, duration, or monitoring threshold;\n- start, stop, hold, resume, titrate, taper, or deprescribe anything;\n- check interactions, allergies, contraindications, organ-function suitability, or treatment eligibility;\n- infer missing clinical content, intervals, dates, targets, escalation criteria, or instructions;\n- triage, determine urgency, provide emergency advice, or create a safety plan;\n- predict outcomes, prognosis, response, benefit, harm, or clinical appropriateness;\n- replace medication reconciliation, pharmacist review, informed consent, clinician review, or an authorized clinical system;\n- claim FDA approval, HIPAA compliance, legal compliance, completeness of care, clinical safety, or standard-of-care conformity.\n\nIf a request crosses a boundary, stop. Ask for a locally verified clinician-authored record or route the matter to the responsible licensed professional. Do not redirect to another skill to obtain a patient-specific recommendation.\n\nIf a concern may be urgent or emergent, stop this workflow and route it through the institution's current clinical escalation or emergency process. This skill does not decide urgency and does not provide emergency instructions.\n\n## Required visible notice\n\nEvery component and derived schedule must display:\n\n> **DRAFT — NOT MEDICAL ADVICE — DOCUMENTATION-ONLY — AUTHORIZED CLINICIAN SIGN-OFF REQUIRED**\n\nStructural success never removes this notice. Only the authorized local workflow may set the release gate.\n\n## Data gate\n\nPrefer synthetic or qualified de-identified structured manifests. Do not place patient names, medical-record numbers, contact details, dates of birth, addresses, free-text notes, images, or other direct identifiers in examples.\n\nFor any real-patient or patient-derived data:\n\n1. Work only in a locally authorized environment under the institution's current privacy, security, retention, and access policies.\n2. Use the minimum information necessary for the documented purpose, even when a legal exception may apply.\n3. Do not send content to a model, search engine, API, image service, telemetry service, or any other external tool.\n4. Do not copy content into chat prompts, command history, logs, test fixtures, examples, screenshots, or reports.\n5. Run bundled scripts only against local paths. Their reports identify rule codes and field paths, not clinical values.\n6. Require qualified privacy review before treating patient-derived material as de-identified or releasing it.\n\nIf these conditions are not documented, do not read or process the content. Use synthetic templates only.\n\n## Allowed inputs\n\nAccept only bounded UTF-8 JSON objects built from these generic templates:\n\n- `assets\u002Fsource_fact_manifest_template.json`\n- `assets\u002Fclinician_authored_intervention_template.json`\n- `assets\u002Fgoals_monitoring_checkpoint_template.json`\n- `assets\u002Finformed_preference_shared_decision_template.json`\n- `assets\u002Ftransition_reconciliation_template.json`\n- `assets\u002Fintended_use_handoff_template.json`\n\nThe templates contain no disease-specific recommendations, example patients, clinical intervals, doses, targets, thresholds, or inferred care pathways. Empty template arrays and pending attestations are intentional release blockers.\n\n## Workflow\n\n### 1. Establish authority and intended use\n\n- Confirm the accountable clinical owner and authorized licensed signatory.\n- Confirm that every clinical decision already exists in a verified local source.\n- Record jurisdiction, institution, setting, document owner, local policies, retention rule, and intended recipients.\n- Record whether the package is synthetic, qualified de-identified, or real-patient minimum-necessary data.\n- Keep the release gate `blocked` until every required review is complete.\n\nRead `references\u002Fsafety_scope.md` and `references\u002Fprivacy_governance.md` before processing patient-derived material.\n\n### 2. Generate a generic package\n\n```bash\npython3 scripts\u002Fgenerate_template.py \\\n  --output-dir .\u002Flocal-plan-package \\\n  --subject-ref SYNTHETIC-CASE-001 \\\n  --classification synthetic\n```\n\nThe generator copies all six templates. It does not create clinical content and does not overwrite existing files.\n\n### 3. Transcribe supplied decisions without inference\n\n- Copy only clinician-authored facts and interventions from verified local sources.\n- Preserve source locators, versions\u002Fdates, author role, verification role, and verification time.\n- Record goals, monitoring items, checkpoint dates, and transition dates exactly as supplied.\n- Record options, benefits, harms, uncertainty, preferences, and the outcome only as documented by the responsible clinician.\n- Leave missing fields unresolved. Never fill them from general knowledge.\n- For medication content, record the clinician-authored text and current local source references; do not interpret or validate it.\n\nSee `references\u002Fdocumentation_workflow.md`, `references\u002Fsource_boundaries.md`, and `references\u002Fshared_decision_handoff.md`.\n\n### 4. Run deterministic local checks\n\nFrom the skill directory:\n\n```bash\npython3 scripts\u002Fvalidate_treatment_plan.py .\u002Flocal-plan-package\npython3 scripts\u002Fvalidate_traceability.py .\u002Flocal-plan-package\npython3 scripts\u002Fcheck_completeness.py .\u002Flocal-plan-package\npython3 scripts\u002Fprivacy_process_check.py .\u002Flocal-plan-package\npython3 scripts\u002Fcheck_consistency.py .\u002Flocal-plan-package\npython3 scripts\u002Ftimeline_generator.py .\u002Flocal-plan-package \\\n  --output .\u002Flocal-plan-package\u002Fexplicit-date-schedule.json\n```\n\nThe scripts:\n\n- reject non-local paths, symlinks, duplicate JSON keys, unknown fields, oversized inputs, excessive nesting, and unbounded collections;\n- never use network access, environment variables, dynamic execution, pickle, subprocesses, images, or LLMs;\n- never assess diagnosis, medication safety, interactions, contraindications, clinical appropriateness, urgency, prognosis, or guideline concordance;\n- schedule only dates already supplied in the package and never derive recurrence or clinical intervals;\n- minimize reports to counts, rule codes, document types, and field paths.\n\n### 5. Human review and release\n\nRequire the accountable authorized team to:\n\n- compare every transcribed item with its signed source;\n- perform medication reconciliation and all clinical checks in approved systems;\n- verify current FDA labeling, Medication Guide, REMS materials, and local formulary\u002Fpolicy when applicable;\n- resolve every discrepancy and missing item;\n- review shared-decision and informed-preference documentation;\n- review transition recipients, ownership, pending results, and local escalation routing;\n- complete privacy, security, legal, regulatory, records, and institutional review as applicable;\n- sign, date, and release through the authorized record system.\n\nThe final handoff must retain provenance and unresolved-item routing. A script pass is not authorization to use the package for care.\n\n## Source boundaries\n\n- Use FDA labeling databases, current Medication Guides, and REMS materials as authoritative source records only when an authorized clinician or pharmacist verifies applicability. This skill does not interpret them.\n- Use WHO or Joint Commission transition guidance only for process structure such as information transfer, reconciliation documentation, ownership, and checklists.\n- Use AHRQ, NICE, or applicable professional guidance to document that shared decision-making occurred; do not generate options or risk estimates.\n- Apply CMS documentation requirements only when the exact program, provider type, jurisdiction, and current local policy are confirmed.\n- Route safety events, product reports, privacy incidents, and other reportable matters through current local governance. This skill records a route; it does not submit reports.\n\nSee `references\u002Fsource_ledger.md` for the dated official-source ledger.\n\n## Verification\n\n```bash\nPYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover \\\n  -s tests\u002Ftreatment-plans -p 'test_*.py' -v\n```\n\nRun AST parsing without bytecode:\n\n```bash\nPYTHONDONTWRITEBYTECODE=1 python3 -c \\\n  \"import ast,pathlib; [ast.parse(p.read_text()) for p in pathlib.Path('scripts').glob('*.py')]\"\n```\n\n## Reference map\n\n- `references\u002FREADME.md` — scope and navigation\n- `references\u002Fsafety_scope.md` — refusal, routing, and release boundaries\n- `references\u002Fprivacy_governance.md` — local handling and de-identification limits\n- `references\u002Fdocumentation_workflow.md` — package lifecycle and review gates\n- `references\u002Fsource_boundaries.md` — FDA labeling, REMS, and governance boundaries\n- `references\u002Fshared_decision_handoff.md` — informed preferences, reconciliation, and transitions\n- `references\u002Fsource_ledger.md` — dated authoritative sources\n- `references\u002Fsecurity_validation.md` — baseline findings and validation record\n\n## Agent operating procedure\n\n1. **Check the environment.** Confirm data access permissions, de-identification status and the governing regulations or protocols.\n2. **Pin down the inputs.** Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.\n3. **Run a small version first.** Work on a de-identified sample or synthetic data first.\n4. **Execute the full task** using the instructions and references above.\n5. **Validate the result.** Check outputs against clinical guidelines and reporting standards; have a qualified human review clinical content.\n6. **Report.** State what was run (versions, commands, parameters), what was checked, and what is still uncertain.\n\n| If this happens | Do this |\n|---|---|\n| Data appears to contain identifiable patient information | Stop and ask the user before processing further. |\n| A function, flag or endpoint in these instructions is missing in the installed version | Check the installed version's own documentation (`help()`, `--help`, official docs), adapt, and tell the user. Never invent an API. |\n| A required input, identifier or parameter is ambiguous | Ask the user, or state the assumption explicitly before running. |\n\n**Integrity rules**\n\n- Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.\n- Outputs are decision support for qualified professionals, not medical advice; never present them as diagnoses or orders.\n- Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.\n- Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.\n\n## Related skills\n\n- `clinical-decision-support`: Prepare and validate research-only clinical decision-support evaluation, evidence-profile, cohort, survival, biomarker\u002Fmodel, privacy, and…\n- `ara-research-manager`: Records research provenance at the end of a coding or research session by scanning the conversation and writing decisions, experiments, dea…\n",{"name":5,"license":15,"metadata":49,"description":7,"compatibility":54},{"tags":50,"version":51,"category":52,"maintainer":53},"treatment plans, clinical documentation, medicine, healthcare","2.2","clinical-and-health","Kalaris Labs","Python 3.11+ standard library; local JSON files only. Bundled CLIs require no network, external services, models, images, credentials, environment variables, or third-party packages.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill treatment-plans",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill treatment-plans",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill treatment-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002FSKILL.md",true,[79,85,89,92,96,100,104,110,114,118,122,126,130,134,138,144,148,152,156,160,164,168],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"assets\u002Fclinician_authored_intervention_template.json","ASSET","资产文件",408,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fassets\u002Fclinician_authored_intervention_template.json",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"assets\u002Fgoals_monitoring_checkpoint_template.json",446,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fassets\u002Fgoals_monitoring_checkpoint_template.json",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":91},"assets\u002Finformed_preference_shared_decision_template.json","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fassets\u002Finformed_preference_shared_decision_template.json",{"path":93,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":94,"sourceHtmlUrl":95},"assets\u002Fintended_use_handoff_template.json",2968,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fassets\u002Fintended_use_handoff_template.json",{"path":97,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":98,"sourceHtmlUrl":99},"assets\u002Fsource_fact_manifest_template.json",381,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fassets\u002Fsource_fact_manifest_template.json",{"path":101,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":102,"sourceHtmlUrl":103},"assets\u002Ftransition_reconciliation_template.json",880,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fassets\u002Ftransition_reconciliation_template.json",{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fdocumentation_workflow.md","REFERENCE","参考文档",6514,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Freferences\u002Fdocumentation_workflow.md",{"path":111,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fprivacy_governance.md",5721,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Freferences\u002Fprivacy_governance.md",{"path":115,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002FREADME.md",1422,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Freferences\u002FREADME.md",{"path":119,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fsafety_scope.md",5355,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Freferences\u002Fsafety_scope.md",{"path":123,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fsecurity_validation.md",3655,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Freferences\u002Fsecurity_validation.md",{"path":127,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fshared_decision_handoff.md",5407,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Freferences\u002Fshared_decision_handoff.md",{"path":131,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fsource_boundaries.md",6274,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Freferences\u002Fsource_boundaries.md",{"path":135,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fsource_ledger.md",7825,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Freferences\u002Fsource_ledger.md",{"path":139,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":142,"sourceHtmlUrl":143},"scripts\u002F_common.py","SCRIPT","脚本",39794,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fscripts\u002F_common.py",{"path":145,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":146,"sourceHtmlUrl":147},"scripts\u002Fcheck_completeness.py",18545,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fscripts\u002Fcheck_completeness.py",{"path":149,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":150,"sourceHtmlUrl":151},"scripts\u002Fcheck_consistency.py",12614,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fscripts\u002Fcheck_consistency.py",{"path":153,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":154,"sourceHtmlUrl":155},"scripts\u002Fgenerate_template.py",3833,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fscripts\u002Fgenerate_template.py",{"path":157,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":158,"sourceHtmlUrl":159},"scripts\u002Fprivacy_process_check.py",6583,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fscripts\u002Fprivacy_process_check.py",{"path":161,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":162,"sourceHtmlUrl":163},"scripts\u002Ftimeline_generator.py",8063,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fscripts\u002Ftimeline_generator.py",{"path":165,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":166,"sourceHtmlUrl":167},"scripts\u002Fvalidate_traceability.py",4596,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fscripts\u002Fvalidate_traceability.py",{"path":169,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":170,"sourceHtmlUrl":171},"scripts\u002Fvalidate_treatment_plan.py",2538,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Ftreatment-plans\u002Fscripts\u002Fvalidate_treatment_plan.py",[173,182,189,196,223,248],{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":181},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":181},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":181},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":44},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":44},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[230,231,232,218,233,234,235,236,237,238,239,240,241,242,208,243,244,245,246,247],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":249,"name":250,"nameZh":6,"description":251,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":177,"licenseFileUrl":6,"sourceHtmlUrl":252,"categories":253,"keywords":261,"publishedAt":44},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[254,257,258],{"categoryNo":255,"categoryName":256,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":259,"categoryName":260,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[250,262,263,264,265,266,267,244,268,209,269,270,271,272,214,273,274,275,276,277],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]