菜单
Repository-local maintainer workflow for refreshing skill assets and references when upstream standards, rubrics, or guidance change. Use when updating compressed artifacts, checklists, and linked policy text across this repository in a consistent PR.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/openmodelingfoundation/skills --skill update-skill命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Guide modelers in applying good modeling practice across the full computational modeling lifecycle, from problem framing through evaluation, uncertainty disclosure, governance, and readiness for handoff to implementation. Use this skill when users want lifecycle guidance, quality self-assessment, required modeling deliverables, or protocol-specific checks for ABM, uncertainty, ethics, participatory modeling, deep uncertainty, or immediate lifecycle triage and handoff. Expected output: staged modeling guidance, identified deficiencies against required practices, handoff-readiness assessment, and a concrete set of required artifacts and review checks.
Generate narrative documentation for computational models and research software, and select the appropriate documentation framework for a given model type. Use this skill when a user wants to: - document a computational model - generate documentation from source code - write an ODD or ODD+2 narrative for an agent-based model - create model narratives for publication or reuse - draft narrative workflow documentation The skill classifies the model type, selects a framework, extracts model structure from supplied materials, and drafts documentation. It does not assess or score existing documentation — use the document-review skill for completeness assessment, gap analysis, or structured review output. For model-card requests or scientific model specifications, route to omfa. Inputs may include source code, pseudocode, READMEs, publications, architecture descriptions, or model metadata.
Use this skill when planning or reviewing FAIR stewardship of digital research objects, including research software, datasets, computational models, and workflows. Use it for FAIR metadata, reproducibility assessment, object/workflow provenance, persistent identifiers, citation, repository organization, dependency and environment management, packaging, portability, archival preparation, preservation, stewardship artifacts, and management planning. FAIR owns stewardship metadata, reproducibility assessment, object/workflow provenance, packaging, and pointers to scientific artifacts; it does not author or canonicalize model-card content. Triggers include making research objects FAIR, reproducible, citable, reusable, publication- or archive-ready; creating FAIR metadata (e.g. codemeta.json, CITATION.cff, RO-Crate); packaging or archiving a repository, dataset, or model; and developing FAIR, data, software, or maintenance plans. Expected output: a FAIR Management Plan as the sole canonical stewardship document,
| name | update-skill |
| description | Repository-local maintainer workflow for refreshing skill assets and references when upstream standards, rubrics, or guidance change. Use when updating compressed artifacts, checklists, and linked policy text across this repository in a consistent PR. |
| user-invocable | false |
Use this skill for maintainer updates in this repository only.
This skill is local to this repository workspace (.github/skills/update-skill) and is not part of the published skill catalog under skills/.
skills/*/SKILL.md)skills/*/references/*)skills/*/assets/*)skills/*/evals.json) when behavior changesassets/REFRESH-PR-NOTE-TEMPLATE.md.Changes to an authoritative artifact or interface contract SHOULD propagate to all dependent skills, guidance, templates, examples, evaluations, and documentation in the same change whenever practical.
Flag dependencies rather than allowing repository drift.
Treat repository documentation, skills, guidance, templates, examples, and evaluations as executable project state.
When a change is made, identify every repository component that depends on the changed concept and keep those components synchronized.
Verify that:
Treat every shared concept as having a single authoritative definition.
Prefer updating dependent references over duplicating or redefining concepts.
Do not silently reconcile architectural inconsistencies.
Instead:
Preserve repository terminology, ownership boundaries, interface contracts, and artifact dependencies.
Avoid stylistic rewrites unless they improve consistency.
Report:
references/REFRESH-WORKFLOW.mdassets/REFRESH-PR-NOTE-TEMPLATE.md