skills-update
Update installed Codex skills from known GitHub sources and set up optional daily automatic skill updates. Use when the user wants to check for newer versions of installed skills, update custom or curated skills, configure skill source metadata, or enable or disable recurring skill update automation.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- skills-update
- description
- Update installed Codex skills from known GitHub sources and set up optional daily automatic skill updates. Use when the user wants to check for newer versions of installed skills, update custom or curated skills, configure skill source metadata, or enable or disable recurring skill update automation.
02 资源文件 2
- 参考文档agents/openai.yaml203 B
- 脚本scripts/update_skills.py22.7 KB
03 SKILL.md 正文
Skills Update
Purpose
Keep installed Codex skills current without manually reinstalling them. Use the bundled updater script for deterministic checks and updates, then summarize exactly what changed and which skills could not be updated safely.
First Run
Before the first update, check whether the user has already answered the automation prompt:
python scripts/update_skills.py --first-run-status
If first_run_required is true, ask exactly:
Do you want to turn on automatic updates? This will set up an automation that runs every day. You can turn it off at any time in
Automations.
If the user says yes, create a daily automation named Update Codex skills with a prompt equivalent to:
Use $skills-update to check installed Codex skills for updates and apply safe updates. Report updated, current, untracked, and failed skills.
Prefer a local daily cron automation at 9:00 AM in the user's locale when the automation tool is available. Then run:
python scripts/update_skills.py --mark-first-run enabled
If the user declines, run:
python scripts/update_skills.py --mark-first-run declined
Update Workflow
- Inspect update sources with a dry run:
python scripts/update_skills.py
-
Explain any
untrackedskills. A plain copied custom skill has no reliable upstream unless it has metadata, a config entry, or is installed as a git checkout. -
Apply updates when the user asked to update or when running from the daily automation:
python scripts/update_skills.py --apply
-
Report the result by category:
updated,current,update_available,untracked,source_missing, anderror. -
Tell the user to restart Codex when skills were updated so the refreshed skill metadata is picked up.
Source Resolution
The updater checks sources in this order:
--sourceentries passed to the script.- Per-skill metadata at
<skill>/.skills-update.json. - Global config at
$CODEX_HOME/skills/.skills-update/sources.json. - A git remote when the installed skill folder is a git checkout.
- Inferred OpenAI curated or experimental source paths in
openai/skills.
Use explicit metadata for custom skills that were installed by copying files:
{
"repo": "owner/repo",
"path": "skills/my-skill",
"ref": "main"
}
Use global config when several custom skills are tracked from one place:
{
"skills": {
"my-skill": {
"repo": "owner/repo",
"path": "skills/my-skill",
"ref": "main"
}
}
}
Safety Rules
- Skip system skills under
.systemunless the user explicitly asks to include them. - Never guess a custom skill's upstream repository from its name alone.
- Always create a timestamped backup before replacing an installed skill.
- Replace whole skill folders only after validating the remote source contains
SKILL.md. - Treat dry-run output as advisory; only
--applychanges installed skills. - If an update fails, report the failure and leave the original skill restored when possible.
Script Reference
Common commands:
python scripts/update_skills.py
python scripts/update_skills.py --apply
python scripts/update_skills.py --json
python scripts/update_skills.py --only frontend-skill --apply
python scripts/update_skills.py --source "my-skill=owner/repo:skills/my-skill@main" --apply
Use --include-system only when the user intentionally wants to check bundled system skills.
04 同仓库更多 Skills
winui-app
Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.
vercel-deploy
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
security-best-practices
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
openai-docs
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains.
netlify-deploy
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.