Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
How to treat conclusions inherited from an earlier session — handover notes, prepared comments, verdict files, plans.
Install Inherited Claims
$ npx skills add werf/werf --skill inherited-claims -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install werf/werf inherited-claims --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/werf/werf.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/inherited-claims .claude/skills/inherited-claims && 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 "inherited-claims" agent skill from https://github.com/werf/werf/tree/main/.agents/skills/inherited-claims into .claude/skills/inherited-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inherited-claims", 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/werf/werf/tree/main/.agents/skills/inherited-claimsType 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 werf/werf --skill inherited-claims -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install werf/werf inherited-claims --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/werf/werf.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/inherited-claims .agents/skills/inherited-claims && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "inherited-claims" agent skill from https://github.com/werf/werf/tree/main/.agents/skills/inherited-claims into .agents/skills/inherited-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inherited-claims", 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 werf/werf --skill inherited-claims -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install werf/werf inherited-claims --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/werf/werf.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/inherited-claims .cursor/skills/inherited-claims && 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 "inherited-claims" agent skill from https://github.com/werf/werf/tree/main/.agents/skills/inherited-claims into .cursor/skills/inherited-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inherited-claims", 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/werf/werf.git --path .agents/skills/inherited-claims--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 werf/werf --skill inherited-claims -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install werf/werf inherited-claims --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/werf/werf.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/inherited-claims .gemini/skills/inherited-claims && 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 "inherited-claims" agent skill from https://github.com/werf/werf/tree/main/.agents/skills/inherited-claims into .gemini/skills/inherited-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inherited-claims", 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 werf/werf inherited-claimsInstalls 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 werf/werf --skill inherited-claims -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/werf/werf.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/inherited-claims .github/skills/inherited-claims && 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 "inherited-claims" agent skill from https://github.com/werf/werf/tree/main/.agents/skills/inherited-claims into .github/skills/inherited-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inherited-claims", 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 werf/werf --skill inherited-claims -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install werf/werf inherited-claims --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/werf/werf.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/inherited-claims .opencode/skills/inherited-claims && 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 "inherited-claims" agent skill from https://github.com/werf/werf/tree/main/.agents/skills/inherited-claims into .opencode/skills/inherited-claims/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inherited-claims", 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
inherited-claims- GitHub stars
- 4.7k
- Token cost
- ~669 tokens
- SKILL.md length
- 409 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
How to treat conclusions inherited from an earlier session — handover notes, prepared comments, verdict files, plans.
- A task starts from context you did not derive yourself
- SKILL.md covers Rules and Why this matters more than it…
- Calls git
- Resumes work described by a previous session
What it does
Inherited Claims is an agent skill from werf/werf. How to treat conclusions inherited from an earlier session — handover notes, prepared comments, verdict files, plans. Use whenever a task starts from context you did not derive yourself, or resumes work described by a previous session.
Its SKILL.md is about 670 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 DevOps & Cloud, covering CI/CD. It works with Docker. The repository describes itself as: A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices. The licence is Apache-2.0.
When your agent uses it
- A task starts from context you did not derive yourself
- Resumes work described by a previous session
Example prompts
- “/inherited-claims”
What it can do on your machine
Read from SKILL.md and the folder at commit 638779c. 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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Inherited Claims loads about 669 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 409 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 werf/werf at commit 638779c, republished under its Apache-2.0 licence (© werf). 409 words, ~669 tokens.
Download SKILL.mdSave it as
.claude/skills/inherited-claims/SKILL.md (or your agent's skills folder).- name
- inherited-claims
- description
- How to treat conclusions inherited from an earlier session — handover notes, prepared comments, verdict files, plans. Use whenever a task starts from context you did not derive yourself, or resumes work described by a previous session.
Inherited Claims
A conclusion carried in from somewhere else is a claim, not a finding — no matter how confident its wording or how detailed its citations. Handover notes, prepared comment texts, verdict files, plans, an issue's own body, a previous agent's summary: all of them were true about a codebase that may no longer exist.
The repo itself carries claims too: a merged PR's title and body, a changelog entry, a migration guide, a release note. Those describe what someone intended to do, not necessarily what shipped.
Rules
- Re-derive every inherited claim from the primary source — the code, the API, the config, the actual command output — before it reaches anywhere a human will read it: a tracker comment, a PR description, a card, a message to the user.
- "X was removed/changed in version N" is a claim even when a merged PR title and the shipped documentation both say it. Check the call site at the released ref —
git show <tag>:<path> | grep <symbol>— before ruling a behavior out or in. Removing the flag that disables a check is not removing the check; a PR can land its own description's headline only in part, and the guide written from that description then documents behavior the code never had (paid in full: a check documented as removed in a migration guide, still executing in the released binary, blamed for nothing until its cost showed up as a 3.6-hour rebuild). - Re-derive the reason, not just the verdict. "Close this as obsolete" may be right while the sentence explaining why is invented; publishing the invented sentence is the damage.
- When an inherited note states a convention and a skill covers the same ground, the skill wins. Load the skill and follow it; do not act on the remembered version.
- Quote what you verified with a
file:line, a flag default, a response body. If a claim cannot be checked cheaply, drop it from the text rather than softening it — a hedge still reads as an assertion. - Batching is where this fails. A pile of pre-written items feels like work already done; it is a pile of unverified claims, and approving them as a batch means publishing them as a batch.
Show full SKILL.md (44 more words)Show less
Why this matters more than it looks
Being wrong in public, in the user's name, costs more than having nothing to say. A stale claim in a tracker is read as the maintainer's position, gets quoted back, and outlives the session that produced it.
© werf, Apache-2.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/inherited-claims of werf/werf.
Open the folder on GitHubat commit 638779c
Compare with similar skills
Inherited Claims 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 |
|---|---|---|---|---|---|---|
| Inherited Claims this skillwerf/werf | 4.7k | — | ~669 | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Megatron-LM Base Image BumpNVIDIA/Megatron-LM | 18k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Actions CreatorFNOSP/FlyNarwhal | 509 | 1 repos | ~2.4k | Automated safety check: Pass | AGPL-3.0 | |
| Swig CI Reproswig/swig | 6.3k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Megalinter Checknvuillam/npm-groovy-lint | 248 | 1 repos | ~3.9k | Automated safety check: Notes | MIT |
Similar skills
- Official
Megatron-LM Base Image Bump
NVIDIA/Megatron-LM
Moves Megatron-LM CI to a newer NVIDIA PyTorch base image, updating both the GitHub and GitLab pins together and handling the CI follow-up.
GitHub Actions Creator
FNOSP/FlyNarwhal
A skill your agent uses when the user wants to create, generate, or set up a GitHub Actions workflow.
Swig CI Repro
swig/swig
Reproduce a GitHub Actions Linux CI failure locally when it does not happen on your machine: a podman/docker image that mirrors the ubuntu-22.04 runner by reusing the real Tools/CI-linux-.sh install…
Megalinter Check
nvuillam/npm-groovy-lint
Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.
DDNS Build and Release Maintenance
NewFuture/DDNS
Maintains the DDNS project's GitHub Actions, Docker and Nuitka builds, packaging and release preparation without touching publishing credentials.
More from werf/werf
Git Conventions
werf/werf
werf conventions for branch names and commit messages. An agent skill from werf/werf.
Pull Request
werf/werf
Generates Pull Request titles and descriptions according to werf conventions.
Review
werf/werf
Code review of a pull request, branch, or diff. An agent skill from werf/werf.
Challenge Review
werf/werf
Independent challenge pass for a non-trivial or high-risk change.
Session Retro
werf/werf
Analyze the current session for harness-worthy lessons — repeated corrections, discovered conventions, skill bugs — and turn them into concrete repo changes: docs, skills, task targets, linter…
Test The Tests
werf/werf
Verify a test actually falsifies the behavior it claims to cover, via real mutation.
Related
Works with
Categories
Questions about Inherited Claims
What does Inherited Claims do?
How to treat conclusions inherited from an earlier session — handover notes, prepared comments, verdict files, plans. Inherited Claims is an agent skill from werf/werf. How to treat conclusions inherited from an earlier session — handover notes, prepared comments, verdict files, plans.
When should I use Inherited Claims?
Inherited Claims fits situations like: A task starts from context you did not derive yourself; resumes work described by a previous session.
How do I install Inherited Claims in Claude Code?
Run `npx skills add werf/werf --skill inherited-claims -a claude-code`. Or copy the skill folder (.agents/skills/inherited-claims in werf/werf) into .claude/skills/inherited-claims in your project. Claude Code loads it when a task matches its description.
How do I install Inherited Claims in Codex?
Run `npx skills add werf/werf --skill inherited-claims -a codex`. Or copy the skill folder (.agents/skills/inherited-claims in werf/werf) into .agents/skills/inherited-claims in your project. Codex loads it when a task matches its description.
Can I use Inherited Claims 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 werf/werf --skill inherited-claims -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inherited-claims, .gemini/skills/inherited-claims, .github/skills/inherited-claims and .opencode/skills/inherited-claims in your project.
What does Inherited Claims need to run?
Going by SKILL.md and its folder, Inherited Claims needs the command-line tools its instructions call (git).
Does Inherited Claims access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Inherited Claims 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 Inherited Claims use?
Inherited Claims is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Inherited Claims use?
About 669 tokens (SKILL.md is roughly 2.7k 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 Inherited Claims?
Skills that share tags, products or a category with Inherited Claims: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Megatron-LM Base Image Bump (NVIDIA/Megatron-LM, 18k stars), GitHub Actions Creator (FNOSP/FlyNarwhal, 509 stars) and Swig CI Repro (swig/swig, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Inherited Claims?
werf (a GitHub organization) maintains it in werf/werf, which has 4,734 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.
Source: werf/werf on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.