docs: optional AI-agent skill for WRF (community contribution, no code changes) - #2354
Open
ktwu01 wants to merge 1 commit into
Open
docs: optional AI-agent skill for WRF (community contribution, no code changes)#2354ktwu01 wants to merge 1 commit into
ktwu01 wants to merge 1 commit into
Conversation
Adds a single line under a 'Community resources' section linking an unofficial, community-maintained AI-agent skill for onboarding new WRF users. No code, build, or default changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi WRF maintainers,
I'm Koutian Wu (ktwu@utexas.edu), a researcher working on AI-assisted scientific
computing workflows at UT Austin. I write agent "skills": structured
markdown documentation that lets an AI coding agent (e.g. a CLI coding agent or
AI IDE) install, build, configure, run, debug, and contribute to a model with
less hand-holding than a cold prompt. I'm doing this for a family of
Earth-system models; WRF is one of them, so I'll note up front that the
shape of this message is shared across that family. The WRF skill itself is
specific to WRF, and lives here:
https://github.com/earth-space-ai/wrf-skill
This PR is a single small, optional pointer, concretely, adds one line under a 'Community resources' section in README.md linking the skill repo, noting
that an unofficial, community-maintained agent skill exists. It changes no model
code, no build system, and no scientific defaults. If you'd rather not link it,
that's completely fine: close this and I'll keep maintaining the skill on my side.
The offer stands either way.
What a "skill" is
A directory (
SKILL.md+reference/*.md): a routing hub the agent readsfirst, then deep-dive docs it loads on demand. It encodes the procedural
knowledge usually picked up by working alongside an experienced developer.
Honest disclaimers (stated up front in the skill)
remains the source of truth; where the skill and upstream disagree, upstream
wins and I treat that as a bug.
drifted line numbers, stale fields, hallucinated flags). The skill says so and
tells the agent to cross-check upstream before acting.
license, which the skill links to and does not relicense.
Why it might be worth a look
It helps onboarding. The most-exercised skill in this family so far is the Noah-MP one, so I'll give that as the data point and flag plainly that it's a sibling skill, not the WRF one: I used it to help an undergraduate go from zero to a scoped, runnable regional simulation plan (Texas, 12.5 km, NLDAS-2 forcing, on TACC) in about 3 DAYS, spin-up reasoning and a budget/smoke-test plan included. The WRF skill is built the same way, drawing on your community's own docs.
Credit where it's due
The skill draws on the wrf-model/WRF repository (release 4.7.1) and its GitHub wiki; it restructures that material for agent use. The acknowledgments section names the upstream maintainers and the
specific docs it draws on. Any errors or oversimplifications in the skill are
mine, not the upstream community's.
Happy to collaborate
I'd genuinely enjoy collaborating on AI-assisted workflows for WRF. If
there's an official place such a skill should live, conventions to follow, or
checks to enforce, I'm glad to adapt it.
Either way, thank you for maintaining WRF.
Koutian Wu
ktwu@utexas.edu
UT Austin
Google Scholar: https://scholar.google.com/citations?user=s9w1k-cAAAAJ
LinkedIn: https://www.linkedin.com/in/ktwu01/