메뉴
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에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/openmodelingfoundation/skills --skill update-skill명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
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,
SOC 직업 분류 기준
SKILL.md 표시 중
| 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