Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Add or drop ServiceNow release support in servicenow.itsm (integration CI matrix, README compatibility table, changelog fragment).
Install Update Snow Release
$ npx skills add ansible-collections/servicenow.itsm --skill update-snow-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ansible-collections/servicenow.itsm update-snow-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ansible-collections/servicenow.itsm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/update-snow-release .claude/skills/update-snow-release && rm -rf skills-srcUse ~/.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/
Install the "update-snow-release" agent skill from https://github.com/ansible-collections/servicenow.itsm/tree/main/.agents/skills/update-snow-release into .claude/skills/update-snow-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-snow-release", 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 install https://github.com/ansible-collections/servicenow.itsm/tree/main/.agents/skills/update-snow-releaseType 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.
$ npx skills add ansible-collections/servicenow.itsm --skill update-snow-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ansible-collections/servicenow.itsm update-snow-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ansible-collections/servicenow.itsm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/update-snow-release .agents/skills/update-snow-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-snow-release" agent skill from https://github.com/ansible-collections/servicenow.itsm/tree/main/.agents/skills/update-snow-release into .agents/skills/update-snow-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-snow-release", 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.
$ npx skills add ansible-collections/servicenow.itsm --skill update-snow-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ansible-collections/servicenow.itsm update-snow-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ansible-collections/servicenow.itsm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/update-snow-release .cursor/skills/update-snow-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "update-snow-release" agent skill from https://github.com/ansible-collections/servicenow.itsm/tree/main/.agents/skills/update-snow-release into .cursor/skills/update-snow-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-snow-release", 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 https://github.com/ansible-collections/servicenow.itsm.git --path .agents/skills/update-snow-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ansible-collections/servicenow.itsm --skill update-snow-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ansible-collections/servicenow.itsm update-snow-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ansible-collections/servicenow.itsm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/update-snow-release .gemini/skills/update-snow-release && rm -rf skills-srcUse ~/.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/
Install the "update-snow-release" agent skill from https://github.com/ansible-collections/servicenow.itsm/tree/main/.agents/skills/update-snow-release into .gemini/skills/update-snow-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-snow-release", 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.
$ gh skill install ansible-collections/servicenow.itsm update-snow-releaseInstalls 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).
$ npx skills add ansible-collections/servicenow.itsm --skill update-snow-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ansible-collections/servicenow.itsm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/update-snow-release .github/skills/update-snow-release && rm -rf skills-srcUse ~/.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/
Install the "update-snow-release" agent skill from https://github.com/ansible-collections/servicenow.itsm/tree/main/.agents/skills/update-snow-release into .github/skills/update-snow-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-snow-release", 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.
$ npx skills add ansible-collections/servicenow.itsm --skill update-snow-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ansible-collections/servicenow.itsm update-snow-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ansible-collections/servicenow.itsm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/update-snow-release .opencode/skills/update-snow-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "update-snow-release" agent skill from https://github.com/ansible-collections/servicenow.itsm/tree/main/.agents/skills/update-snow-release into .opencode/skills/update-snow-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-snow-release", 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
update-snow-release- GitHub stars
- 115
- Token cost
- ~1.4k tokens
- SKILL.md length
- 462 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Add or drop ServiceNow release support in servicenow.itsm (integration CI matrix, README compatibility table, changelog fragment).
- Works in 5 steps: Integration CI —… → README — compatibility table → Changelog fragment — required → …
- The user asks to support a new SNOW release
- SKILL.md covers Scope, Decision: upgrade in place vs…, Workflow checklist and Reference: Australia / Xanadu…
- Calls rg
What it does
Update Snow Release is an agent skill from ansible-collections/servicenow.itsm. Add or drop ServiceNow release support in servicenow.itsm (integration CI matrix, README compatibility table, changelog fragment). Use when the user asks to support a new SNOW release, drop an EOL release, update the test matrix, or mentions release codenames (e.g. Australia, Xanadu, Zurich).
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.
It sits in Development, covering Changelog and release notes and Technical documentation. It works with ServiceNow. The repository describes itself as: Ansible Collection for ServiceNow ITSM. The licence is GPL-3.0.
When your agent uses it
- The user asks to support a new SNOW release
- Drop an EOL release
- Update the test matrix
- Mentions release codenames (e.g
Example prompts
- “/update-snow-release”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cba1d79. 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
Shell commands in SKILL.md call:
rg
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
Update Snow Release loads about 1.4k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 462 words of instructions outside code blocks.
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 ansible-collections/servicenow.itsm at commit cba1d79, republished under its GPL-3.0 licence (© ansible-collections). 462 words, ~1,352 tokens.
Download SKILL.mdSave it as
.claude/skills/update-snow-release/SKILL.md (or your agent's skills folder).- name
- update-snow-release
- description
- Add or drop ServiceNow release support in servicenow.itsm (integration CI matrix, README compatibility table, changelog fragment). Use when the user asks to support a new SNOW release, drop an EOL release, update the test matrix, or mentions release codenames (e.g. Australia, Xanadu, Zurich).
Update ServiceNow release support
This collection does not branch module code on SNOW release names. Support is expressed through CI, README, and changelogs. See also AGENTS.md → Integration CI.
Scope
In scope: .github/workflows/integration_source.yml, README.md compatibility table, changelogs/fragments/, maintainer notes in AGENTS.md if conventions change.
Out of scope (unless integration tests fail): plugins/, tests/, module doc URLs with old bundle names (bundle/tokyo-...), hand-editing CHANGELOG.rst or changelogs/changelog.yaml (generated at release).
Decision: upgrade in place vs new PDI
| Scenario | Workflow change | GitHub secrets |
|---|---|---|
| Upgrade existing newest PDI (usual) | Change servicenow-version label only; keep SN_*_<instance_id> | Do not create or rename secrets — instances upgrade in place |
| Add a new PDI to the matrix | Add matrix entry + full include block | Create eight secrets once in the protected-snow environment: SN_HOST_<id>, SN_USERNAME_<id>, SN_PASSWORD_<id>, SN_CLIENT_ID_<id>, SN_CLIENT_SECRET_<id>, SN_API_KEY_<id>, SN_CLIENT_CERTIFICATE_<id>, SN_CLIENT_KEY_<id> |
Instance ID = numeric suffix from the PDI hostname (e.g. dev7056 → 7056).
Workflow checklist
Copy and track progress:
- [ ] Confirm new release codename and which PDI instance is upgraded
- [ ] Update integration_source.yml matrix
- [ ] Update README.md compatibility table
- [ ] Add changelogs/fragments/<issue>-<topic>.yaml
- [ ] Remind maintainer: GitHub secrets / instance upgrade (if not done)
- [ ] Open PR using .github/pull_request_template.md1. Integration CI — .github/workflows/integration_source.yml
Only file with release-specific configuration. Matrix keeps three SNOW versions (newest + two older).
Upgrade in place (replace oldest / dropped release on newest instance):
servicenow-version:
- "<new_release>" # was <old_release>
- "yokohama"
- "zurich"
include:
- servicenow-version: "<new_release>"
sn_host_secret: SN_HOST_<instance_id>
sn_username_secret: SN_USERNAME_<instance_id>
# ... same pattern for all eight SN_*_<instance_id> secretsDo not name secrets by release codename (e.g. SN_HOST_YOKOHAMA) — always use the PDI instance ID suffix.
Leave workflow comments above servicenow-version intact (they document the instance-ID convention).
Current matrix → instance mapping (update this table when the matrix changes):
servicenow-version | PDI instance | Secret suffix |
|---|---|---|
australia | dev7056 | _7056 |
yokohama | dev7054 | _7054 |
zurich | dev7055 | _7055 |
2. README — compatibility table
In README.md (Supported ServiceNow versions):
- Add new release at the top:
| <NewRelease> | <next_collection_version>+ | TBA | - Retire dropped release: set EOL quarter and bound collection range (e.g.
2.7.0 - 2.14.0 | Q2 2026), following Washington/Vancouver/Xanadu rows. - Next collection version = bump after current
galaxy.ymlversion(e.g.2.14.0→ document2.15.0+).
Show full SKILL.md (186 more words)Show less
3. Changelog fragment — required
Create changelogs/fragments/<descriptive-name>.yaml:
---
minor_changes:
- add support for SNOW <NEW_RELEASE> release
- tests - Drop testing of <OLD_RELEASE>, as it is no longer supported by the collectionAdjust wording if only adding (no drop) or only dropping. Per AGENTS.md, behavior/support changes need a fragment.
4. Discover other references
rg -i '<old_release>|<new_release>' --glob '!CHANGELOG*' --glob '!changelogs/changelog.yaml'Expect hits only in workflow, README, changelogs, and historical docs — not in plugins/ or tests/.
5. Pull request
Use .github/pull_request_template.md:
- ISSUE TYPE: Feature Pull Request (release support)
- COMPONENT NAME:
integration CI / collection compatibility - ADDITIONAL INFORMATION: List maintainer GitHub secret actions and which matrix leg uses which instance ID
Prefer ci: commit prefix. Example: ci: add Australia release support and drop Xanadu from test matrix
Draft PR against ansible-collections/servicenow.itsm main from the contributor fork.
The user should be able to confirm the new version is valid via the CI running in their PR.
Reference: Australia / Xanadu (2026)
| Item | Value |
|---|---|
| Added | australia on instance 7056 (SN_*_7056) |
| Dropped from CI | xanadu (same instance, upgraded in place) |
| README | Australia 2.15.0+; Xanadu 2.7.0 - 2.14.0, EOL Q2 2026 |
| Secret naming | All matrix legs use instance ID suffixes (SN_*_7054, SN_*_7055, SN_*_7056), not release codenames |
Prior art: upstream PR adding Zurich (dropped Washington from matrix); commit adding Xanadu to matrix; migration from SN_*_YOKOHAMA / SN_*_ZURICH to instance IDs.
© ansible-collections, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/update-snow-release of ansible-collections/servicenow.itsm.
Open the folder on GitHubat commit cba1d79
Compare with similar skills
Update Snow Release 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Update Snow Release this skillansible-collections/servicenow.itsm | 115 | — | ~1.4k | Automated safety check: Pass | GPL-3.0 | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Ccb GitHubSeemSeam/claude_codex_bridge | 3.6k | — | ~4.9k | Automated safety check: Pass | Custom licence | |
| Golang Documentationunxed/f4 | 244 | 3 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Simple Englishropensci/ckanr | 104 | 3 repos | ~2k | Automated safety check: Pass | MIT | |
| Opik Documentation Patternscomet-ml/opik | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
Golang Documentation
unxed/f4
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt.
Simple English
ropensci/ckanr
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before…
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
Release
jrswab/axe
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
Related
Works with
Categories
Questions about Update Snow Release
What does Update Snow Release do?
Add or drop ServiceNow release support in servicenow.itsm (integration CI matrix, README compatibility table, changelog fragment). itsm.itsm (integration CI matrix, README compatibility table, changelog fragment).
When should I use Update Snow Release?
Update Snow Release fits situations like: the user asks to support a new SNOW release; drop an EOL release; update the test matrix; mentions release codenames (e.g.
How do I install Update Snow Release in Claude Code?
Run `npx skills add ansible-collections/servicenow.itsm --skill update-snow-release -a claude-code`. Or copy the skill folder (.agents/skills/update-snow-release in ansible-collections/servicenow.itsm) into .claude/skills/update-snow-release in your project. Claude Code loads it when a task matches its description.
How do I install Update Snow Release in Codex?
Run `npx skills add ansible-collections/servicenow.itsm --skill update-snow-release -a codex`. Or copy the skill folder (.agents/skills/update-snow-release in ansible-collections/servicenow.itsm) into .agents/skills/update-snow-release in your project. Codex loads it when a task matches its description.
Can I use Update Snow Release 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 ansible-collections/servicenow.itsm --skill update-snow-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-snow-release, .gemini/skills/update-snow-release, .github/skills/update-snow-release and .opencode/skills/update-snow-release in your project.
What does Update Snow Release need to run?
Going by SKILL.md and its folder, Update Snow Release needs the command-line tools its instructions call (rg).
Does Update Snow Release 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 Update Snow Release 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 Update Snow Release use?
Update Snow Release is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Update Snow Release 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 Update Snow Release?
Skills that share tags, products or a category with Update Snow Release: Simple English (moeru-ai/airi, 50k stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars), Golang Documentation (unxed/f4, 244 stars) and Simple English (ropensci/ckanr, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Update Snow Release?
ansible-collections (a GitHub organization) maintains it in ansible-collections/servicenow.itsm, which has 115 GitHub stars. The repository was last updated on October 2, 2026.
Source: ansible-collections/servicenow.itsm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.