Agent skill

Best Practice Research

by yangyuan-zhen in yangyuan-zhen/PolyWeather

[OMX] Bounded best-practice research wrapper using official/upstream evidence first

AGPL-3.0Auto-check passed

Install Best Practice Research

skills CLI

$ npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install yangyuan-zhen/PolyWeather best-practice-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/yangyuan-zhen/PolyWeather.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/best-practice-research .claude/skills/best-practice-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "best-practice-research" agent skill from https://github.com/yangyuan-zhen/PolyWeather/tree/main/.codex/skills/best-practice-research into .claude/skills/best-practice-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "best-practice-research", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/yangyuan-zhen/PolyWeather/tree/main/.codex/skills/best-practice-research

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install yangyuan-zhen/PolyWeather best-practice-research --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yangyuan-zhen/PolyWeather.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/best-practice-research .agents/skills/best-practice-research && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "best-practice-research" agent skill from https://github.com/yangyuan-zhen/PolyWeather/tree/main/.codex/skills/best-practice-research into .agents/skills/best-practice-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "best-practice-research", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install yangyuan-zhen/PolyWeather best-practice-research --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yangyuan-zhen/PolyWeather.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/best-practice-research .cursor/skills/best-practice-research && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "best-practice-research" agent skill from https://github.com/yangyuan-zhen/PolyWeather/tree/main/.codex/skills/best-practice-research into .cursor/skills/best-practice-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "best-practice-research", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/yangyuan-zhen/PolyWeather.git --path .codex/skills/best-practice-research

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install yangyuan-zhen/PolyWeather best-practice-research --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yangyuan-zhen/PolyWeather.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/best-practice-research .gemini/skills/best-practice-research && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "best-practice-research" agent skill from https://github.com/yangyuan-zhen/PolyWeather/tree/main/.codex/skills/best-practice-research into .gemini/skills/best-practice-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "best-practice-research", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install yangyuan-zhen/PolyWeather best-practice-research

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/yangyuan-zhen/PolyWeather.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/best-practice-research .github/skills/best-practice-research && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "best-practice-research" agent skill from https://github.com/yangyuan-zhen/PolyWeather/tree/main/.codex/skills/best-practice-research into .github/skills/best-practice-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "best-practice-research", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install yangyuan-zhen/PolyWeather best-practice-research --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yangyuan-zhen/PolyWeather.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/best-practice-research .opencode/skills/best-practice-research && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "best-practice-research" agent skill from https://github.com/yangyuan-zhen/PolyWeather/tree/main/.codex/skills/best-practice-research into .opencode/skills/best-practice-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "best-practice-research", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: best-practice-research
GitHub stars: 316
Token cost: ~1.4k tokens
SKILL.md length: 592 words
Files: 1
Skills in repo: 26
Repo updated: Sep 20, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

[OMX] Bounded best-practice research wrapper using official/upstream evidence first

Works in 4 steps: Use explore first for brownfield facts:… → Use researcher for official/upstream… → Use dependency-expert only for… → …
SKILL.md covers Purpose, Terminal By Default, Activate When and Do Not Activate When, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Best Practice Research is an agent skill from yangyuan-zhen/PolyWeather. [OMX] Bounded best-practice research wrapper using official/upstream evidence first

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: polymarket Intelligent Weather Quant Analysis Bot. The licence is AGPL-3.0.

Example prompts

“/best-practice-research”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Use explore first for brownfield facts: current code usage, local constraints, versions, config, and integration points.
Use researcher for official/upstream docs, release notes, standards, migration guides, source-backed examples, and current best-practice…
Use dependency-expert only for adoption/upgrade/replacement/comparison decisions.
Return to the caller with explicit evidence, uncertainty, and any implementation handoff constraints.

What it can do on your machine

Read from SKILL.md and the folder at commit 43e658b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Best Practice Research loads about 1.4k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 592 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~27
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yangyuan-zhen/PolyWeather at commit 43e658b, republished under its AGPL-3.0 licence (© yangyuan-zhen). 592 words, ~1,350 tokens.

