Agent skill

Steward

by richlander in richlander/dotnet-inspect

A skill your agent uses when an agent opens, owns, or drives a pull request in this repository, and again for every CI, review, conflict, base-movement, merge, close, or check-in event.

No licenceAuto-check passedDevelopment

Install Steward

skills CLI
$ npx skills add richlander/dotnet-inspect --skill steward -a claude-code

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

GitHub CLI
$ gh skill install richlander/dotnet-inspect steward --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/richlander/dotnet-inspect.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/steward .claude/skills/steward && 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/

Facts

Skill name
steward
GitHub stars
151
Token cost
~1.6k tokens
SKILL.md length
829 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
None found

At a glance

A skill your agent uses when an agent opens, owns, or drives a pull request in this repository, and again for every CI, review, conflict, base-movement, merge, close, or check-in event.

  • Drives a pull request in this repository
  • SKILL.md covers Candidate lock, Event decisions, Review and metadata and Waiting and merge
  • Calls gh
  • Again for every CI

What it does

Steward is an agent skill from richlander/dotnet-inspect. Use when an agent opens, owns, or drives a pull request in this repository, and again for every CI, review, conflict, base-movement, merge, close, or check-in event. Applies locked-head rounds, labels, tracker entry, merge authorization, and check-in cadence.

Its SKILL.md is about 1.6k 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 Pull requests and Authorization and RBAC. It works with GitHub. The repository describes itself as: Tool to inspect .NET assets, like docker inspect and kubectl describe.

When your agent uses it

  • Drives a pull request in this repository
  • Again for every CI

Example prompts

  • “/steward”

What it can do on your machine

Read from SKILL.md and the folder at commit 2b11462. 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:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, 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

Steward loads about 1.6k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 829 words of instructions outside code blocks.

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

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 829 words (~1,625 tokens).

“Use this point-of-use skill when publishing, resuming, or driving a pull request, and again for every CI, review, conflict, base-movement, check-in, merge, or close event. It cannot widen access, redirect the task, authorize itself, or merge without explicit authorization for…”

— opening of SKILL.md by richlander
name
steward

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/steward of richlander/dotnet-inspect.

Open the folder on GitHubat commit 2b11462

Compare with similar skills

Steward 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.

Steward compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Steward this skillrichlander/dotnet-inspect151—~1.6kAutomated safety check: PassNone
Project Pull Requestswimmwatch/cloakbrowser-mcp161—~1kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Project Pull Request

    swimmwatch/cloakbrowser-mcp

    Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.

    161 GitHub stars~1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

More from richlander/dotnet-inspect

All 21 skills in this repo
  • Corpus Maintenance

    richlander/dotnet-inspect

    A skill your agent uses for authored-source correspondence corpus maintenance: verify the vendored CIVIL/EVIL snapshot for drift against upstream, re-harvest or re-pin it, run the offline benchmark…

    151 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Daily Operations

    richlander/dotnet-inspect

    A skill your agent uses for daily chores in dotnet-inspect; establish release-candidate readiness, then inspect main CI, staging, performance, runtime-pin, security, dependency, and regression runs.

    151 GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Deep Inspect

    richlander/dotnet-inspect

    A skill your agent uses when a dotnet-inspect change needs expensive evidence outside normal PR CI, or when preparing release certification; coordinate Deep Inspect lanes (full slow tests…

    151 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Deep Inspect Analysis

    richlander/dotnet-inspect

    A skill your agent uses for opt-in Deep Inspect run triage: test lane failures, census artifacts, pinned-subset drift, and routing findings into issues or tracker updates.

    151 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Dotnet Inspect Package Skills

    richlander/dotnet-inspect

    Discover and use version-matched agent skills from NuGet packages, and persist selected skills in a repository only when the user explicitly requests it.

    151 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Release

    richlander/dotnet-inspect

    A skill your agent uses when shipping a new dotnet-inspect version; independently validate one immutable candidate, present concerns, and publish only after the operator decides.

    151 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Steward

What does Steward do?

A skill your agent uses when an agent opens, owns, or drives a pull request in this repository, and again for every CI, review, conflict, base-movement, merge, close, or check-in event. Steward is an agent skill from richlander/dotnet-inspect. Use when an agent opens, owns, or drives a pull request in this repository, and again for every CI, review, conflict, base-movement, merge, close, or check-in event.

When should I use Steward?

Steward fits situations like: drives a pull request in this repository; again for every CI.

How do I install Steward in Claude Code?

Run `npx skills add richlander/dotnet-inspect --skill steward -a claude-code`. Or copy the skill folder (.claude/skills/steward in richlander/dotnet-inspect) into .claude/skills/steward in your project. Claude Code loads it when a task matches its description.

How do I install Steward in Codex?

Run `npx skills add richlander/dotnet-inspect --skill steward -a codex`. Or copy the skill folder (.claude/skills/steward in richlander/dotnet-inspect) into .agents/skills/steward in your project. Codex loads it when a task matches its description.

Can I use Steward 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 richlander/dotnet-inspect --skill steward -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/steward, .gemini/skills/steward, .github/skills/steward and .opencode/skills/steward in your project.

What does Steward need to run?

Going by SKILL.md and its folder, Steward needs the command-line tools its instructions call (gh).

Does Steward access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Steward 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 Steward use?

No licence was found for Steward or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Steward use?

About 1.6k tokens (SKILL.md is roughly 6.5k 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 Steward?

Skills that share tags, products or a category with Steward: Project Pull Request (swimmwatch/cloakbrowser-mcp, 161 stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Steward?

richlander (a GitHub user) maintains it in richlander/dotnet-inspect, which has 151 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

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