Download SKILL.mdSave it as .claude/skills/best-practice-research/SKILL.md (or your agent's skills folder).

name: best-practice-research
description: [OMX] Bounded best-practice research wrapper using official/upstream evidence first
argument-hint: <technology|decision|practice question>

Best-Practice Research

Use this skill when a task depends on current external best practices, version-aware guidance, standards, official recommendations, or upstream behavior. This is a workflow wrapper: it routes evidence gathering and synthesis; it is not a new research authority and it does not replace researcher.

Purpose

Produce a cited, reusable best-practice answer or handoff that separates current external evidence from repo-local facts and dependency-selection decisions. For pre-planning investigation, this is the ordinary first research wrapper: gather official/upstream evidence, then hand it to $ralplan or the caller as planning input. Do not present $best-practice-research as a final architecture component or as a validator-gated research loop.

Terminal By Default

This skill is terminal and read-only by default. It gathers evidence and produces a cited recommendation with a handoff, then stops. Do not write or edit files, create or amend commits, run mutating commands, or otherwise modify repository state under this skill — even when the question has clear implementation implications. When implementation is warranted, stop and hand off rather than continuing: name $ralplan for planning and $ultragoal, $team, or executor for execution, and resume only after the user explicitly switches to that workflow.

Activate When

The user asks for best practices, recommended approach, current guidance, official recommendations, standards, or version-aware external behavior.
$ralplan, $deep-interview, $team, or another workflow needs current external evidence before planning or execution can be correct.
The task involves an already chosen technology and needs authoritative usage guidance, migration notes, API behavior, lifecycle rules, or current safety guidance.

Do Not Activate When

The answer is fully repo-local; use explore for codebase facts.
The main question is whether to adopt, replace, upgrade, or compare dependencies; use dependency-expert.
The user only needs implementation against already-grounded requirements; use executor, $ralph, or $team as appropriate.
The task can be answered from stable local project conventions without current external lookup.

Specialist Routing

Use explore first for brownfield facts: current code usage, local constraints, versions, config, and integration points.
Use researcher for official/upstream docs, release notes, standards, migration guides, source-backed examples, and current best-practice evidence for an already chosen technology.
Use dependency-expert only for adoption/upgrade/replacement/comparison decisions.
Return to the caller with explicit evidence, uncertainty, and any implementation handoff constraints.

Show full SKILL.md (224 more words)Show less

Source-Quality Rules

Prefer official documentation, upstream source, release notes, changelogs, standards, and maintainer guidance.
Include source URLs for material claims.
State date/version context for current best-practice claims.
Label third-party summaries as supplemental; do not use them before official/upstream sources.
Flag stale, conflicting, undocumented, or version-mismatched evidence.
Do not over-fetch: gather the smallest evidence set that can support the decision.

Workflow

Classify the question: conceptual best practice, implementation guidance, migration/version guidance, standards/compliance guidance, or mixed local + external guidance.
Gather repo-local facts with explore when local usage or constraints affect the answer.
Gather external evidence with researcher when current or version-aware practice affects correctness.
Synthesize a concise answer with source quality, version/date context, caveats, and an implementation or planning handoff.
Stop when the answer is grounded enough for the caller; otherwise report the exact blocker or specialist handoff needed.

Output Contract

## Best-Practice Research: <question>

### Direct Recommendation
<actionable guidance or decision support>

### Evidence Used
- Official/upstream: <source URL> — <what it establishes>
- Supplemental, if any: <source URL> — <why it is secondary>

### Version / Date Context
<versions, dates, release channels, or unknowns>

### Repo-Local Context
<facts from explore, or "not needed">

### Boundaries / Non-goals
<what this research does not decide>

### Handoff
<planning/execution/test implications; name the next workflow — `$ralplan` for planning, `$ultragoal`/`$team`/`executor` for execution — and note that this skill stops here unless the user explicitly switches workflows>

Stop Rules

Stop after a source-backed recommendation is reusable by the caller.
Stop and route upward if the task becomes dependency comparison, broad architecture, or implementation.
Do not continue researching when remaining work would only polish wording rather than change the recommendation.
This skill never implements. After delivering the recommendation and handoff, stop; do not modify repo files or repo state. Resume only when the user explicitly switches to a planning or implementation workflow named in the handoff.

Task: {{ARGUMENTS}}

Files

Just SKILL.md in .codex/skills/best-practice-research of yangyuan-zhen/PolyWeather.

Open the folder on GitHubat commit 43e658b

Compare with similar skills

Best Practice Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Best Practice Research compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Best Practice Research this skillyangyuan-zhen/PolyWeather	316	—	~1.4k	Automated safety check: Pass	AGPL-3.0	20 days ago
Mock Best Practicesthedaviddias/Front-End-Checklist	74k	—	~425	Automated safety check: Pass	MIT	5 days ago
Interactivity Best Practicesremotion-dev/remotion	63k	—	~181	Automated safety check: Pass	Custom licence	yesterday
X402 Express Wrappersickn33/agentic-awesome-skills	47k	1 repos	~772	Automated safety check: Notes	MIT	2 days ago
Upstream PRyc-software/qm	15k	—	~2.3k	Automated safety check: Notes	MIT	today
Dotnet Best Practicesgithub/awesome-copilot	40k	2 repos	~808	Automated safety check: Pass	MIT	2 days ago

Similar skills

Mock Best Practices
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices.
74k GitHub stars~425 tokensUpdated 5 days ago
Testing & QAAuto-check passed
Interactivity Best Practices
remotion-dev/remotion
Official
Best practices for writing Remotion animations that stay intuitive for agents and editable in Remotion Studio Visual Mode.
63k GitHub stars~181 tokensUpdated yesterday
Media & CreativeAuto-check passed
X402 Express Wrapper
sickn33/agentic-awesome-skills
Wrapper oficial de M2MCent (Node.js) para inyectar muros de pago x402 en APIs o servidores Model Context Protocol (MCP).
47k GitHub starsUsed in 1 repo~772 tokens
Agent WorkflowsAuto-check: notes
Upstream PR
yc-software/qm
Send a change to upstream qm without leaking organization-specific context.
15k GitHub stars~2.3k tokensUpdated today
DevelopmentAuto-check: notes
Dotnet Best Practices
github/awesome-copilot
Official
Ensure .NET/C code meets best practices for the solution/project.
40k GitHub starsUsed in 2 repos~808 tokens
DevelopmentAuto-check passed
Practice
ccch1mneyyy/dsh-TUI
Guide a programming exercise using dsh-tui or a topic the user wants to learn.
4.3k GitHub stars~356 tokensUpdated today
DevelopmentAuto-check passed

Questions about Best Practice Research

What does Best Practice Research do?

[OMX] Bounded best-practice research wrapper using official/upstream evidence first. Best Practice Research is an agent skill from yangyuan-zhen/PolyWeather.

How do I install Best Practice Research in Claude Code?

Run `npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a claude-code`. Or copy the skill folder (.codex/skills/best-practice-research in yangyuan-zhen/PolyWeather) into .claude/skills/best-practice-research in your project. Claude Code loads it when a task matches its description.

How do I install Best Practice Research in Codex?

Run `npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a codex`. Or copy the skill folder (.codex/skills/best-practice-research in yangyuan-zhen/PolyWeather) into .agents/skills/best-practice-research in your project. Codex loads it when a task matches its description.

Can I use Best Practice Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yangyuan-zhen/PolyWeather --skill best-practice-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/best-practice-research, .gemini/skills/best-practice-research, .github/skills/best-practice-research and .opencode/skills/best-practice-research in your project.

What does Best Practice Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Best Practice Research is instructions for the agent only.

Does Best Practice Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Best Practice Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Best Practice Research use?

Best Practice Research is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Best Practice Research use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Best Practice Research?

Skills that share tags, products or a category with Best Practice Research: Mock Best Practices (thedaviddias/Front-End-Checklist, 74k stars), Interactivity Best Practices (remotion-dev/remotion, 63k stars), X402 Express Wrapper (sickn33/agentic-awesome-skills, 47k stars) and Upstream PR (yc-software/qm, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Best Practice Research?

yangyuan-zhen (a GitHub user) maintains it in yangyuan-zhen/PolyWeather, which has 316 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on September 20, 2026.

Source: yangyuan-zhen/PolyWeather on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Best Practice Research

Facts

At a glance

What it does

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Best-Practice Research

Purpose

Terminal By Default

Activate When

Do Not Activate When

Specialist Routing

Source-Quality Rules

Workflow

Output Contract

Stop Rules

Files

Compare with similar skills

Similar skills

More from yangyuan-zhen/PolyWeather

Questions about Best Practice Research